<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hilaire,<br>
<br>
Am 02.01.16 um 10:12 schrieb Hilaire:<br>
</div>
<blockquote cite="mid:56879497.8040008@drgeo.eu" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Le 02/01/2016 09:45, Johan Brichau a
écrit :<br>
</div>
<blockquote
cite="mid:C22570C9-4B96-4205-8101-DAAC37F08140@inceptive.be"
type="cite">
<div class="">My suggestion is not to use the #printOn: method
for rendering the object on a Seaside canvas, but rather
implement a #renderOn: method that avoids concatenating the
String and WideString instances.</div>
<div class=""><br class="">
</div>
</blockquote>
<font size="+1">Thanks for the tip it helps.<br>
However use of renderOn: will have some large implication on my
Seaside components. Each use case of this object in component
need to be rewritten to use only render:. I don't like much this
idea, it makes the written code less elegant and consistent.<br>
</font></blockquote>
since the behavior isn't consistent, I don't see why you should
bother... <br>
<br>
And just to make sure we're not sending you in the wrong direction:
Johan surely doesn't suggest turning your model objects into
WAComponents. You don't have to use #render:, and maybe you
shouldn't even call the method anything like #render, just use some
method that accepts a renderer as parameter and renders html onto
it.<br>
<br>
OTOH, speaking of the inspector: not sure about Pharo, but in VA
there is #printOn: and #debugPrintOn:, so you could also choose to
implement special behavior for inspecting/debugging purposes. This
would probably not really solve the concatenation problem, so maybe
not even a relevant note ;-)<br>
<br>
On a side note: I have decided to not use printOn: for application
purposes if ever possible for similar reasons since I use Seaside.
Too often I had to implement different representation logic for the
application and myself as the developer. Having to go through a
horribly long list of senders of #printString, #printOn: and
sometimes even #asString in order to decide whether it's one or the
other several times was an exercise that asks for avoidance...<br>
<br>
Joachim <br>
<br>
<br>
<pre class="moz-signature" cols="72">--
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel <a class="moz-txt-link-freetext" href="mailto:jtuchel@objektfabrik.de">mailto:jtuchel@objektfabrik.de</a>
Fliederweg 1 <a class="moz-txt-link-freetext" href="http://www.objektfabrik.de">http://www.objektfabrik.de</a>
D-71640 Ludwigsburg <a class="moz-txt-link-freetext" href="http://joachimtuchel.wordpress.com">http://joachimtuchel.wordpress.com</a>
Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
</pre>
</body>
</html>