July 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Inspect it wrong shortcut
by Mariano Martinez Peck March 3, 2011

March 3, 2011

Hi! With latest pharo 304 in Linux the shortcut for inspect it (ctrl + i) doesn't work but alt + i. I have evaluated Preferences enable: #swapCOntrolAndAltKeys. Actually, all the other shortcuts (browse it, do it, explore it, and so on) works with ctrl + XXX but there is a problem with inspect it. Can someone confirm this ? Cheers, Mariano

7 15

[Pharo-project] {Spam?} Re: "Real" packages.
by Bill Schwab Feb. 20, 2010

Feb. 20, 2010

Stef, Re Dolphin, class categories have long been of marginal use; I'll speak for myself on that but suspect others would agree. Packages are of course extremely useful. Method categories are also quite useful, and Dolphin allows multiple categories to be assigned to a given method. Dolphin mixes virtual categories (computed by rules) with static ones maintained by the user (and serialized as part of packages). I can easily see where OB would get quite a speed boost out of it. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 2/10/2009 4:41:10 PM >>> Alexandre implemented long time ago an hybrid model where both kind of packages could coexist and we should probably revive it for 1.1 Stef On Feb 10, 2009, at 10:28 PM, Michael van der Gulik wrote: > > > On Wed, Feb 11, 2009 at 9:21 AM, David RÃ¶thlisberger <squeak(a)webcitas.ch > > wrote: > > > So if we had real packages in Pharo as first class entities, OB > would be much faster > and simpler to maintain. Right now, OB models packages and class > cats itself, has to > take the information from both the Monticello's working copy > managers and the > SystemOrganizer. This is a mess and a huge pain, but what can we do. > We should really invest in bringing real packages to Pharo. > > > If you want "real" packages, I've implemented them in Squeak: > > http://gulik.pbwiki.com/Namespaces > http://gulik.pbwiki.com/Packages > > The places the code is held, including a video and a Squeak image is > linked from here: > http://gulik.pbwiki.com/SecureSqueak > > I'm not interested in Pharo, but the code is there and is released > under the MIT license if anybody else wants it. > > Gulik. > > -- > http://people.squeakfoundation.org/person/mikevdg > http://gulik.pbwiki.com/ > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

12 13

[Pharo-project] request for the new merge tool :)
by StÃ©phane Ducasse Sept. 8, 2009

Sept. 8, 2009

hi gary it would be important to be able to install a method by clicking on it as we could do it in the old one. Stef

9 28

[Pharo-project] keyboard shortcut open a warning
by StÃ©phane Ducasse Aug. 5, 2009

Aug. 5, 2009

may be we should simply remove that item. menu system keyboard shortcuts Stef

4 8

[Pharo-project] [ANN] Pharo 1.0 Beta
by Adrian Lienhard Aug. 5, 2009

Aug. 5, 2009

Hi all, We are excited to announce the first Pharo 1.0 beta release. A new Pharo image (and also Pharo-web image) can be downloaded from the website: http://pharo.cmsbox.ch/pharo-download The corresponding version number of Pharo-core is #10401. I'd like to thank all the people that have contributed to Pharo so far! Have fun, Adrian BTW, I also wrote about Pharo and the beta release on http://www.adrian-lienhard.ch/blog ___________________ http://www.adrian-lienhard.ch/

10 25

[Pharo-project] Pharo name format
by Miguel Enrique CobÃ¡ Martinez Aug. 4, 2009

Aug. 4, 2009

Now that the release date for pharo is close, I propose to use the following sintax for the pharo core products PharoCore-x.y-#####-TagName.zip where x.y is the version of pharo (0.1, 1.0, 1.1, 2.0, 2.1, etc) ##### is the number of image release in that version (10449, 10450, 10451, etc) TagName is a tag for better explain some specific feature of the image (closure, RELEASE, STABLE, beta, etc) e.g. For a normal daily release, say 10450, in the 0.1 branch: PharoCore-0.1-10450.zip For the image that has all tests in green: PharoCore-0.1-10456-AllTestGreen.zip For the image that it is the first stable 1.0: PharoCore-1.0-10478-RELEASE_1_0.zip For the next image with the NewCompiler code integrated, after the 1.0 release: PharoCore-1.0-10490-NewCompiler.zip For a subsecuent 1.1 release, that includes NewCompiler: PharoCore-1.1-10511-RELEASE_1_1.zip When, for example, 1.1 is the current branch, and 1.0 has fixes support and a new emergency release for the old 1.0 branch: PharoCore-1.0-10512-UPDATE_1.zip Release for pharo 2.0: PharoCore-2.0-10890-RELEASE_2_0.zip Other fix in the 1.1 branch (brach 1.0 is out of support): PharoCore-1.1-10915-UPDATE_1.zip Notes: We can also reset the number in each mayor release (0.1, 1.0, 1.1, etc) so that the updates to the old supportes branches can be a continuous. For example, the previous names would be (in the same order of release as the examples above): PharoCore-0.1-10450.zip PharoCore-0.1-10456-AllTestGreen.zip PharoCore-1.0-10001-RELEASE_1_0.zip PharoCore-1.0-10002-NewCompiler.zip PharoCore-1.1-10001-RELEASE_1_1.zip PharoCore-1.0-10003-UPDATE_1.zip PharoCore-2.0-10001-RELEASE_2_0.zip PharoCore-1.1-10002-UPDATE_1.zip etc Also, the PharoCore-1.0-10001-RELEASE_1_0.zip would be a copy of the last image of 0.1 branch (in this example PharoCore-0.1-10456-AllTestGreen.zip) But this is mostly estetic and can potentially confuse new users. What do you think?

7 10

[Pharo-project] Debbuging problems, FFI
by Javier PimÃ¡s Aug. 4, 2009

Aug. 4, 2009

Hi, I'm having problems with the debugger. Every time I try to debug code that uses FFI, if I step over a message that internally does an FFI call, I get an externalCallFailed error and then I land in MethodContext(ContextPart)>>runUntilErrorOrReturnFrom: If I run the code without debugging, then I have no problems at all. I'm using SqueakPharo v3.11.2 with pharo0.1-10373web09.07.2. To reproduce it you can try this: ScriptLoader loadFFI. then load latest GLMorphic from squeaksource, and uncomment the "self break." in GLCanvas>>displayString:from:to:at:strikeFont:kern: doit World fullDrawOn: GLDisplayScreen testCanvas hit debug and step over until you reach ogl glTexImage2D: GLTexture2d with:... also you'll see wrong values for local vars, like aPoint which will look as #(nil nil nil nil nil) when it'll actually have a point. Is there any other way to set up a break point instead of adding self break to the code?? Thanks, Javier. -- Javier PimÃ¡s Ciudad de Buenos Aires

5 14

[Pharo-project] Fix for issue 981 Author class in pharo
by Miguel Enrique CobÃ¡ Martinez Aug. 4, 2009

Aug. 4, 2009

http://code.google.com/p/pharo/issues/detail?id=981 Name: SLICE-ChangeAuthorInitialsAndNameToFullName-MiguelCoba.3 Author: MiguelCoba Time: 25 July 2009, 3:53:41 am UUID: 27a1accc-4f41-4d11-94f5-9bdbb4166bd7 Ancestors: SLICE-ChangeAuthorInitialsAndNameToFullName-MiguelCoba.2 Dependencies: Monticello-MiguelCoba.372, Morphic-MiguelCoba.347, ScriptLoader-MiguelCoba.972, System-Changes-MiguelCoba.11, System-Support-MiguelCoba.62, Tools-MiguelCoba.179 Removes all the code from initials and name on Author class. It is replaced by a new fullName inst var and corresponding methods. The old code it is deprecated and the image contains no more calls to the old code. All the new code should call only the fullName methods in Author This is my first intent to rewrite the Author class to unify the instance variables. Please, check it on a 10392 core image and post your comments/critics. Also, I didn't modify the following methods of Utilities. Tell me what would you like to do with them, please: Utilities fixStamp: Utilities methodsWithInitials: Utilities doesMethod:forClass:bearInitials Cheers, Miguel CobÃ¡

4 4

[Pharo-project] #remoteHostAddress
by Ramiro Diaz Trepat Aug. 2, 2009

Aug. 2, 2009

I am trying to port Magma to Pharo, and I have run across the following issue. Ini Pharo, the method: Socket>>connectTo: hostAddress port: port waitForConnectionFor: timeout (mir 6/17/2007 20:10) "Initiate a connection to the given port at the given host address. Waits until the connection is established or time outs." self connectNonBlockingTo: hostAddress port: port. self waitForConnectionFor: timeout ifTimedOut: [ConnectionTimedOut signal: 'Cannot connect to ' , self *remoteHostAddress* hostNumber , ':' , port asString] #*remoteHostAddress* has no implementors in Pharo. The implementation of this method in Squeak uses *NetNameResolver* Socket>>connectTo: hostAddress port: port waitForConnectionFor: timeout (mu 8/14/2003 15:15) "Initiate a connection to the given port at the given host address. Waits until the connection is established or time outs." self connectNonBlockingTo: hostAddress port: port. self waitForConnectionFor: timeout ifTimedOut: [ConnectionTimedOut signal: 'Cannot connect to ' , (*NetNameResolver* stringFromAddress: hostAddress) , ':' , port asString] Who is maintaining Socket now in Pharo? Has anyone got some advice on how to solve this? Cheers r.

4 8

[Pharo-project] [ANN] Pharo 1.0 Beta - Win32 Installer
by Torsten Bergmann July 31, 2009

July 31, 2009

see http://pharo-project.org/pharo-download -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

1 0