- Pharo-dev - lists.pharo.org

[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

Re: [Pharo-project] Persistence options

by mail list

I have been using goods in production with 3 images banging away at it on Pharo 1.3. It has been working well. (Some days it fires out over 50K emails/sms/apple push notifications so it is reasonbly significant under load) I run a daily backup of the database using an expect script. I am having problems upgrading to Pharo 1.4 but I think that this is just my problem that i need to address. S. On Jun 26, 2012, at 2:22 PM, Milan Mimica wrote: > I've been using Glrop for 3 weeks now (not much I know) to link an existing application data model to an existing RDMS model with all sorts of weird mappings and it works fine. Several times I have started to write patches but it turned out it was a problem in my code. Diagnostics could be better. > This same app was running on Magma (never in production) and it also worked like a charm, If you don't mind your data being stored in some format no one else can read. > > > On 25 June 2012 21:41, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > there are various options for persistence in Pharo > and Seaside. > > What do people use for their applications? Any > experiences or numbers to share? > > I'm interested in both, mainly with the focus on > options for RDBM systems. Whats is the state of Glorp? > > Thx > T. > -- > NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! > Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a > > > > > -- > Milan Mimica > http://sparklet.sf.net

June 26, 2012

Re: [Pharo-project] Persistence options

by Guillermo Polito

Not being Glorp's author, I can tell it has over 600 green tests on pharo. Of course it can have it's problems, but you have some confidence it is ok, and some sources for examples :). On Tue, Jun 26, 2012 at 9:43 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > while a lot of years of suffering are clamming that I need to say: "don't > use RDBMs if you can avoid it", I also should point you to > http://dbxtalk.smallworks.com.ar/, and GlorpDbx which is around and is > the newer port to Pharo you can find :) > > Esteban > > > On Jun 26, 2012, at 8:53 AM, Sven Van Caekenberghe wrote: > > > On 25 Jun 2012, at 21:41, Torsten Bergmann wrote: > > I'm interested in both, mainly with the focus on > > options for RDBM systems. Whats is the state of Glorp? > > > If have been using Glorp with Postgresql and it works surprisingly well. > It is 'good old technology', not as sexy as all this NoSQL stuff, but > reliable, well-known. > I think that Glorp is one of the coolest OO-RDBMS mappers around, in any > language. > > Sven > > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > > > >

June 26, 2012

Re: [Pharo-project] Persistence options

by Esteban Lorenzano

while a lot of years of suffering are clamming that I need to say: "don't use RDBMs if you can avoid it", I also should point you to http://dbxtalk.smallworks.com.ar/, and GlorpDbx which is around and is the newer port to Pharo you can find :) Esteban On Jun 26, 2012, at 8:53 AM, Sven Van Caekenberghe wrote: > > On 25 Jun 2012, at 21:41, Torsten Bergmann wrote: > >> I'm interested in both, mainly with the focus on >> options for RDBM systems. Whats is the state of Glorp? > > If have been using Glorp with Postgresql and it works surprisingly well. > It is 'good old technology', not as sexy as all this NoSQL stuff, but reliable, well-known. > I think that Glorp is one of the coolest OO-RDBMS mappers around, in any language. > > Sven > > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > >

June 26, 2012

Re: [Pharo-project] Pharo and Namespaces

by StÃ©phane Ducasse

BTW we want to finish what we are doing before opening new actions. > Since Colin opened a new thread on Squeak-dev about namespaces > together with an implementation for environments: > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2012-June/164605.html > > I thought it would be good to ask on Pharo too about the state. > > What happened to the project from GermÃ¡n Leiva > http://www.youtube.com/watch?v=n4I7fSVNX2A > > I know it is always a time issue - but what is the overall plan? > > 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

Re: [Pharo-project] Pharo and Namespaces

by StÃ©phane Ducasse

We are working on a module system but it takes time. > Since Colin opened a new thread on Squeak-dev about namespaces > together with an implementation for environments: > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2012-June/164605.html > > I thought it would be good to ask on Pharo too about the state. > > What happened to the project from GermÃ¡n Leiva > http://www.youtube.com/watch?v=n4I7fSVNX2A we do not want class level namespace because this is the mess > > I know it is always a time issue - but what is the overall plan? > > 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