> Is there an explanation posted somewhere of why the developers decided to move > mahogany development to the beta release of wxWindows? As someone who is very > reluctant to switch to a beta version of wxWindows (especially one that hasn't > even been released yet), I feel like I've been left out in the cold here. > > This is a major change. I think this merits a larger change in the version > number and mention on the website (which would have saved me the wasted time > of downloading a 3 MB file I won't use)
We probably could have made more of the change requirement :-( It was driven by a requirement for functionality in the new version. I track the wxWindows cvs HEAD daily and I can honestly say that in the past many months since work on 2.5 started, there have only been two times I recall that the cvs built correctly and then caused M to fail. There have also only been a handful of times when the wxWindows cvs failed to build for whatever reason. Mahogany probably could use a person devoted to keeping our website up to date so if you know anyone, don't hesitate to volunteer them :-) Vadim, maybe a link to http://biolpc22.york.ac.uk/pub/2.5.0p1/ from our website with a brief word of explanation? There are only 3-5 of us that are working on M (ir)regularly in one way or another so more help is desperately needed and since I'm about to start a uni degree in a few weeks, there will be even less on a consistent basis. Over the past several months I have attempted to attract more developers however my attempts have been unsuccessful. Dr. QA ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Mahogany-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-users
