Re: Tool to convert HTML in GWT widgets
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 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.
Re: Tool to convert HTML in GWT widgets
>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 -- 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.
Re: Tool to convert HTML in GWT widgets
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.
Re: MMLc: a Tool to convert HTML in GWT widgets
Thanks, all! MMLc uses, by default, only "lightweight" widgets, already included in the default GWT package (or a few bundled along with it). However, we designed it to be extensible, meaning you can design your templates with placeholders for other widgets you wish, such as a MapWidget (from google maps) or a GWT Rich Text Editor. Thanks again for your interest. Davi On Mon, May 24, 2010 at 6:50 PM, Duong BaTien wrote: > Please keep us in touch. We will definitely look at your technology and > GWT MVP with UIBinder in GWT 2.1 widgets. Your down-to-earth contrast > between MMLc and GWT UIBinder stimulate my interest. > > Thanks for Sharing. > BaTien > > On Mon, 2010-05-24 at 17:35 -0400, Gal Dolber wrote: >> THanks! >> >> 2010/5/24 Duong BaTien >> Congrats: >> >> Will MMLc support GWT Rich Text and client, soon to be open >> source by >> Google Wave client? Will that be a beginning of massive >> templates >> designed by UI designers and assembled by user? >> >> Duong BaTien >> DBGROUPS and BudhNet >> >> >> >> On Mon, 2010-05-24 at 10:04 -0700, rakesh wagh wrote: >> > good job >> > congrats! >> > keep it up. >> > >> > On May 23, 10:59 pm, Davi Pires wrote: >> > > Hi all, >> > > >> > > I'd like to announce that the tool I mentioned here >> earlier (6 months >> > > ago) has finally been opened. >> > > We call it MMLc. From the project description: >> > > >> > > "MMLc is a GWT generator that processes files written in >> an enriched >> > > HTML like syntax and outputs code that instantiates the >> precise >> > > widgets to represent that code. >> > > >> > > MMLc improves collaboration between programmer and >> designers in GWT >> > > projects, bringing back to the designers control over UI >> and style. >> > > Programmers need only to worry with programmers's stuff, >> which is a >> > > Good Thing." >> > > >> > > We are trying to turn GWT into a more team-friendly tool. >> So far, >> > > within our team, we have achieved great success with it. >> > > >> > > Links: >> > > - Project page:http://code.google.com/p/mmlc/ >> > > - An about page that explains it >> all:http://code.google.com/p/mmlc/wiki/AboutMMLC >> > > - The original mail thread on this >> group:http://groups.google.com/group/google-web- >> toolkit/browse_thread/threa... >> > > - Some people asked for a comparison between this project >> and the >> > > UiBinder. We explain it better >> here:http://code.google.com/p/mmlc/wiki/ComparisonToUIBinder >> > > >> > > Some parts of the project (namely, i18n support and >> extensibility) >> > > still lack proper documentation. It should be fixed soon. >> > > >> > > Looking forward to your valuable feedback. >> > > >> > > Cheers, >> > > Davi Pires >> > > >> > > -- >> > > You received this message because you are subscribed to >> the Google Groups "Google Web Toolkit" group. >> > > To post to this group, send email to google-web- >> tool...@googlegroups.com. >> > > To unsubscribe from this group, send email to google-web- >> toolkit+unsubscr...@googlegroups.com. >> > > For more options, visit this group >> athttp://groups.google.com/group/google-web-toolkit?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the >> Google Groups "Google Web Toolkit" group. >> To post to this group, send email to google-web- >> tool...@googlegroups.com. >> To unsubscribe from this group, send email to google-web- >> toolkit+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> >> >> >> >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Google Web Toolkit" group. >> To post to this group, send email to google-web- >> tool...@googlegroups.com. >> To unsubscribe from this group, send email to google-web-toolkit >> +unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this messag
Re: MMLc: a Tool to convert HTML in GWT widgets
Please keep us in touch. We will definitely look at your technology and GWT MVP with UIBinder in GWT 2.1 widgets. Your down-to-earth contrast between MMLc and GWT UIBinder stimulate my interest. Thanks for Sharing. BaTien On Mon, 2010-05-24 at 17:35 -0400, Gal Dolber wrote: > THanks! > > 2010/5/24 Duong BaTien > Congrats: > > Will MMLc support GWT Rich Text and client, soon to be open > source by > Google Wave client? Will that be a beginning of massive > templates > designed by UI designers and assembled by user? > > Duong BaTien > DBGROUPS and BudhNet > > > > On Mon, 2010-05-24 at 10:04 -0700, rakesh wagh wrote: > > good job > > congrats! > > keep it up. > > > > On May 23, 10:59 pm, Davi Pires wrote: > > > Hi all, > > > > > > I'd like to announce that the tool I mentioned here > earlier (6 months > > > ago) has finally been opened. > > > We call it MMLc. From the project description: > > > > > > "MMLc is a GWT generator that processes files written in > an enriched > > > HTML like syntax and outputs code that instantiates the > precise > > > widgets to represent that code. > > > > > > MMLc improves collaboration between programmer and > designers in GWT > > > projects, bringing back to the designers control over UI > and style. > > > Programmers need only to worry with programmers's stuff, > which is a > > > Good Thing." > > > > > > We are trying to turn GWT into a more team-friendly tool. > So far, > > > within our team, we have achieved great success with it. > > > > > > Links: > > > - Project page:http://code.google.com/p/mmlc/ > > > - An about page that explains it > all:http://code.google.com/p/mmlc/wiki/AboutMMLC > > > - The original mail thread on this > group:http://groups.google.com/group/google-web- > toolkit/browse_thread/threa... > > > - Some people asked for a comparison between this project > and the > > > UiBinder. We explain it better > here:http://code.google.com/p/mmlc/wiki/ComparisonToUIBinder > > > > > > Some parts of the project (namely, i18n support and > extensibility) > > > still lack proper documentation. It should be fixed soon. > > > > > > Looking forward to your valuable feedback. > > > > > > Cheers, > > > Davi Pires > > > > > > -- > > > You received this message because you are subscribed to > the Google Groups "Google Web Toolkit" group. > > > To post to this group, send email to google-web- > tool...@googlegroups.com. > > > To unsubscribe from this group, send email to google-web- > toolkit+unsubscr...@googlegroups.com. > > > For more options, visit this group > athttp://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > You received this message because you are subscribed to the > Google Groups "Google Web Toolkit" group. > To post to this group, send email to google-web- > tool...@googlegroups.com. > To unsubscribe from this group, send email to google-web- > toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google > Groups "Google Web Toolkit" group. > To post to this group, send email to google-web- > tool...@googlegroups.com. > To unsubscribe from this group, send email to google-web-toolkit > +unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: MMLc: a Tool to convert HTML in GWT widgets
THanks! 2010/5/24 Duong BaTien > Congrats: > > Will MMLc support GWT Rich Text and client, soon to be open source by > Google Wave client? Will that be a beginning of massive templates > designed by UI designers and assembled by user? > > Duong BaTien > DBGROUPS and BudhNet > > > On Mon, 2010-05-24 at 10:04 -0700, rakesh wagh wrote: > > good job > > congrats! > > keep it up. > > > > On May 23, 10:59 pm, Davi Pires wrote: > > > Hi all, > > > > > > I'd like to announce that the tool I mentioned here earlier (6 months > > > ago) has finally been opened. > > > We call it MMLc. From the project description: > > > > > > "MMLc is a GWT generator that processes files written in an enriched > > > HTML like syntax and outputs code that instantiates the precise > > > widgets to represent that code. > > > > > > MMLc improves collaboration between programmer and designers in GWT > > > projects, bringing back to the designers control over UI and style. > > > Programmers need only to worry with programmers's stuff, which is a > > > Good Thing." > > > > > > We are trying to turn GWT into a more team-friendly tool. So far, > > > within our team, we have achieved great success with it. > > > > > > Links: > > > - Project page:http://code.google.com/p/mmlc/ > > > - An about page that explains it all: > http://code.google.com/p/mmlc/wiki/AboutMMLC > > > - The original mail thread on this group: > http://groups.google.com/group/google-web-toolkit/browse_thread/threa... > > > - Some people asked for a comparison between this project and the > > > UiBinder. We explain it better here: > http://code.google.com/p/mmlc/wiki/ComparisonToUIBinder > > > > > > Some parts of the project (namely, i18n support and extensibility) > > > still lack proper documentation. It should be fixed soon. > > > > > > Looking forward to your valuable feedback. > > > > > > Cheers, > > > Davi Pires > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "Google Web Toolkit" group. > > > To post to this group, send email to > google-web-tool...@googlegroups.com. > > > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > > > For more options, visit this group athttp:// > groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: MMLc: a Tool to convert HTML in GWT widgets
Congrats: Will MMLc support GWT Rich Text and client, soon to be open source by Google Wave client? Will that be a beginning of massive templates designed by UI designers and assembled by user? Duong BaTien DBGROUPS and BudhNet On Mon, 2010-05-24 at 10:04 -0700, rakesh wagh wrote: > good job > congrats! > keep it up. > > On May 23, 10:59 pm, Davi Pires wrote: > > Hi all, > > > > I'd like to announce that the tool I mentioned here earlier (6 months > > ago) has finally been opened. > > We call it MMLc. From the project description: > > > > "MMLc is a GWT generator that processes files written in an enriched > > HTML like syntax and outputs code that instantiates the precise > > widgets to represent that code. > > > > MMLc improves collaboration between programmer and designers in GWT > > projects, bringing back to the designers control over UI and style. > > Programmers need only to worry with programmers's stuff, which is a > > Good Thing." > > > > We are trying to turn GWT into a more team-friendly tool. So far, > > within our team, we have achieved great success with it. > > > > Links: > > - Project page:http://code.google.com/p/mmlc/ > > - An about page that explains it > > all:http://code.google.com/p/mmlc/wiki/AboutMMLC > > - The original mail thread on this > > group:http://groups.google.com/group/google-web-toolkit/browse_thread/threa... > > - Some people asked for a comparison between this project and the > > UiBinder. We explain it better > > here:http://code.google.com/p/mmlc/wiki/ComparisonToUIBinder > > > > Some parts of the project (namely, i18n support and extensibility) > > still lack proper documentation. It should be fixed soon. > > > > Looking forward to your valuable feedback. > > > > Cheers, > > Davi Pires > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to google-web-tool...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-web-toolkit+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: MMLc: a Tool to convert HTML in GWT widgets
good job congrats! keep it up. On May 23, 10:59 pm, Davi Pires wrote: > Hi all, > > I'd like to announce that the tool I mentioned here earlier (6 months > ago) has finally been opened. > We call it MMLc. From the project description: > > "MMLc is a GWT generator that processes files written in an enriched > HTML like syntax and outputs code that instantiates the precise > widgets to represent that code. > > MMLc improves collaboration between programmer and designers in GWT > projects, bringing back to the designers control over UI and style. > Programmers need only to worry with programmers's stuff, which is a > Good Thing." > > We are trying to turn GWT into a more team-friendly tool. So far, > within our team, we have achieved great success with it. > > Links: > - Project page:http://code.google.com/p/mmlc/ > - An about page that explains it > all:http://code.google.com/p/mmlc/wiki/AboutMMLC > - The original mail thread on this > group:http://groups.google.com/group/google-web-toolkit/browse_thread/threa... > - Some people asked for a comparison between this project and the > UiBinder. We explain it better > here:http://code.google.com/p/mmlc/wiki/ComparisonToUIBinder > > Some parts of the project (namely, i18n support and extensibility) > still lack proper documentation. It should be fixed soon. > > Looking forward to your valuable feedback. > > Cheers, > Davi Pires > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
MMLc: a Tool to convert HTML in GWT widgets
Hi all, I'd like to announce that the tool I mentioned here earlier (6 months ago) has finally been opened. We call it MMLc. From the project description: "MMLc is a GWT generator that processes files written in an enriched HTML like syntax and outputs code that instantiates the precise widgets to represent that code. MMLc improves collaboration between programmer and designers in GWT projects, bringing back to the designers control over UI and style. Programmers need only to worry with programmers's stuff, which is a Good Thing." We are trying to turn GWT into a more team-friendly tool. So far, within our team, we have achieved great success with it. Links: - Project page: http://code.google.com/p/mmlc/ - An about page that explains it all: http://code.google.com/p/mmlc/wiki/AboutMMLC - The original mail thread on this group: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/61a6e62bcfda3cdd?pli=1 - Some people asked for a comparison between this project and the UiBinder. We explain it better here: http://code.google.com/p/mmlc/wiki/ComparisonToUIBinder Some parts of the project (namely, i18n support and extensibility) still lack proper documentation. It should be fixed soon. Looking forward to your valuable feedback. Cheers, Davi Pires -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tool to convert HTML in GWT widgets
I confess that I didn't know about the UiBinder. But, now that you mentioned, after taking a look at it, and discussing with the team we are keeping with our own tool. The main difference between the two approaches is that our language to define the widget tree (which we call MHTML) does a best effort approach to be as similar as possible to HTML. The purpose here is to easen the conversion of the pure HTML code into something "parseable" and easily and directly convertible to GWT widgets. For example, while you need a tag to instantiate a ListBox widget, in our case you would write directly the tag. A tag is converted into a FlowPanel, s in InlineLabels, and so on. One thing that the UIBinder does that we don't do is the automatic binding of the widgets into the parent class fields. In our tool, we have to write a few lines that fetch the subwidgets by id, and store them in the class fields. (Although, we are now thinking of implementing the automatic binding on our tool too). While discussing it in our team, everyone (specially the designer) felt much more inclined to continue using our tool. We will do some more work on improving the code, and open up its code soon. Thanks for the feedback. Cheers, Davi Pires On Wed, Nov 25, 2009 at 1:24 AM, Sripathi Krishnan wrote: >> How does it compare to the UIBinder in GWT 2? > > From the description, it is exactly what UiBinder does. > > --Sri > > > 2009/11/25 Yozons Support on Gmail >> >> How does it compare to the UIBinder in GWT 2? I've not used it yet, but >> understand it's an XML file format for building UIs. If they overlap, >> people will more likely prefer UIBinder, but if they do not, I'm sure others >> would be interested. >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- eco-blog: http://tarjaverde.wordpress.com -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tool to convert HTML in GWT widgets
let me know. i can try. also attach some examples... On Wed, Nov 25, 2009 at 12:52 AM, gwtfanb0y wrote: > This sounds very interesting to me, please open up the code for us. > > > On 24 Nov., 22:32, 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 > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tool to convert HTML in GWT widgets
This sounds very interesting to me, please open up the code for us. On 24 Nov., 22:32, 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 "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tool to convert HTML in GWT widgets
> > How does it compare to the UIBinder in GWT 2? > >From the description, it is exactly what UiBinder does. --Sri 2009/11/25 Yozons Support on Gmail > How does it compare to the UIBinder in GWT 2? I've not used it yet, but > understand it's an XML file format for building UIs. If they overlap, > people will more likely prefer UIBinder, but if they do not, I'm sure others > would be interested. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tool to convert HTML in GWT widgets
How does it compare to the UIBinder in GWT 2? I've not used it yet, but understand it's an XML file format for building UIs. If they overlap, people will more likely prefer UIBinder, but if they do not, I'm sure others would be interested. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tool to convert HTML in GWT widgets
+1 It's got my vote--sounds interesting. I actually started writing something similar, but what I have does not approach the sophistication of what you've described. It is still very much a manual process. On Nov 24, 3:32 pm, 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 "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Tool to convert HTML in GWT widgets
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 "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
