Ooh! Now I saw it. The initial letter is from 2009. Sorry for replied to a
zombie thread
Vassilis
On Tue, Nov 8, 2016 at 12:48 PM, Vassilis Virvilis <vasv...@gmail.com>
wrote:
> From the subject I thought that somebody was asking for the "magical" tool.
> By reading becomes evident that somebody has actually implemented the
> "magical" tool which is not magical after all just a lot of work, design,
> builtin assumptions and real life trade offs as all useful software.
>
> Definitely it looks interesting. After all is like UiBinder done in html
> instead of xml.
>
> Congrats.
>
>
> On Tue, Nov 8, 2016 at 12:15 PM, Dhinakar Reddy Pothireddi <
> dhinakarred...@gmail.com> wrote:
>
>> Please open up the code and help us to learn it. Thanks in advance.
>>
>> On Wednesday, November 25, 2009 at 3:02:08 AM UTC+5:30, Davi Pires wrote:
>>>
>>> Hi all,
>>>
>>> In my company, we have been working with GWT for almost a year,
>>> developing a ridesharing application (http://www.bigoo.com.br). I
>>> really can't overstate how much we enjoy developing in java, using
>>> familiar tools, debugging in hosted mode, and so on. But one thing
>>> that has really bothered us for a long time is the dificulty of
>>> integrating the work of developers (who write the code that eventually
>>> outputs the HTML) with the work of designers (who write CSS).
>>>
>>> Eventually we came up with a method where the designer gave the devs
>>> an HTML fragment that worked as a 'contract' between their codes. The
>>> devs had to write the GWT code that instantiated the widgets and set
>>> ids and styles according to the spec. It worked, we did the job, but
>>> there were lots of problems on the way:
>>>
>>> - every little change to the 'contract' (new id, new classes) had to
>>> be implemented by the developer. Therefore, there was a significant
>>> delay between the designer's writing of the css and it being reflected
>>> on the system.
>>> - the designer felt rather demotivated by not having control over
>>> generation of the UI.
>>>
>>> Well, I guess some of these problems have already been mentioned here.
>>> I won't dwell on it anymore.
>>>
>>> Recently we implemented a small tool to help us overcome this problem.
>>> In short, the designer writes the specs in an extended subset of HTML,
>>> outside of the java code, in a properties file. This file is processed
>>> by a generator we wrote that outputs the java code needed to
>>> instantiate the gwt widgets corresponding to that spec.
>>>
>>> In the GWT code we can retrieve each subnode of the tree (or
>>> 'subwidget') by the id, and add to it the appropriate handlers, or set
>>> any other property.
>>>
>>> We have automated the instantiation of the widgets, their addition the
>>> the corresponding parents, the setting of a few properties such as
>>> ids, classes, titles, value and enabled. It has allowed us to
>>> reimplement complete pages, with all the interaction we had before,
>>> significantly speeding up the development process, reducing the size
>>> of the code, making it more readable, and increasing developer and
>>> designer satisfaction.
>>>
>>> I'd like to ask the community if anyone is interested on such a tool.
>>> We are planning on opening up this code, but it still needs some work.
>>> If it's of anyone's interest we would gladly open it.
>>>
>>> Cheers,
>>> Davi Pires
>>>
>>>
>>> --
>>>
>>>
>>> eco-blog: http://tarjaverde.wordpress.com
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Vassilis Virvilis
>
--
Vassilis Virvilis
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
