Google Web Toolkit

Friday, June 27, 2014

Re: You have to try : Putnami Web Toolkit your next GWT Framework.

Hi Eddy,

Thank you for the congrats.

We know that it still an amount of work around the documentation stuff (Completeness, Typos, Javadoc). The framework is young and we keep working hard every day to improve it.

We could focus our efforts on right things, simply with feedback on good but mainly on wrong or unclear things.

What kind of documentation is missing? (Everything of course but as we are only two full time worker we have to sort them and go step by step)

- Complete tutorial (video or not?).

- More detailed examples.

- Javadoc

- Overviews of the frameworks and the features.

- Other ...

We also are sorry for the low level of our English on the current documentation. But we did not practiced for a while. Any help is welcome.

Concerning the forum, we have created a dedicated group to exchange around PWT. Everyone is welcome.

https://groups.google.com/forum/#!forum/putnami-web-toolkit

Also think to follow us on twitter.

https://twitter.com/PutnamiTeam

Regards.

—

Fabien

http://pwt.putnami.org

Le 27 juin 2014 à 02:26, Eddy Ponce <edylio@gmail.com> a écrit :

Looks Great, like other serius UI , congratulations¡, I will try to use it the next week, the problem I think it is about the documentation , we must create a forums for this topic

Re: gwt-plugin for eclipse 4.4 / luna ?

The Google Plugin for Eclipse is maintained and published by Google, not byt the GWT team.

Please use StackOverflow or the Google Plugin for Eclipse forum for GPE-related questions.

I happens someone asked it there already: https://groups.google.com/d/topic/google-plugin-eclipse/4YACQROrB2U (no response yet)

On Thursday, June 26, 2014 2:39:43 AM UTC+2, oneTETSUO wrote:

hello precious,

as noticed, eclipse 4.4 came out on 25nd of june this year ( 2014 ).

may i ask what roadmap leads us to a compliant plugin later on.

as i noticed, the eclipse-plugin-container changed over the time and the gwt-plugin had problems, capturing the changes within. beside it drives me mad sometimes when the configuration of compiler-settings went lost or the button itself stays without functionality. it would be nice, to get a "circa" date for this issue.

best wished to that sprint ...

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Consuming GWT RPC Response

Here is an write up about the GWT-RPC wire format as of GWT 2.5: https://docs.google.com/document/d/1eG0YocsYYbNAtivkLtcaiEE5IOF5u4LUol8-LL0TIKU/edit?hl=de&forcehl=1

-- J.

Re: Best way to style a web app in diffrent ways

Hi thank you.

That is al lot of information and I will try it.

My style ist static. And I don't have to change the whole style. I only have to change the colors of my webapp.

I will tell you when I have any results.

Re: Developing Google Gadget with Eclipse GWT plugin

good! though it seems too long ago.

Abel.

在 2009年8月26日星期三UTC+8下午5时29分11秒，Luca写道：

Hi guys, I wrote some notes on how to use the Eclipse Plugin to
develop Google Gadgets with GWT that are hosted on GAE

http://www.lucamasini.net/Home/gwt/google-app-engine/developing-google-gadget-with-eclipse-gwt-plugin

Hope this can help.
Ciao.

Thursday, June 26, 2014

Re: You have to try : Putnami Web Toolkit your next GWT Framework.

Looks Great, like other serius UI , congratulations¡, I will try to use it the next week, the problem I think it is about the documentation , we must create a forums for this topic

El martes, 17 de junio de 2014 11:13:38 UTC-5, Fabien Dumay escribió:

Hello all,

I'am glad to announce that PWT also called Putnami Web Toolkit is out of the box.

http://pwt.putnami.org

PWT is a powerfull GWT framework which will revolutionize your productivity.

Open source the repository is available on https://github.com/Putnami/putnami-pwt

We built PWT to be lightweight and efficient.

It provides new graphical components based on a solid architecture.

Thanks to Twitter 's Bootstrap, your applications are responsive and easily themable.

The nice graphical components are easy to extend and to customize.

The data binding is a pushover, build form and dynamic tables is now so simple.

Server calls are simplified and optimized. Multiplex your queries, and say good bye to the useless Async interfaces.

Navigation is done to simplified the MVP. Split and scale your application without even knowing.

No third librairies, No external JS. Which provides security and serenity on your achievements and our future.

Focused on the useless code removal, all the graphical design is no more described in the java, but nicely lay on a UI template.

Easy to start, we think that's PWT is a serious alternative for your next web application developments.

All your feedbacks are really precious and will be taken into account with the utmost consideration.

Best regards

Re: Why not use class name as the TYPE of the event

Use the qualified class name would disallow to extend events sharing the same EventHandler.

On the bellow code you can handle all the AbstractSessionEvent extentions with the single AbstractSessionEvent.Handler interface.

public abstract class AbstractSessionEvent extends Event<Handler> {

public interface Handler extends EventHandler {...}

protected static Type< Handler > TYPE = new Type< Handler >();

@Override

protected void dispatch(Handler handler){ … }

}

public class LoginEvent extends AbstractSessionEvent{

public Event.Type< Handler > getAssociatedType() {

return TYPE;

}

public class LogoutEvent extends AbstractSessionEvent{

public Event.Type< Handler > getAssociatedType() {

return TYPE;

}

Their is probably mush more reasons. But I think this one is good enough.

Regards

Fabien.

http://pwt.putnami.org

Le 26 juin 2014 à 09:00, smiletolead <kumar.ganesha@gmail.com> a écrit :

Hi all,

A custom event needs to have a TYPE variable to denote the type of the event. For example:

public class LogoutEvent extends Event<LogoutEventHandler>
{
public static Type<LogoutEventHandler> TYPE = new Type<LogoutEventHandler>();

@Override
protected void dispatch(LogoutEventHandler handler)
{
handler.onLogout();
}

@Override
public com.google.web.bindery.event.shared.Event.Type<LogoutEventHandler> getAssociatedType()
{
return TYPE;
}

}

I am just curious about the need to have the TYPE field. Why GWT could not use the class name of the event(in this case LogoutEvent) to denote the type of the event. Only purpose I see of this type is to have it as a key in the map of events and their handlers. I think even the class name could have served as the key in this map.

Thanks
Ganesh