I believe Nicolas Heron was looking at this, if he had time during the christmas break - if not, please, go ahead, it would solve a few problems. <br><br><div class="gmail_quote">On Tue, Feb 2, 2010 at 3:57 PM, Jervisliu <span dir="ltr">&lt;<a href="mailto:jliu@redhat.com">jliu@redhat.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Michael Neale wrote:<br>
&gt; I know someone was looking at upgrading to GWT 2.0, even with gwt-ext,<br>
&gt; it may still work<br>
&gt;<br>
</div>We can certainly upgrade to GWT 2.0. If we run into any problems during<br>
the upgrade, we can always fix them. There is a Jira ticket relates to<br>
this topic: <a href="https://jira.jboss.org/jira/browse/GUVNOR-158" target="_blank">https://jira.jboss.org/jira/browse/GUVNOR-158</a> (Upgrade key<br>
libary dependencies (post 5.0)).<br>
<br>
Who is working on GWT 2.0 upgrade? If no one else is already starting<br>
looking into GWT2.0, I will volunteer to do this.<br>
<br>
Cheers,<br>
Jervis<br>
<div class="im">&gt; On Tue, Feb 2, 2010 at 10:13 AM, Esteban Aliverti<br>
</div><div class="im">&gt; &lt;<a href="mailto:esteban.aliverti@gmail.com">esteban.aliverti@gmail.com</a> &lt;mailto:<a href="mailto:esteban.aliverti@gmail.com">esteban.aliverti@gmail.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;     Ok, I agree with you. We have discussed this with conan today and<br>
&gt;     get the same conclusion as you. We started looking at mosaic, but<br>
&gt;     the biggest limitation we have right now is the GWT version we are<br>
&gt;     using. New libraries are already using gwt 2.0, so we canīt use<br>
&gt;     the latest versions of them. The same problem arise when composing<br>
&gt;     widgets. GWT 1.5.3 is very basic.<br>
&gt;     We will continue using native GWT or GWTExt until Guvnor is moved<br>
&gt;     to GWT 2.x (I donīt know the effort required for that).<br>
&gt;<br>
&gt;     Best,<br>
&gt;<br>
&gt;<br>
&gt;     On Mon, Feb 1, 2010 at 11:31 PM, Michael Neale<br>
</div><div><div></div><div class="h5">&gt;     &lt;<a href="mailto:michael.neale@gmail.com">michael.neale@gmail.com</a> &lt;mailto:<a href="mailto:michael.neale@gmail.com">michael.neale@gmail.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;         I don&#39;t think it would be a good idea unless migrating to<br>
&gt;         SmartGWT overall - it would just drag on a whole other heavy<br>
&gt;         framework.<br>
&gt;<br>
&gt;         Longer term it would be nice to NOT depend on any JS<br>
&gt;         frameworks- but use GWT native ones - the reason being that<br>
&gt;         only the used bits are compiled in, and also as GWT compiler<br>
&gt;         innovations continue apace, that insures compatability and<br>
&gt;         speed improvements.<br>
&gt;<br>
&gt;         I don&#39;t really see the need to use a JS library like SmartGWT<br>
&gt;         - the only place we used GWT-ext was for the overall &quot;chrome&quot;<br>
&gt;         look - (eg the accordion, tabs) and a few grid views, and a<br>
&gt;         couple of trees, barely 10% of what is in the ext framework.<br>
&gt;<br>
&gt;         I certainly think it is a very bad idea to use a framework<br>
&gt;         like smart GWT now for widgets - the built in GWT ones are<br>
&gt;         pretty basic, but it is worth the effort to compose them into<br>
&gt;         richer ones, or look for GWT &quot;native&quot; ones to reuse - as at<br>
&gt;         least they will be resolved at compile time. Some GWT ones to<br>
&gt;         take a look at: <a href="http://vaadin.com/home" target="_blank">http://vaadin.com/home</a><br>
&gt;         and <a href="http://code.google.com/p/gwt-mosaic/" target="_blank">http://code.google.com/p/gwt-mosaic/</a><br>
&gt;<br>
&gt;         (not that I have anything against javascript, just it makes<br>
&gt;         things much harder with GWT, and kind of defeats the purpose<br>
&gt;         of using it).<br>
&gt;<br>
&gt;         Of course we would like to get off gwt-ext eventually, I don&#39;t<br>
&gt;         think SmartGWT is the way to go, and certainly not introducing<br>
&gt;         it unless we plan to migrate to it.<br>
&gt;<br>
&gt;         On Tue, Feb 2, 2010 at 1:46 AM, Esteban Aliverti<br>
&gt;         &lt;<a href="mailto:esteban.aliverti@gmail.com">esteban.aliverti@gmail.com</a><br>
</div></div><div><div></div><div class="h5">&gt;         &lt;mailto:<a href="mailto:esteban.aliverti@gmail.com">esteban.aliverti@gmail.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;             Hi all,<br>
&gt;             Baunax and I are making some improvements in Guvnor&#39;s rule<br>
&gt;             editor (from/collect/accumulate support, expression<br>
&gt;             builder widget, etc.) and we want to start using Smart GWT<br>
&gt;             (<a href="http://www.smartclient.com/" target="_blank">http://www.smartclient.com/</a>). This library is the<br>
&gt;             successor of GWText (the one Guvnor is using now). You can<br>
&gt;             see this in GWText home<br>
&gt;             page <a href="http://code.google.com/p/gwt-ext/" target="_blank">http://code.google.com/p/gwt-ext/</a>.<br>
&gt;             Some of the reasons we have to move to Smart GWT are:<br>
&gt;<br>
&gt;                 * GWTExt is deprecated. It is no longer under active<br>
&gt;                   development.<br>
&gt;                 * Smart GWT is under LGPL license (just like GWTExt)<br>
&gt;                 * Smart GWT support any version of GWT (from 1.5.3 to<br>
&gt;                   2.0). There shouldn&#39;t be any problem when we start<br>
&gt;                   using GWT 2.xx<br>
&gt;                 * Smart GWT has a lot of widgets, effects, layouts<br>
&gt;                   etc. that can make our life easier ;).<br>
&gt;<br>
&gt;             Of course we are not going to migrate Guvnor to Smart GWT;<br>
&gt;             we want just to use it for the new features we are<br>
&gt;             implementing.<br>
&gt;<br>
&gt;             So, are you guys agree? Does anyone have any objection?<br>
&gt;<br>
&gt;             We are currently working<br>
&gt;             on guvnor_expressionEditor3_baunax_esteban branch.<br>
&gt;<br>
&gt;             Best,<br>
&gt;<br>
&gt;             --<br>
&gt;             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
&gt;<br>
&gt;             Esteban Aliverti<br>
&gt;<br>
&gt;             _______________________________________________<br>
&gt;             rules-dev mailing list<br>
</div></div>&gt;             <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a> &lt;mailto:<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>&gt;<br>
<div class="im">&gt;             <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;         --<br>
&gt;         Michael D Neale<br>
</div>&gt;         home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a> &lt;<a href="http://www.michaelneale.net" target="_blank">http://www.michaelneale.net</a>&gt;<br>
&gt;         blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a> &lt;<a href="http://michaelneale.blogspot.com" target="_blank">http://michaelneale.blogspot.com</a>&gt;<br>
&gt;<br>
&gt;         _______________________________________________<br>
&gt;         rules-dev mailing list<br>
&gt;         <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a> &lt;mailto:<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>&gt;<br>
<div class="im">&gt;         <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;     --<br>
&gt;     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
&gt;<br>
&gt;     Esteban Aliverti<br>
&gt;<br>
&gt;     _______________________________________________<br>
&gt;     rules-dev mailing list<br>
</div>&gt;     <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a> &lt;mailto:<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>&gt;<br>
<div class="im">&gt;     <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Michael D Neale<br>
</div>&gt; home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a> &lt;<a href="http://www.michaelneale.net" target="_blank">http://www.michaelneale.net</a>&gt;<br>
&gt; blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a> &lt;<a href="http://michaelneale.blogspot.com" target="_blank">http://michaelneale.blogspot.com</a>&gt;<br>
<div class="im">&gt; ------------------------------------------------------------------------<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; rules-dev mailing list<br>
&gt; <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
&gt; <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
&gt;<br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<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>
</div></div></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>