September 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12122
by StÃ©phane Ducasse Sept. 3, 2010

Sept. 3, 2010

12122 ----- - 2904 HelpSystemAPIBuilderFailsOnTraits. Thanks Laurent Laffont. Stef and Gabriel

1 0

[Pharo-project] PluggableShoutMorph >> okToStyle still make a reference to Preferences
by Cyrille Delaunay Sept. 3, 2010

Sept. 3, 2010

PluggableShoutMorph >> okToStyle still make a reference to Preferences, which is no longer present in pharo 1.2. It generate problem when opening a debugger for example (which is a problem :)). I opened an issue: http://code.google.com/p/pharo/issues/detail?id=2905

2 4

Re: [Pharo-project] [Pharo-users] TestSprinter
by StÃ©phane Ducasse Sept. 3, 2010

Sept. 3, 2010

icons to see which tests failed since last run and a summary previous run: current: 150 green 149 green 2 failure 2 failutres 1 errors could be presented differently On Sep 3, 2010, at 12:31 AM, Benjamin Van Ryseghem wrote: > Hello everybody > > I'm now working on a new Test Runner tool and I wonder which behaviours do you want me to implement. > > For now, I want the Test Sprinter to be able to : > - search through packages and classes thanks to search fields. > - browse the hierarchy from packages to test methods (with icons). > - create groups of tests easily re-runnable. > > If you have any ideas, I'm waiting for them ;) > > > Thank you > > > Ben _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

2 3

Re: [Pharo-project] [Moose-dev] Re: load moose in Pharo1.2
by Cyrille Delaunay Sept. 3, 2010

Sept. 3, 2010

Now I have exactly the same problem with 'PluggableShoutMorph' in the package Shout (This package is loaded with ConfigurationOfPetitParser). PluggableShoutMorph (like MOEaselTextEditor) declare the two instance variables 'styler' and 'unstyledAcceptText' which are already declared in the superclass PluggableTextMorph (in Pharo 1.2). Maybe those variable have been integrated in the superclass for pharo 1.2 and are no longer usefull ? Anyone know? 2010/9/2 Alexandre Bergel <alexandre(a)bergel.eu> > Strange indeed. This method is apparently never called. This is related > somehow to the completion (which does not work for me. I will contact > Lukas). > > Alexandre > > > On 2 Sep 2010, at 08:22, Cyrille Delaunay wrote: > > > What is strange, is that there is only one reference to > unstyledAcceptText, without affecting it a value. > > > > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> > > No, same problem now with 'unstyledAcceptText' > > > > > > 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> > > And does the loading work now? > > > > Doru > > > > > > On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: > > > > done > > > > 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> > > Yes, please rename it to shoutStyler. > > > > Cheers, > > Doru > > > > > > > > On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: > > > > So that means that a 'styler' instance variable has been defined in > PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the > Mondrian instance variable? > > > > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> > > So a solution is to load in a version of OmniBrowser that is compatible > with 1.2, before loading moose: > > > > (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. > > > > Now, I have another error: > > The class MOEaselTextEditor from Mondrian-Easel re-declare the instance > variable 'styler', which is already defined in its superclass > PluggableTextMorph. > > > > 2010/9/1 Lukas Renggli <renggli(a)gmail.com> > > > > Metacello is loading an ancient version of OB. References to > > Preferences have been removed a long time ago. However there is still > > a problem with the highlighting in Pharo 1.2. You only get a working > > environment if you do not load the package OB-Shout. > > > > Lukas > > > > On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote: > > > Hi Cyrille, > > > > > > That means that OB needs to be fixed :). Could you raise the issue on > the > > > pharo mailing list? > > > > > > Cheers, > > > Doru > > > > > > > > > On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > > > > > >> When I try with the configuration, I get an error when loading the > class > > >> OBMercuryPanel (from the package OB-Standard, that seems to be loaded > with > > >> ConfigurationOfMetacello): > > >> The initialize method is using the old class "Preferences" (that is no > > >> longer present in Pharo 1.2). > > >> > > >> 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> > > >> What do you mean by script? Did you try with the configuration? > > >> > > >> Doru > > >> > > >> > > >> > > >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com> > wrote: > > >> > > >> > Hello, > > >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere > to > > >> > that? > > >> > _______________________________________________ > > >> > Moose-dev mailing list > > >> > Moose-dev(a)iam.unibe.ch > > >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >> > > >> _______________________________________________ > > >> Moose-dev mailing list > > >> Moose-dev(a)iam.unibe.ch > > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >> > > >> _______________________________________________ > > >> Moose-dev mailing list > > >> Moose-dev(a)iam.unibe.ch > > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > -- > > > www.tudorgirba.com > > > > > > "When people care, great things can happen." > > > > > > > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)iam.unibe.ch > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > -- > > Lukas Renggli > > www.lukas-renggli.ch > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "When people care, great things can happen." > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "Being happy is a matter of choice." > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

3 5

[Pharo-project] [ANN] SqueakDBX 1.2 release
by Mariano Martinez Peck Sept. 3, 2010

Sept. 3, 2010

Hi folks. We are realeasing SqueakDBX 1.2, just an small release. For those who doesn't know, SqueakDBX is a database driver to connect to most of the existing databases. For more details, please read www.squeakdbx.org The main changes in this release are: - ConfigurationOfSqueakDBX version: 1.2 - Comments: SqueakDBX stable 1.2 - OpenDBX version: 1.5 - New Features - GlorpDBX connection pool for SqueakDBXDriver. Thanks to John Toohey for this contribution. - New support for Firebird 100% green tests in Windows. - New support for MySQL 4. - New tests for PostgreSQL sequences, for bad data settings, large objects, etc. - We now let a platform to set special options ALWAYS before opening the connection. - Packages remodularization and little changes so that to easily support ports, for example to Dolphin. - Start to support large objects. For the moment: Postgresql supports TEXT, MySQL supports TEXT and BLOB, and SQLite CLOB (error with BLOB), Oracle supports CLOB and NCLOB. - Added the possibility to enable or disable automatic release of connections using WeakRegistry. - Notes - Tested with Cog, resulting in an average of 3x increase and 100% green. - Tested in Pharo 1.0 and 1.1. - Updated Metacello configurations To install it: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSqueakDBX'; load. (ConfigurationOfSqueakDBX project version: '1.2') load. In Pharo 1.1 I recommend to evaluate the following: DBXPlatform disableAutomaticConnectionReleaseOnGC Cheers Mariano

1 0

[Pharo-project] Fwd: [squeak-dev] The Trunk: System-eem.366.mcz
by StÃ©phane Ducasse Sept. 3, 2010

Sept. 3, 2010

seems like we should do something :) Begin forwarded message: > From: John M McIntosh <johnmci(a)smalltalkconsulting.com> > Date: September 1, 2010 1:12:28 AM GMT+02:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Fwd: [squeak-dev] The Trunk: System-eem.366.mcz > Reply-To: johnmci(a)smalltalkconsulting.com > > In case this gets overlooked being hidden in a update for The Trunk: System-eem. > > The EndianCache does need to be cleared at shutdown versus in startup. > I can't speak for the SystemChangeNotifier since I'm not sure what the bug is.. > > Of course I'm not quite sure if anyone in the Pharo group looks and the trunk updates and moves things across? > > > Begin forwarded message: > >> From: commits(a)source.squeak.org >> Date: August 31, 2010 5:47:35 PM PDT >> To: squeak-dev(a)lists.squeakfoundation.org, packages(a)lists.squeakfoundation.org >> Subject: [squeak-dev] The Trunk: System-eem.366.mcz >> Reply-To: squeak-dev(a)lists.squeakfoundation.org >> >> Eliot Miranda uploaded a new version of System to project The Trunk: >> http://source.squeak.org/trunk/System-eem.366.mcz >> >> ==================== Summary ==================== >> >> Name: System-eem.366 >> Author: eem >> Time: 31 August 2010, 10:47:17.97 am >> UUID: 2126e5d9-4d47-4cc1-921f-daefd935aedd >> Ancestors: System-nice.365 >> >> Make sure system notifications for Smalltalk are up-to-date >> on start-up. >> Fix voiding of Smalltalk's endian cache which needs to be done >> in a timely manner. >> >> =============== Diff against System-nice.365 =============== >> >> Item was changed: >> ----- Method: SmalltalkImage class>>startUp (in category 'class initialization') ----- >> startUp >> + SystemChangeNotifier uniqueInstance notify: Smalltalk ofAllSystemChangesUsing: #event:! >> - "XXXX: This is broken. SmalltalkImage startUp happens quite late in the startup sequence; earlier startups may very well need the information about the endianness of the platform." >> - EndianCache := nil. >> - ! >> >> Item was changed: >> ----- Method: SmalltalkImage>>processShutDownList: (in category 'snapshot and quit') ----- >> processShutDownList: quitting >> + "Send #shutDown to each class that needs to wrap up before a snapshot. >> + Also void the endianness chace; this can't safely be done on start-up because >> + Smalltalk is too late in the start-up sequence." >> - "Send #shutDown to each class that needs to wrap up before a snapshot." >> >> + EndianCache := nil. >> + self send: #shutDown: toClassesNamedIn: ShutDownList with: quitting! >> - self send: #shutDown: toClassesNamedIn: ShutDownList with: quitting. >> - ! >> >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

5 6

[Pharo-project] A bit of publicity :)
by GermÃ¡n Arduino Sept. 2, 2010

Sept. 2, 2010

I asked to add Pharo, Seaside and Pier on http://www.findbestopensource.com/ Seems that are added!

2 1

[Pharo-project] seaside3+pharo1.1+cog?
by Esteban Lorenzano Sept. 2, 2010

Sept. 2, 2010

Hi, I wonder if this combination is working... I need to do a quick prototype and I want to make it using this combination. I know there were some problems with seaside+cog... but maybe they are fixed now :) Cheers, Esteban

5 4

[Pharo-project] EntryFieldMorph enhancements
by Fernando olivero Sept. 2, 2010

Sept. 2, 2010

SLICE-Issue-2903-EntryFieldHasErrorAndGrayedLabel-FernandoOlivero.1 The idea is to have specialized Editors that know the validity of the contents being edited. For example i'm working on a CompletionEditor, which knows if the contents are a valid class of the system. For now i've added the method Editor>>hasError ^ false. I will push the CompletionEditor, and the CompletionEntryFieldMorph in a new issue. I've also added the grayed out background label , setted by sending #initialContents. Fernando

1 0

Re: [Pharo-project] Problems in loading GLORP
by Alberto Bacchelli Sept. 2, 2010

Sept. 2, 2010

> BTW, last week I wrote a metacello configuration group to load GlorpDBX with the native postgres driver. You can evaluate first: > > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfGlorpDBX'; > load. > > and then > > (ConfigurationOfGlorpDBX project version: '1.2') load: 'All with PostgreSQL native > Hi, I followed your instructions and I've been able to load GLORP on a Moose Nightly Built image [1]. I run the 844 tests. 839 of them passed (wow), 4 failed and 1 generated an error. These are the problematic ones: GlorpManyToManyDBTest>>#testReadNodeAndDeleteChildWithSaveAndContinue GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary GlorpDateTest>>#testDate GlorpObjectMappedToImaginaryTableTest>>#testReadBackEntireExample GlorpUnitOfWorkTest>>#testRollbackOneToManyAfterAdd Are these tests failing also on other Pharo images (i.e., they are known "problems")? Do you know the impact of these failures? will GLORP be reliable without them? Moose developers, would you include GLORP in the images built by hudson? I think 839 passing tests are good enough for the development image. Ciao, Alberto [1] http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/

2 1