3, 8:55 am, David Peterson wrote:
> Hey ClusterCougar,
>
> I think your implementation is over-complicated. On the client side,
> just stick to two basic interfaces (and concrete implementations there-
> of) - Action and Result (I'm using 'Result' rather than 'R
In my Display interface, I included a method like
Widget getWidgetView();
which (interestingly enough) returns a widget view of the display
object. this eliminates your casting problem, while still maintaining
a degree of anonymity for the Display interface.
On the command pattern thing, I crea
I thought I posted this last night, but I don't see it. Apologies if
this is a dupe.
I've tried to implement the command pattern using generics, but have
some hangups. You can see my code at
http://code.google.com/p/gwt-command-pattern/
Hangups:
1) Too many parameters. It's just not pretty
2)
Yes, it's possible, and even documented :)
http://code.google.com/webtoolkit/tutorials/1.6/JSON.html
On Jun 24, 5:57 am, Portal Developer
wrote:
> Apologies for posting this again, I posted this already but I don't
> see it appearing on the list, might be due to it being moderated.
>
> Hi,
> Is
+1 to the "@JavaOnly" annotation
On Jun 22, 4:57 pm, Tom Sorgie wrote:
> I've been thinking the same thing, but taking it from a reverse
> perspective. In fact i just posted a question about being able to use
> the @GWTCompatible annotation to get reuse out of server code. I
> didn't really co
The reason this is a low priority for the GWT team is because
reflection goes against the "spirit" of GWT. It introduces a lot of
problems that are difficult to deal with in a fashion that would
result in speedy client-side code. My suggestion would be to work
around it, but if you would like help
Not really. The EntryPoint class is not really a class, but a script
that is run to bootstrap your application. Any other use of the
EntryPoint is a little bit of an abuse of the concept. It is possible
to provide a global point of access to the EntryPoint using the
Singleton pattern, but global v
Some things I'm not clear on from your post:
1) Did you inherit the commons module in each of your *.gwt.xml files?
2) When you did the jar packaging, did you include the java source for
the client-side?
3) Are your public resources (i.e. CSS) located in a ".../moduleName/
public/" folder? Were t
Very cool. might want to make an expandable panel as a "toolbox". That
seems to be a pretty standard analogy in diagramming tools. Do you
have a roadmap/design for server-side? are you thinking you'll do a
persistence framework or filesystem storage (i.e. xml)?
On Jun 15, 3:43 am, walterc wrote:
