> > Is there an elegant solution to handle when a new release is
> > deployed while you are in the GWT app?
I thought through some of this awhile ago:
http://draconianoverlord.com/2010/07/07/gwt-seamless-upgrades.html
> IncompatibleRemoteServiceException for GWT-RPC for instance, which is used
> As an example: http://retina.teknonsys.com/
Also cool--thanks!
- Stephen
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send e
> This is more a reply to the linked blog entry but I'll post it here:
> I don't think supporting SASS in ClientBundle requires any change in
> GWT proper; you only need to use something other than CssResource
> (e.g. a SassResource interface) with its own ResourceGenerator
> (linked to the SassRe
> I have been using the cell widgets for a while now and am having
> trouble understanding their purpose.
Well, as you say, the purpose is performance.
> Thoughts?
Personally I avoid cell-based widgets until I really, really need them,
and then push back on putting anything in the cells except
> Is there a clean way to *not* require the user to refresh the page?
Everything Thomas said is right, and I'll chime in with my own experience.
Basically:
- If you use IsSerializable and no type-name elision you won't have to keep
old GWT RPC policy files around between builds (the legacy ser
Hi,
I've been working on a MVP framework that automates a lot of the
display/view aspects of MVP. It also includes some rich models (properties,
etc.) to do Backbone/etc.-style model/view bindings. The two make for a
fairly compelling setup, IMO.
Previously, the framework was called gwt-mpv, b
Hi Logan,
I was looking for the same thing just the other day and didn't find it
either. I don't currently need it right now, but was thinking it would be
nice to have.
If I was going to start out writing one, I would make a really simple usage
of the SimpleBeanEditorDriver, run GWT compile an
Hey,
The xtend language [1] had a new release last week; they purport to be a
"better Java" syntax but interestingly compile-down to Java source code,
not Java byte code. Which means something like GWT can read the .java files
and not care that the original language was not actually Java.
As m
> There are already a few actually:
> http://code.google.com/p/google-web-toolkit/issues/detail?id=3855
> http://code.google.com/p/google-web-toolkit/issues/detail?id=3369
Awesome, thanks, Thomas.
- Stephen
--
You received this message because you are subscribed to the Google Groups
"Google W
I think this is worth filing a bug about. If you could include a minimal
example that reproduces the problem, that would be helpful.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.
>
>
>>
> Not yet and therefore I'm asking those questions. Dart will be introduced
> on 10-12th Oct. during the GOTO Conference.
>
Yeah, I'm really looking forward to the Dart introduction--I wrote a bit
more in a blog post [1], but I think it has the potential to make GWT (or
GWT next-gen) ev
> gain, if anyone can summarize the necessary alternatives to the
> UiBinder content in MVP it would be a huge help.
You do everything the same, your presenter doesn't change, your
view/display interface doesn't change, you just create and wire your
widgets together manually in your view implemen
> We plan to introduce UiBinder for Cells in a future version of GWT,
> hopefully GWT 2.2.
Sweet!
I was mulling that the flyweight-ness of cells would allow them to be
used within the static/no-iteration nature of ui.xml files.
The current API seems like it might need to change though--take
Act
> My problem is that I am not being able to integrate gilead
> with gwt.
You might have better luck in the gilead forums:
http://noon.gilead.free.fr/gilead/index.php?page=support
- Stephen
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group
> Thanks, Stephen, but I am actually trying to find the names of the CSS
> selectors currently used by CellTable so that I can override them in my
> application's CSS files and/or in my uibinder xml files.
As Qian said, the css names are in the interface. See the ClientBundle
docs:
http://code.g
> Am I to conclude then that it is not possible to style a CellTable
> using CSS?
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/user/cellview/client/CellTable.Resources.html
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/user/cellview/client/Cel
> I completely agree with Thomas on this one.
Me too.
> I'd much prefer the GWT team to keep pumping out more function over form.
Agreed!
- Stephen
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to g
> Does anyone know if it is possible in UIBinder to set an id for
> resulting DOM element?
I wanted to do this as well when I started working with UIBinder, but
the feedback I got was that the GWT team thinks that setting ids inside
of ui.xml files is an anti-pattern.
Their reasoning is that, te
> On 10 nov, 18:35, Stephen Haberman wrote:
> > > In the current state, I honestly doubt that RequestFactory should
> > > be used in a productive environment, as it introduces really
> > > hard-to-overlook security problems.
> >
> > That was my impressio
> In the current state, I honestly doubt that RequestFactory should
> be used in a productive environment, as it introduces really
> hard-to-overlook security problems.
That was my impression was well. I agree it will be interesting to see
how, if at all, this gets addressed in future releases.
> Scenario: A user is running version n-1 of a gwt app. Meanwhile,
> version n is deployed. I assume the client will get RPC serialization
> exceptions. The user gets frustrated.
>
> What's the best way to address this?
If you use IsSerializable (and no type name elision), and don't have
any act
> It's an OK solution, but still a workaround because we don't have a
> Widget interface.
GWT 2.1 does have an IsWidget interface, if that is all that you need:
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/app/place/IsWidget.html
If you need more, I've been making int
> 1: Separate samples take more time to set up / install.
> 2: Separate samples take up more space in my window. If they're all
> part of one project, I can close that project, and they all
> disappear.
You can use either Eclipse working sets or a separate workspace if it
really bothers you.
>
> I'd like to use CompositeCell, but I'm having a hard time turning my
> list of individual Headers into a List> specifically because
> Header's valueUpdater is private.
I ended up with a workable CompositeHeader:
http://github.com/stephenh/gwt-mpv/blob/master/user/src/main/java/org/gwtmpv/widge
Hey,
Has anyone done composite headers with the new CellTable?
I'd like to use CompositeCell, but I'm having a hard time turning my
list of individual Headers into a List> specifically because
Header's valueUpdater is private.
If you look at HasCell, it exposes the it's FieldUpdater for the
comp
> The server is the only place where security can apply.
Very much agreed.
> But GWT is mainly a client side topic. Authentication based security
> or roles based security will never be a GWT (client) topic
Perhaps pre-2.1, yes, but the new RequestFactory, given it facilitates
client<->server d
Hi Shawn,
Thanks for the links.
Moving off JDO and Spring MVC (the web framework, not DI) seemed to be
the biggest startup time wins, which is in line with my assertion that
DI itself is not typically the bottleneck.
That being said, the streamhead link:
> http://www.streamhead.com/google-appen
> As DI requires additional cpu cycles to do its magic
I'd be interested to hear if you have any profiling results specifically
showing DI is responsible for the bad startup perf.
My assertion is that if you startup Hibernate + Wicket + whatever
without DI, just configuring them by hand, it will
> What scares you exactly?
Personally, I find the "open source, closed development" aspect of GWT
not necessarily scary, but definitely not as warm and fuzzy as Apache
model "open development" projects.
> AFAIK, RC1 is an API-freeze release;
An API freeze after, what, 1 maybe 2 people (you and
> public class GenericEvent extends GwtEvent {
This is very tangential, but all the talk about a generic event made
me think of a paper a colleague of mine linked me to about potential
design patterns for UI listeners in Scala:
http://lamp.epfl.ch/%7Eimaier/pub/DeprecatingObserversTR2010.pdf
Ag
> It is a bit of a nuisance maintaining two java files for each event.
I agree that GWT events involve a lot of boilerplate.
My approach was to write an annotation processor (native Eclipse/javac
support) where you just write a "spec":
@GenEvent
public class CalendarChangeRequestEventSpec {
D
Hi Sri,
Thanks for the reply.
> *IMHO, once you have deployed new code, you want to tell the users to
> refresh the browsers as soon as possible. Trying to get old clients working
> with new code can work at times; but since there is no guarantee I prefer to
> fail-fast.*
I think it depends. I a
Hi,
I've done some research about keeping GWT deployments as seamless as
possible for both new and old clients.
Basically avoiding (when possible) the LegacySerializationPolicy,
IncompatibleRemoteServiceException, type name elision, no RPC
whitelist, etc. errors that I had been seeing while deplo
I use this css hack:
.notclickable { cursor: default; user-select: none; -moz-user-select:
none; -webkit-user-select: none; }
Not sure where user-select is/is not supported, but it works in the
browsers I personally use. :-)
- Stephen
--
You received this message because you are subscribed to
> We do have views where we do not need an "asWidget" method: those that
> are actually DialogBox or similar and therefore just have show/hide
> methods.
Ah, sure, I didn't think of that; I'm using DialogBox as well. Even
without an explicitly-needed "asWidget" method, it's still Widget-
based,
Hi,
Just curious, is anyone doing non-Widget views in an MVP app?
Coming from gwt-presenter, it has a Display and WidgetDisplay, where
WidgetDisplay has a Widget asWidget method, but Display doesn't (the
idea being Display is not tied to Widget, I guess).
However, I only use WidgetDisplay. Given
> http://code.google.com/p/handlebars/
Spiffy. The page mentions using Eclipse code generation--I like that.
What sort of files are you generating?
- Stephen
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send em
> There are classes that have all these (Label is what I intend to use), but no
> shared interface implementing all.
I wanted shared interfaces too--e.g. IsLabel that unites all of
Label's HasText/etc. interfaces.
I mentioned it in this thread:
http://groups.google.com/group/google-web-toolkit
> I like the model-view-presenter architecture. However I am not at all
> sold on mocking out the view and testing just the presenter. The
> problems is that you are not testing 3 of the potentially most error
> prone parts of the system: 1) The browser and DOM, 2) The GWT widget
> library and 3)
> You wouldn't have a MyView.fooAnchor() getter but a
> MyView.setFooAnchorTarget(String) setter.
Yes, I understand that is how you're supposed to do things now. I'm
saying its annoying to re-type so much boilerplate presenter <->
widget abstraction code into every view in an app.
With IsXxx int
> Or you could use a "delegate", as enlightened in the GWT MVP tutorial
> Part II published earlier this
> week:http://code.google.com/webtoolkit/articles/mvp-architecture-2.html
> (the Presenter interface).
Hm? I'm not seeing how a Presenter interface would let my presenter
call, say, the Ancho
Hi,
I've been doing GWT MVP development lately and, while the HasText,
HasValue, etc. interfaces are nice and facilitate mocking/stubbing
out views, I'm wondering why GWT doesn't go further and add per-widget
interfaces.
For example, if I have a TextBox that I want to both listen for clicks
and s
Using gwt2, I've started getting intermittent stack traces in
JsValueGlue. E.g.:
00:02:18.702 [ERROR] Uncaught exception escaped
java.lang.IllegalArgumentException: Something other than a Java object
was returned from JSNI method
'@com.google.gwt.dom.client.DOMImplMozilla::getInnerText(Lcom/google
Hi,
I'm working with UiBinder to massage designer-created HTML into a GWT
app. It seems like this could be really slick.
The biggest hurdle so far is that the designer's css has a lot of
"#element-id" declarations, which leads to two irritations:
1) Dashes are not a valid java identifier, so I
44 matches
Mail list logo
