I don't think it would be a good idea unless migrating to SmartGWT overall - it would just drag on a whole other heavy framework. <div><br></div><div>Longer term it would be nice to NOT depend on any JS frameworks- but use GWT native ones - the reason being that only the used bits are compiled in, and also as GWT compiler innovations continue apace, that insures compatability and speed improvements. </div>
<div><br></div><div>I don't really see the need to use a JS library like SmartGWT - the only place we used GWT-ext was for the overall "chrome" look - (eg the accordion, tabs) and a few grid views, and a couple of trees, barely 10% of what is in the ext framework. </div>
<div><br></div><div>I certainly think it is a very bad idea to use a framework like smart GWT now for widgets - the built in GWT ones are pretty basic, but it is worth the effort to compose them into richer ones, or look for GWT "native" ones to reuse - as at least they will be resolved at compile time. Some GWT ones to take a look at: <a href="http://vaadin.com/home">http://vaadin.com/home</a> and <a href="http://code.google.com/p/gwt-mosaic/">http://code.google.com/p/gwt-mosaic/</a></div>
<div><br></div><div>(not that I have anything against javascript, just it makes things much harder with GWT, and kind of defeats the purpose of using it).</div><div><br></div><div>Of course we would like to get off gwt-ext eventually, I don't think SmartGWT is the way to go, and certainly not introducing it unless we plan to migrate to it. <br>
<br><div class="gmail_quote">On Tue, Feb 2, 2010 at 1:46 AM, Esteban Aliverti <span dir="ltr"><<a href="mailto:esteban.aliverti@gmail.com">esteban.aliverti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<div>Baunax and I are making some improvements in Guvnor's rule editor (from/collect/accumulate support, expression builder widget, etc.) and we want to start using Smart GWT (<a href="http://www.smartclient.com/" target="_blank">http://www.smartclient.com/</a>). This library is the successor of GWText (the one Guvnor is using now). You can see this in GWText home page <a href="http://code.google.com/p/gwt-ext/" target="_blank">http://code.google.com/p/gwt-ext/</a>.</div>
<div>Some of the reasons we have to move to Smart GWT are:</div><div><ul><li>GWTExt is deprecated. It is <span style="font-family:arial, sans-serif;font-size:13px">no longer under active development.</span></li>
<li><span style="font-family:arial, sans-serif;font-size:13px">Smart GWT is under LGPL license (just like GWTExt)</span></li><li><span style="font-family:arial, sans-serif;font-size:13px">Smart GWT support any version of GWT (from 1.5.3 to 2.0). There shouldn't be any problem when we start using GWT 2.xx</span></li>
<li><span style="font-family:arial, sans-serif;font-size:13px">Smart GWT has a lot of widgets, effects, layouts etc. that can make our life easier ;).</span></li></ul><div><font face="arial, sans-serif">Of course we are not going to migrate Guvnor to Smart GWT; we want just to use it for the new features we are implementing.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">So, are you guys agree? Does anyone have any objection? </font></div><div><font face="arial, sans-serif"><br>
</font></div><div><font face="arial, sans-serif">We are currently working on guvnor_expressionEditor3_baunax_esteban branch.</font></div><div><font face="arial, sans-serif"><br>
</font></div><div><font face="arial, sans-serif">Best,</font></div><br>-- <br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br><br>Esteban Aliverti<br>
</div>
<br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Michael D Neale<br>home: <a href="http://www.michaelneale.net">www.michaelneale.net</a><br>blog: <a href="http://michaelneale.blogspot.com">michaelneale.blogspot.com</a><br>
</div>