Tobias,
the canonical way for this situation (symbols outside the qooxdoo
project but known to be around at runtime), is to use the #ignore pragma
around the top of the using file [1]. E.g. in foo.bar.js you would add
/*
#ignore(ExternalStatic.Namespace.Value)
*/
Maybe when you check project A you'll find such a compiler hint already
in the class code. Why this warning wouldn't show up with qooxdoo 1.6 I
cannot say, as this hasn't changed between 1.6 and 2.0. But as these
warnings are only shown when a class is compiled *afresh*, chances are
you haven't seen it in a long time because the compiled class code has
always been taken from cache.
T.
[1] http://manual.qooxdoo.org/2.0.x/pages/tool/code_structure.html#details
(The manual fails to mention that you can also use trailing wildcards
with #ignore, so you can ignore entire namespaces, e.g. with
#ignore(ExternalStatic.*).)
On 08/03/2012 10:13 AM, Tost, Tobias wrote:
Hi,
I got a strange problem with a project I just migrated from qooxdoo
1.6 to qooxdoo 2.0.1. We have large portions of static, external
javascript code that get referenced directly from within the qooxdoo
application. With project A this works fine without any problems and
qx 2.0.1. The newly migrated project B has issues with the same
accesses, now:
Unfullfilled dependency of class 'foo.bar'[1,75]:
'ExternalStatic.Namespace.Value'
Foo.bar is part of the qx application, ExternalStatic is defined in a
dedicated, stand-alone javascript file. The only solution to fix this
was adding the name "ExternStatic" to MClassDependencies.py QXGLOBALS
so it is "isInterestingIdentifier" returns false and thus omits the
whole namespace.
Is there a proper way to get this done and which option might I have
missed while migrating Project B when Project A is working perfectly
fine with the same config and overall source code structure (while
implementation is different, tough).
Also let me thank you seriously for the quick support and great you
did with qooxdoo -- Great stuff!
Regards,
Tobias
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
