> Now we have removed all logics and the size is still 78 kBytes!!! We
> think it is too big for that implementation. Must be a lot of dead
> code there.
I'm not sure. The infrastructure for classes, properties, events and
such take space, but I wouldn't call this exactly "dead". It is
infrastructure.
>> I think thats technically not possible at all, at least not as
>> comfortable as we want it to be. Adding the methods to the config
>> file is really uncomfortable and in my opinion not an option. And
>> how should the generator know what method will ever be called on
>> runtime in the application? We already have a bug open for removing
>> static methods the same way you described but doing that for member
>> methods is insane! I'm quite sure we don't put much effort on
>> removing those but on static methods, you are absolutely right,
>> especially in case you use one static method of a gigantic utility
>> class.
>
> It is sure possible!
Not automatically and completely safe.
> The question is how it can be done the best way.
> As you register dependencies of objects, classes you can register
> dependencies off line of functions. This register is at generation
"off line of functions"?!
> time so it does not affect runtime. Additionally, it can be easily
> implemented by a generator tag and giving as a part of the
> documentation.
>
> Insane ideas have changed the world many times!
But not always to the better.
>
> 1. Just a draft idea:
>
> @$callme callanother Clazz.runme
> callme : function() {
> this.callanother();
>
> var clazz = new Clazz();
> clazz.runme();
> },
Yes, compiler hints could be used to aid the generator. But you only
would want to fall back to this when a dependency cannot be detected
automatically.
> 2. the other way is parsing, which creates some problems...
Meaning?!
> Pros: good documentation and size reduction by deleting dead code
> Cons: the developer needs to document!!! (but it is really good even
> though most don't like it) = a necessity to document
Pros and cons of what? The tagging or the parsing approach? You should
try to make your chain of thought more obvious.
>
> You still have the opinion that it is useless?
We never said that. You should do a bit of research in our bugzilla
before putting up claims.
>
> Is the interface of the generator easy to plug into, modules?
No.
> Do you
> have any special way of doing that?
Doing what?
T.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
