I can't tell how disappointed I am.
Yep, me too. Yet more time spent futzing around trying to keep my src
tree clean.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this
Hi all,
I've been watching some of the Google IO presentations and have been
learning a lot. One thing I'm missing from my Swing background is a
nice PresentationModel/ValueModel framework (ala JGoodies binding and
SpringRichClient forms). ValueModels can do some pretty cool things
using
The formatting of the post was pretty unreadable so I've copied it
into a google document with some formatting which you can view at:
http://docs.google.com/View?id=dm73tfj_55dqrkpwgx
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Hi there, thanks for your compliments about pectin.
Just as a matter of interest I've started talking with the author of
Bindgen (http://bindgen.org/) about the possibilities of using it with
pectin and things are looking promising. If we can get it working (and
I think we can) you'll be able to
Hi all,
Pectin is an open source form binding and validation framework for
GWT. Version 0.5 has just been released with various fixes and
enhancements (see the release notes for details:
http://code.google.com/p/gwt-pectin/wiki/ReleaseNotes).
There's also a page discussing MVP and Presentation
Hi there,
Like many others I'm looking forward to see what you guys come up with
in the databinding area. But I miss some of the PresentationModel/
ValueModel style frameworks I've come to like in Swing and thought I'd
put in my 2c worth on a basic approach/API that would make me a happy
Howdy,
The main issue I have with your proposal is that I have to define a
second definition of my model (the bean).
While that's a pain it's also deliberate since I'm binding to DTO's
and other domain level objects and these don't (and shouldn't IMHO)
define form based state (such as
I've updated the document on PresentationModel thoughts with
experiences from an initial prototype. On the whole the guice style
builder approach has been very nice and significantly reduces the
effort in learning and remembering the api.
You can read it at:
Howdy,
Is there any plan to upload 1.7 to a public maven repository?
Cheers
Andrew
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
Excellent, thanks for that.
Cheers
On Jul 15, 4:43 pm, nicolas de loof nicolas.del...@gmail.com wrote:
I'm back from holliday and will publish it ASAP
cheers,
Nicolas
2009/7/15 Andrew Pietsch andrew.piet...@gmail.com
Howdy,
Is there any plan to upload 1.7 to a public maven
Hi all,
I've just uploaded a new prototype Form/Binding library based on
PresentationModel/ValueModel pattern. It uses a builder style api
inspired by Guice.
It also support plugins for extending the functionality of the core
framework. Currently there's a metadata plugin and a validation
!
On Aug 13, 9:50 am, Andrew Pietsch andrew.piet...@gmail.com wrote:
Hi all,
I've just uploaded a new prototype Form/Binding library based on
PresentationModel/ValueModel pattern. It uses a builder style api
inspired by Guice.
It also support plugins for extending the functionality
I guess verbosity is somewhat in the eye of the beholder -I would have
thought that watermark(myField).withValueOf(anotherField) was pretty
concise for a dynamic watermark (c;
Pectin came out of developing large scale Swing applications with
highly demanding UX/UI requirements (in the banking
Hi all,
Pectin 0.8 has finally been released and contains quite a number of
additions and improvements. Most notably the new release includes:
* Binders now works on any Value/ListModel and not just with
FormModels.
E.g. binder.bind(MutalbeValueModelT).to(HasValueT) // or
to(ValueTargetT) or
this be?
CheckBox cb = new CheckBox();
cb.setValue(null);
assertFalse(cb.getValue());
rjrjr
On Thu, Aug 26, 2010 at 5:57 PM, Andrew Pietsch
andrew.piet...@gmail.comwrote:
I personally would like to see it support null, not because null is a
valid UI state but just to be consistent
Yep, given that and the `if (cb.getValue)` mentioned by Paul returning
null wouldn't be good. Returning false would be fine with me in this
case. I presume the ValueChangeEvent would use false and not null?
Cheers
Andrew
On Aug 27, 7:27 pm, Thomas Broyer t.bro...@gmail.com wrote:
On 27 août,
16 matches
Mail list logo
