Hi Fritz, this is interesting; I too use protochart (and therefore, prototype) in a qooxdoo app. Works nice, in fact it is already in productive use in a controlling application. First, can you elaborate on under which circumstances the mentioned problem occurs? I mean, is this incompatibility caused by a prototype update, or the qooxdoo svn up (or both of it, ...)? Are you using prototype for more than integrating protochart? As I write apps which have to be in a stable environment at my customers', I use 0.8.2 SDK instead of trunk, but I want to be prepared if things should break when upgrading some app to 0.8.3 (actually, the app I'm talking 'bout only uses remote.Requests, in any other case I prefer RPCs for backend comm).
Second, have you ever thought about porting protochart to qooxdoo (like, qxchart)? I must admit that the idea seemed attractive to me, but I kind of lack the time (although I already messed around with protochart quite a bit). Nevertheless I'm curious if others are interested in a qooxdoo charting module. I'd like to hear your opinion, greetings Stefan Fritz Zaucker wrote: > Hi Derrell, > > I just dont' get it. Both in the playground and also in a small test > application stringify() works just fine. As does RpcExample. > > However, with the same QOOXDOO_PATH (r19935) in config.json my (complex) > application still shows the same (broken) stringify behaviour. Even after > > ./generate.py distclean > ./generate.py source > > I just wanted to give up and then I had a last idea and found the problem > (if not yet the solution). In addition to Qooxdoo I am using prototype and > protochart in my application (sourcing them in index.html). And it seems > that prototype is not (anymore) compatible with Qooxdoo and seems to cause > the stringify() problem (or to be more precise to mess up the Array type > detection). There is an isArray() function in prototype, so probably this is > now getting into the way (still must have something to do with the patch in > r17648). > > I'll remember for the future to make verify every "bug" in a clean > environment (without the prototype library, for example). > > Sorry for the false alarm, I had really thought I had tracked down the > problem and now it's just not there in the controlled environment ... :-( > > Fritz ------------------------------------------------------------------------------ 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
