Hello Stefan,
Its again, interesting to read your mails. But again, I have some questions.
>To all others: Relax, nothing has been checked in! It is just an
>enhancement bug in bugzilla :).
Is this funny?
You wrote "checked in" and as this is a term usually used for repositories,
that was a simple clarification.
I assume this is not the core team's opinion.
How do you know the core teams opinion?
We would appreciate a more professional attitude! Thanks!
As we would too. ;)
Yes, T! It is a tremendous loss off information and that is what is wanted! One
example:
If you have a json array of 250 rows with each 3 key-value pairs, you save the
space (in our case 66%)
T, the keys are repeated 3 x 250 times without sense!
Thats working fine in your example and thats what you needed in your
application. On a technical point, I totally agree with you for your use case.
So your arguments hit exactly the point.
But thats not the only thing relevant for putting it into the framework. There
has to be a general use case for using it and there has to be no other solution
possible. I do believe that both are not valid in this case. Why?
1. We build big applications here too and none ever asked for such a feature.
Additionally, I agree with t, that the JSON could have been set up that way in
the first place if the files are in your control.
2. Thats a single precompilation step which can be done by a command line tool.
Give us test results instead, supporting your "theories" and imagination, with
the above given facts.
Are we in charge to give you results? I don't think so.
T, your rethorics is full of holes and is inconsequent.
And you call that professional attitude?
Are databases compressed in any way to save space? yes, they are and the
reasons are obvious
Do we compile code to execute applications? yes, we do and the reasons are
obvious
Does qooxdoo use compression? yes, it does and it is obvious why
I can not read compressed and changed qooxdoo javascript! The biggest loss of
information and distortion of javascript semantics are generated by the
generator.
Javascript was not intended to be compressed, but qooxdoo is. We know the
reasons.
Again, technically correct but thats not the point. So I won't argue with you
about the technical details on that enhancement. I do not doubt your arguments
here. But maybe you should not doubt that we know the framework best and want
it to be as good as possible for all users.
Regards,
Martin
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
