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 [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
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 <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Peter Uhnak
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 <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] 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 list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On 23-03-15 20:47, Johan Fabry wrote:
That would be nice. Do we know how it should be fixed? It is something I expect people to run into rather often. Stephan
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
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 <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
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 <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Andrei Chis
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:
---> 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 list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
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 <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |