Re: [Pharo-users] Pillar question: PRCitationTransformer

[Yann Dubois]

Hi stef,

You can not have a citation annotation on a writer because the annotation
is transformed before to a PRCitation object. So you need to overwrite
visitCitation.

PRCitationTransformer is called in the phase mechanism. He is added in the
transform pipeline. PRCitationTransformer will be rename to
PRCitationAnnotationTransformer because this class change the citation
annotations and not the citations.

Le 22 août 2016 07:36, "stepharo"  a écrit :

Hi

I'm trying to extend Pillar to get new $publications:...$ structure and it
looks like Pillar is getting more and more complex. And the comments do not
really help because they are short and written for someone already
understanding it. :(

To try to understand I tried to

! Youpi

${cite:ref=Duca18rmod}$

!! Others

but I get

{"content":"!Youpi\n\n\n\n!!Others"}

./pillar export --to=pillar Example.pillar


May be I cannot export to pillar a citation. I have no idea.


I tried to add

PRPillarWriter >> visitCitationAnnotation: aCitation
"We invoke visitAnnotation: to make sure that the rest of the document
is visited."

self halt.
super visitCitationAnnotation: aCitation

Did not stop!

So I put an halt into

PRVisitor >> visitCitationAnnotation: aCitationAnnotation

self halt.
self createNewCitationWith: aCitationAnnotation.
self replace: (OrderedCollection with: tmpCitation) .
super visitCitationAnnotation: aCitationAnnotation

and it stopped.


I tried to understand who is calling

PRCitationTransformer

No luck. I'm sure that there is a magic registration mechanism but I failed
to find it.

Looking at tests (BTW Tests are not documentation or class comments, there
are tests).

It looks like I need a configuration.

 (self actualClass
executeOn:
(PRCompilationContext withDocument: anInput withConfiguration:
aConfig))
input

And then I fall on executeOn: implementors. LLPhase and
PRNodeTransformer.

and I have no idea how a Phase relates to a visitor.

To bad, after all the efforts on Pillar it looks like getting too complex.

So do not think that we can decently ask students to work on improving
Pillar anymore

because they will just get lost and disgusted from Pharo. :(

Sad news isn't.

I hope that I will not have to switch back to LaTeX or markdown (shit).

Stef

[Pharo-users] Update CI books written in Pillar

[Yann Dubois]

Hi !

In the last version of Pillar (4.0.x), Pillar don't manage the compilation
cycle. So the ./compile.sh does not work anymore.

To update our CI, we use a Makefile (I advise you to use this too). You
have an example on :
https://github.com/pillar-markup/Pillar-Archetype/blob/master/welcome/Makefile
.

In this Makefile, we create symbolic links pointing on the output
directory. It causes "out of memory" on Jenkins. To solve this problem, you
need to remove the symbolic links after the compilation. Personnaly, I had

*find book-result -type l -exec unlink {} \;*


at the end of the EnterprisePharo's Jenkins script.

Cheers, Yann

Re: [Pharo-users] Pillar: PRTemplate?

[Yann Dubois]

Hi,

PRTemplate was removed in the development version because our goal is
simplify Pillar. To do this, we want Pillar generate only the content of a
document, so the template system was removed. If you want use PRTemplate,
you can use the last stable release of Pillar, and if you want use the
development version, you wil need to write a Makefile (Our Makefile is not
useful for the moment) and put the content in a template engine like
Mustache (the Pharo version is usable with a command line since this week).

Yann

2016-04-23 18:18 GMT+02:00 Martin Dias :

> Hi Pillar developers,
>
> A method in Ecstatic [1] references a class named PRTemplate (as well as
> PRTemplateError), which probably existed in a previous version of Pillar.
> Do you know what happened to it? I'm trying to update Ecstatic code to work
> with latest Pillar version released.
>
> Regards,
> Martin
>
> [1]: https://github.com/guillep/ecstatic
>

[Pharo-users] [Bug] Sometime RPackage is desync with the system

[Yann Dubois]

Hello,

I loaded a repo', and later, I wanted to look my changes between my current
repo' and the repo' that has been loaded. And I have this message :

KeyNotFound: key #aDeletedMethod not found in MethodDirectory

Re: [Pharo-users] [Bug - Pharo 5.0] Remove a class but not remove for RPackage

[Yann Dubois]

For exemple I have 2 packages

PackageA
 - ClassA
PackageB
 - ClassB
   #iDependToClassA
   #otherMethod

I delete ClassA from the PackageA, so Pharo tell me that the method
#iDependToClassA use the content of the ClassA.
I delete the #iDependToClassA method but on the Browser, the method is not
deleted. I remove the method on the Browser and then,
At this moment, I see the methods was not deleted because it stay on the
metaclass when I want get the method references of the ClassB (with
RPackage>>methodReferences).

Same think was happen after with a Class

[Pharo-users] [Bug - Pharo 5.0] Remove a class but not remove for RPackage

[Yann Dubois]

Hello,

When I delete a class, a window pop to inform me that some methods use this
class. So I remove the methods because they are not usefull without my
class to removed.

But when I close the window, the methods stay on the Browser, so I remove
this methods on the Browser.

Then, I remove an other class and "BOOM" an error appears, the key which
represents my class is not present in the SystemDictionnary (it's normal),
but I can find the key in the RPackage metaclasses.

Re: [Pharo-users] [Pillar] Font-size on DeckJS

[Yann Dubois]

Yes, last week since a presentation in class with Damien Cassou and
stepharo, they said that the presentation generated with pillar has a small
font size and it would be good to having a way to change that.

It s not a pharo issue but I think it could be useful for pillar's users.
Le 18 mars 2016 17:44, "Alexandre Bergel" <alexandre.ber...@me.com> a
écrit :

> Is this related to Pharo?
>
> Alexandre
>
>
> > On Mar 18, 2016, at 5:30 PM, Yann Dubois <yann59.dub...@gmail.com>
> wrote:
> >
> > Hello world,
> >
> > I work today on a problem when we generate a presentation with DeckJS,
> the font size is very small on projection.
> >
> > I've find an issue for this, and you need to create a template with all
> deckJS dependancies, and an other css file to change some rules.
> >
> >
> > To change the font-size of a body slide (not title or subtitle), you
> need to rewrite this rules like this :
> >
> > .deck-slide-scaler p {
> >   font-size: 64px
> > }
> >
> > The scaling always works, and you don't need to touch the deckjs files.
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>

[Pharo-users] [Pillar] Font-size on DeckJS

[Yann Dubois]

Hello world,

I work today on a problem when we generate a presentation with DeckJS, the
font size is very small on projection.

I've find an issue for this, and you need to create a template with all
deckJS dependancies, and an other css file to change some rules.


To change the font-size of a body slide (not title or subtitle), you need
to rewrite this rules like this :

.deck-slide-scaler p {
  font-size: 64px
}

The scaling always works, and you don't need to touch the deckjs files.

Re: [Pharo-users] [Pillar] Logo for Pillar

[Yann Dubois]

I'm existing about this logo, it's a very nice logo.

[Pharo-users] Interogation about recursivity or sequential

[Yann Dubois]

Hello World, Happy new year 2016 !

I actually work on an integration of a double linked list on Pharo and I
have a little interogation.
It's better to use recursivity or senquential algorithm ?

Yann