On Wednesday 12 August 2009 07:14:23 am Nate Lowrie wrote: > I agree on the control. I tend to favor #3 the most but tend to > decouple by passing the appropriate bizobj objects into the dialog > through the constructor. My thoughts on this are that my models for > standard things like customers and orders tend to vary very little, so > I can use this approach without sacrificing modularity and still take > advantage of Dabo's built in UI to biz layer connection properties > (DataSource and DataField). Validation is the only sticky part of the > dialog for me at this point. > > Regards, > > Nate
I too like the idea of Dialogs having knowledge of the bizObj. It makes the dialog more flexible. In my case I've had need to use the dialog as a special data entry feature. This was simplified by passing the bizObj or the Parent. Can the Dialog be reused - no. But like I said it's a special dialog. In the VFP world I used the technique often. 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]
