Any hints on how to load the Magritte-Seaside package?
Regards,
Esteban A. Maringolo
2013/3/28 Tudor Girba :
> Magritte2 is a bit old. Magritte3 loads fine (we are using it in Moose).
>
> Doru
>
>
> On Mar 28, 2013, at 3:11 AM, "Esteban A. Maringolo"
> wrote:
>
>> Did anybody manage to load M
we should plit that in bug entries and take actions collectively :)
On Mar 28, 2013, at 4:56 AM, Yanni Chiu wrote:
> On 27/03/13 10:24 AM, Esteban Lorenzano wrote:
>>
>> Here in Pharo headquarters we are shock that there are just 10 new bugs
>> reported for 2.0 after the release...
>> So... I
On Mar 28, 2013, at 9:39 AM, p...@highoctane.be wrote:
> Yep, seems BlockContext is gone
Yes, it is not used since Pharo 1.0… it's dead code. Of course we can keep it
for
and build a nice Museum of dead code.
Marcus
Yep, seems BlockContext is gone. Ran into that as well. No idea on how
to fix tough. Throwing in BlockClosure instead makes me feel like
playing russian roulette.
Maybe Lukas repository has updates (as for Seaside)
Phil
2013/3/28 Esteban A. Maringolo :
> Did anybody manage to load Magritte 2 at
On Mar 28, 2013, at 4:56 AM, Yanni Chiu wrote:
>
>
> I had noticed that package loading seemed extremely slow, but did not look
> further into it. I think I saw mention that it's due to some usage of
> #become:, during the compiling of code. Based on build times (of just loading
> the rough
Magritte2 is a bit old. Magritte3 loads fine (we are using it in Moose).
Doru
On Mar 28, 2013, at 3:11 AM, "Esteban A. Maringolo"
wrote:
> Did anybody manage to load Magritte 2 at least?
>
> When running this:
> Gofer it
> squeaksource: 'MetacelloRepository';
> package: 'Configuratio
On 27/03/13 10:24 AM, Esteban Lorenzano wrote:
Here in Pharo headquarters we are shock that there are just 10 new bugs
reported for 2.0 after the release...
So... I wonder... is that because we made a really cool release, or just
because nobody is using it?
Just before the release I loaded u
Did anybody manage to load Magritte 2 at least?
When running this:
Gofer it
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfMagritte2';
load.
(ConfigurationOfMagritte2 project version: '2.0.6') load: #('Magritte-Seaside')
I get the following error:
This package depen
EstebanLM wrote
> So... I wonder... is that because we made a really cool release, or just
> because nobody is using it?
I've ported most of my projects to 2.0, but I've been on holidays for a few
weeks, so I haven't updated to the released version. I'll know better this
week, but IIRC most of the
I don't use it yet.
But you can bet you'll hear about it:D
Let things come to you and keep the great work.
sebastian
o/
On Mar 27, 2013, at 11:24 AM, Esteban Lorenzano wrote:
> Hi,
>
> Here in Pharo headquarters we are shock that there are just 10 new bugs
> reported for 2.0 after the
Esteban wrote:
>Here in Pharo headquarters we are shock that there are just 10 new bugs
>reported for 2.0 after the release...
>So... I wonder... is that because we made a really cool release, or just
>because nobody is using it?
It is a cool release and we are using it.
Sorry about the lack o
Thanks!
STef
> Esteban wrote:
>> Here in Pharo headquarters we are shock that there are just 10 new bugs
>> reported for 2.0 after the release...
>> So... I wonder... is that because we made a really cool release, or just
>> because nobody is using it?
>
> It is a cool release and we are usi
I use 2.0 for development of FileSystem-Git and Fuel but it will be quite a
while before we'll have a critical application working on 2.0, so in that
respect: no we don't use 2.0 in production.
Max
On 27.03.2013, at 15:24, Esteban Lorenzano wrote:
> Hi,
>
> Here in Pharo headquarters we are
As far as I am concerned, I report what I do find.
But needing to put bread on the table, I can do that a few days a
week. More to expect as I started the development of a seaside-rest /
amber app (getting inspiration from STH).
Other than that, the system looks like okay from a usage perspective
Hi,
Here in Pharo headquarters we are shock that there are just 10 new bugs
reported for 2.0 after the release...
So... I wonder... is that because we made a really cool release, or just
because nobody is using it?
Cheers,
Esteban
15 matches
Mail list logo
