Hi Johan, Ferlicot Delbecque Cyril <c.ferlicot-delbecque@etudiant.univ-lille1.fr> 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