+1 from me, and would love to help where I can. It would be nice to see Pillar return to being a cross platform project as well. One of the beautiful things about Seaside/Magritte/Pier was it’s compatibility across many dialects of Smalltalk. The “develop in Pharo and deploy in GemStone” was a big draw for me :) One of my clients uses VW so it was great to have these projects there as well.
Pillar was refactored to use Traits and save duplication of (from memory) about 3 methods, but in doing so it became a Pharo-only project. I asked about this and found there wasn’t an interest in maintaining cross platform compatibility, so I saved a copy on git hub [1] and added a PRPillarGemstoneCodeTool class with a simple method for flattening the traits. My hope was being able to maintain a cross platform version of Pillar and keep Pier updated in a manageable way. Frustratingly, my work only allows me the occasional sprints in Smalltalk and without a Pier project to work on, I haven’t had the resources to keep it updated. I’d like to see Pier get some love - it’s an awesome tool. How can I help? [1] https://github.com/JupiterSmalltalk/Pillar <https://github.com/JupiterSmalltalk/Pillar> > On 12 Nov 2016, at 12:16 am, stepharo <steph...@free.fr> wrote: > > Hi peter > > I do not know but I would love that it would work. I should find some time to > do a new pass on pillar. > > On my first todo: > > - fix use of DNU instead of plain magritte methods. > > - extract object out of the command line. > > - document, document and document. > > > Stef > > > > Le 10/11/16 à 22:34, Peter H. Meadows via Pharo-users a écrit : > >
