- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3377 in pharo: AppRegistry remoce dependence to UIManager
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo Labels: Type-Seed New issue 3377 by Benjamin.VanRyseghem.Pharo: AppRegistry remoce dependence to UIManager http://code.google.com/p/pharo/issues/detail?id=3377 fix but using a not so pretty way. I've to discuss with Steph about extensions Attachments: AppRegistryRemoveDependenceToUIManager.1.cs 1.8 KB

1 1

[Pharo-project] Issue 3379 in pharo: ToolSet remove dependence to UIManager
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo Labels: Type-Seed New issue 3379 by Benjamin.VanRyseghem.Pharo: ToolSet remove dependence to UIManager http://code.google.com/p/pharo/issues/detail?id=3379 fix Attachments: ToolSetRemoveDependenceToUIManager.1.cs 859 bytes

1 2

[Pharo-project] [update 1.3] #13022
by StÃ©phane Ducasse Jan. 28, 2011

Jan. 28, 2011

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

1 0

[Pharo-project] Issue 3597 in pharo: Fix RemoteString API
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Fixed Owner: Benjamin...@gmail.com Labels: Type-Seed Milestone-1.3 New issue 3597 by Benjamin...@gmail.com: Fix RemoteString API http://code.google.com/p/pharo/issues/detail?id=3597 RemoteString >>#text used to return a String, and for each instance of RemoteString: each string = each text Looks weird ... Due to that, you had some message like: MyObject newString: classComment text Moreover, due to the use of text instead of string, you couldn't substitute a RemoteString and a String :) Attachments: FixRemoteStringAPI.1.cs 1.4 KB

1 1

[Pharo-project] Pharo 1.2 auto-completion in OB not so cool.
by laurent laffont Jan. 28, 2011

Jan. 28, 2011

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/

1 0

[Pharo-project] About FileSystem (probably not for 1.3)
by StÃ©phane Ducasse Jan. 28, 2011

Jan. 28, 2011

Hi guys, I was checking the state of FileSystem and we cannot push it into pharo like that! Sad but we should not put code where not a single method has a comment. So instead of crying and bashing colin, I started a while ago to understand (great pain) and write comments probably wrong, of course. Now I did several iterations but not enough. So I will read the blog entries of lukas and try to continue. http://www.lukas-renggli.ch/blog/filesystem Now if you want pharo to evolve, then this is clearly a place to help. We should get better class comments, and all the methods with a comment. Else FileSystem will not get integrated. I will veto it. Colin lost all the changes he did after ESUG so we will have to live with that (for example FSPath not being a class for public consumption and others). Stef

7 15

[Pharo-project] Issue 3601 in pharo: Recommended Seaside version in Pharo-1.2 outdated
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Accepted Owner: Torsten....@astares.de CC: renggli, philippe...@gmail.com, marianopeck, stephane...@gmail.com, da...@teleport.com, marcus.d...@gmail.com Labels: Milestone-1.2-DevImage New issue 3601 by Torsten....@astares.de: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 Use a prebuilt Pharo 1.2 from the hudson server. When you run "DEVImageWorkspaces openExternalProjectWorkspace" it is suggested to load ConfigurationOfSeaside30 and load ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.0-alpha5.15') load. it comes up with: "Deprecation: The method SmalltalkImage platformName has been deprecated. Use Smalltalk os platformName" Thats not nice for newbees ;) We should also check the other recommended load scripts ... QUESTION: I think a newer version of Seaside like 3.0.3 would help ... Can anyone confirm that Seaside 3.0.3 is OK for Pharo-dev 1.2

1 4

[Pharo-project] Issue 3595 in pharo: problem starting up with a script on windows
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Accepted Owner: tudor.gi...@gmail.com Labels: Milestone-1.2 Milestone-1.3 Type-ReportDefect New issue 3595 by tudor.gi...@gmail.com: problem starting up with a script on windows http://code.google.com/p/pharo/issues/detail?id=3595 Pharo image: Dev Pharo core version: <copy from World/System/About> Virtual machine used: Cog 2316, 2348 There seems to be a problem with starting a Pharo 1.2-based image with an initial .st script on Windows. The problem seems to be in CodeLoader>>installSourceFiles and it is related to the contentStream retrieved from the HTTPDownloadRequest being nil. The debug log is listed below. I checked the paths and they are all correct. In fact, if I run the same script with a Pharo 1.1.1 image, everything works as expected. I also tried to drag and drop the .st script and again, everything works as expected. So, it seems that there is some initialization problem. I managed to debug some more and the problem seems to be introduced by System-Download after the version System-Download-StephaneDucasse.51. If you try any of the newer version, you should get the error. I worked on a Windows Server 2008 R2 using a Cog VM (both r2316 and r2348). Attachments: PharoDebug.log 7.8 KB

1 5

[Pharo-project] Fwd: Issue 3599 in pharo: Serial Port
by Serge Stinckwich Jan. 28, 2011

Jan. 28, 2011

---------- Forwarded message ---------- From: SÃ©verin Lemaignan <severin.lemaignan(a)laas.fr> Date: 2011/1/28 Subject: Re: [Pharo-project] Issue 3599 in pharo: Serial Port To: Serge Stinckwich <serge.stinckwich(a)gmail.com> Cc: Pharo-project(a)lists.gforge.inria.fr > The quality of the code is not really good, there is a lot of isString > everywhere in order to test if the port is a number or a string > regarding the OS platform used: I did so to avoid to break anything that could already used the com port with integers. If you're confident it's not used (or if it is easy enough to convert it to 'com1', 'com2' strings...) then feel free to remove support for integer. As far as I remember, the underlying system primitive should be able to deal with 'comX' on Windows. Regards, Severin -- Â Â Â Â SÃ©verin Lemaignan - severin.lemaignan(a)laas.fr Â [00] Â Â PhD student on Cognitive Robotics /|__|\ Â LAAS-CNRS - RIS group / Technische Uni MÃ¼nchen - IAS group Â '' Â Â +33561337844 / +498928917780 Â Â Â Â http://www.laas.fr/~slemaign -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

1 0

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Package
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Updates: Summary: [Failing Tests] Package Labels: Milestone-1.2-DevImage Comment #2 on issue 3575 by marcus.d...@gmail.com: [Failing Tests] Package http://code.google.com/p/pharo/issues/detail?id=3575 Monticello tests do not clean up (why only in Full???)

1 0