On 8/25/17, H. Hirzel <hannes.hirzel@gmail.com> wrote:
The package contains two approaches to render a Pillar document object to Morphic.
1. PRVisitor subclass: #PRMorphWriter 2. PRDocumentWriter subclass: #PRMorphWriter2
After removing PRMorphWriter we have what the screen shot shows. PRMorphWriter2 using PRMorphCanvas does the job. PRMorphInterface is a demo class and PRRenderingExamples contains some demo Pillar source code. Stephane, you wrote "Ideally we should add the pillar element to the associated morphic to manage back link from the renderer to the pillar tree. But this is to be done." I do not understand what you mean with this. It sound like there should there be a link from the morph used in rendering to the Pillar document object model node? The way how it is implemented at the moment is different. An instance of the class Text is created. parseButton action: [ document := PRPillarParser new parse: textInput text. morphWriter start: document. textResult text: morphWriter text ]. Then it seems that just a TextMorph is displayed writer text asMorph openInWindow. And what is the reason for this? --Hannes
