On 1/23/07, Paul McNett <[EMAIL PROTECTED]> wrote: > Nate Lowrie wrote: > > Ok, I don't use the class designer but I had a thought about it and a > > lofty design feature today. Pardon this email if the feature is > > already implemented, but I am almost sure that it is not. Today, I > > started developing a Serial Debugging Terminal program for the Dabo > > Demos. I put the serial setup widgets in their own separate panel > > class and just added it. I intended to use the panel for a couple of > > other applications as well. In a way, it's like a subassembly or > > template. I did the same thing for a Contact Information section that > > I coded for John last night. > > > > So this got me thinking. I've been doing this for how long and > > reusing my code. It's good software practice. Then I thought about > > the class designer. If you use it exclusively, there is no way to > > create a panel subassembly and just import into applications....You > > have to code everything by hand over and over again. This sounded > > like a good thing to add, especially for a applications that utilize > > databases and have a lot of common fields like contact information, > > business information, and shipping information. > > > > Thoughts? > > I'm pretty sure that this is already in the class designer. You can load > your own cdxml-classes to drop on a new form or panel. You can subclass > your own cdxml classes. Etc. Or do I misunderstand?
Ok, I was just wondering if we had the capability....... > > > > On a side note, the Serial Debugging Terminal should be available > > tonight. I have the layout coded, now I just gotta do the backend. > > Should be a good example of how to use Dabo in conjunction with other > > python modules to create sophisticated programs. Ed/Paul, I am > > developing it on a separate repository because I want the commit > > history but I don't want non-working code in the dabo demo repository. > > I would like to do a dump/load when I am done to keep the commit > > history. Let me know if this is acceptable, or if you want me to just > > copy files over and lose the commit history. > > It is acceptable and normal to have non-working code in the trunk. > That's the whole reason we have a development branch (trunk). Especially > with new code. I'd say if you want commit history, then you should > commit to Dabo at appropriate intervals. > Got it. Will do. > -- > pkm ~ http://paulmcnett.com > > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
