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

Re: [Pharo-users] Symbolic links in Pharo

by Esteban Lorenzano

right now, you canâtâ¦ btw, even #isSymlink method is currently broken (I coded a replacement with UFFI but while making it work with linux I broke it with macâ¦ and no time yet to finish it :( ) but I suppose also creating symlinks is something we can add soon :) Esteban > On 20 Jun 2016, at 16:22, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: > > Hi, > > I want to create a symbolic link via Pharo. > But I don't know how, I found methods named #isSymlink but none for creation of symbolic links. > > Can we create a symbolic link via Pharo ? > > Thibault

June 20, 2016

Symbolic links in Pharo

by Thibault ARLOING

Hi, I want to create a symbolic link via Pharo. But I don't know how, I found methods named #isSymlink but none for creation of symbolic links. Can we create a symbolic link via Pharo ? Thibault

June 20, 2016

Re: [Pharo-users] #inform: Changed in 5.0?

by Christophe Demarey

Hi Sean, > Le 17 juin 2016 Ã 17:10, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > During startup, I do `UIManager default inform: aString`. It used to show a > Growl morph, but now opens a debugger. Did something change? If so, why and > how do I circumvent the debugger? Thanks. With the introduction of the session manager, error handling during startup actions was revisited. You can check StartupUIManager>>#handleError:log: for errors coming before Morphic is initialized. Once Morphic is initialized, you get a default UI manager (MorphicUIManager if in UI mode). It is managed by UIManagerSessionHandler class. If your startup code is executed with StartupUIManager, it will add a deferred startup action to execute the inform, else it fallback to MorphicUIManager inform. It should do the behavior you expect. Could you give me more info (the stacktrace would be useful)? Cheers, Christophe

June 20, 2016

Re: [Pharo-users] Seamless

by francescoagati

No i was using and old version finded in your pdf draft of seamless Gofer it url: 'http://ss3.gemstone.com/ss/Seamless'; package: 'ConfigurationOfSeamless'; load. ((Smalltalk at: #ConfigurationOfSeamless) project version: '0.4') load. using the version on smalltalkhub all go good when save the image. the only problem finded is if i quit and restart the image with socket open.but i think that when the machine go down or up i must use a callback for start or kill the sockets. Thanks -- View this message in context: http://forum.world.st/Seamless-tp4840907p4901832.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 19, 2016

Re: [Pharo-users] Can't get an SQLite connection to work

by Mark Bratcher

Yes, Pharo 5.0. Hmm... good catch on the driver. I'm on a 64 bit system, so it's probably 64 bits. I'll have to locate a 32 bit driver... Sent from TypeApp On Jun 19, 2016, 2:34 PM, at 2:34 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >also, did you verify sqlite library is 32bits? > >Esteban > >> On 19 Jun 2016, at 20:07, Alistair Grant <akgrant0710(a)gmail.com> >wrote: >> >> Hi Mark, >> >> Assuming you're using Pharo 5.0... >> >> On Sun, Jun 19, 2016 at 06:35:00AM -0400, Mark Bratcher wrote: >>> Hello. >>> >>> When I try to connect to an SQLite database using the DBXTalk/Garage >SQLite3 >>> driver, I made sure I had the SQLite driver .so file in the proper >location >>> and everything. Ultimately, the error I'm getting now is: >"KeyNotFound: key >>> #filename not found in Dictionary". >>> >>> I also tried using NBSQLite3, but have not been able to successfully >load it >>> with the instructions given on smalltalkhub.com for the stable >version. The >>> Gofer load results in the error, "MessageNotUnderstood: receiver of >>> "forCurrentPlatform" is nil". >> >> NBSQlite3 won't work in Pharo 5.0. >> >> >>> I did quite a bit of investigating of each of these errors and can't >seem to >>> find my way around them. Has anyone else encountered them or are >these a >>> sign of something obvious I'm doing incorrectly? I know I've haven't >given >>> much information here, so if there's something specific you need to >know, >>> please ask. :) >> >> Do you specifically want the Garage drivers, to access SQLite >directly, >> or use SQLite3 with Glorp? >> >> The UDBC SQLite3 driver works well in Pharo 5.0 and can be used >directly >> with Glorp. Details of how to load Glorp with SQLite3 are in >> [Pharo-users] [ANN] Glorp-SQLite3 for Pharo 5. >> >> HTH, >> Alistair >> >>

June 19, 2016

Re: [Pharo-users] Can't get an SQLite connection to work

by Esteban Lorenzano

also, did you verify sqlite library is 32bits? Esteban > On 19 Jun 2016, at 20:07, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Mark, > > Assuming you're using Pharo 5.0... > > On Sun, Jun 19, 2016 at 06:35:00AM -0400, Mark Bratcher wrote: >> Hello. >> >> When I try to connect to an SQLite database using the DBXTalk/Garage SQLite3 >> driver, I made sure I had the SQLite driver .so file in the proper location >> and everything. Ultimately, the error I'm getting now is: "KeyNotFound: key >> #filename not found in Dictionary". >> >> I also tried using NBSQLite3, but have not been able to successfully load it >> with the instructions given on smalltalkhub.com for the stable version. The >> Gofer load results in the error, "MessageNotUnderstood: receiver of >> "forCurrentPlatform" is nil". > > NBSQlite3 won't work in Pharo 5.0. > > >> I did quite a bit of investigating of each of these errors and can't seem to >> find my way around them. Has anyone else encountered them or are these a >> sign of something obvious I'm doing incorrectly? I know I've haven't given >> much information here, so if there's something specific you need to know, >> please ask. :) > > Do you specifically want the Garage drivers, to access SQLite directly, > or use SQLite3 with Glorp? > > The UDBC SQLite3 driver works well in Pharo 5.0 and can be used directly > with Glorp. Details of how to load Glorp with SQLite3 are in > [Pharo-users] [ANN] Glorp-SQLite3 for Pharo 5. > > HTH, > Alistair > >

June 19, 2016

Re: [Pharo-users] #inform: Changed in 5.0?

by Denis Kudriashov

In 5.0 there was refactoring of startup process which introduce some kind of StartUpUIManager (not remember exact name). It is installed when image just started. And concrete manager like MorphicUIManager is installed at some last step. (somebody could explain it better) 2016-06-19 18:46 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > Do you perform it inside #defer: message? > > I didn't and it was working in 4.0, but wrapping in #defer: it now works > again in 5.0 > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/inform-Changed-in-5-0-tp4901478p4901815.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 19, 2016

Re: [Pharo-users] Can't get an SQLite connection to work

by Alistair Grant

Hi Mark, Assuming you're using Pharo 5.0... On Sun, Jun 19, 2016 at 06:35:00AM -0400, Mark Bratcher wrote: > Hello. > > When I try to connect to an SQLite database using the DBXTalk/Garage SQLite3 > driver, I made sure I had the SQLite driver .so file in the proper location > and everything. Ultimately, the error I'm getting now is: "KeyNotFound: key > #filename not found in Dictionary". > > I also tried using NBSQLite3, but have not been able to successfully load it > with the instructions given on smalltalkhub.com for the stable version. The > Gofer load results in the error, "MessageNotUnderstood: receiver of > "forCurrentPlatform" is nil". NBSQlite3 won't work in Pharo 5.0. > I did quite a bit of investigating of each of these errors and can't seem to > find my way around them. Has anyone else encountered them or are these a > sign of something obvious I'm doing incorrectly? I know I've haven't given > much information here, so if there's something specific you need to know, > please ask. :) Do you specifically want the Garage drivers, to access SQLite directly, or use SQLite3 with Glorp? The UDBC SQLite3 driver works well in Pharo 5.0 and can be used directly with Glorp. Details of how to load Glorp with SQLite3 are in [Pharo-users] [ANN] Glorp-SQLite3 for Pharo 5. HTH, Alistair

June 19, 2016

Re: [Pharo-users] Pharo 5 and Seaside

by Mark Bratcher

Joachim I just confirmed that on Windows 10, Pharo 5.0 I get the same results you do (missing dependent class, ContextPart) when attempting to load Seaside3 from the Catalog Browser. As I had mentioned previously, the Gofer instructions for installation, described on the Seaside website, seem to work fine, so you could try that. Mark On 6/19/2016 6:41 AM, jtuchel(a)objektfabrik.de wrote: > > Mark, > > I am sure I didnât load all prerequisites. Thatâs what I thought the > Catalog Browser and its machinery would do for me. If I understand > Estebanâs answer correctly, that is the idea, but for some changes > that havenât been reflected for Seaside3 yet, it didnât work. > > So I guess the snippet you provided is the way to go. > > Thanks for answering and looking into this > > Joachim > > *Von: *Mark Bratcher <mailto:mdbratch@gmail.com> > *Gesendet: *Sonntag, 19. Juni 2016 12:11 > *An: *pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > *Betreff: *Re: [Pharo-users] Pharo 5 and Seaside > > I'm running Pharo 5 on Windows. When I installed Seaside 3, I just > used the instructions given for Gofer (entered in the Playground and > executed there). I downloaded the base package: > > Gofernew > url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > package:'ConfigurationOfSeaside3'; > load. > ((Smalltalkat:#ConfigurationOfSeaside3)projectversion:#stable)load. > > I also tried the alternative Gofer instructions shown, and they also > worked without dependency error. So depending upon how you actually > did your load of Seaside 3, maybe you didn't pull in all the dependent > packages. > > Mark > > On 6/19/2016 4:31 AM, jtuchel(a)objektfabrik.de > <mailto:jtuchel@objektfabrik.de> wrote: > > Hi, > > I just downloaded Pharo 5 from pharo.org clicked on the MacOS X > button), opened the Catalog Browser and wanted to load / install > Seaside. I must admit I didn't read anything before I did... ;-) > > Here are a few remarks: > > * Download and installation on OS X El Capitan went smoothly, > just the usual security warning ion first opening. Since I > know Pharo is no malware ( ;-) ), this was not an issue > * There are several entries for Seaside, most of them warn me > they are not tested/blessed for Pharo 5. They do not have a > "Pharo 5" tag. So they could possibly be ommitted in this > default view? > * The "Seaside 3" entry seems to be the suitable one, but fails > with "This package depends on the following classes: > ContextPart" > * it is not really obvious what the difference between "install > stable version" and "install stable version and create group" > is. The word group is something without any meaning in the > context of Smalltalk to me... I clicked on the top-most entry > just because I thought it's first in the menu for a reason. > > So I didn't really get far in this Sunday-morning-experiment :-( > > Joachim > > > > -- > > ----------------------------------------------------------------------- > > Objektfabrik Joachim Tuchelmailto:jtuchel@objektfabrik.de > > Fliederweg 1http://www.objektfabrik.de > > D-71640 Ludwigsburghttp://joachimtuchel.wordpress.com > > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >

June 19, 2016

Re: [Pharo-users] #inform: Changed in 5.0?

by Sean P. DeNigris

Denis Kudriashov wrote > Do you perform it inside #defer: message? I didn't and it was working in 4.0, but wrapping in #defer: it now works again in 5.0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/inform-Changed-in-5-0-tp4901478p4901815.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 19, 2016