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

[Pharo-project] [ANN] New Cocoa Squeak VM release

by Esteban Lorenzano

Hi, I want to announce the release of a new version of Cocoa Squeak VM (non Cog), version 5.7.4. It can be downloaded here: http://squeakvm.org/mac/release/Squeak%205.7.4.zip Since this is my first release, there are no big changes to take into account: 1) It's based on VMMaker 221 (latest) 2) it has a minor bugfix on arguments passed to the image (it was ignoring first argument). 3) My biggest change is that I drop the "b" from the release version, I didn't like it, and I think nobody else likes it :) and also is clear to understand, IMHO. Now you can read the version as: Major Version.Minor Version.Bugfix Version. This release ships with this internal plugins included: ADPCMCodecPlugin B3DEnginePlugin BalloonEnginePlugin BitBltSimulation BMPReadWriterPlugin ClipboardExtendedPlugin DeflatePlugin DSAPlugin FFIPlugin FFTPlugin FilePlugin FloatArrayPlugin GeniePlugin HostWindowPlugin JPEGReaderPlugin JPEGReadWriter2Plugin KlattSynthesizerPlugin LargeIntegersPlugin Matrix2x3Plugin MacMenubarPlugin MiscPrimitivePlugin NewsqueakIA32ABIPlugin ObjectiveCPlugin RePlugin SecurityPlugin SocketPlugin SoundCodecPlugin SoundGenerationPlugin SoundPlugin StarSqueakPlugin SurfacePlugin UUIDPlugin DropPlugin Enjoy, Esteban, with mac vm maintainer hat

Feb. 2, 2011

Re: [Pharo-project] 1.2: class var #Instance not allowed

by Marcus Denker

On Feb 2, 2011, at 2:32 PM, Igor Stasenko wrote: > 2011/2/2 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: >> Hi guys, >> >> One more problem: if some class have a class variable named #Instance, >> it is not loadable anymore. >> >> It seems that problem is in Class>>bindingOf: method, where check is >> done in a "declared environment", which happens to be a global >> SystemDictionary, where a class Instance actually exists. >> >> This means that no class var with a name which collides with a name of >> class is allowed? >> >> > The bug is not in the #bindingOf: > > it just answers (correctly) that for given name there are already a > binding exists in system. > So, it should be allowed to declare the class variable with same name. > But there are some nuances: > - what to do if supeclass also defining binding for this name? > - what if pool dicitonary in (super)class defines binding for given name? > > should we allow shadowing of these cases as well, or just for globals? > The question is: was this allowed before in 1.1? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 2, 2011

Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #7 on issue 3623 by marcus.d...(a)gmail.com: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 I would re-open as it is exactly the same. (things that are fixes for things already integrated should get new entries...)

Feb. 2, 2011

Re: [Pharo-project] what do we do for OmniBrowser?

by Dmitri Zagidulin

I agree with HernÃ¡n. OB is incredibly valuable, and I was delighted to see that it was included out of the box in 1.2 (when switching to Pharo from Squeak). We cannot let it slide or remove it (btw, I still can't believe we as a community let SeasideTesting be broken in 1.2). HernÃ¡n -- I would love to offer any sort of help maintaining it. I don't know much about GUI/Morphic coding, though of course I'd like to learn. But I would definitely be willing to help test it, etc. ~Dmitri On Wed, Feb 2, 2011 at 9:48 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Just to give some feedback because I mostly use the core image. OB is > one of our most valuable tools, it would be a pity if cannot be > integrated. > I could help mantaining but not alone, I'm sick of programming in isolation. > > HernÃ¡n > > 2011/2/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Ok so far no reaction. >> So may be we should remove OB from 1.2 dev? >> >> Stef >> >> >>> Lukas will not maintain OB for Pharo 1.2 and personnally I will not do it because I do not have the knowledge and the time. >>> So now this is time to know what do we do for OmniBrowser. I have all my ears open. >>> >>> >>> The first step I would do >>> Â Â Â - host OB for 1.1 in a repository where we have write access. >>> Â Â Â - create a configurationOf for OB and save it there >>> >>> >>> Stef >> >> >> > >

Feb. 2, 2011

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #8 on issue 3506 by marcus.d...(a)gmail.com: TextMorph's #autoFit: and #wrapFlag: are confusing http://code.google.com/p/pharo/issues/detail?id=3506 13036

Feb. 2, 2011

[Pharo-project] [update 1.3] #13036

by Marcus Denker

13036 ----- Issue 3520: Workspaces do not recognize previously evaluated temps Issue 3643: TextMorph >> enableTextChange is missing Issue 3506: TextMorphs #autoFit: and #wrapFlag: are confusing -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 2, 2011

Re: [Pharo-project] Issue 3643 in pharo: TextMorph >> enableTextChange is missing

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 3643 by marcus.d...(a)gmail.com: TextMorph >> enableTextChange is missing http://code.google.com/p/pharo/issues/detail?id=3643 in 13036

Feb. 2, 2011

Re: [Pharo-project] what do we do for OmniBrowser?

by HernÃ¡n Morales Durand

Just to give some feedback because I mostly use the core image. OB is one of our most valuable tools, it would be a pity if cannot be integrated. I could help mantaining but not alone, I'm sick of programming in isolation. HernÃ¡n 2011/2/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Ok so far no reaction. > So may be we should remove OB from 1.2 dev? > > Stef > > >> Lukas will not maintain OB for Pharo 1.2 and personnally I will not do it because I do not have the knowledge and the time. >> So now this is time to know what do we do for OmniBrowser. I have all my ears open. >> >> >> The first step I would do >> Â Â Â - host OB for 1.1 in a repository where we have write access. >> Â Â Â - create a configurationOf for OB and save it there >> >> >> Stef > > >

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Updates: Status: Closed Comment #19 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 in 13036

Feb. 2, 2011

Re: [Pharo-project] Issue 3643 in pharo: TextMorph >> enableTextChange is missing

by pharo＠googlecode.com

Comment #5 on issue 3643 by marcus.d...(a)gmail.com: TextMorph >> enableTextChange is missing http://code.google.com/p/pharo/issues/detail?id=3643 in 12330 TODO: 1.3

Feb. 2, 2011