Greg, thanks for you feedback.
On 08/29/2013 06:04 AM, Gregory Beaver wrote: > Dear qooxdoo, > > I wrote a very complicated application based on qooxdoo a few years > ago. It still works great but there are some kinks that I was trying > to work out. I spent 13 hours over the past week trying to get 50 > lines of code to work. Maybe you should hit the mailing list earlier. Sometimes you don't see the trees for the wood, and it just needs another pair of eye balls to spot it. > 8 of that was trying to debug a problem with appearance and the > magical fact you have to tell some things what they should look like > in some circumstances, but not in others. No errors or warnings to > assist either. The link between widgets and appearance is soft. Maybe you can open an enhancement bug to the end that, given a certain flag, the source version would spit out how the runtime is associating application objects with appearance id's. That might help. > > Then, I ran into a weird bug with selection that I cannot reproduce > with any shorter code, and spent 6 hours writing no new code and > simply trying to figure out where the hell selection is converted to > actual highlighting in qx.ui.list.List 50 lines should be fine for the Playground, given it doesn't involve other application classes. > > As of right now, I have erased all the work and thrown in the towel. > I have not had this much frustration and impossibility of solving a > banal issue since I worked with Microsoft Access in 2000. You must have been very lucky all the way since... > > There has got to be a better way to do things. Too much is magic, the > generated code has no line breaks and can't be stepped through even in > source mode. That's hard to believe as the source version uses the original source files, with line breaks, comments and all. > > I have literally run out of all of my available time allotted for this > project, and we have to stick with the older not-quite-working code as > a result. > > If any of you have successfully found a time-efficient way to debug > problems in selection or binding or any other qooxdoo black magic, I > would appreciate the tips for the next time I have a block of time to > try something. Until then, I hope my utter failure is a wake up call > from a former evangelist of qooxdoo (one of my blog posts is a top hit > in google search for qooxdoo with many visitors every day). One thing I cannot stress enough is that you run the qooxdoo migration on your code base when you update the SDK version (which I assume you did). The migration will adjust your code to changed APIs, getting a lot of things out of your way, and will otherwise print out a various helpful hints for you to follow. Same goes for warnings in the source version. T. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
