Agreed. The actual requirement verification logic has no dependencies to DOM-level classes, it's the check methods such as hasFirefox etc. that do. We should move these to (a) separate class(es).
Regards, Daniel On 01/12/2012 01:26 PM, thron7 wrote: > > > On 01/12/2012 01:20 PM, Alexander Steitz wrote: >> Hi Leo, >> >> the "MRequirements" mixin does make use of the "qx.core.Environment" class >> which itself has these dependencies. Since in the Node.js environment no DOM >> is available the use of the "document" API fails. > > I don't think its the fault of the Environment class, but MRequirements > draws in all browser-related feature checks. As Alex wrote, they make > use of e.g. the "document" object, as in this case, which is not > available in Node. Hence MRequirements cannot currently be used outside > a browser environment. You may open an enhancement bug for this. > > > T. > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Mar 27 - Feb 2 > Save $400 by Jan. 27 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev2 > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
