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

Re: [Pharo-project] Issue 3377 in pharo: AppRegistry remoce dependence to UIManager

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3377 by stephane...(a)gmail.com: AppRegistry remoce dependence to UIManager http://code.google.com/p/pharo/issues/detail?id=3377 in 13023

Jan. 28, 2011

Re: [Pharo-project] Issue 3379 in pharo: ToolSet remove dependence to UIManager

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3379 by stephane...(a)gmail.com: ToolSet remove dependence to UIManager http://code.google.com/p/pharo/issues/detail?id=3379 13023 We moved askDefault to UIManager as an extension

Jan. 28, 2011

Re: [Pharo-project] [squeak-dev] Accessing external resources in a cross-platform way

by David T. Lewis

On Fri, Jan 28, 2011 at 01:51:22PM +0100, Hern??n Morales Durand wrote: > Let's say you want to resolve paths in a cross platform way > > Binaries @ 'MyExec' > Libraries @ 'MyLib' > SystemLibraries @ 'SystemLib' > etc. > > then Binaries is > > In Windows: #( 'C:\Program Files\' 'C:\Archivos de Programa\' ...) " > and all standard locations including translations " > In UNIX: #('/usr/bin/' '/usr/local/bin' ....) " and all standard locations " > etc > > Now you may say it is necessary to scan all directories to find > MyExec, yes but you may then save that location > > myBinaryLocation := Binaries @ 'MyExec'. > > so you scan for it just once. > > What do you think? it is already implemented anywhere? > If not what package do you think is more suitable or prepared for > implementing it? Hern??n, This is of course very platform dependent, and it is more complex than you might expect due to differences in file systems, operating systems, volume names (windows), environment variables and search path conventions. Both Windows and Unix use various seach paths accessible through environment variables, and the conventions for this tend to change over time with different OS versions. So it would probably be best to rely directly on those environment variables for identifying search paths. Aside from the conventions for default locations and search paths, some of what you are looking for may also be implemented for Windows and Unix in SqS/CommandShell in class ShellSyntax: My instances implement parsing of strings in a manner similar to a simple Unix command shell. I provide path name expansion in the context of an external file system, and support the syntax required for IO redirection. All file name globbing and PATH searching are implemented in Smalltalk rather than in C library functions or an external command shell. Most of my syntax is applicable for any operating system. Where needed, platform specific methods are in my "platform dependent" category. Currently, Unix and Windows are supported, and other platforms have not been tested. The primary difference between Unix and Windows support is that device names (such as 'C:') are used in Windows path strings. Separate current working directory strings are maintained for all Windows device names. For Unix, a single current working directory path is used. On Windows, this permits the CommandShell 'cd' command to support changing directories to another device without losing track of the current working directory for the previous device. Command pipeline syntax is not supported here. See CommandShell for the implementation of command pipelines. Dave

Jan. 28, 2011

[Pharo-project] [update 1.3] #13022

by StÃ©phane Ducasse

13022 ----- - Issue 3597: Fix RemoteString API. Thanks Benjamin van Ryseghem. - Fixed bold application in a text. - Removed a self haltOnce: 2 in mouseEnter. - Now we do not read back code annotation such as bold and italic. The idea is to only store code without styling annotation outside the code. It will simplify the rewrite of the system. Stef and Benjamin

Jan. 28, 2011

Re: [Pharo-project] Issue 3597 in pharo: Fix RemoteString API

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3597 by stephane...(a)gmail.com: Fix RemoteString API http://code.google.com/p/pharo/issues/detail?id=3597 in 13022

Jan. 28, 2011

Re: [Pharo-project] CommandShell

by David T. Lewis

On Thu, Jan 27, 2011 at 11:55:17PM -0800, Sean P. DeNigris wrote: > > After loading CommandShell-dtl.50 (and .45, which works in Squeak 4.1), when > I evaluate: > (PipeableOSProcess command: 'ls') output > > I get a NonBooleanReceiver error when AttachableFileStream>>upToEndOfFile > calls #atEndOfFile, which returns nil. > > Sean > > p.s. I also tried loading the latest Pharo package from the CommandShell > repo Regardless of whether you are using a Squeak or Pharo image, I always suggest using the latest versions of OSProcess and CommandShell from SqueakSource. I develop in Squeak, but have tried to maintain compatibility with Pharo. If something does not work it Pharo, it's a bug. Dave

Jan. 28, 2011

[Pharo-project] Pharo 1.2 auto-completion in OB not so cool.

by laurent laffont

Hi, In Pharo 1.2 there's inconsistency in auto-completion between Workspace and Browser. In Workspace, if I type |builder| builder := UITheme builder. builder newText then press the tab key, I have the method newTextEntryFor:getText:setText:help: in the list (which is what I want). In the browser, I get only the method defined in UITheme (and builder is an instance of ComposableMorph). It's very disturbing (for me). May be there's a way to tell completion to look for all implementors ? Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Jan. 28, 2011

[Pharo-project] Issue 3607 in pharo: MNU #stylerStyled: in Finder for basic usage

by pharo＠googlecode.com

Status: Accepted Owner: laurent....(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3607 by laurent....(a)gmail.com: MNU #stylerStyled: in Finder for basic usage http://code.google.com/p/pharo/issues/detail?id=3607 Pharo image: 1.2 dev build #99 Steps to reproduce: 1. open Finder 2. in search field search for a method (ex: collect:) 3. expand a result (ex: allElementsCollect:) 4. click on a child node (ex: XMLNodeWithElements) You get: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: Works on PharoCore 1.2 PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: Receiver: a PluggableTextMorph(280494080) Arguments and temporary variables: aMessage: stylerStyled: a Text for 'allElementsCollect: aBlock | collectedElem...etc... exception: MessageNotUnderstood: PluggableTextMorph>>stylerStyled: resumeValue: nil Receiver's instance variables: bounds: 195@408 corner: 805@539 owner: a StandardWindow(1058013184) submorphs: an Array(a TransformMorph(941359104)) fullBounds: 195@408 corner: 805@539 color: Color white extension: a MorphExtension (73400320) [locked] borderWidth: 1 borderColor: (Color r: 0.833 g: 0.833 b: 0.833) model: a FinderUI(936378368) slotName: nil open: false scrollBar: a ScrollBar(287047680) scroller: a TransformMorph(941359104) retractableScrollBar: false scrollBarOnLeft: false getMenuSelector: #msgPaneMenu:shifted: getMenuTitleSelector: nil hasFocus: false hScrollBar: a ScrollBar(78381056) textMorph: a TextMorphForEditView(880017408) getTextSelector: #sourceCode setTextSelector: #compileSource: getSelectionSelector: nil hasUnacceptedEdits: false askBeforeDiscardingEdits: true selectionInterval: (1 to: 0) hasEditingConflicts: false acceptAction: nil getColorSelector: nil unstyledAcceptText: nil styler: a SHTextStylerST80 styled: false SHTextStylerST80(SHTextStyler)>>style: Receiver: a SHTextStylerST80 Arguments and temporary variables: aText: a Text for 'allElementsCollect: aBlock | collectedElements | collecte...etc... Receiver's instance variables: sem: nil backgroundProcess: nil text: a Text for 'allElementsCollect: aBlock | collectedElements | collected...etc... monitor: a Monitor view: a PluggableTextMorph(280494080) stylingEnabled: true classOrMetaClass: XMLNodeWithElements workspace: nil font: nil parser: a SHParserST80 environment: nil pixelHeight: 12.0 PluggableTextMorph>>setText: Receiver: a PluggableTextMorph(280494080) Arguments and temporary variables: aText: 'allElementsCollect: aBlock | collectedElements | collectedElements :...etc... Receiver's instance variables: bounds: 195@408 corner: 805@539 owner: a StandardWindow(1058013184) submorphs: an Array(a TransformMorph(941359104)) fullBounds: 195@408 corner: 805@539 color: Color white extension: a MorphExtension (73400320) [locked] borderWidth: 1 borderColor: (Color r: 0.833 g: 0.833 b: 0.833) model: a FinderUI(936378368) slotName: nil open: false scrollBar: a ScrollBar(287047680) scroller: a TransformMorph(941359104) retractableScrollBar: false scrollBarOnLeft: false getMenuSelector: #msgPaneMenu:shifted: getMenuTitleSelector: nil hasFocus: false hScrollBar: a ScrollBar(78381056) textMorph: a TextMorphForEditView(880017408) getTextSelector: #sourceCode setTextSelector: #compileSource: getSelectionSelector: nil hasUnacceptedEdits: false askBeforeDiscardingEdits: true selectionInterval: (1 to: 0) hasEditingConflicts: false acceptAction: nil getColorSelector: nil unstyledAcceptText: nil styler: a SHTextStylerST80 styled: false FinderUI>>updateSourceCode Receiver: a FinderUI(936378368) Arguments and temporary variables: code: 'allElementsCollect: aBlock | collectedElements | collectedElements :=...etc... Receiver's instance variables: bounds: 0@0 corner: 50@40 owner: nil submorphs: #() fullBounds: nil color: Color blue extension: a MorphExtension (959447040) [other: (myDependents -> a DependentsA...etc... finder: a Finder searchingTextArea: an EditableDropListMorph(111935488) sourceTextArea: a PluggableTextMorph(280494080) packagesTree: nil useRegExCheckbox: a CheckboxMorph(99352576)

Jan. 28, 2011

Re: [Pharo-project] Issue 3606 in pharo: [1.1.2] [Failing Test] Undeclared in package shout

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2 Milestone-1.1.2-DevImage Comment #2 on issue 3606 by marcus.d...(a)gmail.com: [1.1.2] [Failing Test] Undeclared in package shout http://code.google.com/p/pharo/issues/detail?id=3606 (No comment was entered for this change.)

Jan. 28, 2011

[Pharo-project] [ANN 1.2RC2] and TODO 1.2

by Marcus Denker

Hi, 1.2 ==== We now have a RC2 of the Core image. -> all tests are green: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/ -> no known show stopping issues This can be downloaded here: https://gforge.inria.fr/frs/download.php/28189/PharoCore-1.2rc2-12324.zip But of course what people want to actually use is the Full Image (with Refactoring Tools...) For 1.2Full, we have some issues left before we can do a release. Hudson: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… Bugs: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.2-DevImage The nice thing is that with the Hudson server, up-to-date 1.2RC2 can be downloaded: image: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… One-Click: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… We should use it and test... 1.1 === While fixing those, we should take care to not break the 1.1Full Build. *And* we should take th opportunity to make it green, too. I already (in parallel to 1.2), fixed (or added workarounds) to all failing tests in Core. What is left is 1.1.2 Full: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.1.2-DevIma… https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.1/lastCompletedBuild/t… 1.3a === As simple changes where piling up *and* we need to move on, we started 1.3 this week. This has seen already 21 updates (and 51 closed bug tracker entries). The first goal will be to get all tests green, I will make sure that only issues are tagged 1.3 that are either to be integrated, failing tests or show-stoppers. This way we wil have a TODO list of issues to be fixed first. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 28, 2011