[xwiki-devs] JS UI framework for rich client interface?
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? regards Pascal
Pascal Voitot wrote:
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. -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Tue, Jun 24, 2008 at 10:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Pascal Voitot wrote:
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 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.
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 :))
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Pascal Voitot wrote:
On Tue, Jun 24, 2008 at 10:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Pascal Voitot wrote:
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 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.
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 :))
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/
On Tue, Jun 24, 2008 at 12:02 PM, Sergiu Dumitriu <[email protected]> wrote:
Pascal Voitot wrote:
On Tue, Jun 24, 2008 at 10:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Pascal Voitot wrote:
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 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.
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 :))
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.
I think I will use a simple script which has been tested enough to be usable but I won't add any new framework... Always the same problem: how to do nice and pro and clean while keeping it light and quick and reducing development load...
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (2)
-
Pascal Voitot -
Sergiu Dumitriu