[JIRA] Closed: (OFBIZ-163) Usability improvment relevant for WIDGETs

     [ http://jira.undersunconsulting.com/browse/OFBIZ-163?page=all ]
     
David E. Jones closed OFBIZ-163:
--------------------------------

     Assign To: David E. Jones  (was: Jira Administrator)
    Resolution: Incomplete

A good concept, but needs more research and analysis. Will wait for it to re-emerge, hopefully along with enough interest to mobilize resources to move it along.

> Usability improvment relevant for WIDGETs  
> --------------------------------------------
>
>          Key: OFBIZ-163
>          URL: http://jira.undersunconsulting.com/browse/OFBIZ-163
>      Project: [OFBiz] Open For Business
>         Type: Improvement
>   Components: widget
>     Versions: SVN
>     Reporter: Michael Pfurtscheller
>     Assignee: David E. Jones

>
>
> Enhancement of the formwidget. For storing form "value-templates" and such as described in the thread on the mailinglist:
> http://lists.ofbiz.org/mailman/htdig/dev/2005-February/thread.html#7741
> Extract from the thread:
> Michael,
> This sounds like it would be a very nice tool, and it should be quite
> possible to implement, including a data model that could generically
> store template field values.
> This would require less effort than what has been discussed about the
> help system, but it is still a fair amount of effort. It's great to
> send ideas to the mailing lists and I'm sure everyone appreciates it
> since there is a chance that someone will need something like these in
> the future and will have the resources available to get it done. Before
> that I wouldn't expect much... There are dozens or hundreds of ideas
> about what to do with the project every month and probably 90% of them
> don't get implemented or are not implemented until perhaps months or
> years later. It's really a resource issue, for everyone...
> -David
> On Feb 6, 2005, at 12:33 PM, mpf at zentric.com wrote:
> > Hi,
> >
> >  i would like to discuss a proposal to make life of ofbiz component
> > managers and users easier. It came up in my mind when thinking about
> > the online help proposal and adrians approach to templates /models in
> > the accounting engine.
> >
> >  Current Situation:
> >  When you open a form (any form in ) it is empty or contains static
> > defaults (from a users point of view). Often its the case that you
> > want to enter 4 products in a row that are almost similar except
> > productid and one or two fields. But you have to reenter every field
> > (they are allways to much) which is a sucking task!Or you only have
> > products of 3 types that you would like your form-field to be
> > prefilled with. Ofbiz and systems I know need to implement types and
> > templates for each form individually.
> >
> >  Proposal
> >
> >  With the widgets there is the possibility to have a central piece of
> > code to maintain generic value templates. A central pirece of code to
> > store, find, delete generic values templates. We would need 1 entity
> > genericValueTemplates with templateId and a blob to store the
> > xml-representation of the generic-value (similar to persisting the
> > attributes of scheduled jobs in ofbiz).
> >
> >  So every form gets an attribute wether or not to display the
> > following function-links
> >  - store as template,
> >  - find template
> >
> >  If one klicks "find template" in the form widget he'll get a new
> > window (something like a calander selector) . There he'll be able to
> > select from a list of templates that are associated with the entity
> > that is represented by the form. He selects the appropiate template
> > and the form-widgets fields get prefilled with default values that
> > where stored in the xml.
> >
> >  This approach could be extended for some more features that seem not
> > to hard to implement, to me and are quit unconventional but proven
> > good in other applications.
> >  - Add a checkbox to the save action to say "I want to reopen this
> > form after storing with the values I had just entered as default
> > Instead of returning to a base point.
> >  - Add a action url to each "type" field to create maintain that type.
> > This way a user never has to search for the place: Where to create a
> > new productType or partyType or whatever. It seems to be simple but
> > the impact for the user is incredible since he doesnt need anymore how
> > to get to specific form screens. For the developer this saves a lot of
> > documentation time!
> >
> >  Im no code guru! So I have just the feeling that it would be possible
> > without to much twisting the system! And it would fit good into the
> > architecture of the widgets.????
> >  Please correct me if Im totally on the wrong track. If this could be
> > talked through and aggred upon I'll summarize it in the wiki....
> >
> >
> >  However I desperatly would like to see the online helpystem come true
> > as soon as possible....
> >
> >  mit freundlichen Grüssen/ Kind regards / muchos saludos
> >  --
> >  Dipl. Wirt.-Ing. Michael Pfurtscheller
> >  zentric GmbH & Co. KG
> >  mobil: [phone]
> >  fon: [phone]
> >  fax: [phone]
> >  icq# 8724822
> > mailto:michael.pfurtscheller at zentric.com
> > http://www.zentric.com
> >

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.undersunconsulting.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira