Paul Libbrecht wrote:

The little I look into it from a user perspective... it looks horribly windowsish... I find both Ext controls (at least as in Curriki) or GWT controls much less tainted.

Among little difficulties, scroll-wheel (that is, MacBook's two-finger-trackpad) isn't working.

Where ? I've got it right on many widgets Jerome.

Maybe I'm old fashion but I still don't understand what is the interest of providing the API documentation only using a doc-browser which prevents most self-organization one is used to (e.g. open in a new tab, bookmark, put in history). Both SmartClient and Ext do this mistake. (I've never seen a desktop javadoc reader which has really beaten the web-based ones)

paul

Le 02-déc.-08 à 19:02, Vincent Massol a écrit :

...

Hi,

I'd like to propose using smartGWT/smartClient for all our widget needs both in GWT and in JS: * Their set is pretty impressive and has all we need. * It's under LGPL * Sanjiv has moved from Ext GWT to SmartGWT and since he's had a bad history with Ext GWT we can assume he has received enough reassurance from smartClient to remain open source and under the LGPL license. * It's both GWT and JS and we need both * The little of the source I have seen look very clean.

Some links: * http://www.jroller.com/sjivan/entry/smartgwt_1_0_released * http://code.google.com/p/smartgwt/ * http://www​.ongwt.com​/post/2008​/11/27/Sma​rtGWT-%3A-​A- QampA-wi​th-Sanjiv-​Jivan2 * http://www.smartclient.com/product/smartLGPL.jsp

Here's my +1 (barring any issue we see when we start using it of course)

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

------------------------------------------------------------------------

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

Thank for the info.. You guys have been doing amazing work. This is really impressive. I'm +1 for using smartgwt.. Ludovic ckendrick wrote:

Hi Guys, just chiming in from Isomorphic..

Scrollwheel wasn't working specifically in Safari (they only recently added events for this), but this is fixed as of the next beta, due out (we hope) this weekend.

We are in the midst of adding new skins that are a close match to Outlook 2007. If you weren't aware, this is what Ext (and countless others) have been cloning:

http://images.google.com/images?q=outlook%202007

We will soon post samples in this thread on our forums:

http://forums.smartclient.com/showthread.php?t=3060

Cheers, Charles

Jerome Velociter-2 wrote:

...

Paul Libbrecht wrote:

...

The little I look into it from a user perspective... it looks horribly windowsish... I find both Ext controls (at least as in Curriki) or GWT controls much less tainted.

Among little difficulties, scroll-wheel (that is, MacBook's two-finger-trackpad) isn't working.

Where ? I've got it right on many widgets

Jerome.

...

Maybe I'm old fashion but I still don't understand what is the interest of providing the API documentation only using a doc-browser which prevents most self-organization one is used to (e.g. open in a new tab, bookmark, put in history). Both SmartClient and Ext do this mistake. (I've never seen a desktop javadoc reader which has really beaten the web-based ones)

paul

Le 02-déc.-08 à 19:02, Vincent Massol a écrit :

...

Hi,

I'd like to propose using smartGWT/smartClient for all our widget needs both in GWT and in JS: * Their set is pretty impressive and has all we need. * It's under LGPL * Sanjiv has moved from Ext GWT to SmartGWT and since he's had a bad history with Ext GWT we can assume he has received enough reassurance from smartClient to remain open source and under the LGPL license. * It's both GWT and JS and we need both * The little of the source I have seen look very clean.

Some links: * http://www.jroller.com/sjivan/entry/smartgwt_1_0_released * http://code.google.com/p/smartgwt/ * http://www​.ongwt.com​/post/2008​/11/27/Sma​rtGWT-%3A-​A- QampA-wi​th-Sanjiv-​Jivan2 * http://www.smartclient.com/product/smartLGPL.jsp

Here's my +1 (barring any issue we see when we start using it of course)

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

------------------------------------------------------------------------

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

On Dec 2, 2008, at 10:18 PM, Marius Dumitru Florea wrote:

I'm +0 right now. There are some things that I have to check about SmartGWT widgets:

* can I load only the widgets I use and not the whole library? * how much do they rely on GWT widget framework? * can I update to the latest GWT version without breaking them? * have they been written using deferred binding with browser specific code in different classes or do they wrap spaghetti JavaScript code? * are they easily customizable? * are their developers active on their forums/mailing lists?

These are all very good questions and we definitely need answers for them. One other point: if we don't use smartGWT which library will we use? I don't know many comprehensive widget libraries that: * are under a compatible license (Ext GWT/JS are not under a compatible license) * have both GWT and JS widgets * is comprehensive (i.e. we don't have various libraries, all having different look and feels) Note that I'm strongly against redeveloping widgets we need from scratch, as we've done for our live grid, our lightbox or for the sandbox calendar since it has almost all drawbacks you can imagine: * time consuming * hard maintenance (you need to fix all bugs + feature requests) * need to document them * less good than a specialized version where people have focused on developing it * will need to move to a standardized library in the future for sure, hence the double cost (cost of writing it in the first place + cost of dumping it and using the standardized library) Let's cross fingers and hope that smartGWT fills the bill. Thanks -Vincent

Vincent Massol wrote:

...

Hi,

I'd like to propose using smartGWT/smartClient for all our widget needs both in GWT and in JS: * Their set is pretty impressive and has all we need. * It's under LGPL * Sanjiv has moved from Ext GWT to SmartGWT and since he's had a bad history with Ext GWT we can assume he has received enough reassurance from smartClient to remain open source and under the LGPL license. * It's both GWT and JS and we need both * The little of the source I have seen look very clean.

Some links: * http://www.jroller.com/sjivan/entry/smartgwt_1_0_released * http://code.google.com/p/smartgwt/ * http://www​.ongwt.com​/post/2008​/11/27/Sma​rtGWT-%3A-​A- QampA-wi​th-Sanjiv-​Jivan2 * http://www.smartclient.com/product/smartLGPL.jsp

Here's my +1 (barring any issue we see when we start using it of course)

Thanks -Vincent

Hi Guys, Chiming in from Isomorphic - we'd love to see xWiki pick up SmartGWT. If I weren't already working on SmartClient a project like xWiki is probably what I'd be involved with :) So let me address your concerns: 1) Piecewise loading of widgets: yes you can load the framework piecewise. At coarse granularity we have major modules like "Grids", "Forms", "DataBinding". At finer granularity you can pick and choose individual files and make a custom build. 2) GWT widget dependency: SmartClient (the JavaScript engine inside SmartGWT) runs completely standalone, so I think the answer is "not at all". We have interoperability with other GWT widgets however. If I didn't address your concern please let me know. 3) New GWT versions: I don't forsee a problem, but have you had issues of this kind before? 4) Browser-specific code: Neither approach really. We have a foundation layer and widgets above this foundation do not need browser-specific code. 5) Customization: Probably our longest suit, both in terms of the skinning system (even if you don't like the themes, you'll notice that there's a huge breadth of look and feel, it's not just color changes) and also in terms of the model for custom components: http://www.smartclient.com/#_Extending_Component.Reuse 6) Active developers: extremely active, just check our forums. Hey we're even here on *your* forums ;) Cheers Charles Marius Dumitru Florea wrote:

I'm +0 right now. There are some things that I have to check about SmartGWT widgets:

* can I load only the widgets I use and not the whole library? * how much do they rely on GWT widget framework? * can I update to the latest GWT version without breaking them? * have they been written using deferred binding with browser specific code in different classes or do they wrap spaghetti JavaScript code? * are they easily customizable? * are their developers active on their forums/mailing lists?

Thanks, Marius

Vincent Massol wrote:

...

Hi,

I'd like to propose using smartGWT/smartClient for all our widget needs both in GWT and in JS: * Their set is pretty impressive and has all we need. * It's under LGPL * Sanjiv has moved from Ext GWT to SmartGWT and since he's had a bad history with Ext GWT we can assume he has received enough reassurance from smartClient to remain open source and under the LGPL license. * It's both GWT and JS and we need both * The little of the source I have seen look very clean.

Some links: * http://www.jroller.com/sjivan/entry/smartgwt_1_0_released * http://code.google.com/p/smartgwt/ * http://www​.ongwt.com​/post/2008​/11/27/Sma​rtGWT-%3A-​A- QampA-wi​th-Sanjiv-​Jivan2 * http://www.smartclient.com/product/smartLGPL.jsp

Here's my +1 (barring any issue we see when we start using it of course)

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

---

devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

-- View this message in context: http://n2.nabble.com/-VOTE--Use-SmartGWT-for-WYSIWYG-widgets-and-SmartClient... Sent from the XWiki- Dev mailing list archive at Nabble.com.