lento / spam Goto Github PK

mockups from Petru:

From SPAM design

From SPAM design

From SPAM design

It could be useful to attach files to notes, must look a bit more into this to see how it would work with project repositories and previews...

when an asset is created in a category not previously used in that container, the page should be updated by creating a new livetable for the category.

when I try to upload a sequence of images I get a Internal server error.

when a new asset is created ... one of steps in his creation is to define the "asset extension"
for example: ground_TXT.jpg
as you can see, files that will be allowed to be uploaded are *.jpg
the extension jpg or JPG are the same, or not?
but SPAM in this case doesn't allow to upload the image ... it is case sensitive

is this a design choice or a bug?

I would like to make a proposal related to "live widgets" below "LW"

why?
every time I install or re-install SPAM I recreate the link pointing to the newest version of the "LW" this because the "LW" must be downloaded from github and is not installed automatically.

I don't know if there is another project that use this library. Is there?
if not ... my proposal is to incorporate the "LW" in the repository of SPAM, for example in the "spam/lib/livewidgets" and use him internally. To maintain always the consistency of this dependency.

maybe there is another solution for this...?

if there is not another project that use "LW"... then we need, at less, to include instructions in the SPAM's README file about how to install the last version of "LW" in SPAM.

fix dialog form handling for browsers that don't have form.getFormData()

create the developers documentation structure

the file is uploaded with 0 lenght

the project tree in the sidebar should be persistent, and remeber opened/closed state for nodes using cookies

see: http://www.jstree.com/documentation

the new API makes it possible to upload a file without reading it all in memory (a must for large files!)
see: https://hacks.mozilla.org/2010/07/firefox-4-formdata-and-the-new-file-url-object/

It will work in firefox 4.0, must check chrome, safari and opera

add fields for:

• image
• link
• phone number

settings could be saved in the database and accessed from the admin sidebar

we keep the files in the repository anyways, so it's safe to remove them and just warn the user about it

todo:

• fix conditional display: http://github.com/lento/tw2livewidgets/issues#issue/1
• port custom status widgets: #20
• restore liveboxes when this is fixed: http://github.com/lento/tw2livewidgets/issues#issue/2
• make asset page update when an asset is created in a new category: #11
• make project sidebar update when the project structure is changed: #12

at the moment the links in the sidebar are harcoded in the template, so if a site want to add its custom links it must tweak the template and this can make it hard to merge custom addons.

A modular system could define a way to "register" controllers so that the sidebar can be created automatically.

port overlay forms to the new dialog system

todo:

• port Asset: #13 (done)
• port Tag: #14 (done)

in base al lavoro fato nei anni abbiamo perfezionato i colori per lo status degli asset

• rejected: ff0000 (rosso)
• revision(submited): ffff00
• working(wip): 00ccff
• idle: 969696
• approuved: 64ff64
• frozen(close): 008000
• editable(new): dddddd

when user have made a commit without inserting a comment ... the comment field appear empty.

Notes would be more useful (and way more cool) if we could use a markup language in them, allowing things like formatting, quoting and intra-referencing.

notifications can be missed if the page is scrolled down enough to hide the header.
Better to let them slide up from the bottom of the browser window, so they are always visible.

• StatusIcon
• StatusIconBox

this would make it easier to upgrade old projects when the database schema is updated

that is the expected behaviour in a login page

all assets in SPAM are owned by spam-user and when an asset is created, this are the write permission only for owner, in this situation by spam-user.

this is good ...

the problem is that we now use a mini work space to work on assets on we need the write permissions on this
"mini work space" - is intended as: when a user check out an asset, spam add the write permission to this asset folder for current user. when a user release the asset is push all relevant data to repository and clear all irrelevant such as backup copy, cache, and temp file, test files.

at less we need a write permission for user group for now ... every time when a asset is published to spam.

at first the profile page will only contain a link to change the user's password, in the future we can add a profile image, email address, etc.

a mockup from Petru:

From SPAM design

a quick reference can help new users getting used to Spam.
It should have:

• a legenda explaining asset status and their colors

the way tab titles flow on multiple lines now is not that nice ;)

set a minimum width for the content

spam don't handle the non unicode character
for example when a user insert a symbol like "à, ò, è, é, ù, ì" in asset comment the spam give an error like: ordinal non in range(128) and all asset for that categories are not visualized.

like scenes with shots or shots with assets
...maybe with a fat warning about backing up the database!