I know it might be an old topic, but I have tried to implement thomas idea (
http://tbroyer.posterous.com/gwt-21-activities-nesting-yagni ) in teh
following github project. I will be happy to have some comments/suggestions.
https://github.com/ronanquillevere/GWT-Multi-Activities
Regards
On Frid
First of all, thanks to everyone who contributed to this thread and
many thanks to folks who contributed to GWT!
Just wanted to comment on activities/view/presenters:
I actually like it that there is a separate concept of an activity
because it directly corresponds to user activity. Activity is
Yep, it was a typo.
Thanks,
/dmc
On Mon, Nov 8, 2010 at 9:49 PM, zixzigma wrote:
> Hello David,
> looking at your example:
>
>> SimplePanel westWidget = new SimplePanel();
>
>
>> westActivityManager.setDisplay(westPanel);
>
> is this a typo ?
> should have been westActivityManager.set
Hello David,
looking at your example:
> SimplePanel westWidget = new SimplePanel();
> westActivityManager.setDisplay(westPanel);
is this a typo ?
should have been westActivityManager.setDisplay( westWidget ); ?
thank you
On Oct 29, 6:57 am, David Chandler wrote:
> Gene,
>
> Thank y
On 4 nov, 11:54, Nicolas Antoniazzi
wrote:
> Very interresting Thomas. It is similar in some ways to the gwt-presenter
> project.
>
> Just a question. You says that views are singleton. I understand the reason
> (efficiency). But does not it leads to UI state problems ?
> By instance, if you cal
Very interresting Thomas. It is similar in some ways to the gwt-presenter
project.
Just a question. You says that views are singleton. I understand the reason
(efficiency). But does not it leads to UI state problems ?
By instance, if you call a method on your view that adds a new css class to
an e
On 4 nov, 03:32, David Chandler wrote:
> Thanks for your thoughts, Nicolas. I believe the reason we've not
> created View and Presenter interfaces to date is because there are two
> different styles of MVP widely in use, only one of which allows the
> view to call the presenter as in your exampl
Thanks for your thoughts, Nicolas. I believe the reason we've not
created View and Presenter interfaces to date is because there are two
different styles of MVP widely in use, only one of which allows the
view to call the presenter as in your example. Which leaves us in the
funny position that the
>
> Thanks for your comments. Do you mind sharing with us what would go in
the Presenter interface to allow you to "fully use" MVP? We're very
much open to ideas from the community as to how to make it work
better.
Well, in my opinion, it would be clearer to create 2 new interfaces :
1) a "Pre
On 3 nov, 13:13, Nicolas ANTONIAZZI
wrote:
>
> I discovered with your great post that Activity were not necesserely
> Presenters. I think that I will have to think again about the concept behind
> activity because altough it seems simple, I think that I do not really get
> the advantages of usin
Hi Nicolas,
Thanks for your comments. Do you mind sharing with us what would go in
the Presenter interface to allow you to "fully use" MVP? We're very
much open to ideas from the community as to how to make it work
better.
Thank you,
/dmc
On Wed, Nov 3, 2010 at 8:13 AM, Nicolas ANTONIAZZI
wrote
Ok that's more clear now.
I totally agree that not all presenters have to be an activity.
Thus, there is something missing in the "MVP" class provided by GWT 2.1
since it does not allow us to fully use MVP in this case. It would be great
to get at least a tiny interface for this in future release
On 3 nov, 11:16, Nicolas ANTONIAZZI
wrote:
>
> Would not be easier to create a Presenter interface that provides a start()
> method, that would be extended by Activity ?
> Thus, it would clarify the concept : Activity interface is an overlayer of
> Presenter for Place management, and Presenter is
Hello,
I migrated all my code to GWT 2.1. I was a bit surprised to not find any
NestedPresenter helper. I created my "own" with an interface called
NestedPresenter that provides a "start(HasWidgets.ForIsWidget container);"
method.
I prefered doing it this way instead of using multiple ActivityMan
Hello David,
I am very excited about the GWT 2.1 release, and planning to use it
for a new upcoming project.
I have been following and studying the MVP for quite a while now and
experimenting with milestone releases.
Just wanted to share some of my thoughts:
I personally find the name "Activity
And if you think, as a lot of people seems to do, that nesting
presenters helps make your app cleaner, then you can look at MVP
solutions built on top of GWT that natively support presenter nesting
such as GWTP:
http://gwtplatform.com
Cheers,
Philippe
On Oct 29, 8:40 am, Thomas Broyer wrote:
On 29 oct, 06:52, DrG wrote:
> Hi,
>
> I have been reading the excellent article
> at:http://code.google.com/webtoolkit/doc/latest/DevGuideMvpActivitiesAnd...
>
> And love the new built in objects that facilitate the MVP design
> paradigm. My initial thought is great but how does this system c
Gene,
Thank you for your thoughtful questions. As you have observed,
Activities and Places do not directly support nesting, but there are a
couple different ways you can implement composite views:
1) An ActivityManager is responsible for swapping activities within
one container widget; however, y
Hi,
I have been reading the excellent article at:
http://code.google.com/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html
And love the new built in objects that facilitate the MVP design
paradigm. My initial thought is great but how does this system cope
with Nested Views or Dock Panel
19 matches
Mail list logo
