hi nille, thanks a lot for your information.
anyone know about question no.1 ? I use it in a change password page.
Now I'm using the java class of tapestry page to write the validation
of this variables.
Cheers
Abangkis
On Mon, Feb 2, 2009 at 6:52 AM, nillehammer
wrote:
> Hi Abangkis,
> I am
You'd probably want to use the option to move the
Out of curiosity, has anyone that's claimed it's trivial to get jQuery
working in Tapestry actually tried it?
IIRC, I ran into a bunch of issues with the load order of JS files. I
think it had to do with Tapestry placing include lines at the bottom
of the DOM but my document ready listener appear
Hi Abangkis,
I am not familiar with versions of Tapestry prior to 5.0. So I cannot
answer your first question. Your second one is explained on the
following page:
http://tapestry.apache.org/tapestry5/guide/pagenav.html
Scroll to the middle of that page the section named "Page Render
Requests". In a
Em Sun, 01 Feb 2009 15:45:49 -0300, Borut Bolčina
escreveu:
IMHO creating more "high level" components and better documentation are
the things to spend time on, if not even crucial and certainly not
switching JS library just after the framework was released.
I agree 100%, as you can easi
Ditto from me.
Geoff
On 02/02/2009, at 5:45 AM, Borut Bolčina wrote:
IMHO creating more "high level" components and better documentation
are the
things to spend time on, if not even crucial and certainly not
switching JS
library just after the framework was released.
Regards,
Borut
2009/
Borut Bolčina wrote:
Hello,
nice work. I was looking at the compponents you have made and the TextField
(http://equanda.org/equanda-tapestry5/textfield.html) seems somethink like I
will need shortly. The docs says: "When the value in the text field changes,
the zone will be updated...", but that
IMHO creating more "high level" components and better documentation are the
things to spend time on, if not even crucial and certainly not switching JS
library just after the framework was released.
Regards,
Borut
2009/2/1
> > Whether or not one "likes" jQuery or not isn't the point. Tapestry i
Chris, you're the man ;-)
2009/1/31 Chris Lewis
> Whether or not one "likes" jQuery or not isn't the point. Tapestry is built
> with prototype, and it works. That's the point. Were it built with jQuery, I
> would have raised the same question if the suggestion of switching to
> prototype had bee
> Whether or not one "likes" jQuery or not isn't the point. Tapestry is
> built with prototype, and it works. That's the point. Were it built with
> jQuery, I would have raised the same question if the suggestion of
> switching to prototype had been brought up. It's not my preference
> that's behin
On Sun, Feb 1, 2009 at 5:31 AM, manuel aldana wrote:
> yes, that was the only point I would moan about ;)
>
> I once analyzed the package layout (from 5.0.18):
> http://aldana-online.de/screenshots/packageOverview.png
>
> You mean with 'left the barn', that you are package refactoring for 5.1.0?
yes, that was the only point I would moan about ;)
I once analyzed the package layout (from 5.0.18):
http://aldana-online.de/screenshots/packageOverview.png
You mean with 'left the barn', that you are package refactoring for 5.1.0?
Howard Lewis Ship schrieb:
Thanks. Having your dirty laundr
12 matches
Mail list logo
