by aviy
tags:
border:
Hi All
Anyone who interesting on news about GWT.
 
I have found this video form Google I/O 13 which talks about the future of GWT.
First these are good news in a sense that now we see real actions that the  GWT steering committee are going to do. include next releases dates. 
 
The Highlights that i think are interesting:
by olga
tags:
border:

 Usually we want to use our model classes inside of the GWT project. But it is impossible without additional configuration of a model package.

 

The first step is to add file model.gwt.xml to the model package for conversion of the regular java package to the GWT module.

 

model.gwt.xml :

<module>
	<inherits name='com.google.gwt.user.User' />

	<source path="model"></source>
</module>

 

by sefi
tags:
border:

Hi, Recently I gave a GWT overview lecture for Tikal internal crowd. This made me look for guidelines on how to create a presentation that is both informative and interesting to hear. Sure, it depends on the content – that is a given. But it seems there are good and bad ways to create a presentation. [...]

by sefi
border:

  Hello again!

 

This will be part 6 of the series, you can check out the previous ones here.

 

Today, we'll discuss View-Presenter communication (events and other alternatives).

I'll be comparing Flex implementation for PureMVC vs. GWTP View-Presenter paradigms.

 

by sefi
tags:
border:

Hey! Last time, we talked about I18N and as promised, this time we’ll discuss CSS handling. Since you can’t really talk about CSS without talking about images, we’ll also mention them as well. Well, as seasoned Flex devs, you know that using CSS in Flex is a brease. You just slap the style tag in [...]

by sefi
border:

 Hey!

 

Last time, we talked about I18N and as promised, this time we'll discuss CSS handling.

Since you can't really talk about CSS without talking about images, we'll also mention them as well.

by sefi
tags:
border:

Hello again, This time I want to talk about localization (a.k.a. i18n). As Flex developers, as I assume you already know, all you have to do is create a *.properties file (say Messages.properties) and in it define keys with localized values, like: Then, in the main application mxml, you would define the resource bundles: And [...]

by sefi
border:

Hello again,

 

This time I want to talk about localization (a.k.a. i18n).

As Flex developers, as I assume you already know, all you have to do is create a *.properties file (say Messages.properties) and in it define keys with localized values, like:

columnHeaderName=Name

 

Then, in the main application mxml, you would define the resource bundles:

	<mx:Metadata>
		[ResourceBundle("Messages")]
	</mx:Metadata>

 

And basically you're done. All you need to do to use it, is use the ResourceManager class to access the localized value of the key.

Simple stuff, right?

 

Not so with GWT...

by ittayd
tags:
border:

A good list of pros and cons about GWT. Well thought of

by sefi
tags:
border:

First, a small update: Those who read my last post, here, know that I was planning to use MVP with gwt-dispatch. Well, at the time, GWTP seemed like an overhead and it included a fork of gwt-dispatch anyway so I thought MVP with gwt-dispatch would be lightweight and straight forward. But, it seems GWTP has a [...]

Pages