On Tuesday, September 28, 2010 03:27:39 pm Paul McNett wrote: > On 9/28/10 3:19 PM, John Fabiani wrote: > > On Tuesday, September 28, 2010 01:59:59 pm Ed Leafe wrote: > >> Not quite true. Most of the integration between the UI and the bizobj > >> layer does not exist in dialogs. So yes, you can do it, but you'll end > >> up coding a lot of it by hand. > > > > I understand and yes I have been able to integrate the data layers (with > > some work). I later discovered that bad planning was the real cause for > > using a dialog as a primary form. > > > > Actually, I think tabs can almost eliminate any need for dialogs that act > > like forms. > > My app has a gargantuan dialog that the users interact with frequently. I > can visualize other designs for it but I think the users would revolt if I > did, because it works very well and the Save/Cancel decision tree is > simple enough for everyone to understand. > > Paul
I didn't say there weren't reasons I just said I have eliminated most of the reasons. For example you are popping up a dialog to gain information from the user. Is it possible you could have forced a move to a tab and program the modal requirements. I have a form that immediately moves to a tab after the user selects a product item. The user can cancel or process a request but can't move off the tab. By doing this I'm getting the best of using a form and I have a modal data entry screen. It works for me and in this case I think it made sense to the user. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
