Hey, Am 24.09.2013 um 09:57 schrieb Peter Schneider <[email protected]>:
>> Hey, >> >>> I have recently started to port my web desktop from QooxDoo 0.7 to 3.0 >>> and I have to say that I have not yet come to the point to appreciate >>> all of the changes in the API. >> >> Well, you migrate from a at least 5 year old qooxdoo version to the current >> development. I hope you understand that some APIs changed over these long >> time >> period and some of the decisions made during that time might be not the best >> decision from todays view, even if they were the right thing to do back then. > > Not a true argument! I migrated from 2.1.2 to 3.0 (the smallest possible > step!) and face the same problems. 3.0 was a major release with a lot of changes under the hood and we put a lot of effort in keeping those changes away from the application developer. The last time the framework had such a huge change was between 0.7.4 and 0.8 which required the developer a lot more of manual migration work than this time. ;) >>> With that said, I replaced my homegrown code for loading scripts in 0.7 >>> with qx.io.ScriptLoader and in 3.0.1 it seems I'll have to replace this >>> again with qx.bom.request.Script >> >> I understand that this change is annoying for you. But this class was marked >> as >> experimental which means use at your own risk and we do not consider it ready >> for production. This also means we can remove the class without any >> deprecation >> because its experimental. > > That's an argument, but _how_ can I search for experimental classes? > Should I take a look through my complete dependency tree and look at the > source code/API description? It's marked in the API documentation, in the documentation of the experimental classes to be precise. But we don't have possibility to search for it except in the code base. > Or is there a generator option that tells me about experimental classes? > For deprecated classes/methods I think this is done, but I haven't come across > a 'experimental class warning' ever. > > >>> [...] >> I don't think its good to start a discussion on the mailing list and in a bug >> report: >> http://bugzilla.qooxdoo.org/show_bug.cgi?id=6064 >> Please check the discussion there and see my detailed posts on former >> questions >> there. > > What's wrong with a discussion? > Or do you want it to be moved to the bug report? Discussions are welcome and good. I only want to keep it in one place to make sure we don't miss any argument. Regards, Martin ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
