On Fri, Oct 31, 2008 at 11:41 AM, thron7 <[EMAIL PROTECTED]>wrote:
>
> Usage of missing classes, i.e. classes that were not detected during a
> library scan (this is also the case if it is the second, third, ...
> class in a .js file).
>
> >> If not, need they display?
>
> It was seen as an enhancement. Actually, you were one to request it
> (http://bugzilla.qooxdoo.org/show_bug.cgi?id=1133 :).
>
Yup. And a fine enhancement it has turned out to be. :-)
But there was an entry missing in the migration data for DataEvent, which I
> added.
Great. Thanks.
This brings up another interesting point. That error in the API build has
apparently been there for a long time, but nobody noticed it (or at least,
didn't fix the class causing the problem, so I'm assuming they didn't notice
it). I have had errors in my own build that I didn't notice too. The
reason is that there's a LOT of superfluous information being presented,
that masks any real issues. Is it possible to tell the generator to shut up
about all but important stuff? I'd like for the generator not to say
anything at all on success, just like most compilers. Warnings and errors
should then make themselves obvious. (I'll look for your response here, but
I'll also post a ticket for this.)
Cheers,
Derrell
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
