Page History

...

The following is a proposal for the definition of a list of short and medium term tasks list: your input, suggestions and help is welcome. Please add your comment at the bottom of the page.

Legenda:

• "People interested": the people that think that the feature should be considered a priority for the project (in the short term)

• "People willing to help": persons that are in the position to help with the development of the task; if possible specify an approximately number of hours per week or month to give an idea of the total resources available for each task

...

• Have less (or even none) buttons in header
• It was also suggesteed to use screenlet like how gmail does. Notably
  • Three buttons max
  • Dropdown for other actions
  • The idea of duplicating at bottom
• Having breadcrumbs under the title bar
• Using portlets in place of screenlets
• Recently (12/08) I it was discussed if we should remove the screenlet's navigation-form-name attribute. There are (at least) 3 reasons for that
  • Less informations/features than with default (pages numbers, ability to jump to any page)
  • The last button does not always work (try with widget.form.defaultViewSize=2 when listing invoices)
  • Pagination should be available to the user always in the same way in order to have a consistent UI.
    Then we have 2 possibilities
    1. Remove this attribute and all current uses.
    2. Keep it but then
       1. we should at least make it works (last button issue)
       2. make it consistent with the standard way (direct page access)

...

Now we have the ability to put parms into the label in the I8N files, so the tooltips would have the same ability. Like "Click here to ($whatever)" would turn into "Click here to see the productlist" as a tool tip. You would just have the fieldname like in the labels file.
Barring having a seperate file, then having the tooltip_$fieldname like tooltip_$Phonenumber would work.

Fields-group

Add a mechanism to allow to collapse/uncollapse all groups-fields in one click (something like that also exists in Compiere UI, see above) Done, I wonder if we should use an icon, or even both ?

• Use the screenlet and put an icon (or a word, it's an icon in Compiere) in the screenlet title bar for that.
• OR
• Another (easier) possibility would be to use the 1st field-group and to make a relation between it and other field-groups. This because in all cases we will no make this 1st field-group collapsible (at least it's how we have done so far) and we could then put an artifact there. This would also allow to not have a mandatory screenlet when using collapsible field-groups

Some i18n issues and best practices

• Typography : Typography depends on languages. For instance in French we put a space before and after colons, there are other cases of course. So punctuation should be always part of labels.
• HTML : We already discussed about not putting any HTML tags in labels. Also we should not put any < and & which would not be correctly rendered (http://www.w3.org/TR/REC-xml/#dt-chardata), so should be escaped.

...