Pillar 1.1.0 released

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Pillar 1.1.0 released

Damien Cassou-2
Cyril Ferlicot and I have polished Pillar 1.0.0 a little. Here is 1.1.0
changelog:

- add shebang to generated pillarPostExport.sh
- improve pillarPostExport.sh messages a little
- HTML exporter
  - output a <figure> if and only if the Pillar figure has both a
    caption and a label
- LaTeX exporter
  - output a \begin{figure} if and only if the Pillar figure has both
    a caption and a label

Cyril migrated the list of issues and feature requests from
smalltalkhub.com to

             https://github.com/pillar-markup/pillar/issues

Please report issues, describe feature requests and ask questions there.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Pillar 1.1.0 released

Johan Brichau-2
Hi,

I just noticed that in the most recent version of Pillar, the instvar #embedded was removed from PRReference
This breaks Pier… though right before this change I could make Pier3 work with Pillar just fine.

The embedded var is used to specify that component references are to be embedded in the page. There are more components than Figures in Pier.

I am just trying to use and work with Pier3 for Seaside book and website, so it would be great if you can consider adding the embedded variable again.

thanks guys!
Johan

ps: email me directly, since I might miss replies via the mailinglist.

> On 07 Sep 2015, at 09:51, Damien Cassou <[hidden email]> wrote:
>
> Cyril Ferlicot and I have polished Pillar 1.0.0 a little. Here is 1.1.0
> changelog:
>
> - add shebang to generated pillarPostExport.sh
> - improve pillarPostExport.sh messages a little
> - HTML exporter
>  - output a <figure> if and only if the Pillar figure has both a
>    caption and a label
> - LaTeX exporter
>  - output a \begin{figure} if and only if the Pillar figure has both
>    a caption and a label
>
> Cyril migrated the list of issues and feature requests from
> smalltalkhub.com to
>
>             https://github.com/pillar-markup/pillar/issues
>
> Please report issues, describe feature requests and ask questions there.
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
>


Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Pillar 1.1.0 released

Damien Cassou-2

Hi Johan,

Ferlicot Delbecque Cyril <[hidden email]> writes:

> Le 13/09/2015 10:28, Johan Brichau a écrit :
>> I just noticed that in the most recent version of Pillar, the instvar
>> #embedded was removed from PRReference This breaks Pier… though right
>> before this change I could make Pier3 work with Pillar just fine.
>>
>> The embedded var is used to specify that component references are to
>> be embedded in the page. There are more components than Figures in
>> Pier.
>>
> We removed that because since Figures are not link anymore we do not
> need it. If the reference is a link, it is not embedded, else it is.
> We plan latter to have more embedded item than Figures, maybe we can
> just and a class between Reference and Figure (PREmbeddedReferences).
> With that we do not need the ivar.
>
> But since Pier3 doesn't evolve anymore I proposed to someone to freeze
> the version of Pillar needed for the stable version of Pier3. But I
> didn't get an answer.

I totally agree with Cyril. We can't limit the development of a
dependency forever because a dependent has more or less stopped
evolving.

Before, a figure was a link with embedded = true. This was silly because
each visitor had to do something specific for figures (e.g., in html you
want a <img>, in latex you want \includegraphics). This is totally
different from what is expected of a link.

Now a figure is not a link anymore, it is a reference. There can be
multiple kinds of references but the embedded parameter what not of any
use for Pillar anymore. So we decided to remove it, knowing that Pier
used it to embed Pier components. So, Pier users have 2 solutions now:

- either adapt Pier's configuration so that it uses an old version of
  Pillar;

- or adapt Pier's code to rely on the new Pillar. This might require
  some adaptations to Pillar which we can discuss.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Pillar 1.1.0 released

Johan Brichau-2
In reply to this post by Johan Brichau-2
Hi Cyril,

You are right. It’s better to just fix the version of Pillar for Pier and that works just fine for me now.
We will see what happens later if someone has the time to look at Pier.

cheers
Johan

> On 13 Sep 2015, at 12:22, Ferlicot Delbecque Cyril <[hidden email]> wrote:
>
> Le 13/09/2015 10:28, Johan Brichau a écrit :
>> Hi,
>>
>> I just noticed that in the most recent version of Pillar, the instvar #embedded was removed from PRReference
>> This breaks Pier… though right before this change I could make Pier3 work with Pillar just fine.
>>
>> The embedded var is used to specify that component references are to be embedded in the page. There are more components than Figures in Pier.
>>
>
> Hi Johan,
>
> We removed that because since Figures are not link anymore we do not
> need it. If the reference is a link, it is not embedded, else it is. We
> plan latter to have more embedded item than Figures, maybe we can just
> and a class between Reference and Figure (PREmbeddedReferences).
> With that we do not need the ivar.
>
> But since Pier3 doesn't evolve anymore I proposed to someone to freeze
> the version of Pillar needed for the stable version of Pier3. But I
> didn't get an answer.
>
> --
> Cyril
>
>> I am just trying to use and work with Pier3 for Seaside book and website, so it would be great if you can consider adding the embedded variable again.
>>
>> thanks guys!
>> Johan
>>
>> ps: email me directly, since I might miss replies via the mailinglist.
>>
>>
>
>