> I don't get how to define this in the config file. Basically it's just
> another type of dependency. We also do not lost depencies of classes
> in the configuration.
Oh, yes we do, just remember the "require" config key.
> Just the top-level includes.
And I consider these "external" libraries also top-level.
> Especially
> regarding variants etc. it might be useful to have this in the code
> instead of the configuration. It's more flexible IMHO.
>
That might be something to think about at some point. But compiler hints
are also variants-ignorant, so they are not very flexible too in this
regard.
> Keeping it at class-level might also help when thinking of resources
> e.g. assets which could be integrated using the already available
> #asset hints.
>
> Maybe this means a pseudo helper class for every external lib, but
> still might be better than placing it into the config.
>
I think the config is good place to start as this is a major change in
the semantics of the build system. Better than hiding it somewhere in
class code. Mind that alternatively these libraries go into the index.html.
T.
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
