Hi Thomas, it's easy to reproduce this issue, just add include: "qx.*" into config.json and you get it. You must set qxvariant["qx.debug"] to "on".
Cheers - Petr 2009/4/6 thron7 <[email protected]> > Ok, there is already a bug open concerning dependency issues (#2188), > and this problem might be related. I've added a comment to this end. It > would be helpful if you could reproduce it in a Skeleton app. > > T. > > Petr Kobalíček wrote: > > Hi thron, > > > > good news :) Half of problems described here are gone (tried yesterday > > trunk). But the assert failure is still here. > > > > I tracked this problem and it's here: > > > > qx/lang/Object.js: > > > > /** > > * Get the keys of a map as array as returned by a "for ... in" statement. > > * > > * @signature function(map) > > * @param map {Object} the map > > * @return {Array} array of the keys of the map > > */ > > getKeys : qx.core.Variant.select("qx.client", > > { > > "mshtml" : function(map) > > { > > * if (qx.core.Variant.isSet("qx.debug", "on")) { > > qx.core.Assert.assertMap(map, "Invalid argument 'map'"); > > }* > > > > var arr = []; > > for (var key in map) { > > arr.push(key); > > } > > > > // IE does not return "shadowed" keys even if they are defined directly > > // in the object. This is incompatible to the ECMA standard!! > > // This is why this checks are needed. > > var hasOwnProperty = Object.prototype.hasOwnProperty; > > for (var i=0, a=this._shadowedKeys, l=a.length; i<l; i++) > > { > > if (hasOwnProperty.call(map, a[i])) { > > arr.push(a[i]); > > } > > } > > > > return arr; > > }, > > > > "default" : function(map) > > { > > * if (qx.core.Variant.isSet("qx.debug", "on")) { > > qx.core.Assert.assertMap(map, "Invalid argument 'map'"); > > }* > > > > var arr = []; > > > > for (var key in map) { > > arr.push(key); > > } > > > > return arr; > > } > > }), > > > > Error is : qx.core.Assert is undefined. > > > > I tried to add #require(qx.core.Assert) into qx.core.Object.js, but > > this didn't helped. > > > > - Petr > > > > 2009/4/4 thron7 <[email protected] > > <mailto:[email protected]>>: > > >> Hi thron, > > >> > > >> It's qxbuild package (currently under construction), I will reply to > > >> this mail when I finished releasing it and you can look at it (you are > > >> probably more familiar in build system than me). > > > > > > I'm not sure. Given the things you do you must be pretty familiar > > with the > > > build system yourself :). > > > > > >> Thanks for your time, I need your help to catch this :) > > > > > > I'm not sure I have the resources to dig into that. As I said before, I > > > would need a generic qooxdoo issue to work with. I don't think I can > > debug > > > your custom build. Apart from that I can only give you some general > > > pointers: > > > > > > - take a good look at the generator output while it runs, look for > > > irregularities (like unlikely numbers of classes, etc.); > > > - maybe use the -v command line switch to get more detailed messages > > (you > > > might want to redirect this to a file for later browsing); > > > - if you are working against trunk, make yourself familiar with the > > 0.8.2 > > > release notes, in order to catch all the things that have changed from > > > 0.8.1. > > > > > > HTH, > > > Thomas > > > > > >> - Petr > > >> > > >> 2009/4/3 Thomas Herchenröder <[email protected] > > <mailto:[email protected]>>: > > >>> > > >>> > > >>> Petr Kobalíèek wrote: > > >>>> Hi thron, maybe we not understand each other :) > > >>>> > > >>>> I'm talking about compiling only qooxdoo without my scripts and this > > >>>> compiled qooxdoo will fail. > > >>> > > >>> Well, but even if you are "compiling only qooxdoo" you do so within a > > >>> specific environment like e.g. the config.json (some details of which > > >>> you disclosed in your other mail). And "fail" can only a complete > > >>> application, not the compiled qooxdoo alone. What application is > that? > > >>> Can you e.g. reproduce it in a skeleton app? > > >>> > > >>>> I'm not studied why it failed, but I think > > >>>> that it's in wrong order or some things are not included at all. > > >>>> > > >>> > > >>> Well, since it is very hard for us to assess your environment and the > > >>> whereabouts of your build, I'm afraid you have to dig a bit deeper to > > >>> come up with a bug description that is generic to qooxdoo, ideally > > >>> reproduceable in a skeleton app. > > >>> > > >>> T. > > >>> > > >>>> So pure qooxdoo can't be compiled by this way :( > > >>>> > > >>>> Cheers > > >>>> - Petr > > >>>> > > >>>> 2009/4/3 thron7 <[email protected] > > <mailto:[email protected]>>: > > >>>> > > >>>>> Petr Kobalíèek wrote: > > >>>>> > > >>>>>> Hi thron, > > >>>>>> > > >>>>>> debug on or off is qxbuild settings that is used in config.json to > > >>>>>> turn debugging on / off. I think that this is not important, > > >>>>>> important > > >>>>>> is that if I build everything qooxdoo script will fail. > > >>>>>> > > >>>>>> > > >>>>> Well, I think if you set qx.debug to on it has to fail since e.g. > > >>>>> assertions are not supported in the build version. I guess > > that's why > > >>>>> qx.core.Assert is undefined. > > >>>>> > > >>>>> As for the undefined qx.locale, this is strange. Did you check the > > >>>>> compiled output whether qx.locale is included? Maybe it's in the > > wrong > > >>>>> order?! > > >>>>> > > >>>>> T. > > >>>>> > > >>>>> > > >>>>>> - Petr > > >>>>>> > > >>>>>> 2009/4/2 thron7 <[email protected] > > <mailto:[email protected]>>: > > >>>>>> > > >>>>>> > > >>>>>>> Actually, I don't know what you are talking about. E.g. what does > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>> (debug off) > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>> and > > >>>>>>> > > >>>>>>> > > >>>>>>>> (debug on) > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>> mean? > > >>>>>>> > > >>>>>>> T. > > >>>>>>> > > >>>>>>> > > >>>>>>> > > > ------------------------------------------------------------------------------ > > >>>>>>> _______________________________________________ > > >>>>>>> qooxdoo-devel mailing list > > >>>>>>> [email protected] > > <mailto:[email protected]> > > >>>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>> > > > ------------------------------------------------------------------------------ > > >>>>>> _______________________________________________ > > >>>>>> qooxdoo-devel mailing list > > >>>>>> [email protected] > > <mailto:[email protected]> > > >>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>> > > > ------------------------------------------------------------------------------ > > >>>>> _______________________________________________ > > >>>>> qooxdoo-devel mailing list > > >>>>> [email protected] > > <mailto:[email protected]> > > >>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > >>>>> > > >>>>> > > >>>> > > >>>> > > > ------------------------------------------------------------------------------ > > >>>> _______________________________________________ > > >>>> qooxdoo-devel mailing list > > >>>> [email protected] > > <mailto:[email protected]> > > >>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > >>>> > > >>>> > > >>>> > > >>> > > >>> -- > > >>> Thomas Herchenröder > > >>> Core Development - Web Technologies > > >>> > > >>> 1&1 Internet AG phone: +49 (0)721 91374-4482 > > >>> Ernst-Frey-Str.9 web : www.1und1.de <http://www.1und1.de> > > >>> 76135 Karlsruhe qooxdoo.org <http://qooxdoo.org> > > >>> > > >>> Amtsgericht Montabaur HRB 6484 > > >>> > > >>> Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, > > >>> Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning > > Kettler, > > >>> Dr. Oliver Mauss, Jan Oetjen > > >>> Aufsichtsratsvorsitzender: Michael Scheeren > > >>> > > >>> > > >>> > > >>> > > > ------------------------------------------------------------------------------ > > >>> _______________________________________________ > > >>> qooxdoo-devel mailing list > > >>> [email protected] > > <mailto:[email protected]> > > >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > >>> > > >> > > >> > > > ------------------------------------------------------------------------------ > > >> _______________________________________________ > > >> qooxdoo-devel mailing list > > >> [email protected] > > <mailto:[email protected]> > > >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > >> > > >> > > >> > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > > qooxdoo-devel mailing list > > > [email protected] > > <mailto:[email protected]> > > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > > > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > qooxdoo-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
