On Aug 11, 2009, at 10:25 PM, [email protected] wrote:
> After reviewing the dabo-users archives and trying out stuff today,
> seems
> like there are 3 ways a parent form and a child dialog can share
> information:
>
> 1. The child dialog can be kept alive long enough (using the hide()
> function) for the calling parent form to get information from
> objects on the
> child dialog, after which the child can be closed, and the parent
> can make use
> of the information.
>
> 2. The child dialog can write information back to properties on the
> parent
> form before closing, after which the parent form can make use of the
> information.
>
> 3. The child dialog can access the bizobjs of the parent form, and
> do all
> the work there in the child dialog, before closing and returning
> control to
> the parent.
>
> We managed to get all three of these approaches to work in simple
> forms
> today.
There are probably a few other ways, too. But the important thing is
your design is flexible enough for your needs.
The first design puts the parent in control; the child doesn't need
to know anything about the parent. This means that the child dialog
will not be tightly coupled to the calling form, and allows for re-
use; it is the preferred method for creating generic components. The
latter two approaches have varying degrees of coupling between the
dialog and the form (in #2) and the bizobjs (#3). If the dialog is
single-purpose, then this coupling is not much of an issue.
-- Ed Leafe
_______________________________________________
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]
