Hi Lukas,<div><br></div><div>This sounds really useful. <br><div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Since these changes are not backward compatible I&#39;ll try to provide<br>

automatic refactorings for most parts. Moving existing code to the new<br>
codebase will certainly cause some problems, but in the long run I<br>
believe this to be a much better approach than the current one. If<br>
people have any feedback, concerns or other changes that would be<br>
important in the same run I am happy to hear them.<br></blockquote><div><br></div><div>I am using similar tricks to the ones Yanni indicated above to build instance specific instances - so it looks like your proposal would simplify that code considerably. I&#39;ve also been bitten by the name clash with #description.</div>
<div><br></div><div>One specific annoyance I have is with class extension description methods that are installed by addons that I can&#39;t disable (I currently delete the methods). Specifically:</div><div><br></div><div>
<div>PRCase&gt;&gt;descriptionDocumentTagCloud: aDescription</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>^ aDescription beTagCloud</div></div><div><br></div><div>PRStructure&gt;&gt;descriptionNameTagCloud: aDescription</div>
<div><span class="Apple-tab-span" style="white-space:pre">	</span>^ aDescription beTagCloud</div><div><br></div><div><br></div><div>I use the TagCloud addon, but don&#39;t want the structure name to be included and instead of document I use plain text (arguably the plain text change might be more widely applicable, but probably the first is more specific to my use cases)</div>
<div><br></div><div>Perhaps it&#39;s overcomplicating to be able to disable class extension descriptions - without making the code incomprehensible.</div><div><br></div><div>---</div><div><br></div><div>The other issue is with Magritte description caching and Gemstone. After I change a description in Gemstone I have to remember to flush the description cache. This seems to be due to a combination of Gemstone&#39;s classHistory and lack of support for weak collections(?). Is this on your radar?</div>
<div><br></div><div>----</div><div><br></div><div>I imagine your proposed changes will require some effort to rework Pier - as it uses Magritte extensively - I guess we can all pitch in to try to make it happen smoothly - perhaps we could organise a Camp Magritte/Pier??</div>
<div><br></div><div>----</div><div><br></div><div>Nick</div><div><br></div></div></div></div>