Generally speaking, it is sometimes a good idea to just double check your methods against the API, or use code completion if you use an IDE. For example, with Boa Constructor if you have written wx.ToolBar. ad then hit Ctrl-Space, it brings up a menu of methods, and selecting one will add AddSeparator( automatically.
Yeah, this is what I do. I use Wingware’s IDE and it just autocomplete’s most wx method names for me. But I know how to spell that one too. I’ll probably get confused in 2.9 when wx finally drops the American spelling for the Color methods though.
Generally speaking, it is sometimes a good idea to just double check your methods against the API, or use code completion if you use an IDE. For example, with Boa Constructor if you have written wx.ToolBar. ad then hit Ctrl-Space, it brings up a menu of methods, and selecting one will add AddSeparator( automatically.
I am trying WingIDE for about 2 weeks now and I am really impressed
with the autocomplete, it works on much more then other IDE’s (e.g.
SQLAlchemy models and more) I have tried and the thing I really
like is its “Source Assistant” (call tips in some other IDE’s with
hyper link to the doc) and just after that the “goto definition” and
refactor.
I am still a bit fighting with its debugger and it is a bit slow on
start up.
I might have to stop drinking wine for a bit and purchase a copy.
For debugging wx applications, I just put breakpoints in event handlers and then use the Debug Probe. Works for most things. I did notice that Wing has issues with matplotlib in wx if you put a breakpoint into the initialization area. I was getting weird errors from that. And it has issues with TurboGears autocomplete or goto, which I told them about and they’re fixing. The Wing devs are very helpful at upgrading their product and/or helping their users. They told me I could select a class and hit F4 to jump to the source, which I had somehow missed.
Anyway, I do hope to compare it to PyCharm sometime. But I’m pretty happy with Wing.
For debugging wx applications, I just put breakpoints in event handlers and then use the Debug Probe. Works for most things. I did notice that Wing has issues with matplotlib in wx if you put a breakpoint into the initialization area. I was getting weird errors from that. And it has issues with TurboGears autocomplete or goto, which I told them about and they're fixing. The Wing devs are very helpful at upgrading their product and/or helping their users. They told me I could select a class and hit F4 to jump to the source, which I had somehow missed.
I used ctrl and mouse click which jumps to the definition within this file or opens the file which has the definition, Boa has this too.
Anyway, I do hope to compare it to PyCharm sometime.
Gave it a try a little while back, but didn't see anything which is not also in Wing and start up is really slow and UI is not as flexible as Wing's.
