- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3784 in pharo: ImageForDevelopers uses SHWorkspace which is not defined in the image

by pharo＠googlecode.com

Comment #7 on issue 3784 by stephane...(a)gmail.com: ImageForDevelopers uses SHWorkspace which is not defined in the image http://code.google.com/p/pharo/issues/detail?id=3784 Ok let us see that in 1.3.

March 7, 2011

Re: [Pharo-project] Issue 3780 in pharo: DEVImageWOrkspace in prebuilt Pharo 1.2 gives DNU due to missing SHWorkspace class

by pharo＠googlecode.com

Updates: Status: closed Mergedinto: -3784 Comment #5 on issue 3780 by stephane...(a)gmail.com: DEVImageWOrkspace in prebuilt Pharo 1.2 gives DNU due to missing SHWorkspace class http://code.google.com/p/pharo/issues/detail?id=3780 (No comment was entered for this change.)

March 7, 2011

Re: [Pharo-project] Issue 3778 in pharo: cleaning cursor: and cursor

by pharo＠googlecode.com

Comment #6 on issue 3778 by stephane...(a)gmail.com: cleaning cursor: and cursor http://code.google.com/p/pharo/issues/detail?id=3778 May be we should split the code in batch because probably it is changing something that is currently been executed.

March 7, 2011

Re: [Pharo-project] Pharo on Apple App Store... or Cydia?

by Craig Latta

Hi-- (Conversation between Alexandre and Hilaire:) > > > I think we should have a clear roadmap on how to get a pharo > > > application in the appstore. The train is passing by and we are > > > not taking it. > > > > Yes, nevertheless you may want to take the alternative high speed > > train. > > Which is? I know it's probably not the sort of alternative you had in mind, but is anyone here interested in at least getting Pharo into Cydia? (Cydia is, among other things, the "app store" for folks who have jailbroken their iOS devices.) I'm sure several people would find it useful; it'd be a convenient way to get Pharo onto iThings and it would run with its full capabilities. -C -- Craig Latta www.netjam.org/resume +31 06 2757 7177 + 1 415 287 3547

March 7, 2011

Re: [Pharo-project] Kernel

by Benjamin

On Mar 7, 2011, at 11:04 AM, Alexandre Jasmin wrote: > On Fri, 04 Mar 2011 13:51:46 +0100, Benjamin wrote: > >> I finally success (with the help of Igor) to trace and create a new >> Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes >> 230 classes ;) > > Your image helps me a lot. > > I'm trying to get the Squeak VM compiling with Adobe Alchemy. Alchemy is > a C compiler targeting the flash VM. > > My initial approach is to stub about all entry points expect for ioBeep() > which prints a debug message. But I had problems loading a normal image. > I think it's just too big for flash to handle. In any case this kernel > image worked wonderfully! > > Thanks! > > > I'm glad that my work could help someone :) As Stef said, if you can provide us more info, it will be really cool ;) Thanks for your feedback ;) Ben

March 7, 2011

Re: [Pharo-project] Issue 3778 in pharo: cleaning cursor: and cursor

by pharo＠googlecode.com

Comment #5 on issue 3778 by stephane...(a)gmail.com: cleaning cursor: and cursor http://code.google.com/p/pharo/issues/detail?id=3778 Nor mine :( How did you load it.

March 7, 2011

Re: [Pharo-project] Issue 3778 in pharo: cleaning cursor: and cursor

by pharo＠googlecode.com

Comment #4 on issue 3778 by stephane...(a)gmail.com: cleaning cursor: and cursor http://code.google.com/p/pharo/issues/detail?id=3778 oops I cannot load your changeset

March 7, 2011

Re: [Pharo-project] Issue 3778 in pharo: cleaning cursor: and cursor

by pharo＠googlecode.com

Comment #3 on issue 3778 by stephane...(a)gmail.com: cleaning cursor: and cursor http://code.google.com/p/pharo/issues/detail?id=3778 Thanks! this is great to do pair programming with you like that :)

March 7, 2011

Re: [Pharo-project] OSProcess

by StÃ©phane Ducasse

I tried in 1.2- Core and it did not work. :( Stef On Mar 7, 2011, at 11:58 AM, stephane ducasse wrote: > I saw the mail of miguel :) > > Do you know if OSProcess is working on 1.3? > > > Hi all, > > I have updated the Metacello configuration for OSProcess. > > Changes > ------- > > - Uses symbolic versions > - Adds support for release 4.4.0 of OSProcess > - Applies MetacelloToolBox validations to the old versions of the > configuration and corrects them > > Install > -------- > > In a PharoCore image evaluate in a workspace: > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOSProcess'; > load. > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > #stable) load. > > This will install the stable version for the platform you are installing > to. This is using symbolic versions and permits to rely on the > maintainers to specify the stable version (4.3.11, 4.3.12, 4.4.0) for a > given platform version (PharoCore 1.1.1, PharoCore 1.2). > > Other versions and groups > --------------------------- > > To load older versions: > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > '4.3.11') load. > > To load other groups: > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > #stable) load: 'Tests'. > > or > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > '4.3.11') load: 'Tests'. > > > Platforms > ---------- > > This was tested on > > - PharoCore 1.1.1 > 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes > > - PharoCore 1.2 (build #199 from Hudson) > 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes > > P.S. I'm cross-posting to pharo and metacello lists but I don't know > what is the correct way to announce a new configuration. Advise? > > Enjoy! > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > On Mar 7, 2011, at 11:44 AM, StÃ©phane Ducasse wrote: > >> Hi guys >> >> I'm updtating the ConfigurationOfCoral and I loaded >> >> >> baseline >> >> spec project: 'OSProcess' with: [ >> spec >> className: 'ConfigurationOfOSProcess'; >> file: 'ConfigurationOfOSProcess'; >> version: '4.4.0'; >> repository: 'http://www.squeaksource.com/OSProcess' ]. >> >> >> version >> >> spec for: #'common' do: [ >> spec >> package: 'Filesystem' with: 'Filesystem-DamienPollet.114'; >> project: 'OSProcess' with: '4.4.0'; >> package: 'AST-Core' with: 'AST-Core-lr.87'; >> package: 'PetitParser' with: 'PetitParser-TudorGirba.209'; >> package: 'PetitTest' with: 'PetitTests-TudorGirba.28'; >> package: 'PetitSmaltalk' with: 'PetitSmalltalk-lr.46'.] >> >> and when I run the test I get accessor error. >> >> Any idea what would be problem? >> The VM? >> >> I use 5.7b3 >> >> Sted >> > >

March 7, 2011

Re: [Pharo-project] OSProcess

by stephane ducasse

I saw the mail of miguel :) Do you know if OSProcess is working on 1.3? Hi all, I have updated the Metacello configuration for OSProcess. Changes ------- - Uses symbolic versions - Adds support for release 4.4.0 of OSProcess - Applies MetacelloToolBox validations to the old versions of the configuration and corrects them Install -------- In a PharoCore image evaluate in a workspace: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOSProcess'; load. ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: #stable) load. This will install the stable version for the platform you are installing to. This is using symbolic versions and permits to rely on the maintainers to specify the stable version (4.3.11, 4.3.12, 4.4.0) for a given platform version (PharoCore 1.1.1, PharoCore 1.2). Other versions and groups --------------------------- To load older versions: ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: '4.3.11') load. To load other groups: ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: #stable) load: 'Tests'. or ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: '4.3.11') load: 'Tests'. Platforms ---------- This was tested on - PharoCore 1.1.1 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes - PharoCore 1.2 (build #199 from Hudson) 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes P.S. I'm cross-posting to pharo and metacello lists but I don't know what is the correct way to announce a new configuration. Advise? Enjoy! -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx On Mar 7, 2011, at 11:44 AM, StÃ©phane Ducasse wrote: > Hi guys > > I'm updtating the ConfigurationOfCoral and I loaded > > > baseline > > spec project: 'OSProcess' with: [ > spec > className: 'ConfigurationOfOSProcess'; > file: 'ConfigurationOfOSProcess'; > version: '4.4.0'; > repository: 'http://www.squeaksource.com/OSProcess' ]. > > > version > > spec for: #'common' do: [ > spec > package: 'Filesystem' with: 'Filesystem-DamienPollet.114'; > project: 'OSProcess' with: '4.4.0'; > package: 'AST-Core' with: 'AST-Core-lr.87'; > package: 'PetitParser' with: 'PetitParser-TudorGirba.209'; > package: 'PetitTest' with: 'PetitTests-TudorGirba.28'; > package: 'PetitSmaltalk' with: 'PetitSmalltalk-lr.46'.] > > and when I run the test I get accessor error. > > Any idea what would be problem? > The VM? > > I use 5.7b3 > > Sted >

March 7, 2011