On 01 Jun 2016, at 20:44, Damien Cassou <Damien.Cassou@inria.fr> wrote:
On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Iâm installing pillar like this:
pillar: spec spec project: 'Pillar' with: [ spec className: 'ConfigurationOfPillar'; loads: #('html exporter'); repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]
who, according to me, should give me elements to parse pillar I don't have the code at hand but this not what I expect : the parser is not necessary to export html, you just need a document model (which you could get through a Markdown parser for example). Without the parser you canât do anything so I would expect the parser to be a core part. But anyway, even agreeing with your PoV, if I load #(html exporter), then I have unreferenced pillar classes in the resulting image (PRDocumentItem class>>#parser has a strong reference⦠and even that method should not be there according with your statement).
Esteban this is not really true. I manupilate citezen objects and want to export them as html and I was wondering: should I emit pillar -> parser -> model -> html or model -> html and this is what I will do.
but anyway, for me the important part is: what do I need to load to have the parser? there is no group âparserâ in ConfigurationOfPillar.
cheers! Esteban
export to html⦠but when I finish, my installation is lacking a parser.
⦠and PRDocumentItem class>>#parser is having an undeclared behaviour (PRPillarParserMain is not in the system). This has probably been fixed by Yann already in the development version.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill