Zeljko Trogrlic wrote:
>
> Hello,
>
> I think that real OO approach will be to add
>
> HTMLDocument extends Document
>
> and keep plain Document class simple - without head and body. Actually,
> there is Html class, should it be used as HTMLDocument?
>
>From a principle point of view, I agree. However, that would have
tremendous repercussions for now... That's why I am leaving the Document
class alone, so as not to affect all those people using ECS now
(although you are right... he's right, Jon...).
In any case, what I have ended up doing is having XMLDocument be a stand
alone class (it does not extend Document) because there are too many
HTML constructs in Document now, which is what you are getting at
Zeljko. So it implements its own output, codeset, etc. That way if we
ever do move to a more generic Document, we can change XMLDocument over
easily, and for now XMLDocument doesn't have all sorts of goofy methods
like setHead() and getHead() that are meaningless and confusing.
Again, I think you have the right idea, but it would destory every user
of ECS who uses Document... and that's not OK right now.
Comments?
-Brett
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
