March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: Https Url in Pharo 1.2

by StÃ©phane Ducasse

thanks for the information. Stef On Mar 6, 2011, at 6:10 PM, Sven Van Caekenberghe wrote: > > On 06 Mar 2011, at 09:59, StÃ©phane Ducasse wrote: > >> What is the status? >> Now we should clearly have a solution in the future. > > I tried it before and I got it working on Pharo/Cog/MacOSX a little bit, but it wasn't a 'it just works' experience. > I also looked at the plugin's C code and noticed that it wasn't complete on Mac OS X and not even on Linux. > The interaction between the plugin and the Smalltalk code and especially the integration with SocketStream was not very encouraging. > > Sven > > > >

March 6, 2011

Re: [Pharo-project] Pharo 1.2 and test failures

by Marcus Denker

On Mar 6, 2011, at 11:32 AM, Norbert Hartl wrote: > well, I provided a fix already. And it seems that 3 mails to the list and the mentioning withing this mail does not make it visible. It needs an integration step or just to load the newest ImageForDevelopers > > How to tell? > I think the ConfigurationOfPharo needs to be updated... I am all in all not happy with the process we have... we should fix it. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 6, 2011

Re: [Pharo-project] a slim holiday present, cpic

by Eliot Miranda

Argh! Here's a fix to a bad bug in the last version (cp "$1.image" "$1.changes" "$d" => cp "$1.image" "$1.changes" "$2")!! -------8<------- #!/bin/sh # copy image and changes force=0 if [ "$1" = -f ]; then force=1 shift fi if [ $# != 2 -o "$1" = "-?" -o "$1" = --help ]; then echo "usage: $0 [-f] image-name-no-ext [image-name-no-ext|dir]" test $# != 2 && exit 1 exit 0 fi if [ -f "$2.image" -o -f "$2.changes" ]; then if [ "$force" = 0 ]; then echo "$2.image and/or $2.changes already exist." 1>&2 exit 1 fi elif [ -d "$2" ]; then if [ -f "$2/`basename "$1"`.image" -o -f "$2/`basename "$1"`.changes" ]; then if [ "$force" = 0 ]; then echo "$2/`basename "$1"`.image and/or $2/`basename "$1"`.changes already exist." 1>&2 exit 1 fi fi cp "$1.image" "$1.changes" "$2" exit 0 fi cp "$1.image" "$2.image" cp "$1.changes" "$2.changes" On Fri, Dec 17, 2010 at 2:33 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi All, > > don't know if this is useful to you or whether you've already written > it yourself but I finally caved and wrote a shell command that copies an > image/changes file pair, replacing the hundreds of times I've issued the two > parallel commands, cpic = copy image and changes. Happy holidays > -------8<------- > #!/bin/sh > # copy image and changes > force=0 > if [ "$1" = -f ]; then > force=1 > shift > fi > if [ $# != 2 -o "$1" = "-?" -o "$1" = --help ]; then > echo "usage: $0 [-f] image-name-no-ext [image-name-no-ext|dir]" > test $# != 2 && exit 1 > exit 0 > fi > if [ -f "$2.image" -o -f "$2.changes" ]; then > if [ "$force" = 0 ]; then > echo "$2.image and/or $2.changes already exist." 1>&2 > exit 1 > fi > elif [ -d "$2" ]; then > if [ -f "$2/$1.image" -o -f "$2/$1.changes" ]; then > if [ "$force" = 0 ]; then > echo "$2/$1.image and/or $2/$1.changes already exist." 1>&2 > exit 1 > fi > fi > cp "$1.image" "$1.changes" "$d" > exit 0 > fi > cp "$1.image" "$2.image" > cp "$1.changes" "$2.changes" >

March 6, 2011

Re: [Pharo-project] a slim holiday present, cpic

by Eliot Miranda

Here's an update to cpic that fixes cases where one copies images from other than the current directory -------8<------- #!/bin/sh # copy image and changes force=0 if [ "$1" = -f ]; then force=1 shift fi if [ $# != 2 -o "$1" = "-?" -o "$1" = --help ]; then echo "usage: $0 [-f] image-name-no-ext [image-name-no-ext|dir]" test $# != 2 && exit 1 exit 0 fi if [ -f "$2.image" -o -f "$2.changes" ]; then if [ "$force" = 0 ]; then echo "$2.image and/or $2.changes already exist." 1>&2 exit 1 fi elif [ -d "$2" ]; then if [ -f "$2/`basename "$1"`.image" -o -f "$2/`basename "$1"`.changes" ]; then if [ "$force" = 0 ]; then echo "$2/`basename "$1"`.image and/or $2/`basename "$1"`.changes already exist." 1>&2 exit 1 fi fi cp "$1.image" "$1.changes" "$d" exit 0 fi cp "$1.image" "$2.image" cp "$1.changes" "$2.changes" On Fri, Dec 17, 2010 at 2:33 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi All, > > don't know if this is useful to you or whether you've already written > it yourself but I finally caved and wrote a shell command that copies an > image/changes file pair, replacing the hundreds of times I've issued the two > parallel commands, cpic = copy image and changes. Happy holidays > -------8<------- > #!/bin/sh > # copy image and changes > force=0 > if [ "$1" = -f ]; then > force=1 > shift > fi > if [ $# != 2 -o "$1" = "-?" -o "$1" = --help ]; then > echo "usage: $0 [-f] image-name-no-ext [image-name-no-ext|dir]" > test $# != 2 && exit 1 > exit 0 > fi > if [ -f "$2.image" -o -f "$2.changes" ]; then > if [ "$force" = 0 ]; then > echo "$2.image and/or $2.changes already exist." 1>&2 > exit 1 > fi > elif [ -d "$2" ]; then > if [ -f "$2/$1.image" -o -f "$2/$1.changes" ]; then > if [ "$force" = 0 ]; then > echo "$2/$1.image and/or $2/$1.changes already exist." 1>&2 > exit 1 > fi > fi > cp "$1.image" "$1.changes" "$d" > exit 0 > fi > cp "$1.image" "$2.image" > cp "$1.changes" "$2.changes" >

March 6, 2011

Re: [Pharo-project] Issue 1915 in pharo: Making ToolSet more flexible

by pharo＠googlecode.com

Comment #9 on issue 1915 by siguc...(a)gmail.com: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915 (No comment was entered for this change.) Attachments: FixingToolsReferences.1.cs 24.5 KB

March 6, 2011

[Pharo-project] Issue 3788 in pharo: Should fix all the menu category of ToolRegistry and deprecate the methods.

by pharo＠googlecode.com

Status: Accepted Owner: siguc...(a)gmail.com Labels: Milestone-1.3 New issue 3788 by siguc...(a)gmail.com: Should fix all the menu category of ToolRegistry and deprecate the methods. http://code.google.com/p/pharo/issues/detail?id=3788 The category 'menu' is just for backward compatibility. The methods should be deprecated.

March 6, 2011

[Pharo-project] Issue 3787 in pharo: Project current setChangeSet: aChangeSet.

by pharo＠googlecode.com

Status: Accepted Owner: siguc...(a)gmail.com Labels: Milestone-1.3 New issue 3787 by siguc...(a)gmail.com: Project current setChangeSet: aChangeSet. http://code.google.com/p/pharo/issues/detail?id=3787 Looks suspicious. Probably a left over.

March 6, 2011

Re: [Pharo-project] Fwd: Https Url in Pharo 1.2

by Sven Van Caekenberghe

On 06 Mar 2011, at 09:59, StÃ©phane Ducasse wrote: > What is the status? > Now we should clearly have a solution in the future. I tried it before and I got it working on Pharo/Cog/MacOSX a little bit, but it wasn't a 'it just works' experience. I also looked at the plugin's C code and noticed that it wasn't complete on Mac OS X and not even on Linux. The interaction between the plugin and the Smalltalk code and especially the integration with SocketStream was not very encouraging. Sven

March 6, 2011

Re: [Pharo-project] Issue 1915 in pharo: Making ToolSet more flexible

by pharo＠googlecode.com

Updates: Status: Fixed Comment #8 on issue 1915 by siguc...(a)gmail.com: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915 browseDirectToolReferences "Browse all direct references of all of my registered tools. Useful for converting calls like: MyTool foo into: Smalltalk tools myTool foo " | bindings sn | bindings := tools values select: [:each | each value isBehavior ] thenCollect: [:each | each value binding ]. bindings := bindings copyWith: (Smalltalk bindingOf: #ToolSet). sn := SystemNavigation default. ^ sn browseMessageList: ( sn allMethodsSelect: [:m | (m literals allButLast select: [:lit| lit isVariableBinding ]) includesAnyOf: bindings ] ) name: 'All direct references to tools to fix'

March 6, 2011

Re: [Pharo-project] Issue 1915 in pharo: Making ToolSet more flexible

by pharo＠googlecode.com

Comment #7 on issue 1915 by siguc...(a)gmail.com: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915 We should state that the menu category is for backward compatibility and we should remove them afterwards.

March 6, 2011