August 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Vm-dev] Android Cog VM/Pharo Builds at INRIA Jenkins
by StÃ©phane Ducasse Aug. 8, 2012

Aug. 8, 2012

thanks Dmitry I'm sure that igor would love that you use the vm blog to collect vm information :). Stef On Aug 7, 2012, at 4:04 PM, Dmitry Golubovsky wrote: > > Hi, > > There are two CI (continuous integration) jobs running periodically at > the INRIA Jenkins server: CogDroid and PharoDroid. The former is an > unbundled NonJIT Cog VM for Android which can run any Smalltalk image > original Cog VM can run. The latter is the same Cog VM bundled with a > generic Pharo 1.4 Smalltalk image. These two builds complement each > other, and together they comprise an Android analog of the one-click > Pharo distribution: a practically usable piece of software ready for > development and exploration of possible uses of Smalltalk on mobile > devices. > > Whoever is interested to try Pharo and other compatible Smalltalk > implementations on Android devices are welcome to use these builds. A > brief overview with installation and usage recommendations can be > found here: > > http://code.google.com/p/squeakvm-tablet/wiki/JenkinsBuilds > > The developer of CogDroid and PharoDroid hopes that these new Android > applications will help the adoption of Smalltalk for writing > applications for mobile devices. > > Any thoughts, suggestions and critics are welcome. > > Thanks. > > -- > Dmitry Golubovsky > > Anywhere on the Web

1 0

Re: [Pharo-project] R.I.P. SystemChangeNotifier
by Fernando Olivero Aug. 7, 2012

Aug. 7, 2012

Goodbye Pen, ImageSegment, FileDirectory, and now SystemChangeNotifier! NICE work you guys! (Soon, we will even have an image without Morphic at all... ) We need to make a graveyard (a fun web page for the Pharo site? ) for all deceased objects, so we don't forget them, and why we chose to let them die... Fernando On Tue, Aug 7, 2012 at 3:46 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Tue, Aug 7, 2012 at 12:50 PM, Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> wrote: > Hi, > > Today we finally finish the removal of SystemChangeNotifier. This is a big step forward to unify all system events into announcements. Current notification center is named "SystemAnnouncer" and all events has been reified into more meaningful announcements... > This operation was really hard because is like changing the heart of a living person :) > For 99.99% of users, this will be absolute transparent, but there are some cases where maybe some problems emerge. Please, take this into account to migrate your code soon. > Don't wait until is to late! > > > mmmmm did you remove #doSilently: ? > > > -- > Mariano > http://marianopeck.wordpress.com >

1 0

[Pharo-project] Android Cog VM/Pharo Builds at INRIA Jenkins
by Dmitry Golubovsky Aug. 7, 2012

Aug. 7, 2012

Hi, There are two CI (continuous integration) jobs running periodically at the INRIA Jenkins server: CogDroid and PharoDroid. The former is an unbundled NonJIT Cog VM for Android which can run any Smalltalk image original Cog VM can run. The latter is the same Cog VM bundled with a generic Pharo 1.4 Smalltalk image. These two builds complement each other, and together they comprise an Android analog of the one-click Pharo distribution: a practically usable piece of software ready for development and exploration of possible uses of Smalltalk on mobile devices. Whoever is interested to try Pharo and other compatible Smalltalk implementations on Android devices are welcome to use these builds. A brief overview with installation and usage recommendations can be found here: http://code.google.com/p/squeakvm-tablet/wiki/JenkinsBuilds The developer of CogDroid and PharoDroid hopes that these new Android applications will help the adoption of Smalltalk for writing applications for mobile devices. Any thoughts, suggestions and critics are welcome. Thanks. -- Dmitry Golubovsky Anywhere on the Web

2 1

[Pharo-project] R.I.P. SystemChangeNotifier
by Esteban Lorenzano Aug. 7, 2012

Aug. 7, 2012

Hi, Today we finally finish the removal of SystemChangeNotifier. This is a big step forward to unify all system events into announcements. Current notification center is named "SystemAnnouncer" and all events has been reified into more meaningful announcements... This operation was really hard because is like changing the heart of a living person :) For 99.99% of users, this will be absolute transparent, but there are some cases where maybe some problems emerge. Please, take this into account to migrate your code soon. Don't wait until is to late! Cheers, Esteban

4 3

[Pharo-project] [update 2.0] #20245
by Esteban Lorenzano Aug. 7, 2012

Aug. 7, 2012

20245 ----- Issue 6510: update zinc http://code.google.com/p/pharo/issues/detail?id=6510 Issue 6514: Add allDefinedExtensionMethods to RPackage http://code.google.com/p/pharo/issues/detail?id=6514 Issue 6521: RPackageOrganizer>>initialize does not initialize from scratch http://code.google.com/p/pharo/issues/detail?id=6521 Issue 6523: Bug in RPackage >> systemSubPackages http://code.google.com/p/pharo/issues/detail?id=6523 Issue 6526: RPackage is not removing extensions from a removed class http://code.google.com/p/pharo/issues/detail?id=6526

4 4

[Pharo-project] [update 2.0] #20246
by Esteban Lorenzano Aug. 7, 2012

Aug. 7, 2012

20246 ----- Issue 6518: SystemChangeNotifier - cleanup step 4 http://code.google.com/p/pharo/issues/detail?id=6518 Issue 6524: StartupPreferences loads non-Smalltalk files http://code.google.com/p/pharo/issues/detail?id=6524 Issue 6528: GroupAnnouncer announcer DNU http://code.google.com/p/pharo/issues/detail?id=6528 Issue 6529: Method changes not picked up by MC Browser http://code.google.com/p/pharo/issues/detail?id=6529

1 0

[Pharo-project] Jenkins: SCM polling activity overload
by Sean P. DeNigris Aug. 7, 2012

Aug. 7, 2012

See https://ci.lille.inria.fr/pharo/descriptor/hudson.triggers.SCMTrigger/ : There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands. Check if your polling is hanging, and/or increase the number of threads if necessary. The following polling activities are currently in progress: Project â Running for Scripts-download 18 hr -- View this message in context: http://forum.world.st/Jenkins-SCM-polling-activity-overload-tp4643404.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] Integrating Issue 6524: StartupPreferences loads non-Smalltalk files
by Sean P. DeNigris Aug. 7, 2012

Aug. 7, 2012

Issue 6524: StartupPreferences loads non-Smalltalk files http://code.google.com/p/pharo/issues/detail?id=6524 I'd like to get this integrated ASAP. Thanks, Sean -- View this message in context: http://forum.world.st/Integrating-Issue-6524-StartupPreferences-loads-non-S… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 3

[Pharo-project] SqueakSource is down
by DeNigris Sean Aug. 7, 2012

Aug. 7, 2012

http://www.downforeveryoneorjustme.com/http://www.squeaksource.com

1 0

[Pharo-project] Playing with a declarative startup/shutdown subscription mechanism
by Guillermo Polito Aug. 6, 2012

Aug. 6, 2012

Hi! Last days I was playing to replace the image startup/shutdown mechanism via a pragma subscription because I was pissed off with how difficult is to integrate the change of a new startup in the system. The idea is: - reduce the mess on subscription/unsubscription, initialization, etc - reduce dependencies of external packages in core packages. This way, if you want to subscribe a class side method to be executed on startup, you annotate it: SomeClass>>startUp: resuming <systemStartup: #application> self blahblah. SomeClass>>startUp: quitting <systemShutdown: #kernel> self blahblah. Now, instead of an order in classes startup, I played with the idea of having run levels (which I named #kernel, #application and #user because I was not inspired :P). Then I replaced the whole system startup and It's working... The code is very simple, you can have a look at the category *System-Tasks*which can be downloaded from: MCGemstoneRepository location: 'http://ss3.gemstone.com/ss/PharoTaskForces' user: '' password: '' SLICE-Issue-666-Playing-With-startup-GuillermoPolito.2 Be careful, that package contains the startup code + the replacement of the old startup by the new one :). Now, I'd like to have some feedback, u like it? u buy it? which should be the names for the run levels? how many run levels should we have? :P Cheers, Guille

5 6