On 3/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > This is python. dShell redirects stdout and stderr to its terminal. > > If it's not redirected standard python notation is to pipe to the > > terminal. You can always pipe it to a file. > > > > Why would you want it in a form? > > > > Sorry, should have been clearer; this when using the Class Designer- > sometimes it 'silently fails', and you have no idea why. All is > revealed when you look at the terminal you used to run it. But > thinking about it a bit more, this actually makes sense- the Class > Designer is only a small part of the eventual IDE, and the IDE is the > logical place to grab and parse these errors. > So ignore this point ;-).
I see. When we actually have an IDE, I suspect that these will be put into the Dabo error log messages. The goal though is to have it were the CD doesn't fail. > > > > * form.showmodal() > > > -should throw exception until supported by underlying wxPython > > > -currently 'looks like' it's working, but doesn't stop event > > > processing for the rest > > > of the app; now know this is documented on the wiki, but it's not > > > obvious when > > > you're in an editor ;-) > > > > I do believe this is a Wx problem. As was stated before, Dabo is > > limited by the underlying libraries that it uses. > > > > Fair enough. > > > > * Help/documentation > > > -could include static copy of wiki docs (e.g. captured via wget) > > > > Where? In the class designer help? > > > > > -api doc generated with something like epydoc with graphviz > > > -in ClassEditor help- introspect dabo libraries and present doc > > > strings in a tree > > > widget-like thing? > > > > I think that we'll get to these 2 once the code starts to stop > > changing....Right now it is so turbulent that it doesn't really > > behoove us to do this. But if you want to take a crack at this, feel > > free. > > > > Right now, a separate tarball would be great. Long term, I guess it's > a given parts of the above will be in the IDE. > As to API docs, turns out Paul has already done it, I just hadn't > noticed the link on the main website: http://paul.dabodev.com/doc/api/ > > > > * dialog classes- confusing to have both show and Show methods > > > > Show is part of the wx subclass. We can't get rid of it. We needed > > to add addition functionality to the Show method, so we created show > > which does it's thing and calls Show. > > > > You should not be using Show at all. Instead, use show, showModal, or > > showModaless. > > Erg. Ok, thanks for the explanation, that's understandable. > But I take it that none of the modal related options are working yet. > > Thanks for the reply Nate. > > Julian > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
