Stefano Mazzocchi wrote:
> 4) Currently only IE 5.5+ implements this using the
> contentEditable='true' attribute on every element. Mozilla has scheduled
> such a feature for version 1.1 to be released in July. See
>
> http://bugzilla.mozilla.org/show_bug.cgi?id=97284
>
> [please, go there and vote for that bug so that it ends up in the tree
> faster!]
Voted! 41 votes so far.
> 5) Xopus uses contentEditable="true" as a in-place editing widget and
> adds a layer of driving logic based on client side XML/XSLT/XMLSchema to
> implement MVC. This is a possible solution but, for sure, not the only
> one. The same processing (creating a editing controlling javascript for
> the page) can be done on the server side. No, Ugo, we don't need to do
> it on the client side.
As long as the number of roundtrips from client to server is kept to a
minimum, I agree with you.
> Also, I believe that there is no need for XSLT on the client side (CSS
> styling is enough for most inline editing needs, since the hard-core
> transformations normally don't happen at the content level but at the
> page structure level, which is normally *never* edited this way!)
Of course.
Ugo
--
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
