June 2010 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Writing extensions

by Mariano Martinez Peck

Hi Bob and welcome. There are two possibiities I know to write/communicate to C: - The FFI plugin is intended to call external libraries from Smalltalk http://wiki.squeak.org/squeak/1414 http://forum.world.st/FFI-Documentation-td2225148.html#a2225148 - Write your own VM primitives http://wiki.squeak.org/squeak/356 http://wiki.squeak.org/squeak/3336 http://wiki.squeak.org/squeak/6102 Probably there are much more links, but maybe this is enough to remember you what you used. Let us know Mariano On Mon, Jun 14, 2010 at 9:02 PM, Bob Cowdery <bob(a)bobcowdery.plus.com>wrote: > Hi all, > > I played with Squeak about 4 years ago and I built some extensions in C. > I would like to do the same again with Pharo and I have a big lump of C > I would like to interface to. I can't actually remember what I did > before and can't seem to find the tutorial I used. Could somebody point > me in the right direction please. > > Thanks > Bob > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 21, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Sven Van Caekenberghe

Mariano, I made my own loader and patches packages for loading Glorp+PostgresV2 into Pharo 1.1rc2. Both can be found at http://www.squeaksource.com/ADayAtTheBeach GlorpPostgreSQLPharoLoader-SvenVanCaekenberghe.3.mcz GlorpPostgreSQLPharoPatches-SvenVanCaekenberghe.1.mcz All PostgresV2 tests succeed, as do all GlorpTest-DBTests. The GlorpTest package has the following result: 844 run, 838 passes, 0 expected failures, 4 failures, 2 errors, 0 unexpected passes Failures: GlorpSelectCommandTest>>#testExecute GlorpUnitOfWorkTest>>#testRollbackOneToManyAfterAdd GlorpDateTest>>#testDate GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary Errors: GlorpManyToManyDBTest>>#testReadNodeAndDeleteChildWithSaveAndContinue GlorpObjectMappedToImaginaryTableTest>>#testReadBackEntireExample My own code runs fine though. I hope you consider my patches, thanks, Sven BTW: the original #timestampWithTimezoneConverter simply could never work: it expects a +/- sign inbetween the timezone's offset's hour and minute fields ! it falls out of the tests because only timestamo without timezones are used.

June 14, 2010

Writing extensions

by Bob Cowdery

Hi all, I played with Squeak about 4 years ago and I built some extensions in C. I would like to do the same again with Pharo and I have a big lump of C I would like to interface to. I can't actually remember what I did before and can't seem to find the tutorial I used. Could somebody point me in the right direction please. Thanks Bob

June 14, 2010

Re: [Pharo-users] [SPAM] Re: WebClient

by Sven Van Caekenberghe

StÃ©phane, On 11 Jun 2010, at 23:09, StÃ©phane Ducasse wrote: > Hi sven > >> Hi, >> >> Andreas Raab's 'new' WebClient/WebServer seems quite nice, as he says himself: >> >> As a result, we now have what I think is a pretty decent HTTP server and client implementation for Squeak 4.1 and hopefully we can nuke HTTPSocket sometime soon. WebClient is superior in every respect. >> >> Is this something that will / should fit seamlessly into Pharo ? Or even become preinstalled ? > > could be but not at the price to have concatenation of string and numbers. > So this means that somebody would have to do a pass on the code and produce a pharo version that squeakers may want or not. I went over the code and produced a version of WebClient-Core (and WebClient-Test) that passes all units tests in Pharo 1.1 rc 2: Filename: WebClient-Core-SvenVanCaekenberghe.24.mcz Author: Sven Van Caekenberghe Timestamp: 14 June 2010 4:24:21 pm UUID: 92b7f407-8df1-4472-962b-45d99f2364b8 Ancestors: WebClient-Core-ar.23.mcz Filename: WebClient-Tests-SvenVanCaekenberghe.12.mcz Author: Sven Van Caekenberghe Timestamp: 14 June 2010 4:25 pm UUID: f495c2cd-54bb-42a9-a6d7-f380cd656f3f Ancestors: WebClient-Tests-ar.11.mcz Both at http://www.squeaksource.com/ADayAtTheBeach. The only remaining method needed from the old WebClient-Pharo package is String#squeakToUtf8 squeakToUtf8 "Convert the receiver into a UTF8-encoded string" ^self convertToWithConverter: UTF8TextConverter new. There are only 4 callers so I could change that as well, should I ? I checked the references to UTF8TextConverter and it feels as if you don't want a method like #squeakToUtf8 (apart from the name ;-) >> I didn't try his ConfigurationOfWebClient since the last version was unreadable and it seemed like an experiment, while his textual explanation was easy to follow. >> >> To load it into and to make the unit tests run in Pharo 1.0 I had to make a couple of fixes (to WebCookie#printOn: and WebServer class#serverString). Who should I sent these changes to ? > > to andreas? > may be ask him if he wants to have a version working also for pharo but without String#, override I will contact Andreas directly once I know your position on the last remaining item. Sven BTW, Is there a way to make a (old school) ChangeSet (or even another 'patch' package) out of the differences between versions in Monticello ? >> But even then 1 unit test failed (#testServerDestroy). >> >> Furthermore, some the changes in his package WebClient-Pharo seem a bit dangerous, especially a modification to SocketStream#peek (and the failed test was doing a peek) and an override of String#, some others are unneccessary as far as I can see. >> >> Sven >> >> -- >> Sven Van Caekenberghe - mailto:sven@beta9.be >> Beta Nine - software engineering - http://www.beta9.be >> .Mac - svc(a)mac.com - http://homepage.mac.com/svc >> >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 14, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by laurent laffont

On Sun, Jun 13, 2010 at 11:19 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based > in PharoCore rc2 11400. > Help menu is gone ? Was fixed in http://code.google.com/p/pharo/issues/detail?id=2442 Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > A little remark is that this is the first release candidate, not the second > one. There was a problem when building the PharoCore rc1 and thus, we used > PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image. > > We are getting closer to the stable release of Pharo 1.1 so we would really > appreaciate any kind of feedback. Use it, load your packages and > applications, run tests, etc. > > The download link is: > https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.… > > Cheers > > Mariano > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

June 14, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by StÃ©phane Ducasse

mariano I suggest that we remove the newinspector from the dev tools because this is still really strange to use it. Stef On Jun 13, 2010, at 11:19 PM, Mariano Martinez Peck wrote: > Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based in PharoCore rc2 11400. > > A little remark is that this is the first release candidate, not the second one. There was a problem when building the PharoCore rc1 and thus, we used PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image. > > We are getting closer to the stable release of Pharo 1.1 so we would really appreaciate any kind of feedback. Use it, load your packages and applications, run tests, etc. > > The download link is: https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.… > > Cheers > > Mariano > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 14, 2010

[BetaTesting] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by Mariano Martinez Peck

Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based in PharoCore rc2 11400. A little remark is that this is the first release candidate, not the second one. There was a problem when building the PharoCore rc1 and thus, we used PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image. We are getting closer to the stable release of Pharo 1.1 so we would really appreaciate any kind of feedback. Use it, load your packages and applications, run tests, etc. The download link is: https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.… Cheers Mariano

June 13, 2010

Re: [Pharo-users] Priority of WeakArray finalizationProcess

by StÃ©phane Ducasse

On Jun 13, 2010, at 10:32 AM, Joachim Geidel wrote: > Am 12.06.10 21:51 schrieb StÃ©phane Ducasse: >> thanks for this report. >> Yes if you can add a bug report this would be great. >> >> Stef >> >> On Jun 12, 2010, at 9:16 PM, Joachim Geidel wrote: >> >>> While testing JNIPort on Pharo 1.0 and Pharo 1.1, I noticed that in Pharo >>> 1.0, a JVM (a wrapper object for the Java Virtual Machine) could be >>> initialized in ca. 4 seconds, while this needed 11 to 12 seconds in Pharo >>> 1.1. > > http://bugs.squeak.org/view.php?id=7546 > 0007546: WeakRegistry deadlock during finalization > > http://code.google.com/p/pharo/issues/detail?id=2551 > Issue 2551: Performance degradation of WeakRegistry in Pharo 1.1 > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 13, 2010

Re: [Pharo-users] Priority of WeakArray finalizationProcess

by Joachim Geidel

Am 12.06.10 21:51 schrieb StÃ©phane Ducasse: > thanks for this report. > Yes if you can add a bug report this would be great. > > Stef > > On Jun 12, 2010, at 9:16 PM, Joachim Geidel wrote: > >> While testing JNIPort on Pharo 1.0 and Pharo 1.1, I noticed that in Pharo >> 1.0, a JVM (a wrapper object for the Java Virtual Machine) could be >> initialized in ca. 4 seconds, while this needed 11 to 12 seconds in Pharo >> 1.1. http://bugs.squeak.org/view.php?id=7546 0007546: WeakRegistry deadlock during finalization http://code.google.com/p/pharo/issues/detail?id=2551 Issue 2551: Performance degradation of WeakRegistry in Pharo 1.1

June 13, 2010

Re: [Pharo-users] [squeak-dev] Priority of WeakArray finalizationProcess

by Joachim Geidel

Am 12.06.10 21:47 schrieb Levente Uzonyi: > On Sat, 12 Jun 2010, Joachim Geidel wrote: >> I am not sure if changing the priority of the finalizationProcess could >> possibly break something, and I also do not yet understand why changing the >> priority makes such a big difference both in Squeak and Pharo. > > I think normal processes (with priority 40) could starve the finalization > process if it's priority were <= 40 (#systemBackgroundPriority is 20). That's true, I hadn't thought of that. >> How should this issue be handled? Should I add this as issues to the bug >> tracking tools for Pharo and Squeak respectively? > > I uploaded a fix to the Inbox: Collections-ul.362. If you're using a Trunk > image, just update it and load this package to your image. If you're using > a stock 4.1 image, then the easiest way to get the fix, is to add the > following line to the end of WeakKeyDictionary >> #finalizeValues > > cleanUpAfterRemove ifTrue: [ self fixCollisionsFrom: array size ] > > If you have the time, please check if this fixes the issue for Squeak. Unfortunately, this doesn't help with the deadlock issue. Cheers, Joachim Geidel

June 13, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Mariano Martinez Peck

On Fri, Jun 11, 2010 at 10:49 AM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > Mariano, > > I had to change PGConnection class>>#timestampWithTimezoneConverter > otherwise it wouldn't want to parse my timestamp with time zone colums that > look like '2010-06-16 00:01:00+02' (no millis to skip, no minutes in the > offset). Now, my fix is a bit dirty, because it assumes that what I see on > my system is the rule while it probably isn't. > > timestampWithTimezoneConverter > > ^[ :s | > | direction offset | > direction := (s at: 20) = $- ifTrue: [ -1 ] ifFalse: [ 1 ]. > offset := Duration > hours: (s copyFrom: 21 to: 22) asInteger * > direction. > DateAndTime > year: (s copyFrom: 1 to: 4) asInteger > month: (s copyFrom: 6 to: 7) asInteger > day: (s copyFrom: 9 to: 10) asInteger > hour: (s copyFrom: 12 to: 13) asInteger > minute: (s copyFrom: 15 to: 16) asInteger > second: (s copyFrom: 18 to: 19) asInteger > offset: offset ] > > I can definitively write a better version that handles different kinds of > formats in a flexible way. I also think the #copyFrom:to:'s are waistful and > could at least be replaced with ReadStream>>#on:from:to:'s. This goes for > some other converters as well. This code is execute for each column so seems > resource critical. > > The problem with this is what you said: maybe it is not a normal problem, but just for *you*. I don't know. Maybe you should ask in Glorp mailing list ? > This change did not come up as a failed unit test, so maybe I should also > try to add one ? > > and yes, if it is a generic problem, it would be great to generate a test and commit both ;) > On my Pharo 1.0 image, all PGConnection tests pass. > > Of the 844 GlorpTest tests, 2 fail: > GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary and > GlorpSelectCommandTest>>#testExecute. do you know why they fail or how to fix them ? > GlorpTest-DBTests all succeed. ok > GlorpMainBackendTest fails. > > No problem with this one, forget it. > I also had to add NativePostgresDriver>>#externalDatabaseErrorSignal > > externalDatabaseErrorSignal > ^Dialect error > mmm this should be implemented in the accessor, why you need it in the driver? > This also came up during day to day usage and not as a test failure. > > So, for Glorp itself there were no real problems ;-) > great. We should move on Pharo 1.1 > > Maybe just one feature request: on VW NC 7.7 Glorp (when you enable > logging) prints timing info on all queries, on Pharo only for updates and > deletes, which is strange. > > wierd...probaly that's since a lot of time.....if you can digg into the problem, let me know. I can add you as developer if you want. Thanks in advance Mariano > Sven > > On 11 Jun 2010, at 00:32, Mariano Martinez Peck wrote: > > > > > > > On Thu, Jun 10, 2010 at 9:07 PM, Sven Van Caekenberghe <sven(a)beta9.be> > wrote: > > Mariano, > > > > The fact that you did the port is more than official enough for me ;-) > > > > First, thanks a lot for the port, I know that this must be a lot of work. > > > > I think that Glorp and the different drivers are _very_ important for > many people: talking to an RDBMS is an absolute requirement in almost any > serious application. Without it, Pharo/Seaside becomes almost unusable in > most commercial contexts. Only in some specific cases the other persistency > strategies would be applicable. > > > > Thanks. This is exactly why we did SqueakDBX ;) and then GlorpDBX. > > > > > > I would very much like to help in making the Glorp+PostgreSQL combination > easy to use in Pharo. Writing a ConfigurationOf.. is a bit to much for me > right now though. > > > > > > Great. So, at least, we should make it work, then we see how to load it. > > > > > > > > Concerning my changes, I can send them to you, or save modified versions > of the packages where you want. BTW, I was working on Pharo 1.0 > > > > mmmmm I thought Glorp was already working in 1.0. Weird...which are the > changes? yes, please send me your changes. We have committed Glorp packages > in SqueakDBX repository as we have been changing a lot of things. A big > refactor to Glorp in order to support multiple database drivers. > > > > You can send me the changes or commit them to the packages that are in > SqueakDBX repository at least. I am not sure in Glorp original repository, > but at least in SqueakDBX repository for sure: > http://www.squeaksource.com/SqueakDBX > > > > Please, run all the tests before comitting. > > > > Cheers > > > > Mariano > > > > > > > > Should we continue this discussion over the mailing list or privately ? > > > > Sven > > > > > > > > > > > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 12, 2010

Re: [Pharo-users] Priority of WeakArray finalizationProcess

by StÃ©phane Ducasse

thanks for this report. Yes if you can add a bug report this would be great. Stef On Jun 12, 2010, at 9:16 PM, Joachim Geidel wrote: > While testing JNIPort on Pharo 1.0 and Pharo 1.1, I noticed that in Pharo > 1.0, a JVM (a wrapper object for the Java Virtual Machine) could be > initialized in ca. 4 seconds, while this needed 11 to 12 seconds in Pharo > 1.1. When I profiled the JVM startup in 1.1, the profile reported that less > than 20% of the time was spent there; the rest was not accounted for in the > report. > > In Squeak 4.1, I encountered a deadlock problem related to Squeak's current > WeakRegistry implementation when the JVM is started. This problem > disappeared when I changed the finalizationProcess of WeakArray such that it > runs at systemBackgroundPriority instead of userBackgroundPriority. > > Applying the same change to Pharo 1.1 makes a big difference. The JVM starts > in 4.4 seconds, approximately matching the time it takes in Pharo 1.0. > > Starting the JVM in Squeak 4.1 is about 20% faster than Pharo 1.1. As the > difference is in the part which is not accounted for by the time profiler, > it is probably due to the differences in the implementation of > WeakIdentityKeyDictionary which have an impact on the performance of the > finalizationProcess. > > I am not sure if changing the priority of the finalizationProcess could > possibly break something, and I also do not yet understand why changing the > priority makes such a big difference both in Squeak and Pharo. > > How should this issue be handled? Should I add this as issues to the bug > tracking tools for Pharo and Squeak respectively? > > Cheers, > Joachim Geidel > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 12, 2010

Priority of WeakArray finalizationProcess

by Joachim Geidel

While testing JNIPort on Pharo 1.0 and Pharo 1.1, I noticed that in Pharo 1.0, a JVM (a wrapper object for the Java Virtual Machine) could be initialized in ca. 4 seconds, while this needed 11 to 12 seconds in Pharo 1.1. When I profiled the JVM startup in 1.1, the profile reported that less than 20% of the time was spent there; the rest was not accounted for in the report. In Squeak 4.1, I encountered a deadlock problem related to Squeak's current WeakRegistry implementation when the JVM is started. This problem disappeared when I changed the finalizationProcess of WeakArray such that it runs at systemBackgroundPriority instead of userBackgroundPriority. Applying the same change to Pharo 1.1 makes a big difference. The JVM starts in 4.4 seconds, approximately matching the time it takes in Pharo 1.0. Starting the JVM in Squeak 4.1 is about 20% faster than Pharo 1.1. As the difference is in the part which is not accounted for by the time profiler, it is probably due to the differences in the implementation of WeakIdentityKeyDictionary which have an impact on the performance of the finalizationProcess. I am not sure if changing the priority of the finalizationProcess could possibly break something, and I also do not yet understand why changing the priority makes such a big difference both in Squeak and Pharo. How should this issue be handled? Should I add this as issues to the bug tracking tools for Pharo and Squeak respectively? Cheers, Joachim Geidel

June 12, 2010

Re: [Pharo-users] Using Pharo 1.1

by StÃ©phane Ducasse

> But again, that is *only* if you want to track the latest developments, > the common is you take a given vesion, develop your app in there, and > when you have a release, take a new pharo version, update it, load your > code, run your tests and deploy :) yes this model stresses you less. And you can give feedback at check points and we can integrate potential issues that you discover when you tried to migrate from one chekc point to the other. Stef

June 11, 2010

Re: [Pharo-users] Alien for Squeak 4.1/Pharo 1.1?

by StÃ©phane Ducasse

>>>>> >>>> >>>> can you point us to them? > > I had a look at Alien-Prereqs and Alien-Core. Actually, it seems that all > extensions to system classes except the conversion and utility methods can > be removed in all three platforms. The only exception is > Parser>>pragmaStatement. It is needed in Pharo 1.0, which contains an old > version of that method. we will probably then integrate the parser changes. > > I have added a comment to Pharo issue #1360 > (http://code.google.com/p/pharo/issues/detail?id=1360) with attached > Monticello versions of Pharo-Prereqs and Pharo-Core which are compatible > with Pharo 1.0, 1.1, and Squeak 4.1. Pharo-Prereqs is only needed in Pharo > 1.0. The Alien tests were green on all three platforms. > > I have accidentally published Alien-Core to SqueakSource, but have asked > John McIntosh to delete the version. I think that my changes should be > reviewed by someone with better knowledge of Alien and who knows how to > update the ConfigurationOfAlien, before they are released publicly. Sorry > for the inconvinience, I will be more careful next time. > > Best regards, > Joachim Geidel > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 11, 2010

Re: [Pharo-users] WebClient

by StÃ©phane Ducasse

Hi sven > Hi, > > Andreas Raab's 'new' WebClient/WebServer seems quite nice, as he says himself: > > As a result, we now have what I think is a pretty decent HTTP server and client implementation for Squeak 4.1 and hopefully we can nuke HTTPSocket sometime soon. WebClient is superior in every respect. > > Is this something that will / should fit seamlessly into Pharo ? Or even become preinstalled ? could be but not at the price to have concatenation of string and numbers. So this means that somebody would have to do a pass on the code and produce a pharo version that squeakers may want or not. > I didn't try his ConfigurationOfWebClient since the last version was unreadable and it seemed like an experiment, while his textual explanation was easy to follow. > > To load it into and to make the unit tests run in Pharo 1.0 I had to make a couple of fixes (to WebCookie#printOn: and WebServer class#serverString). Who should I sent these changes to ? to andreas? may be ask him if he wants to have a version working also for pharo but without String#, override > But even then 1 unit test failed (#testServerDestroy). > > Furthermore, some the changes in his package WebClient-Pharo seem a bit dangerous, especially a modification to SocketStream#peek (and the failed test was doing a peek) and an override of String#, some others are unneccessary as far as I can see. > > Sven > > -- > Sven Van Caekenberghe - mailto:sven@beta9.be > Beta Nine - software engineering - http://www.beta9.be > .Mac - svc(a)mac.com - http://homepage.mac.com/svc > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 11, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Sven Van Caekenberghe

Mariano, I had to change PGConnection class>>#timestampWithTimezoneConverter otherwise it wouldn't want to parse my timestamp with time zone colums that look like '2010-06-16 00:01:00+02' (no millis to skip, no minutes in the offset). Now, my fix is a bit dirty, because it assumes that what I see on my system is the rule while it probably isn't. timestampWithTimezoneConverter ^[ :s | | direction offset | direction := (s at: 20) = $- ifTrue: [ -1 ] ifFalse: [ 1 ]. offset := Duration hours: (s copyFrom: 21 to: 22) asInteger * direction. DateAndTime year: (s copyFrom: 1 to: 4) asInteger month: (s copyFrom: 6 to: 7) asInteger day: (s copyFrom: 9 to: 10) asInteger hour: (s copyFrom: 12 to: 13) asInteger minute: (s copyFrom: 15 to: 16) asInteger second: (s copyFrom: 18 to: 19) asInteger offset: offset ] I can definitively write a better version that handles different kinds of formats in a flexible way. I also think the #copyFrom:to:'s are waistful and could at least be replaced with ReadStream>>#on:from:to:'s. This goes for some other converters as well. This code is execute for each column so seems resource critical. This change did not come up as a failed unit test, so maybe I should also try to add one ? On my Pharo 1.0 image, all PGConnection tests pass. Of the 844 GlorpTest tests, 2 fail: GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary and GlorpSelectCommandTest>>#testExecute. GlorpTest-DBTests all succeed. GlorpMainBackendTest fails. I also had to add NativePostgresDriver>>#externalDatabaseErrorSignal externalDatabaseErrorSignal ^Dialect error This also came up during day to day usage and not as a test failure. So, for Glorp itself there were no real problems ;-) Maybe just one feature request: on VW NC 7.7 Glorp (when you enable logging) prints timing info on all queries, on Pharo only for updates and deletes, which is strange. Sven On 11 Jun 2010, at 00:32, Mariano Martinez Peck wrote: > > > On Thu, Jun 10, 2010 at 9:07 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Mariano, > > The fact that you did the port is more than official enough for me ;-) > > First, thanks a lot for the port, I know that this must be a lot of work. > > I think that Glorp and the different drivers are _very_ important for many people: talking to an RDBMS is an absolute requirement in almost any serious application. Without it, Pharo/Seaside becomes almost unusable in most commercial contexts. Only in some specific cases the other persistency strategies would be applicable. > > Thanks. This is exactly why we did SqueakDBX ;) and then GlorpDBX. > > > I would very much like to help in making the Glorp+PostgreSQL combination easy to use in Pharo. Writing a ConfigurationOf.. is a bit to much for me right now though. > > > Great. So, at least, we should make it work, then we see how to load it. > > > > Concerning my changes, I can send them to you, or save modified versions of the packages where you want. BTW, I was working on Pharo 1.0 > > mmmmm I thought Glorp was already working in 1.0. Weird...which are the changes? yes, please send me your changes. We have committed Glorp packages in SqueakDBX repository as we have been changing a lot of things. A big refactor to Glorp in order to support multiple database drivers. > > You can send me the changes or commit them to the packages that are in SqueakDBX repository at least. I am not sure in Glorp original repository, but at least in SqueakDBX repository for sure: http://www.squeaksource.com/SqueakDBX > > Please, run all the tests before comitting. > > Cheers > > Mariano > > > > Should we continue this discussion over the mailing list or privately ? > > Sven > > > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 11, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Mariano Martinez Peck

On Thu, Jun 10, 2010 at 9:07 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > Mariano, > > The fact that you did the port is more than official enough for me ;-) > > First, thanks a lot for the port, I know that this must be a lot of work. > > I think that Glorp and the different drivers are _very_ important for many > people: talking to an RDBMS is an absolute requirement in almost any serious > application. Without it, Pharo/Seaside becomes almost unusable in most > commercial contexts. Only in some specific cases the other persistency > strategies would be applicable. > Thanks. This is exactly why we did SqueakDBX ;) and then GlorpDBX. > > I would very much like to help in making the Glorp+PostgreSQL combination > easy to use in Pharo. Writing a ConfigurationOf.. is a bit to much for me > right now though. > Great. So, at least, we should make it work, then we see how to load it. > > Concerning my changes, I can send them to you, or save modified versions of > the packages where you want. BTW, I was working on Pharo 1.0 > mmmmm I thought Glorp was already working in 1.0. Weird...which are the changes? yes, please send me your changes. We have committed Glorp packages in SqueakDBX repository as we have been changing a lot of things. A big refactor to Glorp in order to support multiple database drivers. You can send me the changes or commit them to the packages that are in SqueakDBX repository at least. I am not sure in Glorp original repository, but at least in SqueakDBX repository for sure: http://www.squeaksource.com/SqueakDBX Please, run all the tests before comitting. Cheers Mariano > > Should we continue this discussion over the mailing list or privately ? > > Sven > > > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 10, 2010

Pharo book TableLayout tutorial

by laurent laffont

Hi, I've added a tutorial on TableLayout http://book.pharo-project.org/book/GUI/PolymorphTutorial/TableLayout/ which follows the one on Proportional Layout. Again, thanks for feedback and English check. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

June 10, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Sven Van Caekenberghe

Mariano, The fact that you did the port is more than official enough for me ;-) First, thanks a lot for the port, I know that this must be a lot of work. I think that Glorp and the different drivers are _very_ important for many people: talking to an RDBMS is an absolute requirement in almost any serious application. Without it, Pharo/Seaside becomes almost unusable in most commercial contexts. Only in some specific cases the other persistency strategies would be applicable. I would very much like to help in making the Glorp+PostgreSQL combination easy to use in Pharo. Writing a ConfigurationOf.. is a bit to much for me right now though. Concerning my changes, I can send them to you, or save modified versions of the packages where you want. BTW, I was working on Pharo 1.0 Should we continue this discussion over the mailing list or privately ? Sven

June 10, 2010

Twitter Blog: More Than Dabbling

by Sven Van Caekenberghe

Dabble has been bought by Twitter ! http://blog.twitter.com/2010/06/more-than-dabbling.html Let's hope they keep using Smalltalk. In any case, congratulations to Avi en co. Sven

June 10, 2010

Re: [Pharo-users] Using Pharo 1.1

by Sven Van Caekenberghe

Thanks for the quick answer, Mariano, I understand now. I'll work from the published 1.1 images. Sven On 10 Jun 2010, at 19:44, Mariano Martinez Peck wrote: > On Thu, Jun 10, 2010 at 4:45 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Hi, > > Yet another question. > > I keep hearing and reading that Pharo 1.1 is quite usable and a lot better than 1.0 that I am currently using. Is that true ? > > > yes > > If I download Pharo-1.1-11367-Betadev10.05.1 how do I then keep up to date with the development that is presumably still going on ? > > It seems like only Pharo-Core images have this 'software update' world menu item ? > > > yes, they don't have it. Read: http://forum.world.st/update-1-1-11371-tp2229126p2231195.html > > > Or do I just have to keep on downloading the lastest released beta ? > > Just download each new PharoDev version. If you want, you can take a core and try to build yourself a dev image on top of that. But that could be unstable. > > Cheers > > mariano > > > Sorry for all the beginner questions... > > Thx, > > Sven

June 10, 2010

Re: [Pharo-users] Using Pharo 1.1

by Miguel Enrique CobÃ¡ MartÃnez

El jue, 10-06-2010 a las 19:44 +0200, Mariano Martinez Peck escribiÃ³: > > > On Thu, Jun 10, 2010 at 4:45 PM, Sven Van Caekenberghe <sven(a)beta9.be> > wrote: > Hi, > > Yet another question. > > I keep hearing and reading that Pharo 1.1 is quite usable and > a lot better than 1.0 that I am currently using. Is that > true ? > > > yes > > If I download Pharo-1.1-11367-Betadev10.05.1 how do I then > keep up to date with the development that is presumably still > going on ? > > It seems like only Pharo-Core images have this 'software > update' world menu item ? > > > yes, they don't have it. Read: > http://forum.world.st/update-1-1-11371-tp2229126p2231195.html > > > Or do I just have to keep on downloading the lastest released > beta ? > > Just download each new PharoDev version. If you want, you can take a > core and try to build yourself a dev image on top of that. But that > could be unstable. Or you could use a dev image and *only if you know that nothing bad happens to your code or the packages you use for your app* you could update manually by opening a workspace and evaluating every so: Utilities updateFromServer. But again, that is *only* if you want to track the latest developments, the common is you take a given vesion, develop your app in there, and when you have a release, take a new pharo version, update it, load your code, run your tests and deploy :) Cheers > > Cheers > > mariano > > > Sorry for all the beginner questions... > > Thx, > > Sven > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Miguel CobÃ¡ http://miguel.leugim.com.mx

June 10, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Mariano Martinez Peck

On Thu, Jun 10, 2010 at 4:20 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > Hi, > > A similar question regarding Glorp & PosgresV2: what is the official Pharo > standpoint regarding this ? > > I did the port of Glorp to Pharo and the dbx stuff. I don't know the "official standpoint", thus. > There is no ConfigurationOfGlorpNativePostgreSQL (there are some for DBX, > but I don't need that). > > No, no time to do it. If you want, you can easily do it. You can take as a base the one I did for squeakDBX. > I used GlorpPharoLoader loadGlorpWithNativePostgreSQLDriver. > That's what I did before I had Metacello. It is "deprecated" for SquerakDBX as now the way to install it is with Metacello, but for Glorp alone there is no Metacello...so you can use it, or as I said, create yourself a COnfigurationOfGLorp > > I had to make some small changes to GlorpDriverPostgreSQL and PostgresV2 to > make more tests succeed. > Can you explain me them? I can commit it when I have time. Or do it yourself. Does your changes also work in Pharo 1.0? > > The installer did also load the underscore.cs hack adding an ugly star in > Monticello to Compiler (Scanner#xLetter). > Yes, although it is not needed anymore in Pharo 1.1 as it is fixed :) > > But all in all it does work great and fast. > :) > > Is this something for the Pharo list or should I go ask my questions > somewhere else ? > Here is ok for this kinf of questions. If it is too Glorp related, maybe Glorp mailing list is better. cheers mariano > > Sven > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 10, 2010

Re: [Pharo-users] Using Pharo 1.1

by Mariano Martinez Peck

On Thu, Jun 10, 2010 at 4:45 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > Hi, > > Yet another question. > > I keep hearing and reading that Pharo 1.1 is quite usable and a lot better > than 1.0 that I am currently using. Is that true ? > > yes > If I download Pharo-1.1-11367-Betadev10.05.1 how do I then keep up to date > with the development that is presumably still going on ? > > It seems like only Pharo-Core images have this 'software update' world menu > item ? > > yes, they don't have it. Read: http://forum.world.st/update-1-1-11371-tp2229126p2231195.html > Or do I just have to keep on downloading the lastest released beta ? > Just download each new PharoDev version. If you want, you can take a core and try to build yourself a dev image on top of that. But that could be unstable. Cheers mariano > > Sorry for all the beginner questions... > > Thx, > > Sven > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 10, 2010