23 Mar
2015
23 Mar
'15
6:47 p.m.
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
23 Mar
23 Mar
6:49 p.m.
Also I am interested only in presenter for Roassal, is there separate
configuration for that?
On Mon, Mar 23, 2015 at 6:47 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
6:53 p.m.
New subject: [Pharo-users] loading Glamour in Pharo 4
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update the
tools that depend on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
If you are interested just in the Roassal presented you could try and only
load the package Glamour-Roassal2-Presentations + Roassal.
However, depending on what changes you might need to also update glamour.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 6:47 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
8:47 p.m.
New subject: [Pharo-users] loading Glamour in Pharo 4
I think it is pretty telling that 2 different persons basically had the same issue in 3
days. Should this issue be considered as something to have fixed for the Pharo 4 release?
On Mar 23, 2015, at 14:53, Andrei Chis
<chisvasileandrei(a)gmail.com> wrote:
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update the tools that depend
on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
If you are interested just in the Roassal presented you could try and only load the
package Glamour-Roassal2-Presentations + Roassal.
However, depending on what changes you might need to also update glamour.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 6:47 PM, Peter Uhnák <i.uhnak(a)gmail.com
<mailto:i.uhnak@gmail.com>> wrote:
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
9:06 p.m.
New subject: [Pharo-users] loading Glamour in Pharo 4
On 23-03-15 20:47, Johan Fabry wrote:
I think it is pretty telling that 2 different persons
basically had
the same issue in 3 days. Should this issue be considered as something
to have fixed for the Pharo 4 release?
That would be nice. Do we know how it should
be fixed?
It is something I expect people to run into rather often.
Stephan
On Mar 23, 2015, at 14:53, Andrei Chis
<chisvasileandrei(a)gmail.com
<mailto:chisvasileandrei@gmail.com>> wrote:
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update
the tools that depend on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
If you are interested just in the Roassal presented you could try and
only load the package Glamour-Roassal2-Presentations + Roassal.
However, depending on what changes you might need to also update glamour.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 6:47 PM, Peter Uhnák <i.uhnak(a)gmail.com
<mailto:i.uhnak@gmail.com>> wrote:
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand:
#addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry>
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:10 p.m.
New subject: [Pharo-dev] Re: [Pharo-users] loading Glamour in Pharo 4
One can load a newer version of monticello to be able to force the loading
of dependent configurations.
Still this would not fix the underlying issue: one cannot update a library
from the system without also updating the tools that depend on it.
For example, if morphic would be loaded through a configuration you could
not load the latest version of morphic without also loading the latest
version of all the tools.
The best solution could be to not depend on glamour #development unless
really needed.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 9:06 PM, stephan <stephan(a)stack.nl> wrote:
On 23-03-15 20:47, Johan Fabry wrote:
I think it is pretty telling that 2 different persons basically had the
same issue in 3 days. Should this issue be considered as something to have
fixed for the Pharo 4 release?
That would be nice. Do we know how it should be fixed?
It is something I expect people to run into rather often.
Stephan
On Mar 23, 2015, at 14:53, Andrei Chis <chisvasileandrei(a)gmail.com>
wrote:
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update the
tools that depend on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
If you are interested just in the Roassal presented you could try and
only load the package Glamour-Roassal2-Presentations + Roassal.
However, depending on what changes you might need to also update glamour.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 6:47 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:40 p.m.
New subject: [Pharo-dev] Re: [Pharo-users] loading Glamour in Pharo 4
Hi,
After the release of Pharo 4, we will release Moose with all stable
configurations. This should work afterwards.
Then we will move the development of Moose to Pharo 5.
Cheers,
Doru
On Mon, Mar 23, 2015 at 9:10 PM, Andrei Chis <chisvasileandrei(a)gmail.com>
wrote:
One can load a newer version of monticello to be able
to force the loading
of dependent configurations.
Still this would not fix the underlying issue: one cannot update a library
from the system without also updating the tools that depend on it.
For example, if morphic would be loaded through a configuration you could
not load the latest version of morphic without also loading the latest
version of all the tools.
The best solution could be to not depend on glamour #development unless
really needed.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 9:06 PM, stephan <stephan(a)stack.nl> wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
On 23-03-15 20:47, Johan Fabry wrote:
I think it is pretty telling that 2 different persons basically had the
same issue in 3 days. Should this issue be considered as something to have
fixed for the Pharo 4 release?
That would be nice. Do we know how it should be fixed?
It is something I expect people to run into rather often.
Stephan
On Mar 23, 2015, at 14:53, Andrei Chis <chisvasileandrei(a)gmail.com>
wrote:
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update the
tools that depend on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
If you are interested just in the Roassal presented you could try and
only load the package Glamour-Roassal2-Presentations + Roassal.
However, depending on what changes you might need to also update glamour.
Cheers,
Andrei
On Mon, Mar 23, 2015 at 6:47 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
After loading Glamour dev in Pharo 40
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new
smalltalkhubUser: 'Moose' project: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDevelopment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
when I try opening Playground I get
AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic:
And Spotter throws
GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction:
Am I missing some extra dependency?
Thanks,
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
27 Mar
27 Mar
6:44 p.m.
New subject: [Pharo-users] loading Glamour in Pharo 4
Running the update script in the latest image (40585) causes a DNU: Instances of
UndefinedObject are not indexable. :-(
I can only see the stack trace in the pre-debugger. Clicking in the pre-debugger or trying
to close a window causes the DNU again. The problem seems to be in
RubFindReplaceService>>textArea:
On Mar 23, 2015, at 14:53, Andrei Chis
<chisvasileandrei(a)gmail.com> wrote:
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update the tools that depend
on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
6:48 p.m.
New subject: [Pharo-users] loading Glamour in Pharo 4
The same problem appeared on jenkins now. To be fixed really soon.
Cheers,
Andrei
On Fri, Mar 27, 2015 at 6:44 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
Running the update script in the latest image (40585)
causes a DNU:
Instances of UndefinedObject are not indexable. :-(
I can only see the stack trace in the pre-debugger. Clicking in the
pre-debugger or trying to close a window causes the DNU again. The problem
seems to be in RubFindReplaceService>>textArea:
On Mar 23, 2015, at 14:53, Andrei Chis <chisvasileandrei(a)gmail.com> wrote:
There are several tools in Pharo that depend on Glamour.
If you update glamour to the latest version you also need to update the
tools that depend on it.
This script updated everything:
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. '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 ].
ConfigurationOfGToolkitCore loadDevelopment.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
3324
days inactive
3328
days old
8 comments
5 participants
participants (5)
-
Andrei Chis -
Johan Fabry -
Peter Uhnák -
stephan -
Tudor Girba