Hi list, I finally created my application with all the new features I needed under qx 0.7.4. Everything worked fine till yesterday ;)
The windows-update installed IE10 on my machine and my application didn't work anymore. A known problem (Invalid Character DOM Exception in IE9) occurred. I could fix it in 0.7.4 but many other things didn't work too. My colleague are also using IE10 and on there machine everything works without problems... So I decided to give the migration from 0.7 to 2.2.1 a second chance ;) I migrated my application to 0.8 but still with all legacy-widgets included. And here I really need your help. I followed the migration-guide from http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07#manual_work But I just don't know what to do with this future-embed-thing. Could someone help me here? Some of my questions are: 1. what to do with f.e. qx.legacy.util.AliasManager.getInstance("myicons", ...).add ? this is no widget. Can I just use it without the future-widget? When I remove the "legacy" my application will not show any icon anymore... 2. how to use the future-widget in detail? How to layout it? Do I have to remove all legacy-widgets ( I have 259 legacy-widgets included in my project ;)) before migrating to 2.2.1? Or can I just do the next migration and then remove the legacy-widgets? Thanks a lot! Tobi -----Ursprüngliche Nachricht----- Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]] Gesendet: Montag, 25. Februar 2013 07:00 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? Thanks for your help. But i spend almost 2 days for trying to convert the app to 0.8. I found a way to use the 0.7-version with our new restfull webservices. After I made all changes in my application I may have the time to create a complete new application under qooxdoo 2.1.x. I have one more question (qx 0.7.4): We have a restful-webservice which needs authentication (f.e. http://localhost/myapp/documents) When I enter a wrong combination of user/password, the browser automatically opens a login-promt because our webservice-framework throws a 401-error. Is there any way, except of not throwing a 401-error, to prevent the browser to open this login-promt? Of course we could throw another error-code but that wouldn't be a correct solution. Thanks -----Ursprüngliche Nachricht----- Von: thron7 [mailto:[email protected]] Gesendet: Freitag, 22. Februar 2013 12:10 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 02/22/2013 11:04 AM, Fritz Zaucker wrote: > Hi Tobias > > On Fri, 22 Feb 2013, Tobias Koller \(GERMO GmbH\) wrote: > >> After including the ".theme.*" I was able to start my application and >> I thought that's it, but unfortunately it doesn't work. >> >> F.e. all the events I fire (with this.dispatchevent) doesn't work. No >> EventListener is starting after event was fired. 'dispatchevent' is still supported in 0.8, but the listener API changed (see further). So maybe your custom events are just not registered properly. That should be easy to find out. Locate a listener that is not responding and check the return value from the addListener call. > This sounds strange ... can you isolate this by pulling some small > part out of your application? > >> Maybe I should create a complete new application with qooxdoo 2.1.1... > we have several applications that started with 0.7 and are now using > trunk > (pre2.2) successfully. We did, however, follow the Qooxdoo development > as closely as possible, so the migration steps were usually small. But > I wouldn't just give up if I were you. Although rewriting an > application with all the experiences of the first version usually give > a much better second version ... ;-) ... but I think if you went this > route it should not be just because Qooxdoo changed ... > > Did you carefully read the migration.log files? Perhaps you missed > some manual changes that are required? Indeed, the event system was changed with 0.8, but the changes were mostly automatic. Your migration.log should be full of them. The 0.8-alpha2 release notes had an entire section devoted to events [1]. T. [1] http://qooxdoo.org/project/release_notes/0.8-alpha2#events ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
