MartinWittemann wrote: > Hello Burak, > its interesting that you come up with that topic. Not even two hours ago I > talked to Fabian about your first two topics. As you sure know, we can not > just move stuff without deprecating them. So one thing is for sure, there > will be a io2 namespace in the release. But we plan to deprecate it and get > it all to the io namespace. >
hi martin, so 1.0 not going to be much of an api freeze anyway? that's fine by me then. > I also agree with you that we should have another implementation for all the > transport things in the framework. But I don't know either if or what time > we will have the resources to implement new code. Sure not before a 1.0 > release. That needs some more time to think about and to implement. > i agree. i'd vote for postponing the 1.0 release for this reason, if ever you'd bother to ask the community. backend communication is one of the most important components! > For your bug question, there is already bugs open for the io2 namespace. > http://bugzilla.qooxdoo.org/show_bug.cgi?id=1163 > yes, but what about my other points? i'm especially interested in core devs' thoughts about 3.b best regards, burak ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
