Hi Peter - Recently I saw your "Pier3 with latest Pillar" post to the Pharo group, and was intrigued about your changes. If you can't get them in Pillar, maybe they could be modified to be added to Pier3 or the Pier3AddOns build. Recently I updated the config to correct the version of Seaside that was loading, and now all of the builds are green for:
https://ci.inria.fr/pharo-contribution/job/Pier3Addons/
I can't recall who gave me write access, but I expect they are on this list.
Thanks,
John
Quoting from http://sdmeta.gforge.inria.fr/Teaching/Lille/0910-MetaModelisation/07-08-Co… section 4.1:
The Adaptive- Model has two instance variables, the first being used to refer to the descriptions of the instance and the other one to keep a list of the actual values of the model. Transforming the class of the adaptive model into a Trait [18] allows us turn any existing class into an adaptive model and to combine the descriptions defined in the class with the ones provided by the instance.
I cannot find this trait. Does it exist in magritte? I see MAAdaptiveModel, but I am indeed trying to add adaptivity to a class, and am struggling with it
oops. I tried squeak 5.1, not 5.0
> On 09 Sep 2016, at 08:18, Tapple Gao <tapplek(a)gmail.com> wrote:
>
> For the record, here’s the installation incantations that didn’t work, in the order I tried them:
>
> === In Squeak 5.0, attempt 1 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick’.
>
> Metacello new
> configuration: 'Pier3';
> repository: 'http://www.smalltalkhub.com/mc/Pier/Pier3/main';
> version: #stable;
> load.
>
>
> === In Squeak 5.0, attempt 2 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick’.
>
> Metacello new
> configuration: 'Pillar';
> repository: 'http://www.smalltalkhub.com/mc/Pier/Pillar/main';
> version: #stable;
> load.
>
>
> === In Squeak 5.0, attempt 3 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick’.
>
> Metacello new
> configuration: 'Magritte3';
> repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
> version: #stable;
> load.
>
>
> === Pharo 5, attempt 1 ===
>
> install seaside3, then pier 3, from catalog
>
>
> === Pharo 5, attempt 2 ===
>
> install seaside3, then pillar, from catalog
>
>
> === Pharo 5, attempt 3 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick'.
>
> Metacello new
> configuration: 'Magritte3';
> repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
> version: #stable;
> load.
>
> Metacello new
> configuration: 'Pier3';
> repository: 'http://www.smalltalkhub.com/mc/Pier/Pier3/main';
> version: #stable;
> load.
>
>
> === Pharo 4, attempt 1 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #'release3.1';
> load: 'OneClick'.
>
> Metacello new
> configuration: 'Magritte3';
> repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
> version: #'release3.5';
> load.
>
> The final one failed in the most interesting way; it broke seaside by installing a mix of seaside for pharo 4 and seaside for pharo 5
>
>> On 09 Sep 2016, at 08:02, Tapple Gao <tapplek(a)gmail.com> wrote:
>>
>> Thank you. I uploaded my changes to http://www.smalltalkhub.com/#!/~tapple . However, I realized they are for an older version of pier, from before the Pillar split, so they’ll probably be a pain to merge. I’m using this pier one-click image from lukas: http://www.piercms.com/download (pharo 1.3). I’ve never been able to install a working pier using metacello on any image for the past year. I tried again yesterday, and, after another 5 failed attempts on 3 different images, finally found a working incantation:
>>
>> "Instructions: Take fresh pharo 4.0 image, run the following, and pier works. Thanks to https://www.list.inf.unibe.ch/pipermail/smallwiki/2015-December/008025.html"
>>
>> Metacello new
>> configuration: 'Seaside3';
>> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>> version: #'release3.1';
>> load: 'OneClick'.
>>
>> Metacello new
>> configuration: 'Pier3';
>> repository: 'http://www.smalltalkhub.com/mc/Pier/Pier3/main';
>> version: #'release3.0';
>> load.
>>
>> It will take me some time to merge my changes, migrate my website, and properly test everything in a newer pier. I’ll let you know when I have.
>>
>>> On 08 Sep 2016, at 13:38, Damien Pollet <damien.pollet(a)gmail.com> wrote:
>>>
>>> Hi !
>>>
>>> Monticello is a distributed version control system, so you could have your own repository on smalltalkhub to commit your modifications. In fact, given how MC (doesn't) handles branches, it's probably the recommended way of doing if you want experimental/development code to be clearly separate from the official branch.
>>>
>>> In terms of getting your changes merged in the official release, I'd suggest discussing them on one of the Pharo lists, or on the Slack channel. Some of the owners of the Magritte and Pier repos on sthub and recent developers are active there and should be able to help and even review your code or add you to the contributors.
>>>
>>>
>>> On 8 September 2016 at 12:15, Tapple Gao <tapplek(a)gmail.com> wrote:
>>> Hello all. It’s been a long time since I contributed to a smalltalk project, but I’d like to start again.
>>>
>>> I’m developing a complex website based on Pier and Magritte: https://fiberhood.nl
>>>
>>> Even though I’ve barely started, I’ve already found several things to fix in Pier and Magritte, and would like to submit my fixes back upstream. How should I do that? I assume I don’t have commit access to http://www.smalltalkhub.com/#!/~Magritte and http://www.smalltalkhub.com/#!/~Pier , although I don’t really know how to tell. I’m used to squeaksource, where it plainly says Global: Read or Global: Read and Write
>>>
>>> My username on smalltalkhub is tapple: http://www.smalltalkhub.com/#!/~tapple
>>> _______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.list.inf.unibe.ch/listinfo/smallwiki
>>>
>>>
>>>
>>> --
>>> Damien Pollet
>>> type less, do more [ | ] http://people.untyped.org/damien.pollet
>>> _______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.list.inf.unibe.ch/listinfo/smallwiki
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.list.inf.unibe.ch/listinfo/smallwiki
>
Hello all. It’s been a long time since I contributed to a smalltalk project, but I’d like to start again.
I’m developing a complex website based on Pier and Magritte: https://fiberhood.nl
Even though I’ve barely started, I’ve already found several things to fix in Pier and Magritte, and would like to submit my fixes back upstream. How should I do that? I assume I don’t have commit access to http://www.smalltalkhub.com/#!/~Magritte and http://www.smalltalkhub.com/#!/~Pier , although I don’t really know how to tell. I’m used to squeaksource, where it plainly says Global: Read or Global: Read and Write
My username on smalltalkhub is tapple: http://www.smalltalkhub.com/#!/~tapple
Hi,
Please spread widely, and sorry for multiple posts.
(this post can be see here: http://pharo.org/news/pharo-5.0-released <http://pharo.org/news/pharo-5.0-released>)
Dear World,
The time has come for Pharo 5.0!
This is our most significant release yet. Here are some highlights:
- The PharoVM is now based on Spur, the new memory management, and it brings with it a 35% speedup!
- A new unified foreign function interface (UFFI) replaced NativeBoost to provide a strong Spur-compatible framework for interfacing with the outside world.
- The Glamorous Toolkit now includes the GTDebugger to offer a moldable infrastructure that allows the developer to customize the debugger deeply.
- The underlying Reflectivity mechanism has reached maturity with multiple pieces coming together to empower developers to instrument their own systems. For example, we now have breakpoints implemented as just a simple extension of this mechanism.
- QualityAssistant is now part of the image to provide live feedback during development.
These are just the more prominent highlights, but the details are just as important. We have closed 2446 issues in Pharo 5. Take a moment to go through a more detailed recount of the progress: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change….
While the technical improvements are significant, just think of getting 30% faster out-of-the-box, still the most impressive fact is that the new code that got in the main Pharo 5.0 image was contributed by 100 people. Together we have touched 43% of the classes, and 20% of the methods. The following visualization rendered with Roassal in Pharo 5.0 is dedicated to this effort. The picture shows the touched classes and packages in gray, the authors and the links to the changed classes in red, and, using an automatically generated visual id, you can spot authors that have worked on similar projects.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Abdelghani Alidra, Clara Allende, David Allouche, Nicolas Anquetil, Thibault Arloing, Jean Baptiste Arnaud, Mangesh Bendre, Clement Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Johan Brichau, Camillo Bruni, Miguel Campusano, Damien Cassou, Nicolas Cellier, Danny Chan, Andrei Chis, Christopher Coat, Ben Coman, Bernardo Contreras, Gabriel Omar Cotelli, Tommaso Dal Sasso, Paul De Bruicker, Sean De Nigris, Christophe Demarey, Simon Denier, Marcus Denker, Martin Dias, John Dougan, Stephane Ducasse, Stephan Eggermont, Johan Fabry, Sergio Fedi, Cyril Ferlicot, Holger Hans Peter Freyther, Joshua Gargus, Tudor Girba, Thierry Goubier, Kris Gybels, Norbert Hartl, Thomas Heniart, Dale Henrichs, Nicolai Hess, Alejandro Infante, Henrik Johansen, Goran Krampe, Pavel Krivanek, Juraj Kubelka, Denis Kudriashov, Matthieu Lacaton, Laurent Laffont, Kevin Lanvin, Jannik Laval, Alexander Lazarević, Skip Lentz, Max Leske, Dave Lewis, Esteban Lorenzano, Sheridan Mahoney, Mariano Martinez Peck, Max Mattone, John McIntosh, Rene Meusel, Eliot Miranda, Henrik Nergaard, Marion Noirbent, Merwan Ouddane, Nick Papoulias, Nicolas Passerini, Alain Plantec, Guillermo Polito, Damien Pollet, Baptiste Quide, Andreas Raab (RIP), Alain Rastoul, Stefan Reichhart, Lukas Renggli, Mark Rizun, Michael Rueger, Valentin Ryckewaert, Ronie Salgado, Udo Schneider, Boris Spasojevic, Igor Stasenko, Roger Stebler, Serge Stinckwich, Aliaksei Syrel, Camille Teruel, Pablo Tesone, Yuriy Tymchuk, Peter Uhnak, Masashi Umezawa, Dion Stewart, Sven Van Caekenberghe, Jan Van De Sandt, Benjamin Van Ryseghem, Toon Verwaest, Franck Warlouzet.
(If you contributed with Pharo 5.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy!
The Pharo Team
Hi,
We often use MAReport to display tables of data. We'd like to also be
able to edit cells in such a table. There is MADescribedComponentColumn
which allows using a component in a cell, but it does not quite do the
trick because it is read-only (and its implementation does not allow
otherwise).
I am currently on a mission to figure out how we can do this cleanly
using Magritte.
Has anyone else had such a requirement / plan to solve it out there?
Regards
- Iwan
--
Reahl, the Python only web framework: http://www.reahl.org
Hi,
I found that Pier3 is not loading in Pharo 5 (and I suppose neither in others).
Reason:
1) Stable is marked as 3.0… I needed to do:
(ConfigurationOfPier3 project version: #'release3.1') load.
then it starts loading but since is not loading Magritte3, it does not works.
… and Magritte3 also does not load fine (GRPharoPlatform dependency).
:)
cheers,
Esteban
I am going to start porting Magritte3.5 to GemStone/GsDevKit_home[4].
I will manage the GemStone source up on GitHub in a GsDevKit/Magritte3
project[1]. I would like to include a license file with the project and
the starting point should be the official Magritte license so I'm
wondering where I will find such a beast.
There is no license file here[2] and while the project license is marked
as MIT on SmalltalkHub[3], I don't see an actual license file.
I figured I would ask before I started looking for something more
official and as a last resort invent one...
As an FYI, I plan to keep the "unadulterated packages" on the master
branch and create a gs_master branch for the changes I make in the port
... If I have bugfixes I will feed them back to SmalltalkHub ...
Dale
[1] https://github.com/GsDevKit/Magritte3
[2] https://github.com/magritte-metamodel/magritte
[3] https://github.com/magritte-metamodel/magritte
[4]
https://github.com/GsDevKit/GsDevKit_home#open-source-development-kit-for-g…
Ciao,
i have a Pharo4.0 Latest update: #40625
where i install, from Configuration Browser, the stable version of :
Pier3 (JohnCBorden.52)
Pier3Addons (StephanEggermont.95)
Now when i open the relative web application:
pier and piersetup
i found some problematic and errors.
Can anyone help me to understand the status of these applications?
How i can load them into Pharo 4.0 ?
Thanks for considerations,
Dario
Name: ConfigurationOfMagritte3-StephanEggermont.118
Author: StephanEggermont
Time: 10 October 2015, 9:09:24.252164 pm
UUID: 5d39ab33-c062-4754-ad55-4feb4b59199d
Ancestors: ConfigurationOfMagritte3-StephanEggermont.117
Update Grease to stable version #'release1.2' is version 3.5.0
Name: ConfigurationOfMagritte3-StephanEggermont.117
Author: StephanEggermont
Time: 10 October 2015, 5:56:07.098168 pm
UUID: e61105b7-4521-4428-9881-795f10251beb
Ancestors: ConfigurationOfMagritte3-SeanDeNigris.116
In place change: block with MagritteGlamourForPharo40 only for Pharo 4.
