What needs to be done to get Pier3 to use the latest Pillar code? I think I've got it partly working with a few small changes. (an isEmbedded method was missing, and PRFigure needed some changes). Relevant slack discussion below. Peter Meadows [6:45 AM] I was trying to run Pier3 Max Leske [6:45 AM] I assume that didnât work as you had expected :slightly_smiling_face: Peter Meadows [6:45 AM] It half works [6:46] I can read pier pages but not edit them Max Leske [6:47 AM] Do you see a debugger? Peter Meadows [6:47 AM] when? Max Leske [6:48 AM] When you try to edit a page. Or does it just silently refuse to work? Peter Meadows [6:49 AM] it's silent Max Leske [6:49 AM] Hm. [6:50] Did you load Pier3 through the catalog as well? Peter Meadows [6:51 AM] but i had to change some things, and i might not have done it in the best way. Because the newest pillar seems to make PRFigures when it should used to make PRLinks .. or something. I don't really understand it. [6:52] no. custom [6:52] the catalog uses an old version of pillar [6:52] i think [6:55] I had to change PRDocumentParser to PRPillarParser Peter Meadows [7:00 AM] and why does Magritte need seaside? I thought they made it completely independent? Max Leske [7:02 AM] It doesnât. As far as I can tell, the problem is somewhere between Pier and Seaside. [7:03] When I try to load Pier I get exactly the same error as you but I can load Seaside3 by itself without problems. This may possibly be a Metacello bug. [7:05] Concerning pillar, you probably best ask Cyril Ferlicot. And for trouble with Seaside / Pier itâs best to ask on the seaside mailing list Peter Meadows [7:08 AM] ahh. well that might explain why it has been confusing/confounding me! Peter Meadows [7:20 AM] does Metacello not have a very verbose setting? Stephan Eggermont [7:48 AM] @anteater: Pillar forked from Pier and did not maintain compatibility. I have not updated configurations for Pharo 6. Magritte and Seaside are independent. Load the right metacello group to get a combination. Stephan Eggermont [7:54 AM] @anteater: just load Pier3 from the catalog and check the package cache to see if what is loaded is what you expect. Without pharo6 tags, very old stuff gets loaded Peter Meadows [7:56 AM] Yes, but I wanted my Pier to use the latest pillar code. Surely that was always the plan? It hasn't changed dramatically i think? [7:57] If it was actually a fork they would/should have changed the name! Stephan Eggermont [12:43 PM] @anteater it is definitely a fork with lots of breaking changes. No compatibility [12:46] Pillar broke compatibility on purpose and had zero interest in keeping things working [12:50] ConfigurationOfMagritte3 load loads a default group, which is often not what you want Cyril Ferlicot [12:54 PM] Is there a lot to change in Pillar/Pier to keep compatibility? Pierce Ng [2:01 PM] @cyrilferlicot the Pillar part of Pier has been taken out of Pier and made standalone, so Pier has to be updated to use Pillar. i looked at this a while back so maybe Pier has been kept updated. Stephan Eggermont [2:49 PM] @cyrilferlicot: flatten traits. Pier is cross-dialect. The other things were easy, just breaking the build once a month Cyril Ferlicot [2:51 PM] Maybe when Pillar will move to github we will be able to do a Pharo branch with trait and a flattened branch for cross dialects. [2:52] I think I broke a lot of compatibility during my internship but that was not because I did not wanted to keep compatibility but more because I did not knew the relation between Pillar and Pier. That was the first time I contributed to a real project :slightly_smiling_face: Stephan Eggermont [2:52 PM] Should not be difficult. It just asks for some attention to downstream consequences Dimitris Chloupis [2:53 PM] you are not the only one [2:54] even in the PBE we had half the files in pier extension and half with pillar extension Stephan Eggermont [3:06 PM] @cyrilferlicot: I didn't assume you intended to break things. Pierce Ng [4:07 PM] my blog has switched to pillar. before it was shelling out to the markdown executable called discount. so now the blog has one fewer dependency. thank you for the standalone pillar.