overall thinking about invoice editing user interface

[jzarate]

• regarding item taxes
  • two simple name, value text inputs (as it is now)
  • use a javascript input() function to insert the fields (as they do in google docs when setting the title of a document).
  • use a dom popup with a selector (that would imply editing taxes elsewhere in the app).

• regarding field labels:
  • put classical labels on the fields
  • leave it "as is", letting the default field values inform about the fields.
  • use floating popup help texts

• regarding error messages
  • where to put them?

• which ones of the invoice fields should be input_in_edit type ??

[jzarate]

regarding forms:

• actually they have an ajax interface. once the user press one of the buttons ("save", "save as draft" or "save and send by email"), the form is saved via an ajax request (only the form of the page is reloaded). "google style".
• we need to implement some way of visually letting know the user when the invoice is "syncronized" with the server and when not. some kind of color icons on a well-visible place within the invoice so, at every time, the user knows if the data he's seen at the screen are "saved" or not.
• I even think we should do it not based on events only (when some field is modified and it's not sent to the server, activate the "not saved" icon, etc ...), but only on a periodical executer.

ideas welcome