search

Metacello / metacello-wiki

Automatically exported from code.google.com/p/metacello
1 stars 0 forks source link

Help System requirements have changed #139

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I guess the Help System has been in cluded in pharo 1.3. Presumably the right 
answer is to fix the ConfigurationOfHelpSystem so that it works correctly in 
1.3 (by not loading anything), but I'll have to look at the issue in more 
detail to figure this one out completely ...

See: http://code.google.com/p/pharo/issues/detail?id=4160 for details

Original issue reported on code.google.com by henrichs...@gmail.com on 13 May 2011 at 8:28

GoogleCodeExporter commented 9 years ago 
Hi Dale. So, it is not even enough to remove the includes of Metacello-Help  in 
ConfigurationOfPharo, because this is included in the default on 
ConfigurationOfMetacello. And so, it is included when doing the 
#ensureMetacello. 

The problem is that in ConfigurationOFMetacello you are doing for #squeakCommon 
a "spec     group: 'default' with: #('Metacello-Help'); "   but in Pharo we have 
our Help-System.  So...what I did was to remove that from #squeakCommon and add 
to #squeak this 

"spec group: 'default' with: #('Metacello-Help');   
            yourself.
            ].

Here I attach the changeset if you agree.

Original comment by marianopeck on 14 May 2011 at 5:34

Attachments:

GoogleCodeExporter commented 9 years ago 
It looks like Pharo Issue 4160 
(http://code.google.com/p/pharo/issues/detail?id=4160) was addressed without 
requiring any Metacello configuration changes (ShortcutsHelp was apparently the 
culprit).

Just this morning I have loaded Metacello in Pharo1.3-13233 with no ill 
affects, which is the way it is supposed to work - The mcz packages that are 
preloaded into PharoCore1.3 are _later_ versions than called for in the 
ConfigurationOfHelpSystem and Metacello does not load the earlier versions, so 
there is no problem.

Gofer is also required by Metacello and the ConfigurationOfGofer has been 
triggered by a load since about version 1.1, but because the mcz files are 
later versions nothing has had to be done ...

Eventually, I should change the config for both Gofer and the help system, so I 
will leave this bug open until that is done...

Original comment by henrichs...@gmail.com on 6 Jun 2011 at 8:29

GoogleCodeExporter commented 9 years ago

Original comment by henrichs...@gmail.com on 18 Jan 2012 at 7:01