Le 11/11/16 à 22:35, Jupiter Jones a écrit :
+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.
Yes but at the end of the day. You see we cannot work for free and in
addition got constraints that are dragging us behind.
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.
I will see if the trait usage make sense and can be removed. But you see
if everything we do has to be compatible better be dead.
I would prefer to see GS having an infrastructure to load Pharo kernels.
We are pushing the bootstrap for this reasons.
Because you see Pharo will use more and more slots because they are
really really cool and powerful.
What do you do with Pillar? Because I write books, slides, and websites
so this is an important piece of software for me.
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
Join and hack.
On 12 Nov 2016, at 12:16 am, stepharo <steph...@free.fr
<mailto: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 :
