Em Wed, 14 Oct 2009 23:04:12 -0300, Martin Strand
escreveu:
Had you used and Tapestry would simply have
rendered the html as you wrote it but there would be no integration with
your server side code and any submitted data would have been sent off to
the far reaches of cyberspace. ;)
To clarify further...
You have to use a Tapestry Form component, not a regular HTML form.
Otherwise there are important things you can't do:
- you can't use the Errors component to display the errors (eg.
). Tapestry depends on it being within a T5 Form.
- you can't refer to the Form in the p
* Naturally I'd have preferred to use "t:hidden" rather than "t:textfield"
for the hidden field. Unfortunately, I get the error "Unable to resolve
'hidden' to a component class name."
I think Hidden was added in Tapestry 5.1 so if you're using 5.0 "hidden" won't
be an existing component.
*
On 15/10/2009, at 11:11 AM, Lindsay Ridgeway wrote:
* I'm still not clear when to use "t:" and when not to. For
example, could
I have used "form" instead of "t:form"? I don't know.
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/lang/previewabletemplates
--
Martin Strand-4 wrote:
>
> Perhaps something like this?
Thanks for your reply, Martin. I appreciate the time you put into it.
I've continued experimenting on my own. Here's a generic version of what
I've come up with:
THE JAVASCRIPT
function extraStep() {
alert("ENTER extraStep");
Perhaps something like this?
Not tested at all but I suppose it ought to work.
in your template:
window.onload = function () {
alert('about to submit');
document.forms[0].firstChild.value = 'i just set the hidden value';
document.forms[0].submit();
};
in your cla
Hi, Martin. Thanks for your response. Unfortunately, I still feel lost.
(Let me say that I have programmed computers every day for over 40 years and
have spent the last three days totally immersed in Tapestry documentation
and a large existing Tapestry code base that doesn't happen to have an
e
Em Wed, 14 Oct 2009 14:16:30 -0300, Lindsay Ridgeway
escreveu:
But in addition, each submit button is associated with a different
JavaScript function. Each JavaScript function enters into a particular
dialog in order to obtain some information. The JavaScript function
needs to store that
I'd also like to have multiple Java methods that receive control depending
on which submit button is clicked.
You can accomplish this with the Submit component, which fires an event of your
choice, e.g.
@Component(parameters = "event=buttonOneClicked")
private Submit buttonOne;
void onButtonO
http://catb.org/~esr/faqs/smart-questions.html
Am 14.10.2009 20:00 schrieb Lindsay Ridgeway:
Hi, Ulrich. Are you saying my request for assistance in understanding how to
submit from JavaScript was inappropriate?
I could have followed the approach of other posts I've seen on this list: I
could
Hi, Ulrich. Are you saying my request for assistance in understanding how to
submit from JavaScript was inappropriate?
I could have followed the approach of other posts I've seen on this list: I
could have copy/pasted all the false trails I've been down and all the
useless error messages I've go
Why don't you just give us your complete specs and let us do your work. For
free of course!
Uli
Am 14.10.2009 19:16 schrieb Lindsay Ridgeway:
[If this question has been answered, please send me a link. I'm new to
Nabble, I couldn't find such an answer, I apologize if it's there.]
I'm new to
12 matches
Mail list logo
