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

[Pharo-project] git victim

by Camillo Bruni

I am looking for a volunteer / slave / victim.. Is anyone interested in filing out all versions of Pharo 2.0 to git using filetree? I want to have a git repository with all the sources filed out, so we can properly track and annotate changes! (hint to all data miners out there) -------------------------------------------------------------------------- I started a jenkins job (99% finished) https://ci.lille.inria.fr/pharo/job/Pharo2.0-Git-Export/ which will commit each new pharo version to our github repository git@github.com:PharoProject/pharo-core.git Now of course this would make more sense to do with all versions (0.9 ... 2.0) ! -------------------------------------------------------------------------- best cami

June 26, 2012

Re: [Pharo-project] MetacelloPharoPlatform>>#do:displaying:

by Sean P. DeNigris

Sven Van Caekenberghe wrote > > MetacelloPharoPlatform>>#do:displaying: > should be using #current: instead of #value: > I created an issue and posted to the Metacello list... http://forum.world.st/MetacelloPharoPlatform-gt-gt-do-displaying-for-Pharo-… Cheers, Sean -- View this message in context: http://forum.world.st/MetacelloPharoPlatform-do-displaying-tp4636668p463668… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 26, 2012

Re: [Pharo-project] Persistence options

by Mariano Martinez Peck

On Tue, Jun 26, 2012 at 2:21 PM, Philippe Marschall < philippe.marschall(a)netcetera.ch> wrote: > On 06/26/2012 12:32 PM, Mariano Martinez Peck wrote: > > 2012/6/26 Torsten Bergmann <astares(a)gmx.de> > > > >> Regarding Glorp: how well does the Pharo port work with > >> non-Postgresql already: MySQL, SQLServer, Oracle, Firebird, ... ? > >> > > > > They do all work with OpenDBXDriver. Of course you will need the OpenDBX > > library and the database client library. > > For Glorp, it is working for: Oracle, MySql, PostgreSQL, SQLite, > SqlServer > > and ODBC > > You should probably add that without an mt VM the drivers either block > or poll. This is hardly ideal and not comparable to the "native" > PostgreS and MySQL drivers that use sockets and don't have these issues. > > Indeed. But it seems that with our "mini-locks" or busy waiting in the image side is enough for the real existing users. Nobody actually complained about this limitation. In fact, in VW, by default, queries are blocking... they are *not* azync unless you explicitly tell it. This is because creating threads also take time and if most of the queries are fast, then it is even better the locking strategy. > Cheers > Philippe > > > > -- Mariano http://marianopeck.wordpress.com

June 26, 2012

Re: [Pharo-project] Persistence options

by Philippe Marschall

On 06/26/2012 12:32 PM, Mariano Martinez Peck wrote: > 2012/6/26 Torsten Bergmann <astares(a)gmx.de> > >> Regarding Glorp: how well does the Pharo port work with >> non-Postgresql already: MySQL, SQLServer, Oracle, Firebird, ... ? >> > > They do all work with OpenDBXDriver. Of course you will need the OpenDBX > library and the database client library. > For Glorp, it is working for: Oracle, MySql, PostgreSQL, SQLite, SqlServer > and ODBC You should probably add that without an mt VM the drivers either block or poll. This is hardly ideal and not comparable to the "native" PostgreS and MySQL drivers that use sockets and don't have these issues. Cheers Philippe

June 26, 2012

[Pharo-project] MetacelloPharoPlatform>>#do:displaying:

by Torsten Bergmann

Sven wrote: >This was *very* annoying, getting a deprecation a million times when load a >Metacello config. > >MetacelloPharoPlatform>>#do:displaying: > >should be using #current: instead of #value: >... >I am not suret where this class lives or comes from. Yes this is annoying in Pharo 2.0 when deprecation is "on" in the compiler settings. The class is from Metacello-Platform.pharo-dkh.27 http://seaside.gemstone.com/ss/metacello.html ask Dale to integrate the fix or give you write permission for the metacello repo. A workaround is to disable the deprecations in the settings. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

June 26, 2012

[Pharo-project] MetacelloPharoPlatform>>#do:displaying:

by Sven Van Caekenberghe

This was *very* annoying, getting a deprecation a million times when load a Metacello config. MetacelloPharoPlatform>>#do:displaying: should be using #current: instead of #value: do: aBlock displaying: aString self bypassProgressBars ifTrue: [ ^super do: aBlock displaying: aString ]. aString displayProgressAt: Sensor cursorPoint from: 0 to: 2 during: [:bar | bar current: 1. aBlock value. bar current: 2 ] (fileout attached). I am not suret where this class lives or comes from. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

June 26, 2012

Re: [Pharo-project] Because we do not have enough failing tests...

by StÃ©phane Ducasse

I would really to move the test to their "conceptual package" and added in the associated configuration. Right now I'm sick and cannot promise anything. stef On Jun 26, 2012, at 12:27 PM, Pavel Krivanek wrote: > ...I tried to fix the the Jenkins Tests job for Pharo Kernel to > process all kernel related jobs and not only a subset that was > loadable without errors. So now we have 170 failures. > > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/job/Pharo%20Kernel%… > > Most of them are related to bad packaging - for example > TextDiffBuilderTest is between System tests, Compiler tests are > dependent on Morphic etc. > > Fuel tests are not processed because of the archive error. Graphics > Tests are not loaded too. They should be divided because they mix file > formats tests with Point and Form tests. And of course the Tests > package must be divided because it contains tests for Monticello, > Polymorph etc. This are the only categories from this package I load: > > Tests-Bugs > Tests-CodeImport > Tests-Compression > Tests-Exceptions > Tests-Files > Tests-Finalization > Tests-Localization > Tests-Object Events > Tests-ObjectsAsMethods > Tests-Release > Tests-System > Tests-System-CommandLine > Tests-SystemChangeNotification > Tests-SystemTests-Support > Tests-Traits > Tests-Traits-MOP > Tests-VM > > There is some minor issue with Tests-System because it includes a > class with shared pools. That makes problems with fileIn and fileOut > of this category. > > Cheers, > -- Pavel >

June 26, 2012

Re: [Pharo-project] Persistence options

by Mariano Martinez Peck

2012/6/26 Torsten Bergmann <astares(a)gmx.de> > Regarding Glorp: how well does the Pharo port work with > non-Postgresql already: MySQL, SQLServer, Oracle, Firebird, ... ? > They do all work with OpenDBXDriver. Of course you will need the OpenDBX library and the database client library. For Glorp, it is working for: Oracle, MySql, PostgreSQL, SQLite, SqlServer and ODBC See: http://rmod.lille.inria.fr/archives/talks/2012-PharoConf-DBXTalk.pdf Cheers, -- Mariano http://marianopeck.wordpress.com

June 26, 2012

[Pharo-project] Persistence options

by Torsten Bergmann

Regarding Glorp: how well does the Pharo port work with non-Postgresql already: MySQL, SQLServer, Oracle, Firebird, ... ? Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

June 26, 2012

[Pharo-project] Because we do not have enough failing tests...

by Pavel Krivanek

...I tried to fix the the Jenkins Tests job for Pharo Kernel to process all kernel related jobs and not only a subset that was loadable without errors. So now we have 170 failures. https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/job/Pharo%20Kernel%… Most of them are related to bad packaging - for example TextDiffBuilderTest is between System tests, Compiler tests are dependent on Morphic etc. Fuel tests are not processed because of the archive error. Graphics Tests are not loaded too. They should be divided because they mix file formats tests with Point and Form tests. And of course the Tests package must be divided because it contains tests for Monticello, Polymorph etc. This are the only categories from this package I load: Tests-Bugs Tests-CodeImport Tests-Compression Tests-Exceptions Tests-Files Tests-Finalization Tests-Localization Tests-Object Events Tests-ObjectsAsMethods Tests-Release Tests-System Tests-System-CommandLine Tests-SystemChangeNotification Tests-SystemTests-Support Tests-Traits Tests-Traits-MOP Tests-VM There is some minor issue with Tests-System because it includes a class with shared pools. That makes problems with fileIn and fileOut of this category. Cheers, -- Pavel

June 26, 2012