rough estimate for date of next release?

Kevin_Altis · May 1, 2004, 8:01pm

So, any guesses on when 2.5.2.1 or 2.5.1.6 or whatever target you have is going to be released and/or when we'll see it on this list? The main reason I'm curious is that when 2.5.1.5 was released there was talk of doing an intermediate Mac OS X release as Stefan and Kevin O. fixed bugs, but that never materialized and I would like to know what is fixed and what isn't so I can start reporting bugs again

I expect that release 0.8 of PythonCard is about 2-3 weeks away as well and it would be nice if the next wxPython is out before then, but if not, I need to plan for 2.5.1.5 support.

ka

Kevin_Ollivier4 · May 1, 2004, 8:57pm

Hi Kevin,

So, any guesses on when 2.5.2.1 or 2.5.1.6 or whatever target you have is going to be released and/or when we'll see it on this list? The main reason I'm curious is that when 2.5.1.5 was released there was talk of doing an intermediate Mac OS X release as Stefan and Kevin O. fixed bugs, but that never materialized and I would like to know what is fixed and what isn't so I can start reporting bugs again

Sorry, it seems both Stefan and I have gotten quite busy. For me the primary issue has been school, but the good news on my front is that I'm finishing a major paper today, and a Java project tomorrow, and then I just have exams in a little over a week (I'll probably take finals the 10th-11th). From there, (assuming I pass I'll have my degree in BSing... err, I mean my BS degree in Computer Science, and after that I'll have some free time again. =)

But truth to tell, the CVS HEAD for wxPython is in pretty good shape. The patches I sent to Robin last week fix most all of the serious issues that have arisen (crashes and tracebacks). I still have one on the way, but it's for wxPopupControl, not a major control. As of my last test, a few days ago, there are about 4 other issues left, 2 of which are cosmetic and not serious. The others are with wxThread and wxCheckListBox (which isn't complete under the new DataBrowser implementation), but I don't think those issues should stop people from testing. I would say it's about good enough for a "preview release" of the new version, though I'd like to have those last issues resolved by the time we have a public release on wxPython.org.

I expect that release 0.8 of PythonCard is about 2-3 weeks away as well and it would be nice if the next wxPython is out before then, but if not, I need to plan for 2.5.1.5 support.

Until exams are over, I probably won't have time to roll an OS X release on my end, so it'll be up to Robin if he's ready to put something out. But here's what I would suggest doing:

- Put out a "developer preview" release of wxPython on OS X so that people can start playing with the new codebase

- See how that goes, and if there aren't many error reports, put out a preview release of 2.5.1.6 for all platforms.

- Target a final release Mid-May, hopefully before PythonCard. If you shoot for somewhere around the 21st of May, that would give me some extra time to work on the bugs that do remain and will hopefully lead to a more polished release. I *may* also be able to get in a truly native wxComboBox in that timeframe too (it's half implemented in my branch), but no promises.

Robin, I know I'm just making suggestions while I can't do the work here ;-), so what do you think? Does this work for you?

BTW, have you seen the wxMac CVS HEAD codebase recently? I was just curious about your impressions.

Back to properly citing my references.... ^_^;

Thanks,

Kevin

···

On May 1, 2004, at 1:01 PM, Kevin Altis wrote:

Robin · May 1, 2004, 9:11pm

Kevin Altis wrote:

So, any guesses on when 2.5.2.1 or 2.5.1.6 or whatever target you have is going to be released and/or when we'll see it on this list?

Don't know yet. There have been other changes[1] besides the major ones in wxMac that have impacted a lot of things. For the past couple weeks I've been focusing on stablizing the changes and resolving issues on Windows and GTK (in addition to workign on the reference docs,) and it sounds like there is still a bit of stabalization and such going on for wxMac. I expect that sometime next week that my focus will shift over to wxMac again (plus the docs) and so we'll see how it goes. If it all looks good then I'll try making some preview releases.

[1] One of the changes that impacted a lot of stuff was that wxADJUST_MINSIZE is now the default behaviour for window items added to a sizer. This made a lot of layouts break when classes didn't have a good implementaion for DoGetBestSize and/or they were relying on the larger than best size that an item had when adding it to the sizer. I think I've managed to get almost all of those issues working as good or better than they were before. In a nutshell, if an initial size was specified for a window when it was created then when it is added to a sizer that will be set as the window's minimal size, and the sizers will honor that minimal size if it is set. Otherwise it uses the value returned from GetBestSize. The one scenario that doesn't quite work the same as before is when a window is created with default size, and then before adding it to the sizer it is given some other size. In that case the best size will be used instead of the size it had when added to the sizer. To resolve that you just need to call SetSizeHints to set the item's minsize.

The other change that has had lots of ripples is that the way that windows inherit (or don't) font and colour attributes from their parent windows. (With 2 or 3 different attepmts!) Also, how a window's default font is determined has changed. Since the more modern GUIs like XP, OSX and GTK2 can have different attribute defaults on a per window type basis, and also be controlled by the theme, in many cases it doesn't make sense to always rely on a system-wide default or to get the attributes from the parent. There are still a few glitches in the new system here and there but they are being resolved. For the most part things will just work and you won't notice much difference, unless you were doing some tricks that rely on the old system, (such as setting the font on the dialog or panel in order to get all child controls to use that font.)

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!