From: Lane S. <la...@op...> - 2003-07-21 18:46:46
|
Let's then create a cvs module called OptionalTools and migrate code to this module that is not required by WebMacro. A lot of code will end up there and it could make using WebMacro unfriendly: I have to include two jars and search two doc bases... Regarding context tools. How does this sound: First, a context tool goes away in release 2. It is just a context object like any other. Second, the only way to automatically get an object in the context is to make a declaration in WebMacro.properties not WebMacro.defaults: ContextHelper.NameFoo=ClassFoo ContextHelper.NameBar=ClassBar WebMacro.getContext(), as a convenience, places these objects in the context under the name declared. It is the responsibility of the owner of the context to manage any clean-up on these classes when the context is no longer needed. And, this is not the responsibility of WM to know this point in time. -Lane Brian Goetz wrote: >>I don't like code that's just "laying around" for just a few people to >>use. I also think that all the macros should go .. go into some separate >>util jar or tarball. >> >> > >I think this makes a lot of sense. > > > >------------------------------------------------------- >This SF.net email is sponsored by: VM Ware >With VMware you can run multiple operating systems on a single machine. >WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the >same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 >_______________________________________________ >Webmacro-devel mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/webmacro-devel > > > -- Lane Sharman Learn About Conga, All Java GUI Builder: http://opendoors.com/conga Java Software Portal: http://opendoors.com |