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

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

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

>> > > Your image helps me a lot. > > I'm trying to get the Squeak VM compiling with Adobe Alchemy. tell us more :) > Alchemy is a C compiler targeting the flash VM. ? the flash use bytecode? why does it need a C compiler? > 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! Tell us more :) Stef > > Thanks! > > >

March 7, 2011

Re: [Pharo-project] Assert SystemWindow not visible

by Gary Chambers

If you don't care whether the window had been opened at all then sending #isInWorld to the window is another approach. Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, March 02, 2011 12:37 PM Subject: Re: [Pharo-project] Assert SystemWindow not visible Thank you Henry, good example. Laurent. On Wed, Mar 2, 2011 at 10:35 AM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: Henrik Sperre Johansen wrote: > > > window announcer when: WindowClosed do: [closed := false]. > window openInWorld delete. > self assert: closed. > > meant to write [closed := true], of course :) Cheers, Henry -- View this message in context: http://forum.world.st/Assert-SystemWindow-not-visible-tp3330492p3331232.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 7, 2011

Re: [Pharo-project] Issue 3772 in pharo: taskbar doesnât adapt to resized window

by pharo＠googlecode.com

Comment #1 on issue 3772 by gazzagu...(a)googlemail.com: taskbar doesnât adapt to resized window http://code.google.com/p/pharo/issues/detail?id=3772 Menus in Morphic effectively run their own event loop (using #doOneSubCycle) whereas screen size checking is only done in #doOneCycle (from the main World event loop). Whilst the menu is open screen size changes are not handled.

March 7, 2011

[Pharo-project] OSProcess

by StÃ©phane Ducasse

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