If I wanted to create my own fork of ECS I wouldn't be asking any questions
on the mailing list. I would just take the code and do it.
If you go through XHTML specification you'll see it's a rather small
document revolving around redefining HTML as an XML application. Therefore,
most of the HTML functionality is preserved but it's made to follow more
strict XML rules. And that seemed like an ideal opportunity to extend and
existing piece of software into a new flavour. Especially in an object
oriented environment like Java.
But as Stephan correctly pointed out, ECS 1.x is not very extensible and
unfortunately changes that I proposed would upset too much of the existing
code to do it.
Bojan
> -----Original Message-----
> From: Richard McKinley [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, September 28, 2000 4:41 AM
> To: 'ECS'
> Subject: RE: More XHTML...
>
> I completely agree with you. Thanks for all the awesome free code, by the
> way. My feeling was he wanted to know what *he* had to do to create his
> own
> private fork of ECS. I feel it is just fine the way it is.
>
> -----Original Message-----
> I was trying to demonstrate why it is implemented
> the way it is, and why I'm not willing to change it in the 1.x codebase.
>
> -stephan
>
>
> --
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
