I wrote some articles on the subject :
http://ronanquillevere.github.io/2013/03/03/activities-places-intro.html
I also tried to implement Thomas Broyer's idea to solve the nesting
activities problem: http://blog.ltgt.net/gwt-21-activities-nesting-yagni/ so
I created a Github project, have a
On Wednesday, September 24, 2014 11:39:50 AM UTC-5, Jens wrote:
Please don't take me offensive.
Quite the opposite. You seem defensive.
I would be happy to improve the documentation if I knew what I was talking
about. I'm a GWT newbie, so all I have are questions. My biggest question
On Wednesday, September 24, 2014 9:45:43 AM UTC-5, Joseph Lust wrote:
There are various ways to place links in UiBinder based UI's. The most
basic of these is to simply generate the UI and set the href property of
your target element. Static URL's can be directly inserted in the XML using
That's because they don't use Places, so they don't NEED a colon. GWT is a set
of tools (hence toolkit) that work well together, but each has its purpose,
and should IMO be learned separately before being used together.
BTW, when using Places, you can do better with a widget that calls
My biggest question is where do I find better documentation, because the
documentation provided at gwtproject.org is incomplete and inconsistent.
It may seem sufficient to someone who already knows GWT, but trust me, it
doesn't provide a good introduction.
That is sad to hear :( For
On Monday, September 22, 2014 8:58:43 AM UTC-5, Jens wrote:
Actually everything you have asked is covered in
http://www.gwtproject.org/doc/latest/DevGuideMvpActivitiesAndPlaces.html
- The URL representation of a Place is described in Places section
(Prefix + : + token)
- The @Prefix
There are various ways to place links in UiBinder based UI's. The most
basic of these is to simply generate the UI and set the href property of
your target element. Static URL's can be directly inserted in the XML using
ui:with ... / as covered in the documentation
For more control of the PlaceHistoryMapper, you can use the @Prefix
annotation on a PlaceTokenizer to change the first part of the URL
associated with the Place. For even more control, you can instead implement
PlaceHistoryMapperWithFactory and provide a TokenizerFactory that, in turn,
Is there a good document that explain all of this? How do new GWT
developers learn these things?
On Friday, September 19, 2014 5:49:19 PM UTC-5, Jens wrote:
In general the hash fragment the GWT places framework generates consists
of two parts: a unique prefix that represents the place type
See http://blog.ltgt.net/gwt-21-places/
On 22 September 2014 10:28, ehod...@usdataworks.com wrote:
Is there a good document that explain all of this? How do new GWT
developers learn these things?
On Friday, September 19, 2014 5:49:19 PM UTC-5, Jens wrote:
In general the hash fragment the
Is there a good document that explain all of this? How do new GWT
developers learn these things?
Actually everything you have asked is covered
in http://www.gwtproject.org/doc/latest/DevGuideMvpActivitiesAndPlaces.html
- The URL representation of a Place is described in Places section
I'm writing a GWT app and trying to make Hyperlink widgets work. I've read
http://www.gwtproject.org/doc/latest/DevGuideMvpActivitiesAndPlaces.html and
some of the API docs, but it doesn't seem coherent.
For instance, that web page says I can use an @Prefix annotation on a
PlaceTokenizer to
In general the hash fragment the GWT places framework generates consists of
two parts: a unique prefix that represents the place type and a token that
contains the serialized state of a place instance. Both are separated by a
colon.
You can use @Prefix to change the default unique prefix of a
13 matches
Mail list logo
