2014-05-12 20:47 GMT-03:00 Stephan Eggermont :
> Esteban wrote:
>>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.
>
> I strongly encourage the u
2014-05-12 20:47 GMT-03:00 Stephan Eggermont :
> Esteban wrote:
>>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.
>
> I strongly encourage the u
Esteban wrote:
>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.
I strongly encourage the use of ci images. And of course you should
add your o
2014-05-12 20:21 GMT-03:00 Stephan Eggermont :
> 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
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
Hello
Sorry if this is the wrong place to ask this. I am trying to understand how
Magritte works, initially by following the first example in Ch. 26.2 of the
Seaside book. I have started with a fresh download of Pharo 3.0, and I have
installed Magritte 3 and Seaside 3. I realise that the Seaside
Thanks, Norbert!
On Mon, May 12, 2014 at 11:38 AM, Norbert Hartl wrote:
>
> Am 12.05.2014 um 10:46 schrieb Sabine Knöfel :
>
> Hi Norbert,
>
> what about objects which have been written to mongo with the old version
> and will be read with the new version. Can they be read/found with the new
>
Am 12.05.2014 um 10:46 schrieb Sabine Knöfel :
> Hi Norbert,
>
> what about objects which have been written to mongo with the old version and
> will be read with the new version. Can they be read/found with the new
> version? Or is there a migration needed?
I’d say it should be safe just to u
Hi Norbert,
what about objects which have been written to mongo with the old version
and will be read with the new version. Can they be read/found with the new
version? Or is there a migration needed?
Regards
Sabine
On Thu, May 8, 2014 at 11:30 PM, Norbert Hartl wrote:
> I needed to change t
