Thanks Stef. I'm aware of templates and I saw how to use them when using
pillar from command line.
I have doubts regarding how to it programatically, but I need to take a
look that code before posting concrete questions.
On Thu, Mar 1, 2018 at 9:16 AM, Stephane Ducasse
wrote:
> In fact in Pill
Thanks Offray, I followed previous holly wars :P .
I understand the pros and cons.
Is there any preview option in grafoscopio?
Or an external viewer is a must?
Thanks!
On Wed, Feb 28, 2018 at 2:27 PM, Offray Vladimir Luna Cárdenas <
offray.l...@mutabit.com> wrote:
> Hi Arturo,
>
> It seems that
In fact in Pillar 6/7 you can take template or create your own the
variables are mustache variables.
So this basically means that you inject the latex generated by Pillar into
the latex document
template you want.
Have a look at the template folder.
On Tue, Feb 27, 2018 at 2:42 PM, Arturo Zambran
Hi Arturo,
It seems that you have a project with documentation is pretty important.
I don't want to start a holly war pointing that there is alternatives to
Pillar in Pharo, but maybe you should check Grafoscopio + Pandoc. We can
write pretty complex documents using it, like the Grafoscopio User
M
Thanks for your help.
I will use markdown as a preview, so th PR*Writer write:document is OK.
For the last phase I plan to use latex to generate a pdf following certain
presentation rules.
I wonder if it is possible to use pillar 7 templates programmatically.
Is there some example I can follow?
On Sun, Feb 18, 2018 at 9:01 PM, Stephane Ducasse
wrote:
> Hi arturo
>
> What you saw is the pipeline to produce book and others. Now I do not
> think that you need it.
> To export markdown you do not need the pillar configuration and the rest.
> Check the chapter 6 in the publishing a booklet wi
Hi arturo
What you saw is the pipeline to produce book and others. Now I do not
think that you need it.
To export markdown you do not need the pillar configuration and the rest.
Check the chapter 6 in the publishing a booklet with pillar document.
You can just get your document using the Pillar p
Hi,
I figured it out (at least in part)
configuration := PRPillarConfiguration new.
configuration outputType: PRMarkdownWriter.
export:=PRExportPhase new .
export executeOn:
(PRCompilationContext withDocument: document withConfiguration:
configuration)
This code snipped
