Looks like I'm going to have to eat my hat on this one:
http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/57cae16478971519
It's a proposal to change Activity from an interface to an abstract class...
basically removing the Activity interface and renaming the exis
For anybody considering GWTP (http://gwtplatform.com) as an
alternative to GWT MVP, I want to stress out the fact that, despite
the differences, there are a lot of similarity in the spirit of these
two libraries. For example, gwtplatform's proxies are very similar to
GWT's Activities. The place sys
and what if data from one workspace is used in another ?
In my opionion for this point you could fire a specific event, because, if
data inside a workspace is needed by another one, this means user did
something or a generic condition about displayed data happened. Am I wrong?
--
You received
I am in the similar situation as zixzigma.
one of Thomas Broyer ideas,
>> make each "workspace" it's own GWT app (if they're sufficiently
>>different to deserve it)
could you please explain how this would be possible ?
by breaking the project into modules and use multiple entry points ?
and what
Spot on, Brian.
The kinds of changes to Activities and Places we're contemplating for
future versions of GWT are primarily along the lines of using
annotations and generators to automate the creation of PlaceTokenizers
and ActivityMappers, for example. We're not talking about wholesale
replacement
There's a difference between "experimental" and "immature". I don't think
Activities and Places are experimental. They are building blocks upon which
more functionality can be built. While there may be bigger plans for future
versions of GWT, I'm glad that we have this much to work with sooner rath
Thank you everyone for your wonderful insights.
You provided very helpful suggestions and invaluable solutions to deal
with the problem i described.
I was going to implement some of the solutions offered, but this
comment by Ray Ryan,
got me very worried and kind of put me off.
"The activity and
In my opionion if you release a functionality and tell people "it's better
if you use it", you have to be aware of impacts this new functionality can
have on existing code.
In my opinion use of DockLayout or TabLayout / Panes is not a rare use case,
think about a mail reader.
MVP approach is very g
I think in the case of the composite activity / composite place, you
need to define how closely realted each workspace will be. will there
be any overlap between sub/areas of one workspace and a different
workspace?
You can be careful about how you craft your composite place and how
you tokenize i
Another option would be to look at a 3rd party framework. As Thomas pointed
out, the GWT team isn't trying to address every use case, and that's where
pulling in other frameworks can help. There's no shame in recognizing that
you have a complex use case and using any tools available to help. I have
On 29 nov, 23:44, zixzigma wrote:
> the article also argued, that having the same size/fixed regions leads
> to consistent layout.
>
> in the case of Fixed "WIDTH", that is true.
>
> but if your regions have sub-regions, the sizing is no longer the
> Width, but rather the HEIGHT.
>
> our WEST re
On 30 nov, 06:28, zixzigma wrote:
> Thank you for your comments.
>
> >>So you would have one main activity for each major area with one view
> >>and could have multiple widgets that accomplish what your individual
> >>activities could?
>
> I had thought about this, but my concern is by doing so,
Thank you for your comments.
>>So you would have one main activity for each major area with one view
>>and could have multiple widgets that accomplish what your individual
>>activities could?
I had thought about this, but my concern is by doing so, we lose the
navigation/history/bookmarking.
in
Do you need to think of each area on the left and right as independent
activities? can you, instead, create just one area for the left and
have it be made of multiple widgets. So instead of having a full
activity, you create each box area as it's own widget?
So you would have one main activity for
the article also argued, that having the same size/fixed regions leads
to consistent layout.
in the case of Fixed "WIDTH", that is true.
but if your regions have sub-regions, the sizing is no longer the
Width, but rather the HEIGHT.
our WEST region, can have WEST_NORTH, WEST_MAIN, WEST_SOUTH,
an
15 matches
Mail list logo
