True, most of the output formats for Tobago which come to my mind have
an XML based syntax, therefore you have a DOM and it's pretty easy to
define a JavaScript binding for this DOM.
If I take SVG (I always wanted a SVG renderer for Tobago ;-) as an
example the standard scripting language is J
A workaround is to put something like this on the page
(inside the t:page).
function initOnChange() {
var x = document.getElementById("page:username");
x.onchange = onChangeFunction;
}
function onChangeFunction() {
alert('username changed');
}
Udo
Dani Ke
P.S.:
a solution would be to have a second set of components for HTML based
interfaces only?
regards,
Martin
On 10/6/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> Hmmm
>
> Thing is that for XML based languages, JavaScript has become something
> like a scripting standard.
>
> regards,
>
Hmmm
Thing is that for XML based languages, JavaScript has become something
like a scripting standard.
regards,
Martin
On 10/6/05, Udo Schnurpfeil <[EMAIL PROTECTED]> wrote:
> Hello,
>
> this is a known problem, but we don't have a solution yet.
>
> The main idea of Tobago is that the sourc
Hello,
this is a known problem, but we don't have a solution yet.
The main idea of Tobago is that the source code (especially the JSP
pages) are independent from the output format (e.g. HTML). If we allow
to set "onchange" and "onclick" events, the source code will depend on
the output format
Hi,
I would like to handle onchage or onclick events in the client side.
It seems missing from the Tobago tld.
Is there away around this limitation? Is there a chance to get a fix for that?
TIA
Dani
6 matches
Mail list logo
