Re: design pattern for common functionality between Activities

2010-11-22 Thread koma
No, places and activities are orthogonal to each other a webpage consists of many display regions every display region is managed by a activity manager when a place change occurs, the activity managers are notified and they decide the activity to live inside the display region I tried to explain

Re: design pattern for common functionality between Activities

2010-11-22 Thread tastic
I think that is my entire problem. If I create an AppActivity, I am also creating an AppPlace and trying to tie the two together. Is the relationship between Activity and Place a one to one? On Nov 22, 2:11 pm, koma wrote: > Not really, but it is not that hard to modify HelloMVP to make it > work

Re: design pattern for common functionality between Activities

2010-11-22 Thread koma
Not really, but it is not that hard to modify HelloMVP to make it work. Actually HelloMVP is a really confusing example, because - the activities are called HelloActivity and GoodbyeActivity - the places are called HelloPlace and GoodbyePlace but the activities and places are orthogonal to each

Re: design pattern for common functionality between Activities

2010-11-22 Thread tastic
does anyone have a working example of say, the HelloMVP with activities managing different display regions On Nov 19, 5:30 pm, Marcin Misiewicz wrote: > And you are definitely right. > > On Nov 19, 8:05 pm, koma wrote: > > > > > How I understand things, a display region is a dynamic part of a >

Re: design pattern for common functionality between Activities

2010-11-19 Thread Marcin Misiewicz
And you are definitely right. On Nov 19, 8:05 pm, koma wrote: > How I understand things, a display region is a dynamic part of a > webpage; > > Depending on the place you're at, a display region is populated with a > specific activity. > A activity manager is the manager of a display region and d

Re: design pattern for common functionality between Activities

2010-11-19 Thread koma
How I understand things, a display region is a dynamic part of a webpage; Depending on the place you're at, a display region is populated with a specific activity. A activity manager is the manager of a display region and decides the right activity to show up for a given display region when a cert

Re: design pattern for common functionality between Activities

2010-11-19 Thread tastic
Is each display region the entire group of things, or are we saying that a display region is something like the header of the page with a menu or the footer of the page with links? If each display region is the entire group, then I understand the concept of going to a new place for each, which ulti

Re: design pattern for common functionality between Activities

2010-11-19 Thread Thomas Broyer
On 19 nov, 07:03, tastic wrote: > I have been reading Thomas Broyer's blog now for a full day and am > still having an issue with loading my application. Attached it the > EntryPoint. If you can tell me what I might be doing wrong that would > be awesome. No where you add the different SimplePa

Re: design pattern for common functionality between Activities

2010-11-19 Thread tastic
I have been reading Thomas Broyer's blog now for a full day and am still having an issue with loading my application. Attached it the EntryPoint. If you can tell me what I might be doing wrong that would be awesome. public class Library implements EntryPoint { Logger logger = Logger.getLog

Re: design pattern for common functionality between Activities

2010-11-18 Thread Nicolas Antoniazzi
Hello Koen, I never used Requestfactory so I do not know if it is similar to RPC. In my case, all my RPC Services can send a ServiceRemoteException (declared in Services interfaces). (ServiceRemoteException is a custom exception that I extended for my needs) @RemoteServiceRelativePath("GWT.rpc")

Re: design pattern for common functionality between Activities

2010-11-17 Thread koma
hi Nicolas & others, I understand how you work with the dynamic hosted page, but how do you throw the remote exception like you describe here : On server side, I use a security framework that check permission on rpc call. If user is not logged in (session has expired) but want to access to a "sec

Re: design pattern for common functionality between Activities

2010-11-12 Thread koma
I think i start to understand, after reading the blog posts from Thomas Broyer here: http://tbroyer.posterous.com/gwt-21-activities-nesting-yagni and the other posts in this series Looking at a host page, you can identify different display areas. Every "dynamic" area - not the static part of the h

Re: design pattern for common functionality between Activities

2010-11-08 Thread Nicolas Antoniazzi
I can give you what I did in my application. Maybe that you will prefer this method : * When the application loads, the server store a login/logout status of the user in a json format (just for optimization like this : http://code.google.com/intl/fr/webtoolkit/articles/dynamic_host_page.html. You

design pattern for common functionality between Activities

2010-11-08 Thread koma
Hi GWT gurus, Learning the new GWT 2.1 framework and I got security up&running on my GAE application. Now working with the new Activities/Places. My applicaiton will have a login/logout link in the top right of the website/app. How do I keep this link in sync with the security status of the curr