Page History

...

Links in screenlets.

• Have less (or even noneno) buttons in header
• It was also suggesteed suggested to use screenlet screenlets 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) it was discussed if we should remove the screenlet's navigation-form-name attribute. There are (at least) 3 reasons for that
  • Less informationsinformation/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)

...

• Sorting
  • The tabs should be sortable not only by alphabetical order in English but in other languages too.
  • An user should to be able to position the tabs according to their preference
• Having something to select the apps desired for a "quick links" bar, and maybe have that go beyond just tabbed applications and include individual pages for easy access.
  We still need that for 'old' themes but it looks like they will be deprecated with new themes like Bizness Time...

Quicker

...

and intuitive access to basic

...

functionality

Following Bruno's suggestion about Compiere UI. We could put a link to https://localhost:8443/partymgr/control/createnew everywhere we have a party lookup, using the party label at left of the field. Actually we could generalize everywhere we have a lookup for something.
It's easy to click on the Party tab and then on "Create New". But after reading BJ's reading suggestion, it's also an easy way to teach newbies how to do it. Easy for us to introduce, and easy for newbies to use, maybe with a tooltip "click on party to create". This would fill the Condition #2 of the BJ's article above.
Of course being able to show the screen where the choice of the type of party to create is done, and then the screen where data are entered in an Ajax filled CSS hidden/shown window could be our next target. This would allow to not leave the page the user is on and would create a less disturbing environment.

...