On Sun, Aug 3, 2008 at 6:21 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> In your last commit for your winshell 4.0 rework, something caught my > eye. I noticed that code is still stuffing class entries into .local. > That's the same sort of hack that oodialog was doing (but done > differently, of course :-)). Things that use the winshell classes > really should be doing a ::requires on the package file rather than > relying on something else having done it for them. Yes, in the WinShell package I was going to remove that. Just hadn't got to it yet. There is still some code rework to do. I first just wanted to get it converted enough so that it compiled cleanly. <grin> >I think maybe that > code should be deleted, and if there is a chorus of loud screams about > stuff no longer working, it can always get added back in. I'm not sure if that comment refers to WinShell or ooDialog? In ooDialog I've been toying with the idea of removing the code that puts the classes in the .environment. I was going to ask you what you thought about it. If you noticed, when I added the new .Rect and .Point class, I didn't add those in to that code. In fact I need to have a general discussion about what direction to take with ooDialog. That will be in another post. But on this matter, that of removing the code that puts the ooDialog classes into .environment, is that what you're comment was referring to? -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
