Kevin Ollivier wrote:
Hi Robin,
Thanks! You are, as always, right. <G>
My kids might disagree with you on that! <wink>
I now have a working development build! As for the new build, all I can say is...
WOW! It loads *noticeably* faster (debug loads in approx. 4 seconds, or 1 bounce vs. 4-5) and the CPU load when running wxPython has gotten much, much better! (Down to 20% from 50% when actively using, for example, wxStyledTextCtrl... which now is behaving quite nicely! 5-8% CPU usage when idle - approx. same as MS and Dreamweaver. Not bad at all!) And I have to keep reminding myself - I'm running in *debug* mode! Congrats to you and the wxMac crew, this is a major upgrade - and you haven't gotten anywhere close to finishing wxPython 2.5/3.0! I'm going to be doing more than testing with this new version - I'll probably set it up as my primary build, provided it is not crashing excessively. =)
That's good to hear. It's kinda hard for me to get a grasp on the improvements as I've been seeing them come in baby steps, while you got it all in one giant leap.
However, I do have one problem with my build. demo/demo.py loads the splash screen and then shuts down. No crash, no errors, it just shuts down as if all it was supposed to do was show the splash screen.
Well, what do you know... It's happening to me too, I wonder when that started... (I usually run the individual demo samples too.) I'll try to figure this out soon.
As you are probably aware from my comments above, I am able to run the demos separately and they load and work just fine - so I'm not sure what is going on here. My checkout was from approx. 2-3 days ago - if I do an update, do I need to specify -r wxPy_newswig each time?
No the tag is "sticky" so it will stay with the files in your workspace until you remove it with a "cvs update -A".
Also, one thing you might want to add to the (excellent, BTW) devel build notes is that, at least on Panther, I needed to set SWIG_LIB to /opt/swig/lib/swig1.3 for it to work. I assume this doesn't happen if you build and install to /usr/local, but I think the whole /opt build notes are a good idea.
Strange. I don't have to do that on any of my build systems. I thought that swig's build encoded the --prefix within the executable. What do you get if you run "/opt/swig/bin/swig -swiglib" without the env var set?
Probably this weekend if I can get the demo completely up and running, I'll give it a thorough test. Any idea how long until there is a 2.5.1 release, for wxWin and wxPython?
I'll be happy to make a Panther build and post it.
Cool. Hopefully I'll be getting a new Mac soon that I'll put Panther on. (I want to keep both for a while so I can still make Jaguar builds too without possibly tainting a Panther install with other Pythons and tools...)
BTW, I've gotten success reports (and no complaints) on my latest Panther build so I'm going to post it soon to SF. I'll send you a note when its ready.
Good. Go ahead and upload it to SF's incoming dir and I'll move it into the wxPython project files when you give me the signal.
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!