EnumValidator + move to jdk 1.5 (!)

[Franck Routier]

Hi all,

I just commited a new form validator called EnumValidator, that
validates against, well, an enum: it will check the element value is one
of the enum constants string representation.

I also changed build.source and build.target to 1.5 in
sample.build.properties to allow the use of 1.5 idiom, as discussed on
the list at the beginning of this year (see
http://mail-archive.ow2.org/barracuda/2007-02/msg00024.html )

Hope this will initiate a move to a future release. I plan to add a few
features soon regarding form / components glue layer.

I am also currently playing with jquery ajax library. Anyone has
comments on this ? Maybe it could be integrated in some way with
barracuda ??

Franck




--
Barracuda mailing list
Barracuda@...
http://www.ow2.org/wws/lists/projects/barracuda

[Diez B. Roggisch]

On Wednesday 14 November 2007 17:52:53 Franck Routier wrote:

> Hi all,
>
> I just commited a new form validator called EnumValidator, that
> validates against, well, an enum: it will check the element value is one
> of the enum constants string representation.
>
> I also changed build.source and build.target to 1.5 in
> sample.build.properties to allow the use of 1.5 idiom, as discussed on
> the list at the beginning of this year (see
> http://mail-archive.ow2.org/barracuda/2007-02/msg00024.html )
>
> Hope this will initiate a move to a future release. I plan to add a few
> features soon regarding form / components glue layer.
>
> I am also currently playing with jquery ajax library. Anyone has
> comments on this ? Maybe it could be integrated in some way with
> barracuda ??

I've personally not dabbled with JQuery, but friends of mine
(http://www.soundcloud.com/) totally love it. My tool of choice right now is
MochiKit, in SVN trunk version - which might or might not be released soon,
and unfortunately seems to be declining in adoption. So using jQuery seems a
good idea.

I can't promise that I be able to work much on a new/enhanced barracuda, let
alone work with it - as I'm actually trying to move away from Java :)

But as I work with TurboGears, a python-web-framework I pretty much like, I
might have some suggestions that are interesting.

TG uses several templating engines, of which at least two - KID & genshi - are
very, very similar to what the XMLC/BTemplate approach in Barracuda is, and I
loved the approach back then, and still do.

And what it makes me really like TG is it's widget-system. Essentially, a
widget isn't much more than a bundling of HTML, CSS, JS into one functional
unit. It can be reused, customized via CSS or even HTML, subclassed and so
forth.

All one has to do to use it is to

 - return it from a controller method (the equivalence of a EventListener)

 - call ${widget.display()} in the surrounding template.

This will ensure that

 - the widgets statics are included on top of the page

 - the dynamic parts are rendered at the place in the page

I think this would match very well with B's component approach.

Well, just some thoughts. I would love to see barracuda gain more momentum
again, but I fear I can't be to much of help there :(

Diez


--
Barracuda mailing list
Barracuda@...
http://www.ow2.org/wws/lists/projects/barracuda

[Franck Routier]

Hi Diez,

Every ideas are much welcome !

Mochikit seems interesting indeed (and quite similar to jquery ?)... I
must have a look on it.

Regarding 'Widgets' in Barracuda, I think we made a progress in this
direction with nested components at the beginning of the year. It really
is the purpose of it : provide a widget component (like
BCalendarField, ...). A plus is also that it could know about forms for
repopulation / error, like you did in your contrib package (I already
commited some stuff in trunk, namely the ExtendedComponenet interface,
but I really need to come with docs and examples...).

Moreover, I am working on a BTree component that would render as plain
UL and could embedded the necessary BScript to display as a nice
collspable tree...
I did not think about css... At first, I simply was thinking of using
well known class names, a let the designer put the necessary css... But
we could certainly take the same approch as with javascripts and create
a component similar to BScriptResource (or event the same one)...
I must experiment a bit.

Franck

Le jeudi 15 novembre 2007 à 11:28 +0100, Diez B. Roggisch a écrit :

> On Wednesday 14 November 2007 17:52:53 Franck Routier wrote:
> > Hi all,
> >
> > I just commited a new form validator called EnumValidator, that
> > validates against, well, an enum: it will check the element value is one
> > of the enum constants string representation.
> >
> > I also changed build.source and build.target to 1.5 in
> > sample.build.properties to allow the use of 1.5 idiom, as discussed on
> > the list at the beginning of this year (see
> > http://mail-archive.ow2.org/barracuda/2007-02/msg00024.html )
> >
> > Hope this will initiate a move to a future release. I plan to add a few
> > features soon regarding form / components glue layer.
> >
> > I am also currently playing with jquery ajax library. Anyone has
> > comments on this ? Maybe it could be integrated in some way with
> > barracuda ??
>
> I've personally not dabbled with JQuery, but friends of mine
> (http://www.soundcloud.com/) totally love it. My tool of choice right now is
> MochiKit, in SVN trunk version - which might or might not be released soon,
> and unfortunately seems to be declining in adoption. So using jQuery seems a
> good idea.
>
> I can't promise that I be able to work much on a new/enhanced barracuda, let
> alone work with it - as I'm actually trying to move away from Java :)
>
> But as I work with TurboGears, a python-web-framework I pretty much like, I
> might have some suggestions that are interesting.
>
> TG uses several templating engines, of which at least two - KID & genshi - are
> very, very similar to what the XMLC/BTemplate approach in Barracuda is, and I
> loved the approach back then, and still do.
>
> And what it makes me really like TG is it's widget-system. Essentially, a
> widget isn't much more than a bundling of HTML, CSS, JS into one functional
> unit. It can be reused, customized via CSS or even HTML, subclassed and so
> forth.
>
> All one has to do to use it is to
>
>  - return it from a controller method (the equivalence of a EventListener)
>
>  - call ${widget.display()} in the surrounding template.
>
> This will ensure that
>
>  - the widgets statics are included on top of the page
>
>  - the dynamic parts are rendered at the place in the page
>
> I think this would match very well with B's component approach.
>
> Well, just some thoughts. I would love to see barracuda gain more momentum
> again, but I fear I can't be to much of help there :(
>
> Diez
> pièce jointe document plein texte (message-footer.txt)
> --
> Barracuda mailing list
> Barracuda@...
> http://www.ow2.org/wws/lists/projects/barracuda

--

Franck Routier
Axège Sarl - 23, rue Saint-Simon, 63000 Clermont-Ferrand (FR)
Tél : [phone]
mèl : franck.routier@...




--
Barracuda mailing list
Barracuda@...
http://www.ow2.org/wws/lists/projects/barracuda