On Tue, Jun 05, 2007 at 06:40:35PM -0600, Jack Madison wrote: > and possibly deal with changes to pysoy down the road.
Moot now since I'm already neck deep in libogg2 implementation, but just a note, this is an internal code issue and doesn't effect the API in any way. It's just adopting some extra work. Albiet, work I'm very familiar with and willing to work on again after a 2 year hiatus, and likely somewhat comperable to what libogg1 would take to "get right". > I'd also like to see pysoy maintain what appears > to be a general philosophy of doing more work upfront to do things > right, than just do whatever it takes to get it working. Well thats why we're a year late for a 1.0 release ;-) We kept finding ways the engine could be signifigantly better if it were restructured. At this point we're set on the current model, lest we become a group of constant re-invention, and hold any core restructuring to PySoy 2.0. We are set to release beta-1 around the end of this month, just after the GPLv3 license release. I'm hoping to get 1.0 out by Sept 1st though, if not, we'll release a new beta monthly until we do. This will not delay beta-1, though it may delay 1.0 as I'd *like* to have everything working by then. _______________________________________________ PySoy-Dev mailing list [email protected] http://www.pysoy.org/mailman/listinfo/pysoy-dev
