To everyone who has replied, thanks, in particular Re downloadable dabo documentation: Thanks for the links to the various sources of downloadable docs. I will be svn check'ing them out asap
Re live/in editor documentation: Ok, that wasn't such a good idea on my behalf. I'm used to embedded systems where each API is quite a bit smaller. GUI APIs seem to be *much* bigger ;-) Now I'm getting the hang of it (and am starting to trust that things are more likely to do what you think/expect them to do, rather than something weird), it's all starting to come together. Ed: now I'm getting used to it, the prop sheet is great. And thanks for the pointer to where in the code the logic is. I'm still not sure how/where to structure things using a RAD tool like the class designer, but I'll raise these questions as different topics. Ed Leafe wrote: >>> Import statements are indeed included in the code file. >>> >> They weren't for me- ended up adding them by hand, until I added them >> to the 'managed imports' in the class editor source editor. > > Oh, OK - that's what I meant. There is a place to place your import > statements so that they are available to all your code, and you found > it. > >>>> e.g. dApp instance is in wrapper, so again, editors can't do full >>>> autocompletion >>> Again, I'm not sure what you mean here. >>> As to imports; makes sense now, and it's not really an issue for me to add an 'import dabo' to keep my external editor (well, ok, me) happy ;-) By wrapper- I mean when you're in the class designer and choose 'save as runnable app' it creates an small python script, named the same as the main form's cdxml file. In it is the 'import dabo' (what I was hoping would be in the form code file), and the instantiation of the dApp object. Wingware is smart enough to do a pretty good job of inferring variable types etc from static code- with that explicitly added to the generated code file I found wingware could do even better completion, in some situations. >> Re cdxml-generated code linkage. Yeah, I can see that being tricky. If I come up with any ideas, I'll write again. Having said that, what's there works, and when you get used to it, works pretty well- you've done a good job! > > Did you ever notice that little 'super' button in the code editor? > Ever wonder what that is for? > Egg on my face. :-) Thanks all Julian _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
