- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Persistence options

by Philippe Marschall

On 06/26/2012 02:26 PM, Mariano Martinez Peck wrote: > 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. If it works for you that's great. It's just one of these things that you want to know up front instead of finding out later. Cheers Philippe

June 26, 2012

Re: [Pharo-project] git victim

by Dale Henrichs

June 26, 2012

Re: [Pharo-project] Code completion in all tools

by Sean P. DeNigris

Sean P. DeNigris wrote > > Issue 6146: Code completion in all tools - Part 2 > http://code.google.com/p/pharo/issues/detail?id=6146 > Will someone please review this fix. Right now, methods are highlighted in all-red in the tools... -- View this message in context: http://forum.world.st/Code-completion-in-all-tools-tp4636201p4636701.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 26, 2012

[Pharo-project] Integrating OSProcess?

by Sean P. DeNigris

Issue 5796: Integrate OSProcess http://code.google.com/p/pharo/issues/detail?id=5796 Are we doing this? If so, are we forking it (I hope not), or just integrating updated package versions as Dave releases them? Sean -- View this message in context: http://forum.world.st/Integrating-OSProcess-tp4636695.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 26, 2012

Re: [Pharo-project] git victim

by Serge Stinckwich

Maybe with the new Metacello API for github this is possible without having a slave ;-) On Tue, Jun 26, 2012 at 8:19 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > 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 -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

June 26, 2012

[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