Issue 3447 in pharo: Do we need to menu entry "Shout Workspace"?

Status: Accepted
Owner: marcus.denker
Labels: Milestone-1.2-DevImage

New issue 3447 by marcus.denker: Do we need to menu entry "Shout Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

The normal workspace seems to have syntax hihjligting alreaday

Comment #1 on issue 3447 by marianopeck: Do we need to menu entry "Shout  
Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

no, we don't need. The normal workspace entry IS/Has to be   a  
ShoutWorkspace. But the label in the menu should be just Workspace

On Fri, 17 Dec 2010, [hidden email] wrote:

Why don't you give ShoutCore
(http://source.squeak.org/trunk/ShoutCore-ul.27.mcz ) a try? It works well
in Squeak. There's a menu item to enable/disable Shout in the workspace,
besides the global preference (not Preference) which applies to all
workspaces. It also has the features of ShoutMonticello. It could be
developed as a shared package between Pharo and Squeak, like VMMaker or
OCompletion. What do you think?


Levente

Hi levente

Good idea. Now I do not have cycle to check if this is ok for pharo-dev but we should check that.
By construction and contrary to some people may think we are not against Squeak: You do not build a cool vision by opposition and it is not fun in the mid term. This is just that we want to avoid to have constraints and endless negotiation and ranting. Now of course if there is a fit where we can work together in positive energy, this is more than welcome, so thanks for the proposal.
Ideally I would like to avoid to have all pharo packages in the pharo repository and I would love to manage a pharo system with a nice metacello description but we should do it first to make it happen. and in such a setup shared/components with their own lifecycle makes a lot of sense.

Stef
PS: my goal is to have fun and learn a lot and create an eco system with people making a living out of smalltalk like software

Updates:
        Status: Fixed

Comment #2 on issue 3447 by luc.fabresse: Do we need to menu entry "Shout  
Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

First menu entry 'Workspace' open a shout workspace
I think this is the good one (registered by WorldState  
class>>mostUsedToolsOn:) and same entry as Core

The second menu entry name 'Shout Workspace' is directly registered by  
SHWorkspace class>>shoutWorkspaceOn:.
It should be deactivated in dev.

done in the attached CS by commenting the pragma

Attachments:
        SHWorkspace class-shoutWorkspaceOn.st  368 bytes

Comment #3 on issue 3447 by guillermopolito: Do we need to menu  
entry "Shout Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

Why not removing that method from scratch?

Comment #4 on issue 3447 by luc.fabresse: Do we need to menu entry "Shout  
Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

yes we can do that too ;-)

Comment #5 on issue 3447 by guillermopolito: Do we need to menu  
entry "Shout Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

Mariano said:

Luc, in the cae of 3447, you should commit to the Shout repo since this is  
not part ofpharo core.
BTW....which version of ShoutWorkspace was being installed...because I  
already fixed that in:

Name: ShoutWorkspace.1-maiano.6
Author: maiano
Time: 12 May 2010, 7:53:35 pm
UUID: 8265a4c8-d212-4ac1-b2d5-79b5722ed9c3
Ancestors: ShoutWorkspace.1-Alexandre_Bergel.5

Removed menuCommandOn: aBuilder  from ShoutWorkspace as such item is  
already in the manu (in the part of most common tools) together with  
SystemBrowser, Test Runner and Monticello Browser. If they are not there,  
then they are not under "Tools".


cheers

Maybe we just have to merge a lost version :)

Comment #6 on issue 3447 by guillermopolito: Do we need to menu  
entry "Shout Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

Ok, I integrated it in the last configuration version.  It may be available  
in the next build :)

Updates:
        Status: Closed

Comment #7 on issue 3447 by marcus.denker: Do we need to menu entry "Shout  
Workspace"?
http://code.google.com/p/pharo/issues/detail?id=3447

in build starting 23.12.2010