Re: [Pharo-users] Problem learning about Magritte
Hi Peter That sounds like you have independently installed Seaside and Magritte. You might miss the part connecting them together. Seaside can be used without Magritte, and Magritte without Seaside. That happens if you just install stable Seaside and stable Magritte from the configuration browser. Can you check if you have Magritte-Seaside loaded? That is in the Seaside group of Magritte. If not, you need the other option in the configuration browser, just loading the configuration of Magritte3. Then in a workspace, do-it (ConfigurationOfMagritte3 project version: #stable) load: 'Seaside'. A faster way to start can be to use one of the images from https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded. Stephan
2014-05-12 20:21 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
A faster way to start can be to use one of the images from https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded.
I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long. Regards, Esteban A. Maringolo
On 13/5/14 01:34, Esteban A. Maringolo wrote:
2014-05-12 20:21 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
A faster way to start can be to use one of the images from https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded. I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long.
why? you can just read the configuration of the jenkins job and you know how to build it. The difference is that with the jenkins job we are SURE that the script to load works. Stef
Regards,
Esteban A. Maringolo
I ve both of these things working in my app on pharo3. I'll have a look. Le 13 mai 2014 09:25, "stepharo" <stepharo@free.fr> a écrit :
On 13/5/14 01:34, Esteban A. Maringolo wrote:
2014-05-12 20:21 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
A faster way to start can be to use one of the images from
https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded.
I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long.
why? you can just read the configuration of the jenkins job and you know how to build it. The difference is that with the jenkins job we are SURE that the script to load works.
Stef
Regards,
Esteban A. Maringolo
2014-05-13 4:25 GMT-03:00 stepharo <stepharo@free.fr>:
On 13/5/14 01:34, Esteban A. Maringolo wrote:
2014-05-12 20:21 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
A faster way to start can be to use one of the images from https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded.
I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long.
why? you can just read the configuration of the jenkins job and you know how to build it. The difference is that with the jenkins job we are SURE that the script to load works.
If the script to load works in a clean image I would put it in the project page in SmalltalkHub or similar. And a reference to the CI image in case running the script gets convoluted. Again, CI images for testing of important contributions is great, but if projects/packages can't be loaded easily into an existing image it could mean the packaging is done wrong (developer) or the right packaging can't be specified (Metacello and friends), 99% of the times it is the former. Regards, Esteban A. Maringolo
Hi Stephan Many thanks. I was missing the Magritte-Seaside component. The problem is now fixed. No doubt I will find others! I started from scratch and loaded all the packages because I wanted to understand how these things work, and because I needed a combination of things installed - I have also loaded Voyage and PetitParser, hoping to use all these things together. I did not expect to find all of these in a pre-built image - maybe I was wrong. Many thanks also for the speedy response. I posted my question and went to bed. I did not expect to get an answer after midnight. It is interesting to see that others work even stranger hours than I do! Thanks also to others who commented. To Stepharo: I did not mean to sound critical. I was wondering if an updated version already exists and I have not yet found it. I know quite a bit about Smalltalk from Dolphin, but I am new to Pharo and I feel like a blind man stumbling about. There are so many packages around, and I do not understand what most of them do. Could I just try one supplementary question about using Magritte. The paper 'Magritte - A Meta-Driven Approach to Empower Developers and End Users' by Lukas Renggli, Stephane Ducasse and Adrian Kuhn has a section 3.2 on building an editor, which shows how the same description can generate an editor in Seaside or in Morphic Squeak (!). I know that #asComponent will generate the Seaside version; is there a method #asMorph which will give the morphic version as easily, or if not how do I get an editor as a Pharo window? Thanks again for the help. Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Stephan Eggermont Sent: 13 May 2014 00:22 To: pharo-users@lists.pharo.org Subject: Re: [Pharo-users] Problem learning about Magritte Hi Peter That sounds like you have independently installed Seaside and Magritte. You might miss the part connecting them together. Seaside can be used without Magritte, and Magritte without Seaside. That happens if you just install stable Seaside and stable Magritte from the configuration browser. Can you check if you have Magritte-Seaside loaded? That is in the Seaside group of Magritte. If not, you need the other option in the configuration browser, just loading the configuration of Magritte3. Then in a workspace, do-it (ConfigurationOfMagritte3 project version: #stable) load: 'Seaside'. A faster way to start can be to use one of the images from https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded. Stephan
participants (5)
-
Esteban A. Maringolo -
PBK Research -
phil＠highoctane.be -
Stephan Eggermont -
stepharo