hiago H. de Paula Figueiredo wrote:
>>>
>>> Em Tue, 24 Jun 2008 14:32:15 -0300, Matt Kerr <[EMAIL PROTECTED]>
>>> escreveu:
>>>
>>>> why not specify whether params allow null - rather than break things ?
>>>> default to the old behav
why not specify whether params allow null - rather than break things ?
default to the old behavior.
it's not uncommon to have a null param - dunno why it would be
different in a component.
On Tue, Jun 24, 2008 at 12:54 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> I've been thinking of a c
Hey Juan -
umm ... 2 cents..
if you have a minute, maybe let me know what i'm missing ..
(thanks!)
>Here is the DateInput component for t5:
>http://juanemaya.blogspot.com/2007/05/tapestry-5-date-input-component.html
>I am not sure if that's the best way to do it. I think that building the
>date i
Hey Alexander Lamb -
>First message to this list... getting back to development after some
>time (previously NeXT / WebObjects :-).
[ah, yes. the gold old days :-]
> 1) figure out what url to give
In the calling (~generated) .html - the link to the flash goes something like ..
In WebObjects, I think this is the WOSwitchComponent -
where you can specify the component name to be rendered/substituted
as a binding.
I don't believe such a dynamic component exists in Tapestry.
(In 3.x) I've resorted to @If / @If / @If .. to implement solution
(bleh).
I didn't try @De
Daniel -
If I understand correctly, you're question is where to ultimately put
the upDate(c);, In your example you put it on the setYear() but that
relies on setYear being called last which I don't think is a
guarantee. Alternatively you could put it on all of them (but this
would be inneficie
Navin -
Thanks very much for the reply.
You can use templates for components too (similar to page
templates), by extending the component class from "BaseComponent".
Then you just add an HTML with the same name as the component and
that's all.
Sorry if original post is confusing.
I'm ok
I find Tapestry ok for generating html, but I'm struggling on the
request processing. I don't think I'm alone .. I see many references
to this topic on the mailing list archive -- and it's not very well
described in the documentation :-?
Specifically, reusable components participating in r
I find Tapestry ok for generating html, but I'm struggling on the
request processing. I don't think I'm alone .. I see many references
to this topic on the mailing list archive -- and it's not very well
described in the documentation :-?
Specifically, reusable components participating in r
