24 Jun
2008
24 Jun
'08
12:02 p.m.
Pascal Voitot wrote:
On Tue, Jun 24, 2008 at 10:56 AM, Sergiu Dumitriu
<sergiu(a)xwiki.com> wrote:
In the end, maybe yes. It is a continuous evolution, who knows what will be there in a
year, or two.
There is no one golden framework, and using more than one has an impact on the performance
(as all
JS files must be loaded into memory by the browser). So, we're trying to keep the
number of
frameworks to a minimum.
Since you want to contribute your changes, don't add yet another framework. If you
must, use YUI for
the moment. Sometime someone will clean up all the JS, HTML and CSS.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Pascal Voitot wrote:
I agree with you but I can accept using those dirty frameworks in order to
be quick at providing a clean interface and to focus on my real problem
which is the service logic.
Hello,
I would like to modify object/class editor by integrating some richer UI
widgets such as tabviews.
Apparently, you are trying to get rid of Rico, YUI and trying to do as
much
as possible with Proto...culous
But Protoculous doesn't provide tabviews for example.
In this case, what do you advise as JS framework for this? YUI as it is
already integrated in XWiki and can be used with velocity? GWT by
redeveloping a set of serverside APIs but without the possibility to use
velocity?
Personally, I don't like YUI, as it is done in the Yahoo manner:
crappy.
Also, I don't like GWT, as
it does things the Google way: quirky and obfuscated.
I'd advise to stick to prototype as much as
possible, as a simple tabview
is easy to write in
something around 15 minutes.
Finally, "XWiki core UI" shall always be independent of any JS framework but
prototype, isn't it? (that's what I had understood before sending this mail
:))