Re: [Pharo-dev] gtoolkit 3.10 overview

[Alexandre Bergel]

Pretty cool!

Alexandre


> On Feb 16, 2016, at 7:02 PM, Tudor Girba  wrote:
> 
> Hi,
> 
> I promised to send a summary of the larger changes that came with the recent 
> integration of GToolkit 3.10. Here it is:
> http://www.humane-assessment.com/blog/gtoolkit-3-10/
> 
> Please let us know what you think.
> 
> Cheers,
> Doru
> 
> 
> --
> www.tudorgirba.com
> www.feenk.com
> 
> "What is more important: To be happy, or to make happy?"
> 
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

[Pharo-dev] gtoolkit 3.10 overview

[Tudor Girba]

Hi,

I promised to send a summary of the larger changes that came with the recent 
integration of GToolkit 3.10. Here it is:
http://www.humane-assessment.com/blog/gtoolkit-3-10/

Please let us know what you think.

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"What is more important: To be happy, or to make happy?"

Re: [Pharo-dev] GToolkit loading problem

[Andrei Chis]

https://pharo.fogbugz.com/f/cases/15933/Wrong-metacelloPlatformAttributes-for-pharo-5

On Wed, Jul 8, 2015 at 11:54 AM, Esteban Lorenzano esteba...@gmail.com
wrote:

 you need to create one :P

 On 08 Jul 2015, at 11:47, Andrei Chis chisvasileand...@gmail.com wrote:

 Is there bug report for this or should I create one?

 cheers,
 Andrei

 On Fri, Jul 3, 2015 at 4:58 PM, Esteban Lorenzano esteba...@gmail.com
 wrote:


 On 03 Jul 2015, at 16:42, Andrei Chis chisvasileand...@gmail.com wrote:



 On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek pavel.kriva...@gmail.com
 wrote:

 Hi,

 thank you, Andrei.

 SmalltalkImage#metacelloPlatformAttributes are defined currently as
 (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x')
 for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over
 'common'.


 Ahaaa.
 Then I kind of misunderstood how platform attributes work.
 I need now to update some configurations from GTools.


 but this is an error.
 #metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon
 #pharo #'pharo5.x' #'pharo5.0.x’)

 then your configuration should be taking #common and not #pharo4.x

 cheers,
 Esteban



 Cheers,
 Andrei



 Cheers,
 -- Pavel

 2015-07-03 14:37 GMT+02:00 Andrei Chis chisvasileand...@gmail.com:

 Hi Pavel,

 I fixed the issue in the glamour repo and updated the configurations.

 Still I get the same error when trying to load ConfigurationOfGToolkit
 #stable into PharoIDE, as monticello
 seems to not resolve versions correctly.

 To reproduce first update all configurations:
 {   { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.
 { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
 { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.
 } do: [ :spec |
 Gofer new
 smalltalkhubUser: spec second project: spec third;
 package: spec first;
 load ].

 Then print:
 (ConfigurationOfGToolkitCore project version: #stable) record
 loadDirective

 ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it
 should be 3.0.4
 Now ConfigurationOfGToolkitCore#stable is defined as

 ConfigurationOfGToolkitCore stable: spec
 symbolicVersion: #'stable'
 spec for: #'common' version: '3.0.4'.
 spec for: #'pharo4.x' version: '3.0.2'.

 If I add an entry for pharo5.x then it works.
 Through I think it should also work without one.

 Cheers,
 Andrei


 On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek 
 pavel.kriva...@gmail.com wrote:

 Hi,

 I try to load GT tools to minimal Pharo image (with Morphic) and I
 have problems to do that because it has a dependency cycle it these 
 methods:

   GLMBrickDarkThemer#actionThemer
   GLMBrickThemer#actionThemer

 These methods try to extend classes in Glamour-Morphic-Brick package
 but they belong to Glamour-Core package that is prerequisite of the first
 package.

 The image without GT tools for testing is hrere:
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

 Cheers,
 -- Pavel

Re: [Pharo-dev] GToolkit loading problem

[Andrei Chis]

Is there bug report for this or should I create one?

cheers,
Andrei

On Fri, Jul 3, 2015 at 4:58 PM, Esteban Lorenzano esteba...@gmail.com
wrote:


 On 03 Jul 2015, at 16:42, Andrei Chis chisvasileand...@gmail.com wrote:



 On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek pavel.kriva...@gmail.com
 wrote:

 Hi,

 thank you, Andrei.

 SmalltalkImage#metacelloPlatformAttributes are defined currently as
 (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x')
 for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over
 'common'.


 Ahaaa.
 Then I kind of misunderstood how platform attributes work.
 I need now to update some configurations from GTools.


 but this is an error.
 #metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon #pharo
 #'pharo5.x' #'pharo5.0.x’)

 then your configuration should be taking #common and not #pharo4.x

 cheers,
 Esteban



 Cheers,
 Andrei



 Cheers,
 -- Pavel

 2015-07-03 14:37 GMT+02:00 Andrei Chis chisvasileand...@gmail.com:

 Hi Pavel,

 I fixed the issue in the glamour repo and updated the configurations.

 Still I get the same error when trying to load ConfigurationOfGToolkit
 #stable into PharoIDE, as monticello
 seems to not resolve versions correctly.

 To reproduce first update all configurations:
 {   { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.
 { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
 { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.
 } do: [ :spec |
 Gofer new
 smalltalkhubUser: spec second project: spec third;
 package: spec first;
 load ].

 Then print:
 (ConfigurationOfGToolkitCore project version: #stable) record
 loadDirective

 ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it
 should be 3.0.4
 Now ConfigurationOfGToolkitCore#stable is defined as

 ConfigurationOfGToolkitCore stable: spec
 symbolicVersion: #'stable'
 spec for: #'common' version: '3.0.4'.
 spec for: #'pharo4.x' version: '3.0.2'.

 If I add an entry for pharo5.x then it works.
 Through I think it should also work without one.

 Cheers,
 Andrei


 On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek pavel.kriva...@gmail.com
  wrote:

 Hi,

 I try to load GT tools to minimal Pharo image (with Morphic) and I have
 problems to do that because it has a dependency cycle it these methods:

   GLMBrickDarkThemer#actionThemer
   GLMBrickThemer#actionThemer

 These methods try to extend classes in Glamour-Morphic-Brick package
 but they belong to Glamour-Core package that is prerequisite of the first
 package.

 The image without GT tools for testing is hrere:
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

 Cheers,
 -- Pavel

Re: [Pharo-dev] GToolkit loading problem

[Esteban Lorenzano]

you need to create one :P

 On 08 Jul 2015, at 11:47, Andrei Chis chisvasileand...@gmail.com wrote:
 
 Is there bug report for this or should I create one?
 
 cheers,
 Andrei
 
 On Fri, Jul 3, 2015 at 4:58 PM, Esteban Lorenzano esteba...@gmail.com 
 mailto:esteba...@gmail.com wrote:
 
 On 03 Jul 2015, at 16:42, Andrei Chis chisvasileand...@gmail.com 
 mailto:chisvasileand...@gmail.com wrote:
 
 
 
 On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek pavel.kriva...@gmail.com 
 mailto:pavel.kriva...@gmail.com wrote:
 Hi, 
 
 thank you, Andrei.
 
 SmalltalkImage#metacelloPlatformAttributes are defined currently as 
 (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x') 
 for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over 
 'common'.
 
 Ahaaa.
 Then I kind of misunderstood how platform attributes work.
 I need now to update some configurations from GTools.
 
 but this is an error. 
 #metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon #pharo 
 #'pharo5.x' #'pharo5.0.x’)
 
 then your configuration should be taking #common and not #pharo4.x
 
 cheers, 
 Esteban
 
 
 
 Cheers,
 Andrei
  
 
 Cheers,
 -- Pavel 
 
 2015-07-03 14:37 GMT+02:00 Andrei Chis chisvasileand...@gmail.com 
 mailto:chisvasileand...@gmail.com:
 Hi Pavel,
 
 I fixed the issue in the glamour repo and updated the configurations.
 
 Still I get the same error when trying to load ConfigurationOfGToolkit 
 #stable into PharoIDE, as monticello
 seems to not resolve versions correctly.
 
 To reproduce first update all configurations:
 {   { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.
 { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
 { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.
  { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.
 } do: [ :spec |
 Gofer new
 smalltalkhubUser: spec second project: spec third;
 package: spec first;
 load ].
 
 Then print:
 (ConfigurationOfGToolkitCore project version: #stable) record loadDirective
 
 ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it 
 should be 3.0.4
 Now ConfigurationOfGToolkitCore#stable is defined as
 
 ConfigurationOfGToolkitCore stable: spec
  symbolicVersion: #'stable'
  spec for: #'common' version: '3.0.4'.
  spec for: #'pharo4.x' version: '3.0.2'.
 
 If I add an entry for pharo5.x then it works.
 Through I think it should also work without one.
 
 Cheers,
 Andrei
 
 
 On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek pavel.kriva...@gmail.com 
 mailto:pavel.kriva...@gmail.com wrote:
 Hi, 
 
 I try to load GT tools to minimal Pharo image (with Morphic) and I have 
 problems to do that because it has a dependency cycle it these methods:
 
   GLMBrickDarkThemer#actionThemer
   GLMBrickThemer#actionThemer
 
 These methods try to extend classes in Glamour-Morphic-Brick package but 
 they belong to Glamour-Core package that is prerequisite of the first 
 package. 
 
 The image without GT tools for testing is hrere: 
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/ 
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/
 
 Cheers,
 -- Pavel
 
 
 
 
 
 

Re: [Pharo-dev] GToolkit loading problem

[Andrei Chis]

Hi Pavel,

I fixed the issue in the glamour repo and updated the configurations.

Still I get the same error when trying to load ConfigurationOfGToolkit
#stable into PharoIDE, as monticello
seems to not resolve versions correctly.

To reproduce first update all configurations:
{   { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.
{ 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
{ 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.
{ 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.
{ 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.
{ 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.
} do: [ :spec |
Gofer new
smalltalkhubUser: spec second project: spec third;
package: spec first;
load ].

Then print:
(ConfigurationOfGToolkitCore project version: #stable) record loadDirective

ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it
should be 3.0.4
Now ConfigurationOfGToolkitCore#stable is defined as

ConfigurationOfGToolkitCore stable: spec
symbolicVersion: #'stable'
spec for: #'common' version: '3.0.4'.
spec for: #'pharo4.x' version: '3.0.2'.

If I add an entry for pharo5.x then it works.
Through I think it should also work without one.

Cheers,
Andrei


On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek pavel.kriva...@gmail.com
wrote:

 Hi,

 I try to load GT tools to minimal Pharo image (with Morphic) and I have
 problems to do that because it has a dependency cycle it these methods:

   GLMBrickDarkThemer#actionThemer
   GLMBrickThemer#actionThemer

 These methods try to extend classes in Glamour-Morphic-Brick package but
 they belong to Glamour-Core package that is prerequisite of the first
 package.

 The image without GT tools for testing is hrere:
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

 Cheers,
 -- Pavel

Re: [Pharo-dev] GToolkit loading problem

[Esteban Lorenzano]

 On 03 Jul 2015, at 16:42, Andrei Chis chisvasileand...@gmail.com wrote:
 
 
 
 On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek pavel.kriva...@gmail.com 
 mailto:pavel.kriva...@gmail.com wrote:
 Hi, 
 
 thank you, Andrei.
 
 SmalltalkImage#metacelloPlatformAttributes are defined currently as 
 (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x') 
 for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over 
 'common'.
 
 Ahaaa.
 Then I kind of misunderstood how platform attributes work.
 I need now to update some configurations from GTools.

but this is an error. 
#metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon #pharo 
#'pharo5.x' #'pharo5.0.x’)

then your configuration should be taking #common and not #pharo4.x

cheers, 
Esteban

 
 
 Cheers,
 Andrei
  
 
 Cheers,
 -- Pavel 
 
 2015-07-03 14:37 GMT+02:00 Andrei Chis chisvasileand...@gmail.com 
 mailto:chisvasileand...@gmail.com:
 Hi Pavel,
 
 I fixed the issue in the glamour repo and updated the configurations.
 
 Still I get the same error when trying to load ConfigurationOfGToolkit 
 #stable into PharoIDE, as monticello
 seems to not resolve versions correctly.
 
 To reproduce first update all configurations:
 {   { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.
 { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
 { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.
   { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.
 } do: [ :spec |
 Gofer new
 smalltalkhubUser: spec second project: spec third;
 package: spec first;
 load ].
 
 Then print:
 (ConfigurationOfGToolkitCore project version: #stable) record loadDirective
 
 ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it 
 should be 3.0.4
 Now ConfigurationOfGToolkitCore#stable is defined as
 
 ConfigurationOfGToolkitCore stable: spec
   symbolicVersion: #'stable'
   spec for: #'common' version: '3.0.4'.
   spec for: #'pharo4.x' version: '3.0.2'.
 
 If I add an entry for pharo5.x then it works.
 Through I think it should also work without one.
 
 Cheers,
 Andrei
 
 
 On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek pavel.kriva...@gmail.com 
 mailto:pavel.kriva...@gmail.com wrote:
 Hi, 
 
 I try to load GT tools to minimal Pharo image (with Morphic) and I have 
 problems to do that because it has a dependency cycle it these methods:
 
   GLMBrickDarkThemer#actionThemer
   GLMBrickThemer#actionThemer
 
 These methods try to extend classes in Glamour-Morphic-Brick package but they 
 belong to Glamour-Core package that is prerequisite of the first package. 
 
 The image without GT tools for testing is hrere: 
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/ 
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/
 
 Cheers,
 -- Pavel
 
 
 
 

Re: [Pharo-dev] GToolkit loading problem

[Andrei Chis]

On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek pavel.kriva...@gmail.com
wrote:

 Hi,

 thank you, Andrei.

 SmalltalkImage#metacelloPlatformAttributes are defined currently as
 (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x')
 for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over
 'common'.


Ahaaa.
Then I kind of misunderstood how platform attributes work.
I need now to update some configurations from GTools.


Cheers,
Andrei



 Cheers,
 -- Pavel

 2015-07-03 14:37 GMT+02:00 Andrei Chis chisvasileand...@gmail.com:

 Hi Pavel,

 I fixed the issue in the glamour repo and updated the configurations.

 Still I get the same error when trying to load ConfigurationOfGToolkit
 #stable into PharoIDE, as monticello
 seems to not resolve versions correctly.

 To reproduce first update all configurations:
 {   { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.
 { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
 { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.
 { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.
 } do: [ :spec |
 Gofer new
 smalltalkhubUser: spec second project: spec third;
 package: spec first;
 load ].

 Then print:
 (ConfigurationOfGToolkitCore project version: #stable) record
 loadDirective

 ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it
 should be 3.0.4
 Now ConfigurationOfGToolkitCore#stable is defined as

 ConfigurationOfGToolkitCore stable: spec
 symbolicVersion: #'stable'
 spec for: #'common' version: '3.0.4'.
 spec for: #'pharo4.x' version: '3.0.2'.

 If I add an entry for pharo5.x then it works.
 Through I think it should also work without one.

 Cheers,
 Andrei


 On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek pavel.kriva...@gmail.com
 wrote:

 Hi,

 I try to load GT tools to minimal Pharo image (with Morphic) and I have
 problems to do that because it has a dependency cycle it these methods:

   GLMBrickDarkThemer#actionThemer
   GLMBrickThemer#actionThemer

 These methods try to extend classes in Glamour-Morphic-Brick package but
 they belong to Glamour-Core package that is prerequisite of the first
 package.

 The image without GT tools for testing is hrere:
 https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

 Cheers,
 -- Pavel

[Pharo-dev] GToolkit loading problem

[Pavel Krivanek]

Hi,

I try to load GT tools to minimal Pharo image (with Morphic) and I have
problems to do that because it has a dependency cycle it these methods:

  GLMBrickDarkThemer#actionThemer
  GLMBrickThemer#actionThemer

These methods try to extend classes in Glamour-Morphic-Brick package but
they belong to Glamour-Core package that is prerequisite of the first
package.

The image without GT tools for testing is hrere:
https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

Cheers,
-- Pavel

Re: [Pharo-dev] GToolkit in Pharo 4?

[Yuriy Tymchuk]

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 maxle...@gmail.com wrote:
 
 Ok, thanks.
 
 
 On 28.07.2014, at 22:37, Stephan Eggermont step...@stack.nl 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
 
 
 

Re: [Pharo-dev] 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 yuriy.tymc...@me.com 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 maxle...@gmail.com wrote:
 
  Ok, thanks.
 
 
  On 28.07.2014, at 22:37, Stephan Eggermont step...@stack.nl 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
 
 
 

Re: [Pharo-dev] GToolkit in Pharo 4?

[Tudor Girba]

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 chisvasileand...@gmail.com
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 yuriy.tymc...@me.com
 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 maxle...@gmail.com wrote:
 
  Ok, thanks.
 
 
  On 28.07.2014, at 22:37, Stephan Eggermont step...@stack.nl 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
 
 
 






-- 
www.tudorgirba.com

Every thing has its own flow

Re: [Pharo-dev] GToolkit

[Tudor Girba]

Hi Estaban,

On Mon, Sep 15, 2014 at 3:30 AM, Esteban A. Maringolo emaring...@gmail.com
wrote:

 2014-09-14 15:53 GMT-03:00 Tudor Girba tu...@tudorgirba.com:
  Hi Phil,

  It would be cool to know the reasons why people have to use other tools.
  Perhaps we can do something about it.

 If it involves text edition or manipulation, I use external tools
 because of the lack of certain features in Pharo workspaces (or even
 syntax highlighting limits) or due to the comfort I find in using the
 same key bindings/shortcuts I use everywhere to edit a csv file, SQL
 script, chunk or whatever. That's one of the reasons. :)


Could we go into details here? I am genuinely interested in collected these
use cases.

As noted before, syntax highlighting is now supported in GToolkit via
Rubric. What kind of keybindings are we talking about?

Another one is that I found the option to do things externally to be
 safer than relying on a unique tool to do all the tasks.
 Rule of Composition and Rule of Modularity according to the Unix
 Philosophy.

Not to mention the Rule of Parsimony: Write a big program only when
 it is clear by demonstration that nothing else with do. :)


I think we should not mistaken big for powerful and neither should we do it
the other way around. If there is anything we show in Pharo is that we can
do small and powerful.

But, please keep in mind that I am referring to activities that you would
like to do without leaving your objects.

Cheers,
Doru



 Regards!

 Esteban A. Maringolo




-- 
www.tudorgirba.com

Every thing has its own flow

Re: [Pharo-dev] GToolkit

[Esteban A. Maringolo]

2014-09-15 14:50 GMT-03:00 Tudor Girba tu...@tudorgirba.com:
 Hi Estaban,

 On Mon, Sep 15, 2014 at 3:30 AM, Esteban A. Maringolo emaring...@gmail.com
 wrote:

 2014-09-14 15:53 GMT-03:00 Tudor Girba tu...@tudorgirba.com:
  Hi Phil,

  It would be cool to know the reasons why people have to use other tools.
  Perhaps we can do something about it.

 If it involves text edition or manipulation, I use external tools
 because of the lack of certain features in Pharo workspaces (or even
 syntax highlighting limits) or due to the comfort I find in using the
 same key bindings/shortcuts I use everywhere to edit a csv file, SQL
 script, chunk or whatever. That's one of the reasons. :)

 Could we go into details here? I am genuinely interested in collected these
 use cases.

Sure.

 As noted before, syntax highlighting is now supported in GToolkit via
 Rubric.

I haven't used Rubric. So I can't really talk about it.

But text editing speed in Pharo is perceivable slower than, ej,
Notepad++ or gVim.
It won't affect the normal use, because most methods are small, but as
the code gets larger it slows down (exponentially?).

 What kind of keybindings are we talking about?

I'm referring to common Windows keybindings: Ctrl+arrow, Ctrl+Home,
Ctrl+Shift+End, Ctrl+F, Ctrl+H, Ctrl+A, etc. Some are supported by
Pharo, others don't.

Regards!

Esteban A. Maringolo

Re: [Pharo-dev] GToolkit

[Tudor Girba]

Hi Phil,

Thanks for the kind words. I am really happy this experience makes it to
the core of Pharo.

Indeed, the goal is to offer a comprehensive set of arguments to get people
to not leave the environment. I myself, do my best to not leave it. As soon
as I notice that I have to leave the environment, I try to build the tools
to help me not do it. For example, this is how the database, file and
Pillar support were born.

It would be cool to know the reasons why people have to use other tools.
Perhaps we can do something about it.

Cheers,
Doru

On Fri, Sep 12, 2014 at 6:14 PM, p...@highoctane.be p...@highoctane.be
wrote:

 I've been working in a data acquisition scenario today and GToolkit proved
 to be of immense help.

 Working in the live application, looking around for data (including file
 contents), and inspecting it all + live debugging is really a sweet
 experience.

 With CommandShell I may not have to leave the environment...


 Phil




-- 
www.tudorgirba.com

Every thing has its own flow

Re: [Pharo-dev] GToolkit

[Esteban A. Maringolo]

2014-09-14 15:53 GMT-03:00 Tudor Girba tu...@tudorgirba.com:
 Hi Phil,

 It would be cool to know the reasons why people have to use other tools.
 Perhaps we can do something about it.

If it involves text edition or manipulation, I use external tools
because of the lack of certain features in Pharo workspaces (or even
syntax highlighting limits) or due to the comfort I find in using the
same key bindings/shortcuts I use everywhere to edit a csv file, SQL
script, chunk or whatever. That's one of the reasons. :)

Another one is that I found the option to do things externally to be
safer than relying on a unique tool to do all the tasks.
Rule of Composition and Rule of Modularity according to the Unix
Philosophy.
Not to mention the Rule of Parsimony: Write a big program only when
it is clear by demonstration that nothing else with do. :)

Regards!

Esteban A. Maringolo

[Pharo-dev] GToolkit

[p...@highoctane.be]

I've been working in a data acquisition scenario today and GToolkit proved
to be of immense help.

Working in the live application, looking around for data (including file
contents), and inspecting it all + live debugging is really a sweet
experience.

With CommandShell I may not have to leave the environment...


Phil

Re: [Pharo-dev] GToolkit

[kilon alios]

maybe make a video and upload to youtube of your workflow , I am sure I
will learn something from it :)

On Fri, Sep 12, 2014 at 7:14 PM, p...@highoctane.be p...@highoctane.be
wrote:

 I've been working in a data acquisition scenario today and GToolkit proved
 to be of immense help.

 Working in the live application, looking around for data (including file
 contents), and inspecting it all + live debugging is really a sweet
 experience.

 With CommandShell I may not have to leave the environment...


 Phil

Re: [Pharo-dev] GToolkit

[Andrei Chis]

On Fri, Sep 12, 2014 at 6:29 PM, kilon alios kilon.al...@gmail.com wrote:

 maybe make a video and upload to youtube of your workflow , I am sure I
 will learn something from it :)


+1




 On Fri, Sep 12, 2014 at 7:14 PM, p...@highoctane.be p...@highoctane.be
 wrote:

 I've been working in a data acquisition scenario today and GToolkit
 proved to be of immense help.

 Working in the live application, looking around for data (including file
 contents), and inspecting it all + live debugging is really a sweet
 experience.

 With CommandShell I may not have to leave the environment...


 Phil

Re: [Pharo-dev] GToolkit in Pharo 4?

[Max Leske]

Ok, thanks.


On 28.07.2014, at 22:37, Stephan Eggermont step...@stack.nl 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
 

[Pharo-dev] 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

Re: [Pharo-dev] GToolkit in Pharo 4?

[Stephan Eggermont]

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