Hi!<br><br>Related with the issue <a href="http://code.google.com/p/pharo/issues/detail?id=2757">http://code.google.com/p/pharo/issues/detail?id=2757</a> (Issue <a href="http://code.google.com/p/pharo/issues/detail?id=2757">2757</a>:
 
 
 <span class="h3">Refactor StringHolder</span>) I was looking at the StringHolder hierarchy, and well, it&#39;s not very nice.� Playing to see how difficult should it be to refactor the hierarchy and decouple a bit those things, I took Workspace off from there, and writing 2 methods it happened to work well (at least with what I tested, hehe).<br>
<br>Sooo, I wondered why a StringHolder, what responsibilities it has, and what ones should it have...� I found that most of the messages a StringHolder understands are for browsing things and inspect things, such as the Paragraph editor does :).� And that&#39;s why Workspace could do all his stuff when I made him inherit from Object...<br>
<br>StringHolder class comment says: &quot;I am a kind of Model that includes a piece of text.� In some cases, the text can be edited, and in some the text is a method.&quot;<br><br>And I smell that its main responsibility is to hold a Text or a String in its contents variable, and all its subclasses are there because of that...� And if so, I don&#39;t like that inheritance approach :).<br>
<br>I want to destroy (literally) that hierarchy :).� And maybe it helps us in coming refactors and cleanings, so we can do them with less fear :P.<br><br>Well, this mail is just for ask for advice and argue about the correctness of this change (or not).<br>
<br>Thanks for reading up to here!<br>Guille<br>