Hello Burak, We plan to have the API consistent among all 1.x releases. But as you sure know, improving things means sometimes changing the API. But we always have the old API available and working (at least we plan to).
Moving the 1.0 release to some later point is currently no option. There are not only the io things "not perfect" in the framework. So waiting for all stuff to be the way we like it could take some time (years). The whole table is a point we need to discuss here in the team. We planed to build a new table on the virtual widgets infrastructure which has not happened jet. So we first need to get our plans and roadmap for the upcoming year ready to tell you how much time we can invest in the "old" table. If you think that renaming of the table namespaces are a good idea, you can file a bug report but as i said, i don't know if we have time to fix it soon. The topic of remote models is sure on our list but in the context of data binding. There is already a bug for that (http://bugzilla.qooxdoo.org/show_bug.cgi?id=2993) which will be addressed soon (at least I hope so). Best, Martin Burak Arslan-2 wrote: > > 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 > > -- View this message in context: http://n2.nabble.com/rpc-in-qooxdoo-tp4058077p4064650.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
