GToolkit in Pharo 4?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

GToolkit in Pharo 4?

Max Leske
I’ve tried loading GToolkit into Pharo 4 from a configuration:

spec for: #'pharo4.x' do: [
        spec project: 'GToolkit' with: [
                spec
                        className: 'ConfigurationOfGToolkit';
                        version: #bleedingEdge;
                        file:  'ConfigurationOfGToolkit';
                        repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main';
                        postLoadDoIt: #setUpIDE ] ].

I didn’t exactly expect it to work but I was hoping it would… :) Any ideas if / when that configuration will work (it doesn’t have to be perfect. I’m happy to work with #bleedingEdge).

Cheers,
Max
Reply | Threaded
Open this post in threaded view
|

Re: GToolkit in Pharo 4?

Stephan Eggermont-3
Just fix the configuration. Nothing there for pharo 4.x
And as baseline012 refers to #development everywhere,
you'll need to check all dependencies too

Stephan

Reply | Threaded
Open this post in threaded view
|

Re: GToolkit in Pharo 4?

Max Leske
Ok, thanks.


On 28.07.2014, at 22:37, Stephan Eggermont <[hidden email]> wrote:

> Just fix the configuration. Nothing there for pharo 4.x
> And as baseline012 refers to #development everywhere,
> you'll need to check all dependencies too
>
> Stephan
>


Reply | Threaded
Open this post in threaded view
|

Re: GToolkit in Pharo 4?

Uko2
So is it working for you? Because when I load it, I get emergency evaluator when debugger should open…

Uko

> On 29 Jul 2014, at 09:17, Max Leske <[hidden email]> wrote:
>
> Ok, thanks.
>
>
> On 28.07.2014, at 22:37, Stephan Eggermont <[hidden email]> wrote:
>
>> Just fix the configuration. Nothing there for pharo 4.x
>> And as baseline012 refers to #development everywhere,
>> you'll need to check all dependencies too
>>
>> Stephan
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: GToolkit in Pharo 4?

Andrei Chis
Not all GT-Tools work in Pharo 4 (e.g. the debugger does not work).
You can load the Playground + a subset of the inspector (without roassal) using the code below.
(You still need to manually enable them from the setting browser -> GT)

Gofer new smalltalkhubUser: 'Moose'
        project: 'GToolkit';
        package: 'ConfigurationOfGTPlayground';
        load.

(((Smalltalk at: #ConfigurationOfGTPlayground) project version: '0.1-baseline') load).


On Mon, Sep 22, 2014 at 5:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
So is it working for you? Because when I load it, I get emergency evaluator when debugger should open…

Uko

> On 29 Jul 2014, at 09:17, Max Leske <[hidden email]> wrote:
>
> Ok, thanks.
>
>
> On 28.07.2014, at 22:37, Stephan Eggermont <[hidden email]> wrote:
>
>> Just fix the configuration. Nothing there for pharo 4.x
>> And as baseline012 refers to #development everywhere,
>> you'll need to check all dependencies too
>>
>> Stephan
>>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: GToolkit in Pharo 4?

Tudor Girba-2
Thanks Andrei!

For the rest of the tools, we kindly ask you to be patient until we release Moose 5 and switch development to Pharo 4.

Cheers,
Doru

On Mon, Sep 22, 2014 at 5:43 PM, Andrei Chis <[hidden email]> wrote:
Not all GT-Tools work in Pharo 4 (e.g. the debugger does not work).
You can load the Playground + a subset of the inspector (without roassal) using the code below.
(You still need to manually enable them from the setting browser -> GT)

Gofer new smalltalkhubUser: 'Moose'
        project: 'GToolkit';
        package: 'ConfigurationOfGTPlayground';
        load.

(((Smalltalk at: #ConfigurationOfGTPlayground) project version: '0.1-baseline') load).


On Mon, Sep 22, 2014 at 5:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
So is it working for you? Because when I load it, I get emergency evaluator when debugger should open…

Uko

> On 29 Jul 2014, at 09:17, Max Leske <[hidden email]> wrote:
>
> Ok, thanks.
>
>
> On 28.07.2014, at 22:37, Stephan Eggermont <[hidden email]> wrote:
>
>> Just fix the configuration. Nothing there for pharo 4.x
>> And as baseline012 refers to #development everywhere,
>> you'll need to check all dependencies too
>>
>> Stephan
>>
>
>






--

"Every thing has its own flow"