Arguably, the name #encodeOn: is equally problematic. Or at least, the implementors should probably dispatch back to the Document or to something since the encoding could well depend on the type of Document and the object being encoded?<div>
<br></div><div>Julian<br><br><div class="gmail_quote">On Fri, Sep 18, 2009 at 12:50 AM, Robert Shiplett <span dir="ltr"><<a href="mailto:grshiplett2@yahoo.com">grshiplett2@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font:inherit"><p>String</p><p>>>encodeOn: aDocument<br> aDocument htmlEncoder nextPutAll: self<br></p><p><br></p><p>WAEmail</p><p>
>>encodeOn: aDocument<br> self encodeOn: aDocument htmlEncoder usingQuotes: false<br></p><p><br></p><p>"Could we get by with</p><p> >>markupEncoder </p><p>?</p><p>"</p></td></tr></tbody></table><br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br></div>