:) Seems like I&#39;m the one who likes to talk to himself...<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Wj3C7c"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In the custom render method you can use Magritte to generate a<br>

read-only view of the fields, try something along:<br>
<br>
html table: [<br>
 &nbsp; &nbsp; &nbsp; &nbsp;aStructure description do: [ :each |<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(each isEditable and: [ each componentClass notNil ]) ifTrue: [<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;html tableRow: [<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;html tableHeading: each label.<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;html tableData: [<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(each componentClass memento: aStructure description: each)<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;renderViewerOn: html ] ] ] ] ]</blockquote></div><div><br>This way it ignores pier syntax including all the &#39;special&#39; symbols in text... I can&#39;t understand how to fix it?<br>

</div></div></blockquote></div><br></div></div>I played a little bit more with Pier and understood this question was somewhat stupid...<br><br>My current idea is the following... For my site I have to do again and again the same thing: render all the &#39;details&#39; of the current object and then render &#39;overview&#39; of it&#39;s children. So, considering the 1-st part (details) I&#39;d like to tag some fields as details of the object. So I implemented according methods (<i><b>#isDetail</b></i>, <i><b>#isDetail:</b></i>, <b><i>#beDetail</i></b>) in <i><b>MADescription</b></i>. Then I want create DetailedCase as a subclass of <i><b>PRCase </b></i>and override there <i><b>#accept: </b></i><br>

<br><div style="margin-left: 40px;">DetailedCase &gt;&gt; accept: aVisitor<br>&nbsp; aVisitor visitDetailedCase: self<br></div><br>In <b><i>PRViewRenderer &gt;&gt; visitDetailedCase: anObject</i></b> I want to visit every property (is it correct term?) of <i><b>anObject </b></i>described as detail... <br>

<u>but I can&#39;t understand how i can do it... can I get a property of object by description (or vice versa)?</u><br><br>I expect to get all the details about anObject properly presented on the page this way. Am I right? <br>
</blockquote></div><br>I did: <br><br><div style="margin-left: 40px;">PRViewRenderer &gt;&gt;  visitDetailedCase: anObject <br>&nbsp;&nbsp;&nbsp; self remember: anObject while: [ super visitDetailedCase: anObject ]<br><br>PRDeepRenderer &gt;&gt; visitDetailedCase: anObject <br>
&nbsp;&nbsp;&nbsp; anObject detailedDescription<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; do: [:each | self<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; visit: (<b>each accessor read: anObject</b>)]<br><br>PRVisitor &gt;&gt; visitDetailedCase: anObject <br>&nbsp;&nbsp;&nbsp; self visitCase: anObject<br></div>
<br><br>It seems to work except the case when I tag <i><b>MAStringDescription </b></i>with <i><b>#beDetail</b></i>. In that case it tries to visit a String which is collection and so each of its characters should be visited but visiting is not implemented for most of objects including Chars... and I&#39;m affraid the same error will be raised for some other types of description... <br>
<br>Hope to hear (or find by myself if only I&#39;ll have enough time) how to do it all the right way tomorrow... :)<br><br>-- <br>Dennis Schetinin<br>