> There is also a button on the > Code Editor window that does the same thing as the menu.
Good. This is more RAD. > Also, I've added a cool convenience feature. If you start your code > with lines before the 'def' statement, those lines are automatically > assumed to be import-type statements that will be added to the top of > the class definition. So if you're coding something and realize that > you need the 'os' module, you can write the code like this: The lines before the 'def' statement, they will stay temporarily. I suppose. Thanks -- Jaime Mora Ramones Tantoyuca Veracruz, Mexico "Ed Leafe" <[EMAIL PROTECTED]> escribió en el mensaje news:[EMAIL PROTECTED] > On May 29, 2006, at 1:54 PM, Jaime Mora Ramones wrote: > > >> or should there be a menu option that brings up an edit box > >> for entering all the class-level import statements? > > > > This option it would be better. > > Good, because that's what I went with. There is also a button on the > Code Editor window that does the same thing as the menu. > > Also, I've added a cool convenience feature. If you start your code > with lines before the 'def' statement, those lines are automatically > assumed to be import-type statements that will be added to the top of > the class definition. So if you're coding something and realize that > you need the 'os' module, you can write the code like this: > > import os > def afterInit(self): > self.hasFile = os.path.exists(self.someFile) > > ...and when you either switch to another code editing page, or save > the design, the 'import os' line is automatically moved into the > class-level imports. > > I'm still testing a bit and tweaking things, but this should be > posted in less than an hour. > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com > > > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
