All, While documenting changes I had previously implemented in ooDialog, I found that either:
The change had been made before the new APIs were available and a better implementation could be done with the new APIs. or My first pass at using the new API wasn't quite what I wanted. In both cases this lead me to rework the code before documenting the code the way it was locked me into something I wasn't happy with. Now I'm at the point where I just about have the documentation caught up, except for 3 new class areas: Menus, DateTimePicker, and MonthCalendar. Without even looking at that code, I know I want to redo it using the new APIs. Since that will take me a substantial amount of time, I'm thinking that these 3 class areas should be left out of this release. (The idea actually came from Jon.) 1.) Does that meet with everyone's approval? 2.) Does anyone think it is sufficient to make sure nothing in these 3 areas is in the documentation, or should I also back out the code itself? I would like to say, anyone that uses undocumented code does so at there own risk. And leave the code in. But, I'm not sure that is reasonable. Well, I'm sure it is reasonable to me, I'm just not sure what others think. <grin> -- Mark Miesfeld ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
