search

neo09 / gwt-platform

Automatically exported from code.google.com/p/gwt-platform
0 stars 0 forks source link

Consider a many-to-many relationship between name tokens and presenters #78

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Right now, the relationship between presenters and name tokens is one-to-
one. That is, a given name token can only be attached to one presenter, and 
a presenter can only have one name token.

A many-to-one relationship (many presenters share the same name token) 
could be a nice way to simultaneously reveal many presenters given a single 
place request.

A one-to-many relationship (one presenter has many name tokens) could be a 
nice way for a side-presenter to reveal itself under a number of different 
place requests.

A many-to-many relationship would have both these advantages.

The many-to-one is probably easy to support (although we could not 
guarantee the order in which the presenters are revealed).

A nice way to support the one-to-many would be to allow for regexp in name 
tokens.

Original issue reported on code.google.com by philippe.beaudoin on 30 Apr 2010 at 5:35

GoogleCodeExporter commented 9 years ago 
Question to consider: how are place request parsed/prepared with such 
relationships? 
i.e. How should prepareFromRequest and prepareRequest work?

Original comment by philippe.beaudoin on 30 Apr 2010 at 5:38

GoogleCodeExporter commented 9 years ago 
Something to consider: As we allow many name tokens per presenter, it could 
make sense 
to have non-singleton presenters (one per name token).

This is discussed here:
http://groups.google.com/group/gwt-platform/browse_thread/thread/689ac639ff46bb4
e

Original comment by philippe.beaudoin on 22 May 2010 at 4:41

GoogleCodeExporter commented 9 years ago

Original comment by philippe.beaudoin on 22 Sep 2010 at 1:35

GoogleCodeExporter commented 9 years ago 
And about dynamic name tokens... 
for example: /#!username
just like twitter do...

is it possible? actually, I do a workaround in revealErrorPlace for this and it 
almost work.. is just a very ugly code.

I think it could be a nice feature...

Original comment by caarlos0 on 10 Nov 2011 at 10:29

GoogleCodeExporter commented 9 years ago 
It is possible to do! :D You only have to create your own Proxy instead of
creating it with @NameToken and  @ProxyStandard.

Original comment by goudreau...@gmail.com on 10 Nov 2011 at 12:17

GoogleCodeExporter commented 9 years ago 
Could you please elaborate on creating your own Proxy instead of using the 
annotations?

Thanks,
Maurice

Original comment by maurice....@gmail.com on 20 Dec 2011 at 12:06