On Sat, Oct 4, 2008 at 7:09 AM, Nate Lowrie <[EMAIL PROTECTED]> wrote: > On Sat, Oct 4, 2008 at 3:31 AM, Uwe Grauer > <[EMAIL PROTECTED]> wrote: >> Paul McNett wrote: >>> [changed to dabo-dev for my comments] >>> >>> Ed Leafe wrote: >>>> On Oct 3, 2008, at 5:41 PM, Mike Mabey wrote: >>>> >>>>> On the wiki <http://dabodev.com/wiki/ >>>>> HowToReturnAValueFromAModalForm> on How >>>>> To Return A Value From A Modal Form, the last update says that >>>>> wxPython >>>>> still doesn't support forms modally yet. Is this still the case? >>>>> And if >>>>> so, is there a way to work around this so as to use a form (which >>>>> has bizobj >>>>> capabilities) as a spawned dialog-type box and still be able to >>>>> return a >>>>> value to the calling app? >>>> No, unfortunately this ability has not been added. When we started >>>> with wxPython several years ago, there was a hope that this was going >>>> to be changed sooner rather than later, so we wrote the classes in >>>> anticipation of supporting that feature. But now it looks as though it >>>> is unlikely to ever happen. >>>> >>>> It's certainly possible to do what you ask, but not as simple as with >>>> a regular form, with its built-in data awareness. What do you need to >>>> do exactly? Perhaps we could come up with an alternative approach that >>>> would be easier to implement. >>> >>> All we need to do is abstract the data-aware stuff from dForm into some >>> abstract mixin that we can combine with dForm, dDialog, or any other >>> container. I meant to do this years ago but never got around to it. >>> There's a ticket for it. I don't think it'll be hard, but could be tedious. >>> >>> Paul >> >> This would be a very nice addition. >> +1 for this outstanding feature. > > I do believe we had a thread on this a couple of months ago that > coincided with the discussions on making the dropdown list support > choices from a database through properties. I would like to see this > happen and in addition automatically pass the registered bizobjs from > the form to the dialog. For now, I think the best solution is to pass > the bizobj references through the __init__ function on the dialog. > Remember to call super. Data changes are passed back out through the > bizobjs.
I forgot to add that while this feature is useful, only some dialogs use it. I use dabo's ui for non-database apps all the time. Maybe we can refactor this mixin and provide both a regular dialog and a data aware dialog to reduce overhead? Or is the overhead no significant enough to warrant this? Nate L. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
