- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Command Shell in Pharo 4

by David T. Lewis

On Tue, Oct 28, 2014 at 11:09:24AM +0200, kilon alios wrote: > So I decided to give Command Shell a spin using today's Pharo 4 release and > I have some issues > > *a) The text is too small* . After some investigation I found that the size > is defined in ShellWindowMorph class>>textStyle > > textStyle > "A fixed width font for the text morph" > > ^ (TextStyle named: 'DefaultFixedTextStyle') > ifNil: [TextStyle default] > > I assume there is a reason why a fixed size font is used . I changed it to > just TextStyle default and works fine. The intent is to provide a readable fixed font for a "text terminal" window. It does not seem to work on Pharo. TextStyle named: 'DefaultFixedTextStyle' does not look like a fixed font to me, and as you say it is too small to be readable. I'm not too familiar with the font handling in Pharo, so if you can suggest a font that works better, that would be great. > > *b) no ~ folder.* Trying a "cd ~" command does not work it complains that > the folder does not exist. CommandShell is a partial simulation of a unix shell. Many features of a real shell are not implemented. In this case, the $~ character is not being interpreted as it would be in a real shell, instead it is simply treated as a text character, so it does nothing at all. > > *c) not able to run shell scripts or other scripts* (eg. python scripts). > For example if I try "./blender.sh" even though this command works fine in > my macos terminal and iTerm2 , it does not work in Command Shell and > complains that it cannot find the command. It may be that default directory conventions are different either on Pharo (compared to Squeak) or on OS X (compared to generic unix). I don't have a Mac so I'm afraid that I am guessing at this. FYI, CommandShell is keeping track of its own notion of the "current working directory". If you do a 'pwd' command in your command shell, it should show you what the command shell thinks is its current working directory. This also works in Widows by the way, which was something of a challenge handling those "drive letters" ;-) HTH, Dave

Oct. 28, 2014

How to ask files to the user?

by Sebastian Tleye

Hi, I need to ask files to the user. I know that one way to do it is as follows UIManager default chooseFullFileNameMatching: nil label: 'Bla bla'. but this does not let the user to choose multiple files. it allows only one. How can I do to allow selection of multiple files? Thanks

Oct. 28, 2014

Re: [Pharo-dev] Command Shell in Pharo 4

by kilon alios

also I tried this $ bash blender.sh Opening Blender ... blender.sh: line 2: cd: /Users/kilon/Library/Application Support/Pharo/images/Ephestos 28-10-2014/blender-build/build_darwin/bin/blender.app/Contents/macos: No such file or directory The file /Users/kilon/blender does not exist. Closed Blender. so it seems that even using the bash command does not work because it appends the path of the pharo image instead of the path of the current directory as it should. Because if I do $ pwd /Users/kilon which is the correct path that I always execute my script from. On Tue, Oct 28, 2014 at 11:09 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > So I decided to give Command Shell a spin using today's Pharo 4 release > and I have some issues > > *a) The text is too small* . After some investigation I found that the > size is defined in ShellWindowMorph class>>textStyle > > textStyle > "A fixed width font for the text morph" > > ^ (TextStyle named: 'DefaultFixedTextStyle') > ifNil: [TextStyle default] > > I assume there is a reason why a fixed size font is used . I changed it to > just TextStyle default and works fine. > > *b) no ~ folder.* Trying a "cd ~" command does not work it complains that > the folder does not exist. > > *c) not able to run shell scripts or other scripts* (eg. python scripts). > For example if I try "./blender.sh" even though this command works fine in > my macos terminal and iTerm2 , it does not work in Command Shell and > complains that it cannot find the command. >

Oct. 28, 2014

Command Shell in Pharo 4

by kilon alios

So I decided to give Command Shell a spin using today's Pharo 4 release and I have some issues *a) The text is too small* . After some investigation I found that the size is defined in ShellWindowMorph class>>textStyle textStyle "A fixed width font for the text morph" ^ (TextStyle named: 'DefaultFixedTextStyle') ifNil: [TextStyle default] I assume there is a reason why a fixed size font is used . I changed it to just TextStyle default and works fine. *b) no ~ folder.* Trying a "cd ~" command does not work it complains that the folder does not exist. *c) not able to run shell scripts or other scripts* (eg. python scripts). For example if I try "./blender.sh" even though this command works fine in my macos terminal and iTerm2 , it does not work in Command Shell and complains that it cannot find the command.

Oct. 28, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40335 Home: https://github.com/pharo-project/pharo-core

Oct. 28, 2014

[pharo-project/pharo-core] b9d8c1: 40335

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: b9d8c19a9268f514a1a086e09bf6e1915d0e314a https://github.com/pharo-project/pharo-core/commit/b9d8c19a9268f514a1a086e0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-28 (Tue, 28 Oct 2014) Changed paths: M RecentSubmissions.package/RecentMessageList.class/instance/initialization/registerToAnnouncements.st M Refactoring-Critics.package/RBAssignmentOnBlockArgumentRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBEquivalentSuperclassMethodsRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBJustSendsSuperRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBLiteralArrayContainsSuspiciousTrueFalseOrNilRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBLongMethodsRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBParseTreeLintRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBSuperSendsNewRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBTempVarOverridesInstVarRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBTemporaryVariableCapitalizationRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBTempsReadBeforeWrittenRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBTransformationRule.class/instance/running/checkMethod_.st M Refactoring-Critics.package/RBUtilityMethodsRule.class/instance/running/checkMethod_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script335.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40335.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40335 14334 Replace Announcer>>#on:send:to:s senders in RecentSubmissions https://pharo.fogbugz.com/f/cases/14334 14332 use #ast, not #parseTree so we benefit from the ASTCache https://pharo.fogbugz.com/f/cases/14332 http://files.pharo.org/image/40/40335.zip

Oct. 28, 2014

[pharo-project/pharo-core] 887eb8: 40334

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 887eb8530835e7644c8f2a63541311718527d816 https://github.com/pharo-project/pharo-core/commit/887eb8530835e7644c8f2a63… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-28 (Tue, 28 Oct 2014) Changed paths: M Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_target_selector_getStateSelector_enablementSelector_argumentList_.st M Morphic-Base.package/MenuMorph.class/instance/construction/add_target_selector_argumentList_.st M Morphic-Base.package/MenuMorph.class/instance/menu/addCustomMenuItems_hand_.st M Morphic-Core.package/Morph.class/instance/debug and other/addDebuggingItemsTo_hand_.st M Morphic-Core.package/Morph.class/instance/layout-menu/addCellLayoutMenuItems_hand_.st M Morphic-Core.package/Morph.class/instance/layout-menu/addLayoutMenuItems_hand_.st M Morphic-Core.package/Morph.class/instance/layout-menu/addTableLayoutMenuItems_hand_.st M Morphic-Core.package/Morph.class/instance/menus/addExportMenuItems_hand_.st M Morphic-Core.package/Morph.class/instance/menus/addFillStyleMenuItems_hand_.st M Morphic-Core.package/Morph.class/instance/meta-actions/addEmbeddingMenuItemsTo_hand_.st M Morphic-Core.package/Morph.class/instance/text-anchor/addTextAnchorMenuItems_hand_.st M Polymorph-Widgets.package/extension/SystemWindow/instance/taskbarButtonMenu_.st M Rubric.package/RubSegmentIconMenuMorph.class/instance/adding item/addToggle_target_selector_getStateSelector_enablementSelector_argumentList_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script334.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40334.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Workspace.package/Workspace.class/instance/window menu/addModelItemsToWindowMenu_.st Log Message: ----------- 40334 14333 clean translated in add:subMenu: and add:icon:subMenu: https://pharo.fogbugz.com/f/cases/14333 http://files.pharo.org/image/40/40334.zip

Oct. 27, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40334 Home: https://github.com/pharo-project/pharo-core

Oct. 27, 2014

Re: [Pharo-dev] [Vm-dev] Re: Should literals be immutable ?

by Levente Uzonyi

On Mon, 27 Oct 2014, stepharo wrote: > Levente > > I think that the first step is not to make sure that you cannot hack inside literals like mad. But to make sure that in 99.99 % of the case, this assumption can hold. > > Stef Let me sum it up: - The question is (by Clement) if it's okay to not implement the slow path. - He assumes that he doesn't have to implement it if literals are immutable. - I showed that literal immutability is not enough to avoid impelemting the slow path. So immutability doesn't affect anything about the need for implementing of the slow path. If Clement decides to not implement it, then one will be able to get the system into an inconsistent state, no matter if literals are immutable or not. If you think that the inconsistent state can only be achieved by hacking, then here's another example without "hacks": SomeClass >> #someMethod ^someBoolean ifTrue: [ Array with: 1 with: 2 with: 3 ] ifFalse: [ Array empty "we don't have to create a new array for this, right? :)" ] SomeOtherClass >> #someOtherMethod: anArray | copy | anArray doSomething. "let's grow that array" copy := Array new: anArray size. copy replaceFrom: 1 to: anArray size with: anArray startingAt: 1. anArray becomeForward: copy. "this is really cheap in Spur (and in VW; even collections and streams use it)" ThirdClass >> #yetAnotherMethod: aSomeClass | x | x := aSomeClass someMethod. y someOtherMethod: x. ^x And now, when #yetAnotherMethod: is sent, we swap the literal in Array class >> #empty with another non-empty array. Based on Eliot's comment about VW, I'm pretty sure the VW guys had problems like this, despite of having immutable literals. Levente

Oct. 27, 2014

MC logic looks strange

by stepharo

Hi when I merge code I see repeated patterns of MC loading all the files from main or inbox. I have the impression that we query really a lot the same repo. Does anybody look at this part? Stef

Oct. 27, 2014