" If you constantly have to fall back on Morphs then you might as well build the whole thing with Morphs."
Whats stops you from using Morphic and Spec at the same time ? It is even possible to use Morphic + Spec + Athens + NBOpenGL + Mars + .... personally I am making my own GUI API using Athens and Morphic. Athens for the actual drawing, Morphic for managing the widgets and the events. I could throw some Spec in it as well if I figure out how it works and see that it fits my way of thinking. From what I have read on Spec recent documentation it has an API for making extensions to it so adding new Morphs to it and Widgets is already doable. For me the main problem is that 90% of Pharo methods are not documented. I dont have a problem fighting with a messy library like Morphic , but taking a look at all these methods with no comments and no documentation just viewing the source is a huge waste of time and effort. I found out that its far easier to implement my own GUI API with Athens which at least it comes with a lengthy tutorial and some basic knowledge of Morphic. Its sad to reject a library just because it does not offer much documentation but I have no choice. So I have to disagree , documenting Morphic is far more important than cleaning it up. Because a method you know how to use but is difficult to use is far more useful than a method that is easy to use but you dont know how to use it.
