- Pharo-dev - lists.pharo.org

Re: [Pharo-project] ODBCWarning

by Schwab,Wilhelm K

Brian, I'm not sure if I did it correctly, but it did not quite do the right thing. It caught the extension methods, but there are a few required classes that are still in the ODBC branch of the Dolphincompatibility package. Does that sound familiar and fixable? Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Brian Brown Sent: Wednesday, September 02, 2009 10:48 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] ODBCWarning On Sep 2, 2009, at 9:12 PM, Schwab,Wilhelm K wrote: Failing that, is there a way to get Monticello to save only part of a package? For example, it would be a lot easier for me to screen DolphinCompatibility-ODBC than all of DolphinCompatibility. Are there tools to save only that part of it? Bill I believe if you create a new package in the Monticello browser named DolphinCompatibility-ODBC and save it, you will get what you want. It's always easy to save sub packages using the more specfic category. - Brian -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Esteban A. Maringolo Sent: Wednesday, September 02, 2009 9:21 PM To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] ODBCWarning Bill, I celebrate your work of bringing the dolphin near the pharo ;-) Thanks for your collaboration, Esteban A. Maringolo 2009/9/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> Hello all, I think I have the catalog (tables and field name/type given a table name) working. The latest ODBC offering appears to work, but in fairness to me, it does not work the same way it did (some time ago) when I crossed database access off of my potential-show-stopper list. Re the warnings about change of language, for some strange reason, I find it very easy to believe that this is a Microsoft idiosyncrasy and so I added a suitable #on:do: to capture the warning. That could be bad though; better ideas are welcome. The problem I had going from Linux to Windows will probably persist. Of course, I would like to see the startup/shutdown system revised to make such things easier to get right, after which it would hopefully become short work to fix. The ODBC package derives ODBCRow from IdentityDictionary and ODBCResultSet from Stream. IMHO, it always seems cleaner to compose rather than inherit the limited functionality that the base class provides. However, the inheritance is not really hurting anything here; socket addresses being inherited from byte arrays *is* hurting us. I brushed up against that at one point, but was able to work around it. When it gets between me and something I need, I will introduce an InternetAddress class and try to lazily resolve names and addresses, fix the printing, etc. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, September 01, 2009 3:15 PM To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: [Pharo-project] ODBCWarning The porting continues... It is getting closer to doing something. It just raised an ODBCWarning about the server changing the language to us_english. Any ideas? Either I do not care or should set it up front?? One thing really surprised me, and note that I might have brought this on myself (though I think that is unlikely) by messing with startup and shutdown: the ODBCLibrary was stubbornly clinging to the Linux library from my home machine. I finally used ODBCLibrary default initialize. which seemed to put an end to the separation anxiety. Is there a better fix? I suppose I should try this in a clean image to see if there is really a problem therein, but that will be a little hard to do without a lot of my code, almost any of which either depends on changes I have made or could have caused the problem. Maybe I should ask whether some of you use ODBC on Windows and Linux and have no problems moving between the machines. Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@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

Sept. 3, 2009

Re: [Pharo-project] ODBCWarning

by Brian Brown

On Sep 2, 2009, at 9:12 PM, Schwab,Wilhelm K wrote: > > > Failing that, is there a way to get Monticello to save only part of > a package? For example, it would be a lot easier for me to screen > DolphinCompatibility-ODBC than all of DolphinCompatibility. Are > there tools to save only that part of it? > > Bill I believe if you create a new package in the Monticello browser named DolphinCompatibility-ODBC and save it, you will get what you want. It's always easy to save sub packages using the more specfic category. - Brian > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo- > project-bounces(a)lists.gforge.inria.fr] On Behalf Of Esteban A. > Maringolo > Sent: Wednesday, September 02, 2009 9:21 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] ODBCWarning > > Bill, > > I celebrate your work of bringing the dolphin near the pharo ;-) > > Thanks for your collaboration, > > Esteban A. Maringolo > > > 2009/9/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >> >> Hello all, >> >> I think I have the catalog (tables and field name/type given a >> table name) working. The latest ODBC offering appears to work, but >> in fairness to me, it does not work the same way it did (some time >> ago) when I crossed database access off of my potential-show- >> stopper list. >> >> Re the warnings about change of language, for some strange reason, >> I find it very easy to believe that this is a Microsoft >> idiosyncrasy and so I added a suitable #on:do: to capture the >> warning. That could be bad though; better ideas are welcome. >> >> The problem I had going from Linux to Windows will probably >> persist. Of course, I would like to see the startup/shutdown >> system revised to make such things easier to get right, after which >> it would hopefully become short work to fix. >> >> The ODBC package derives ODBCRow from IdentityDictionary and >> ODBCResultSet from Stream. IMHO, it always seems cleaner to >> compose rather than inherit the limited functionality that the base >> class provides. However, the inheritance is not really hurting >> anything here; socket addresses being inherited from byte arrays >> *is* hurting us. I brushed up against that at one point, but was >> able to work around it. When it gets between me and something I >> need, I will introduce an InternetAddress class and try to lazily >> resolve names and addresses, fix the printing, etc. >> >> Bill >> >> >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >> Schwab,Wilhelm K >> Sent: Tuesday, September 01, 2009 3:15 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: [Pharo-project] ODBCWarning >> >> The porting continues... It is getting closer to doing something. >> It just raised an ODBCWarning about the server changing the >> language to us_english. Any ideas? Either I do not care or should >> set it up front?? >> >> One thing really surprised me, and note that I might have brought >> this >> on myself (though I think that is unlikely) by messing with startup >> and shutdown: the ODBCLibrary was stubbornly clinging to the Linux >> library from my home machine. I finally used >> >> ODBCLibrary default initialize. >> >> which seemed to put an end to the separation anxiety. Is there a >> better fix? I suppose I should try this in a clean image to see if >> there is really a problem therein, but that will be a little hard >> to do without a lot of my code, almost any of which either depends >> on changes I have made or could have caused the problem. >> >> Maybe I should ask whether some of you use ODBC on Windows and >> Linux and have no problems moving between the machines. >> >> Bill >> >> _______________________________________________ >> 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 >

Sept. 3, 2009

Re: [Pharo-project] ODBCWarning

by Schwab,Wilhelm K

Esteban, Of course the real goal is to bring the dolphin to the penguin with the pharo's help :) Thanks to all for making it an attainable goal. A good next step would be to package the catalog functions for others to use. The code currently lives in an ODBC sub-package (or whatever the correct term is) of my DolphinCompatibility package, some of which is very preliminary at present. One concern I have is checking code for comments that should not be made public due to non-disclosure agreements. It would be nice if there were a way to create syntax-highlighted HTML from a PackageInfo instance. Any ideas? Failing that, is there a way to get Monticello to save only part of a package? For example, it would be a lot easier for me to screen DolphinCompatibility-ODBC than all of DolphinCompatibility. Are there tools to save only that part of it? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Esteban A. Maringolo Sent: Wednesday, September 02, 2009 9:21 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] ODBCWarning Bill, I celebrate your work of bringing the dolphin near the pharo ;-) Thanks for your collaboration, Esteban A. Maringolo 2009/9/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > > Hello all, > > I think I have the catalog (tables and field name/type given a table name) working. Â The latest ODBC offering appears to work, but in fairness to me, it does not work the same way it did (some time ago) when I crossed database access off of my potential-show-stopper list. > > Re the warnings about change of language, for some strange reason, I find it very easy to believe that this is a Microsoft idiosyncrasy and so I added a suitable #on:do: to capture the warning. Â That could be bad though; better ideas are welcome. > > The problem I had going from Linux to Windows will probably persist. Â Of course, I would like to see the startup/shutdown system revised to make such things easier to get right, after which it would hopefully become short work to fix. > > The ODBC package derives ODBCRow from IdentityDictionary and ODBCResultSet from Stream. Â IMHO, it always seems cleaner to compose rather than inherit the limited functionality that the base class provides. Â However, the inheritance is not really hurting anything here; socket addresses being inherited from byte arrays *is* hurting us. Â I brushed up against that at one point, but was able to work around it. Â When it gets between me and something I need, I will introduce an InternetAddress class and try to lazily resolve names and addresses, fix the printing, etc. > > Bill > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > Schwab,Wilhelm K > Sent: Tuesday, September 01, 2009 3:15 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] ODBCWarning > > The porting continues... Â It is getting closer to doing something. Â It just raised an ODBCWarning about the server changing the language to us_english. Â Any ideas? Â Either I do not care or should set it up front?? > > One thing really surprised me, and note that I might have brought this > on myself (though I think that is unlikely) by messing with startup > and shutdown: the ODBCLibrary was stubbornly clinging to the Linux > library from my home machine. Â I finally used > > Â Â ODBCLibrary default initialize. > > which seemed to put an end to the separation anxiety. Â Is there a better fix? Â I suppose I should try this in a clean image to see if there is really a problem therein, but that will be a little hard to do without a lot of my code, almost any of which either depends on changes I have made or could have caused the problem. > > Maybe I should ask whether some of you use ODBC on Windows and Linux and have no problems moving between the machines. > > Bill > > _______________________________________________ > 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

Sept. 3, 2009

Re: [Pharo-project] ODBCWarning

by Esteban A. Maringolo

Bill, I celebrate your work of bringing the dolphin near the pharo ;-) Thanks for your collaboration, Esteban A. Maringolo 2009/9/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > > Hello all, > > I think I have the catalog (tables and field name/type given a table name) working. Â The latest ODBC offering appears to work, but in fairness to me, it does not work the same way it did (some time ago) when I crossed database access off of my potential-show-stopper list. > > Re the warnings about change of language, for some strange reason, I find it very easy to believe that this is a Microsoft idiosyncrasy and so I added a suitable #on:do: to capture the warning. Â That could be bad though; better ideas are welcome. > > The problem I had going from Linux to Windows will probably persist. Â Of course, I would like to see the startup/shutdown system revised to make such things easier to get right, after which it would hopefully become short work to fix. > > The ODBC package derives ODBCRow from IdentityDictionary and ODBCResultSet from Stream. Â IMHO, it always seems cleaner to compose rather than inherit the limited functionality that the base class provides. Â However, the inheritance is not really hurting anything here; socket addresses being inherited from byte arrays *is* hurting us. Â I brushed up against that at one point, but was able to work around it. Â When it gets between me and something I need, I will introduce an InternetAddress class and try to lazily resolve names and addresses, fix the printing, etc. > > Bill > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K > Sent: Tuesday, September 01, 2009 3:15 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] ODBCWarning > > The porting continues... Â It is getting closer to doing something. Â It just raised an ODBCWarning about the server changing the language to us_english. Â Any ideas? Â Either I do not care or should set it up front?? > > One thing really surprised me, and note that I might have brought this on myself (though I think that is unlikely) by messing with startup and shutdown: the ODBCLibrary was stubbornly clinging to the Linux library from my home machine. Â I finally used > > Â Â ODBCLibrary default initialize. > > which seemed to put an end to the separation anxiety. Â Is there a better fix? Â I suppose I should try this in a clean image to see if there is really a problem therein, but that will be a little hard to do without a lot of my code, almost any of which either depends on changes I have made or could have caused the problem. > > Maybe I should ask whether some of you use ODBC on Windows and Linux and have no problems moving between the machines. > > Bill > > _______________________________________________ > 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

Sept. 3, 2009

Re: [Pharo-project] ODBCWarning

by Schwab,Wilhelm K

Hello all, I think I have the catalog (tables and field name/type given a table name) working. The latest ODBC offering appears to work, but in fairness to me, it does not work the same way it did (some time ago) when I crossed database access off of my potential-show-stopper list. Re the warnings about change of language, for some strange reason, I find it very easy to believe that this is a Microsoft idiosyncrasy and so I added a suitable #on:do: to capture the warning. That could be bad though; better ideas are welcome. The problem I had going from Linux to Windows will probably persist. Of course, I would like to see the startup/shutdown system revised to make such things easier to get right, after which it would hopefully become short work to fix. The ODBC package derives ODBCRow from IdentityDictionary and ODBCResultSet from Stream. IMHO, it always seems cleaner to compose rather than inherit the limited functionality that the base class provides. However, the inheritance is not really hurting anything here; socket addresses being inherited from byte arrays *is* hurting us. I brushed up against that at one point, but was able to work around it. When it gets between me and something I need, I will introduce an InternetAddress class and try to lazily resolve names and addresses, fix the printing, etc. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, September 01, 2009 3:15 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] ODBCWarning The porting continues... It is getting closer to doing something. It just raised an ODBCWarning about the server changing the language to us_english. Any ideas? Either I do not care or should set it up front?? One thing really surprised me, and note that I might have brought this on myself (though I think that is unlikely) by messing with startup and shutdown: the ODBCLibrary was stubbornly clinging to the Linux library from my home machine. I finally used ODBCLibrary default initialize. which seemed to put an end to the separation anxiety. Is there a better fix? I suppose I should try this in a clean image to see if there is really a problem therein, but that will be a little hard to do without a lot of my code, almost any of which either depends on changes I have made or could have caused the problem. Maybe I should ask whether some of you use ODBC on Windows and Linux and have no problems moving between the machines. Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 3, 2009

[Pharo-project] [update] 10431

by Marcus Denker

10431 ----- Issue 1147: Update ScriptLoader to use seaside 3.0 Issue 1014: Some packages are not associated with the Pharo repository In the Postscrpt: ScriptLoader new addHomeRepositoryToAllPackages -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker UG (haftungsbeschrÃ¤nkt) Sitz KÃ¶ln Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker

Sept. 2, 2009

[Pharo-project] Seaside 3.0 in Pharo

by Torsten Bergmann

As you all know from ESUG or planet.smalltalk.org blogs the Seaside 2.9 framework is now continuing as Seaside 3.0. Since Pharo is now used as the main dev platform for seaside some packages where renamed from "XYZ-Squeak" to "XYZ-Pharo". The project is now also hosted on a new repository http://www.squeaksource.com/Seaside30/ the old seaside 2.9 repository is now renamed to: http://www.squeaksource.com/Seaside29old/ Therefore: ========= To directly load Seaside 3.0 into Pharo Core/Pharo dev I: - adapted the package "LoadOrderTest" in the "Seaside30" repository to use the new repository and ask for 3.0 instead of 2.9 (the package switch from "Squeak" to "Pharo" was already integrated by James Foster here). LoadOrderTest is used by a Pharo ScriptLoader script to load the latest Seaside into Pharo. - created issue for Pharo to adapt ScriptLoader http://code.google.com/p/pharo/issues/detail?id=1147 - fixed issue 1147 with ScriptLoader-TorstenBergmann.1031.mcz in the pharo inbox (deprecating #loadSeaside29 and providing #loadSeaside30) If this gets integrated into a new core image one can then again easily evaluate: ScriptLoader loadOB. ScriptLoader loadSeaside30 to get the latest and greatest for web development. Have fun Torsten BTW: Tested in latest Pharo core #10430 -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

Sept. 2, 2009

Re: [Pharo-project] Closure review

by Michael Roberts

Hi thanks, yes i know Pharo has closures.... On Wed, Sep 2, 2009 at 10:46 PM, Torsten Bergmann<astares(a)gmx.de> wrote: > Hi Michael, > > Pharo has closures already integrated and there is a prebuild image for Squeak too: > > at http://www.squeakvm.org/win32/release/?C=M;O=D you will find > Â Squeak-3.10.2-Closures.zip > that's what i was after. cheers! Mike

Sept. 2, 2009

[Pharo-project] Closure review

by Torsten Bergmann

Hi Michael, Pharo has closures already integrated and there is a prebuild image for Squeak too: at http://www.squeakvm.org/win32/release/?C=M;O=D you will find Squeak-3.10.2-Closures.zip There you will also find a prebuild image for the new trunk development model Squeak has (see squeak-dev). This image should have the closure changes too. Maybe you'll have a look in the changesorter in one of the which may still have the change file for the closure stuff. Otherwise ask Andreas since has has built the image. Note that you need a newer Squeak VM with closure support for Pharo and these specific closure aware Squeak releases. Have fun Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Sept. 2, 2009

[Pharo-project] Closure review

by Michael Roberts

can someone point me to any of the following 1) a definitive set of changesets or MC packages we applied for the closure integration 2) a definitive squeak (or other) image with closures integrated. Did Elliot publish a closure image? i ask because i'm trying to hunt down a debugger bug. I downloaded Squeak 3.10.2 but I don't think that has closures (?). I tried to update it to trunk but the process stalled. i'm not up on squeak these days - is there a snapshot of the trunk somewhere? Anyway just looking for another image i can use to compare method versions. thanks! Mike

Sept. 2, 2009