Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

People interested: Si Chen, Anil Patel
People willing to help: Anil Patel

Improve usability of the Catalog manager

People interested: Si Chen
People willing to help:

Complete the refactoring of Permissions control

...

People interested: Jacopo Cappellato
People willing to help: Jacopo Cappellato (2 hours per week)

Enhance the integration with eBay DONE

Isolate the code into a new specialpurpose component. Complete the support for the creation of eBay auctions from OFBiz; improve the synchronization between OFBiz and eBay: order/shipment status changes, in/out communications, etc...

People interested: Marco Risaliti
People willing to help: Marco Risaliti

OFBIZ-1441

Enhance the integration with Google Product DONE

Isolate the code into a new specialpurpose component. Add more features and options to the product export.

People interested: Marco Risaliti
People willing to help: Marco Risaliti

OFBIZ-1372

Integrate Screen Widget and Form Widget with Dojo.jQery is now used, OBSOLETE

People interested: Mike Wong
People willing to help: Mike Wong

...

Use Apache Commons EL instead of the Flexible String Expander DONE

Committed to trunk December 2008.

UEL in OFBiz

Change the Entity Engine to be user aware for security, logging

This would be a change to require that a userLogin be passed to all Entity Engine calls. The Entity Engine could then check permissions to see if the user can modify or view that entity, or that record. The Entity Engine could also auto-populate fields like created by and updated by.

...

  • 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 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)

OFBiz Theme Gallery DONE

Visual Themes Gallery

Web tools

  • Entity Data maintenance
    • have vertical separators for columns when viewing entity content, This issue is no longer a problem in new themes like Bizness Time...
    • make the Find options a collapsible screenlet, This issue has been partially addressed with the "Advanced Search" in Lookups
    • make styles of the Entity Data Maintenance screens in general the same than used by the widgets. I think it's done
  • At large, maybe restyle all the Web tools page (not a priority
        1. )

Introduce Mashups

Example in OFBIZ-1873

...

  • 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...

Light-blue Theme (or future themes alike) enhancement DONE

Currently we have a Windows Start model UI, or rather a Gnome desktop model but with a sole entry point (Home).
We could, like IMO it's done elegantly in Ubunut/Gnome, have more entries point namely:

  • Top Level Applications We should introduce drop-down menus to group applications (like AR and AP under Accounting). Doint that, we should keep in mind permissions access for each sub-application.
  • Addon Applications (better name ?)
    • Replace the secondary menu (at bottom) with a primary menu top drop-down item.
  • System Applications
  • etc.

I think it's done now with the new themes we have-

Quicker an intuitive access to basic functionnalities

Replace slow popup lookups by faster layered lookups (CSS/Ajax)

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.

...

  • Typography : Typography depends on languages. For instance in French we put a space 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.

Some suggestions

...

on user ML

  • better error/success messages
  • better handling of keyboard tab to move from one field to another
  • more and better multi row submit screens
  • more informative form fields (e.g. showing descriptions instead of just ids)
  • enhancing field interactions (the value of one field can change/ hide/ etc other elements/data in the screen)
  • I (JLR) would add something I saw like in SugarCRM and found very useful : their "info icon" which when you hover over it show related information (for a contact its contact mechs, etc.)