Johann, my impression is you experience a lot of issues which are outside qooxdoo's scope, e.g. using an outdated Python version. You have to meet the requirements mentioned in the manual, and should read all the release notes between your old version and the 1.4.1 you are migrating to.
I can only hope that you carefully studied and followed the migration guide [1], which among other things mentions that if you are migrating from a 0.8.2 or prior version, you have to do a two-step migration first going to 0.8.3, and then to 1.4.1. You cannot migrate this in one go. - Did you do that? [1] http://manual.qooxdoo.org/1.4.1/pages/migration/migration_guide.html On 08/19/2011 05:41 PM, Johann Mellin wrote: > > "- Warning: Hint: Unknown global symbol referenced: reportnr > (newversion.Application:1688)" > "- Warning: Hint: Unknown global symbol referenced: x > (newversion.Application:2323)" > "- Warning: Hint: Unknown global symbol referenced: y > (newversion.Application:2223)" > ... > > I tried to fix it, by adding a "var"-command before every > variable I use, where it was missing. If a variable is passed > to a function I added "this." (i.e. making a > "myfunction(this.myvar);" out of "myfunction(myvar)"). Look, these are warnings (as the beginning of the line implies), so these are certainly not "bigger problems". You should take care of them, but it's not a state of emergency. But getting into this, you cannot just arbitrarily prefix variable names with something. Maybe you forgot a 'var' for a local variable in one place or another. But maybe your application *uses* global variables, so prefixing such one with 'var' will actually break it! Much more you cannot just prefix things with "this.". This is crazy! If you have a global or local variable myvar within a method, prefixing it with "this." will break the connection to it, and rather reference an instance variable this.myvar which might not even exist. With your changes you are then passing 'undefined' to myfunction. Please read a good introduction to objects and methods and the use of 'this' in JavaScript, e.g. in Flanagan's "JavaScript The Definitive Guide". > The warnings vanished. But still the site is empty, because there are > errors in the js-source (According to firebug) and the Javascript is > not executed. > FireBox says for instance: > "setChecked is not a function" Well, you need not worry about any follow-up errors if you treat your code like this. > > Can you help me one more time to find a solution (i.e. to get > the app running). > > If someone has an idea / method to find a solution .... I would be > very grateful! You desperately need to understand what you are doing. Mechanical changes won't get you anywhere. T. ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
