It would upset alot look at the example. If you return an Element from
addElement you can't chain methods together after calling addElement,
breaking alot of code. 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
Richard McKinley
<RichardM@keystonelea To: "'ECS'"
<[EMAIL PROTECTED]>
rning.com> cc:
Sent by: Subject: RE: More XHTML...
<[EMAIL PROTECTED]
s.com>
09/27/00 11:22 AM
Please respond to
"ECS"
Read his question again:
>How much of the upset would be to *return* *Element* *from* *addElement*,
>removeElement and other methods that normally return the more specific
>class(A, Html, Table etc.)?
I didn't say it was a good idea, but he seems to want it for some reason.
Does my proposal answer his question?
-----Original Message-----
No.
Table table = new Table().addElement(new TR().addElement(new TD
())).setWidth("100%").setCellSpacing("10")); // currently works.
If we made that change it wouldn't because Element knows nothing about
setWidth or setCellSpacing as they are specific to Table.
-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]
- More XHTML... Bojan Smojver
- Re: More XHTML... Zaid
- RE: More XHTML... Richard McKinley
- RE: More XHTML... snagy
- RE: More XHTML... Richard McKinley
- RE: More XHTML... snagy
- RE: More XHTML... Richard McKinley
- RE: More XHTML... snagy
- Re: More XHTML... Jon Stevens
- Re: More XHTML... snagy
- RE: More XHTML... Bojan Smojver
- RE: More XHTML... Bojan Smojver
- RE: More XHTML... Bojan Smojver
