Skip to content
This repository has been archived by the owner on Aug 5, 2019. It is now read-only.

GWT Activities is useless in those archetypes #5

Open
tbroyer opened this issue Aug 6, 2016 · 1 comment
Open

GWT Activities is useless in those archetypes #5

tbroyer opened this issue Aug 6, 2016 · 1 comment

Comments

@tbroyer
Copy link

tbroyer commented Aug 6, 2016

There's only one activity in the code, that does all the entry-point is supposed to do; so the ActivityManager and ActivityMapper add unnecessary complexity. The entry-point could use a PlaceChangeEvent.Handler to the same effect.

Using GWT Activities here would make one activity per "menu item" (and given the page layout, that'd be one activity per place –generally speaking, there are more activities than places in a project). I'm really not sure how well that'd play with the Iron elements though…

@zak905
Copy link
Member

zak905 commented Aug 6, 2016

I understand your point. I have already tried having one activity per menu item, but it triggers a weird behavior. As you keep on going from one menu item to another, the UI crashes, I am not sure why. I can create a branch for that, if you want to give it a try.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants