I have to devellop a userinterface(form) to handle an ECO object and all its
associations en subassociations.
Assume following abstract model:
1 Account (---) 0..* ArticleReservations
1.Account (---) 0..* Ticket
1.Ticket (---) 0..* TicketDetails
Remark: Every object has a statemachine and appropiate states.
Approach 1: using autoforms
This way, four separate forms become wide spread all over the screen.
Problem: My customer will be confused using such a GUI, and it must be
solved by another approach
Approach 2: using datagrids.
Place four datagrids on one form, and let things work together using
referencehandles and so on.
All needed triggers can be fired using dedicated buttons. Right! But...
My customer wil be confused about the placement of the triggerbuttons,
because he has to select the right object in the datagrid before firing the
correct trigger.
Problem: this approach is only useable if triggers can be fired using
triggerbuttons (or something like that) on each row in the datagrid.
(clicking nearby changing things)
Approach 3: using usercontrols
For each objectinstance (!), I have to create a Usercontrol, and my
triggerbutton onClick-actions will be decorated with a lot of GUI stuff.
(adding controls, removing controls, databindings, subscribtion to
objectadded and objectremoved, evaluates and so on...)
In first release, the application is single-user on local database (must
migrate to multi-user and databaseserver).
All other approaches are welcome too, but I prefer to keep de code simple or
ECOnomic :-)
Maybe someone can help me to dive into approach 2, because of code reuse to
other (and new) applications.
regards
Peter G.
How about adding a context menu to the grid and letting the user choose
their trigger options there?
Yes, a context menu is also an option. In order of my preference:
1) Data grid with buttons
2) Data grid with context menu
3) Customized auto form or/with user controls
Why placed on second place: because I know my users. Most of them have no
computer experience. That's why I prefer to create a GUI with
point-and-click usability.
What do you think about realization of the first and the second approach?
Second is the easiest one?
Greetings
Peter G.
> Approach 3: using usercontrols
> For each objectinstance (!), I have to create a Usercontrol, and my
> triggerbutton onClick-actions will be decorated with a lot of GUI
> stuff.
> (adding controls, removing controls, databindings, subscribtion to
> objectadded and objectremoved, evaluates and so on...)
> In first release, the application is single-user on local database
> (must migrate to multi-user and databaseserver).
>
> All other approaches are welcome too, but I prefer to keep de code
> simple or
> ECOnomic :-)
> Maybe someone can help me to dive into approach 2, because of code
> reuse to
> other (and new) applications.
> regards
I reported feature request.
This should allow to make autoforms more accurate.
Not sure if this can help bu just have a look:
http://qc.borland.com/wc/qcmain.aspx?d=27124
BTW, the report is Closed. Where from can we get it?
Cheers.
Resolution = retest
I think that means "Reevaluate for next release"
Oke, For now I started implementing the context menu's. With the least
effort to reach the most...
Showing triggerbuttons on each row in a datagrid must be great (buttons like
'Cancel', 'Detail' and so on...)
Thanks for responding.
Peter G