- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] SqueakDBX 1.2 release

by Mariano Martinez Peck

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

Sept. 3, 2010

Re: [Pharo-project] TestSprinter

by Lukas Renggli

On 3 September 2010 02:57, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > xÂ For the latter, I find there is no competition (yet anyway) for a TesCase class side method called #prod: which runs a single test method and either does nothing (good news) or raises a walkback. That's what OB-SUnitIntegration does when you press Cmd+T on a test method/class/package. Also note that you can directly jump to a debugger in the beginning of the test (no matter if it is failing or not) by pressing Cmd+D on a test method. Lukas -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2010

Re: [Pharo-project] Object visitor

by Martin Dias

On Thu, Sep 2, 2010 at 4:53 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Yes. > Visitor is a convenient pattern to perform a computation over each element > of a recursive data structure. > This pattern works well for trees. You need to pay attention to cycle when > using it on a graph. This might be expensive if you have a large graph and > you use a set to keep track of the element you run over. > > It has to be as faster as possible, but I think that the Set would be ok. > Do you want to do this on any object of the image? > > Yes, for any object. It's for serializing a graph of objects into a stream. We need to iterate over the transitive closure of object references. Do you know an existing package that implements this pattern? > Alexandre > > > Thank you for the answer Martin > On 2 Sep 2010, at 10:36, Martin Dias wrote: > > > Hi, > > > > We want to do some processing over the graph of object references. > > > > Do you recommend an implementation of visitor pattern to iterate object > instance variables? > > > > Best regards, > > Martin and Tristan > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 3, 2010

Re: [Pharo-project] [Pharo-users] TestSprinter

by Lukas Renggli

> 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 I doubt that this is useful within an image. I run different sub-sets of my tests far too often to see something meaningful between the current and previous run. Hudson shows the deltas of errors/failures/passes and added/removed tests between builds in various graphs and tables. Lukas -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2010

Re: [Pharo-project] Native (OS-level) windows

by John M McIntosh

There are three parts to your question (a) Does the VM you want to use support Ffenestri, you will need to look at the source code on squeakvm.org SVN tree to understand the answer to that. That would be if the HostWindowPlugin is supported. (b) Does the Smalltalk code allow you to call the HostWindowPlugin api? (c) Does the event loop logic in the Smalltalk code support the following incoming event types. #define WindowEventMetricChange 1 /* size or position of window changed - value1-4 are left/top/right/bottom values */ #define WindowEventClose 2 /* window close icon pressed */ #define WindowEventIconise 3 /* window iconised or hidden etc */ #define WindowEventActivated 4 /* window made active - some platforms only - do not rely upon this */ #define WindowEventPaint 5 /* window area (in value1-4) needs updating. Some platforms do not need to send this, do not rely on it in image */ #define WindowEventStinks 6 /* this window stinks (just to see if people read this stuff) */ In general people want multiple window support right up to the point where they have to implement the GUI part, then they lose interest & bail... Macintosh Carbon VMs 4.2.x and lower support Ffenestri at the VM level, Cocoa VMs 5.x have not been tested due to lack of interest. I've heard that Windows and Unix versions may or may not support them, see (a). On 2010-09-02, at 11:15 PM, Evgeniy Philippov wrote: > Hello folks and Todd Blanchard, > > I have three questions. First question is---what is the current status of Ffenestri, and where can I download some version of Pharo with the most up-to-date Ffenestri support? The second question is---what are the other Pharo OS-level windowing interfaces, and what is their status? And the last question is---what is more complete: Squeak's Ffenestri support, or Pharo's Ffenestri support? > > My intents. I plan to use some version of Squeak or Pharo system for my project (which is a hobby project), and I am mainly interested in OS-level windowing for Linux (Ubuntu) and to a lesser extent for Win32 too. I studied wxSqueak a bit, and concluded that Ffenestri is overall simpler to develop than wxSqueak, and guessed that Ffenestri moves/will move faster when considering the completeness of it, than wxSqueak. > > -- > Evgeniy > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Sept. 3, 2010

Re: [Pharo-project] TestSprinter

by Mariano Martinez Peck

Benjamin, you should read all these threads completly. http://forum.world.st/SUnit-td1297972.html#a1297972 http://forum.world.st/SUnit-td1297972i20.html#a1297974 http://forum.world.st/akuhn-SUnit-chrisma-edition-td1297672.html#a1297672 Read them completly. There a lot of code already done, and a lot of ideas already said. I don't know the status. thus. Cheers Mariano 2010/9/3 Benjamin Van Ryseghem <benjamin.vanryseghem(a)gmail.com> > 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-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 3, 2010

Re: [Pharo-project] Experimental Cocoa OS-X based Squeak Cog JIT VM 5.8b7

by John M McIntosh

Doru, can you send me the crash report? To fix I'll need that. The VM is compiled with the 10.5.x SDK and should work on it. On 2010-09-02, at 10:25 PM, Tudor Girba wrote: > Hi John, > > I tried the VM on Mac OS X 10.5.8 and it just crashes on an image that works perfectly with 5.8.b4. > > I will soon upgrade to Snow Leopard (finally :)), but I can still play around today if you want me to test further. > > Cheers, > Doru > -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Sept. 3, 2010

Re: [Pharo-project] [Pharo-users] TestSprinter

by StÃ©phane Ducasse

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

Sept. 3, 2010

Re: [Pharo-project] Single instance executables

by StÃ©phane Ducasse

;) Stef On Sep 2, 2010, at 11:59 PM, Henrik Sperre Johansen wrote: > On 02.09.2010 21:45, Schwab,Wilhelm K wrote: >> Hello all, >> >> I realize that I hold an unpopular position on this, but it *will* come back to haunt us: we need to have a way to warn the user if a second copy of Pharo is launched. Random meltdowns and lost work will result from the current behavior. Let me be more bold: lost work and random corrrupted images *are resulting* from the current behavior; they are either unrecognized, or simply ignored, but it is happening. >> >> Is there a way to fix it? On Windows, I recall creating an OS semaphore with a given name and if that exists, bail out before the session even gets going. We would need a cross-platform way to do that (or at least a Linux/Mac way to do it - Windows has a mechanism), and then a place to abort startup early enough to prevent problems. Any ideas? >> >> Bill > On Windows, it will give you an error that it was unable to open the changes file when you open the second image. > > Cheers, > Henry > > PS. I think Steph agrees, given his experience with updates that mysteriously contain seemingly random bits of other methods' source code :) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 3, 2010

Re: [Pharo-project] Fwd: [squeak-dev] The Trunk: System-eem.366.mcz

by Tudor Girba

Hi, Indeed, it would be great to get this restarted. I do not have enough capacity to drive, but I can help. Doru On 2 Sep 2010, at 09:27, StÃ©phane Ducasse wrote: > What we started to do and got stalled (for RPackage) is to implement > SystemAnnouncement > a hierarchy that wrap event and should be ready to replace > SystemChangeNotifier. > Alain told me that he wants to help for RPackage so we should get > some speed on that. > Alain if you load ConfigurationOfRPackage in PharoTaskForces you > will see what I mean. > Stef > > > On Sep 1, 2010, at 10:48 PM, Henrik Sperre Johansen wrote: > >> Just remember to add corresponding deregistration in shutdown if >> SystemChangeNotifier is reimplemented using Announcements :) >> >> (hint: Announcers do not care if objects register multiple times to >> the same Announcement) >> >> Cheers, >> Henry >> >> On 01.09.2010 22:41, StÃ©phane Ducasse wrote: >>> muchas gratias. >>> >>> >>> Stef >>> >>> On Sep 1, 2010, at 9:08 PM, Adrian Lienhard wrote: >>> >>>> I created a changeset and attached it to the appropriate ticket: http://code.google.com/p/pharo/issues/detail?id=2896 >>>> >>>> Adrian >>>> >>>> On Sep 1, 2010, at 09:52 , StÃ©phane Ducasse wrote: >>>> >>>>> 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 >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> = >>>>>> ================================================================= >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Sept. 3, 2010