GTools (GTPlayground and GTInspector) integrated

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

we are moving to configurations… conceptually, you *could* give us an SLICE, but a config would be a lot better.  

Esteban

On 30 Sep 2014, at 15:14, Andrei Chis <[hidden email]> wrote:

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

I also like configurations much more but now I need to find a way to keep Moose running on both Pharo 3 and 4 :)

Can I say in a version that I want a particular package to be loaded form a certain repository?

On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <[hidden email]> wrote:

we are moving to configurations… conceptually, you *could* give us an SLICE, but a config would be a lot better.  

Esteban

On 30 Sep 2014, at 15:14, Andrei Chis <[hidden email]> wrote:

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

Sure. You just specify a repository.

Doru

On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis <[hidden email]> wrote:

I also like configurations much more but now I need to find a way to keep Moose running on both Pharo 3 and 4 :)

Can I say in a version that I want a particular package to be loaded form a certain repository?

On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <[hidden email]> wrote:

we are moving to configurations… conceptually, you *could* give us an SLICE, but a config would be a lot better.  

Esteban

On 30 Sep 2014, at 15:14, Andrei Chis <[hidden email]> wrote:

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

--

www.tudorgirba.com

"Every thing has its own flow"

Simple enough :)

I'll create then a project Pharo4Integration in the Moose team and commit everything there.

On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba <[hidden email]> wrote:

Sure. You just specify a repository.

Doru

On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis <[hidden email]> wrote:

I also like configurations much more but now I need to find a way to keep Moose running on both Pharo 3 and 4 :)

Can I say in a version that I want a particular package to be loaded form a certain repository?

On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <[hidden email]> wrote:

we are moving to configurations… conceptually, you *could* give us an SLICE, but a config would be a lot better.  

Esteban

On 30 Sep 2014, at 15:14, Andrei Chis <[hidden email]> wrote:

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

--

www.tudorgirba.com

"Every thing has its own flow"

Better put it in PharoExtras. The projects under the Moose team are all project repositories.

Doru

On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis <[hidden email]> wrote:

Simple enough :)

I'll create then a project Pharo4Integration in the Moose team and commit everything there.

On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba <[hidden email]> wrote:

Sure. You just specify a repository.

Doru

On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis <[hidden email]> wrote:

I also like configurations much more but now I need to find a way to keep Moose running on both Pharo 3 and 4 :)

Can I say in a version that I want a particular package to be loaded form a certain repository?

On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <[hidden email]> wrote:

we are moving to configurations… conceptually, you *could* give us an SLICE, but a config would be a lot better.  

Esteban

On 30 Sep 2014, at 15:14, Andrei Chis <[hidden email]> wrote:

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

--

www.tudorgirba.com

"Every thing has its own flow"

--

www.tudorgirba.com

"Every thing has its own flow"

done 

On 30 Sep 2014, at 16:06, Andrei Chis <[hidden email]> wrote:

ok. I just need access to PharoExtras :)

Andrei

On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba <[hidden email]> wrote:

Better put it in PharoExtras. The projects under the Moose team are all project repositories.

Doru

On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis <[hidden email]> wrote:

Simple enough :)

I'll create then a project Pharo4Integration in the Moose team and commit everything there.

On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba <[hidden email]> wrote:

Sure. You just specify a repository.

Doru

On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis <[hidden email]> wrote:

I also like configurations much more but now I need to find a way to keep Moose running on both Pharo 3 and 4 :)

Can I say in a version that I want a particular package to be loaded form a certain repository?

On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <[hidden email]> wrote:

we are moving to configurations… conceptually, you *could* give us an SLICE, but a config would be a lot better.  

Esteban

On 30 Sep 2014, at 15:14, Andrei Chis <[hidden email]> wrote:

Could I also just provide you with a slice?

Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything.

So as soon as I'll commit something incompatible with Pharo 3 it will break Moose.

I can also provide a version but then I'll have to commit the changed mcz elsewhere.

Not sure which is the best option.

@Doru how far are we from moving Moose to Pharo 4?

On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <[hidden email]> wrote:

remember you will have to give me a 1.0.1 config version :P

On 30 Sep 2014, at 15:00, Andrei Chis <[hidden email]> wrote:

Cool.

Now I found the first bug :)

Seems that there is a problem with declaring variables in a playground. Fixing it now

On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <[hidden email]> wrote:

Oh yeah!!

On 30.09.2014, at 14:51, Esteban Lorenzano <[hidden email]> wrote:

> … that :)
> Which means that now we have a long way to polish them until Pharo4 release.
>
> Please test and provide feedback :)
>
> Esteban

--

www.tudorgirba.com

"Every thing has its own flow"

--

www.tudorgirba.com

"Every thing has its own flow"

2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <[hidden email]>:

… that :)
Which means that now we have a long way to polish them until Pharo4 release.

Please test and provide feedback :)

Esteban

Great!

How about a new Project category in fogbugz for GTools

or should we use just "Tools"?

Nicolai

new project GTools created in fogbugz :)

Esteban

On 30 Sep 2014, at 17:22, Andrei Chis <[hidden email]> wrote:

I guess a new category would make sense.

It would at least make it easy to find and keep track of those bugs related to the GTools

On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <[hidden email]> wrote:

2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <[hidden email]>:

… that :)
Which means that now we have a long way to polish them until Pharo4 release.

Please test and provide feedback :)

Esteban

Great!

How about a new Project category in fogbugz for GTools

or should we use just "Tools"?

Nicolai