Unfortunately, you're going to run into scoping problems with this approach. The merged file will work ok, but the smaller stub files won't be able to make the public classes from the merged file public by just having a ::requires for the merged package.
Rick On Tue, Sep 22, 2009 at 6:53 PM, Mark Miesfeld <[email protected]> wrote: > On Mon, Sep 14, 2009 at 10:20 AM, Sahananda (Jon) Wolfers > <[email protected]> wrote: > >> I think Ideally the ooDialog user should just be able to requires one class >> and everything should be there for them. > > This brings up another idea I've been thinking about for some time. > Instead of having 3 different package files, I'm thinking of merging > them all into one. > > Originally, from comments in the code and the ooDialog doc, I think > the idea was that someone could just require "OODPLAIN.cls" if they > only needed a simple dialog, and that this would "save" system > resources. > > Well, that reasoning is no longer valid, if it ever was, with the new C++ API. > > I would move all the classes into "ooDialog.cls" and for oodPlain.cls > and oodWin32.cls just have a single ::requires 'ooDialog.cls' > statement. That way all new programs would only need to require > ooDialog.cls and it would be transparent to existing programs. > Programs that, for instance, require oodWin32.cls. > > This would be easier for the user and solve a problem I keep bumping > in to. The problem is being able to do a isA() test on dialog > objects. > > For example, in a method context of the DynamicDialog class, I can't > test if self is a CategoryDialog because the CategoryDialog is defined > in the ooDialog.cls package file and the DynamicDialog is defined in > oodPlain.cls package file. If all the classes were in one package > file, and I don't see any reason why they shouldn't be, then the isA() > test would work. > > So, that's what I intend to do, unless there are objections, or cons > to the proposal I've overlooked. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
