- Pharo-users - lists.pharo.org

Re: [Pharo-users] Metacello configuration based on subdirectory of Git repo

by Rafael Luque

Hi Dale, Your second option worked for me. This is the validation error I got for my previous configuration using the MetacelloToolBox: "Error: Missing required field (className:) for project reference 'Stamp' in version '0.1-baseline' { incompleteProjectSpec } [ #validateBaselineVersionSpec: ]" By the other hand, using a filetree url to my local working copy algo resolved the Stamp project dependency. Thank you very much! Rafa Rafael, It looks like in your case that you've got a configuration problem ... and here's the proper fix (but depending upon which vesion of Metacello you're using may or may not work): baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'filetree://full-filesystempath-to-your-pharo-subdirectory '. spec configuration: 'Stamp' with: [ spec repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; loads: 'Stamp'; version: #stable ]. spec package: 'MyStompMessaging' with: [ spec requires: #('Stamp') ] ] if you get an error then the following should work: baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'filetree://full-filesystempath-to-your-pharo-subdirectory '. spec project: 'Stamp-Core' with: [ spec className: 'ConfigurationOfStamp'; repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; loads: 'Stamp'; version: #stable ]. spec package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] I've also submitted a metacello bug[1] to cover this issue, although I may have already fixed the bug in a later version of Metacello, I'm going to double check wihen I get a chance... Finally, I would be interested to know what errors or warnings you might get from validating your configuration (inspect the result of MetacelloToolBox class>>validateConfiguration: with your configuration class as an argument). HTH, Dale [1] https://github.com/dalehenrich/metacello-work/issues/313 On Thu, Nov 13, 2014 at 12:28 PM, Rafael Luque <rafael.luque.leiva(a)gmail.com > wrote: > Thank you for the responses. > > I'll try both of them, but in the meantime I found another problem because > of my lack of experience. > > I'm trying to define in the baseline a dependency with another project, in > particular the Stamp project by Sven Van Caekenberghe [1] in Smalltalkhub > in the following way: > > baseline01: spec > <version: '0.1-baseline'> > spec > for: #common > do: [ > spec blessing: #baseline. > spec repository: 'filetree://full-filesystempath-to-your-pharo- > subdirectory'. > spec > project: 'Stamp-Core' > with: [ > spec > repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; > loads: 'Stamp'; > version: #stable ]. > spec > package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] > > > When I evaluate the following in a Workspace: > > (ConfigurationOfMyPackage project version: '0.1') load. > > I get the followin error: > > MessageNotUnderstood: receiver of "ensureLoadUsing:" is nil > > In the debugger I see that MetacelloMCProjectSpec>>projectPackage is nil. > > In an old thread I found that Dale Henrichs suggests to try this: > > MetacelloProjectRegistration > resetRegistry; > primeRegistryFromImage > > But in my case It does not solve the problem. > > > Thank you in advance. > > > [1] http://smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp/packages/Stamp > [2] > http://forum.world.st/Sample-metacello-configuration-referencing-a-github-p… > > 2014-11-13 19:07 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Le 13/11/2014 18:21, Rafael Luque a Ã©crit : >> >>> Hi all, >>> >>> I'm starting with Pharo and playing with the ways to integrate it with >>> Git. >>> >>> I've read the "Git and Pharo" chapter on "Enterprise Pharo" book by >>> Thierry Goubier and loaded the GitFileTree package. >>> >>> I'm working on a project with several microservices, one of them will be >>> based on Pharo and the other ones in other technologies. The project >>> repository is based in our own Git server and each microservice maps >>> with one subdirectory in the repo. >>> >>> My question is if it is possible to define a Metacello configuration to >>> load my packages from an specific subdirectory of a Git repository. I >>> have tried with the following baseline method, but it fails because does >>> not understand repoPath: >>> >> >> Yes, it is possible to fix a specific subdirectory, with a gitfiletree: >> url, via a dir=aRelativePath. >> >> baseline01: spec >> <version: '0.1-baseline'> >> spec >> for: #common >> do: [ >> spec blessing: #baseline. >> spec repository: 'gitfiletree://my-git-server/my-project&dir=my-pharo- >> subdirectory'. >> spec >> package: 'MyPackage'. >> . . . ] >> >> You can have a look at the ConfigurationOfAltBrowser in the configuration >> browser to see how it triggers downloading the GitFileTree support. >> >> Thierry >> >> >> baseline01: spec >>> <version: '0.1-baseline'> >>> spec >>> for: #common >>> do: [ >>> spec blessing: #baseline. >>> spec repository: 'git@my-git-server:my-project'. >>> spec repoPath: 'my-pharo-subdirectory'. >>> spec >>> package: 'MyPackage'. >>> . . . ] >>> >>> Thank you in advance. >>> >>> >> >> >

Nov. 13, 2014

Re: [Pharo-users] Metacello configuration based on subdirectory of Git repo

by Rafael Luque

Hi Dale, Your second option worked for me. This is the validation error I got for my previous configuration using the MetacelloToolBox: "Error: Missing required field (className:) for project reference 'Stamp' in version '0.1-baseline' { incompleteProjectSpec } [ #validateBaselineVersionSpec: ]" By the other hand, using a filetree URL to my local working copy algo resolved the Stamp project dependency. Thank you very much! Rafa 2014-11-13 21:57 GMT+01:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > Rafael, > > It looks like in your case that you've got a configuration problem ... and > here's the proper fix (but depending upon which vesion of Metacello you're > using may or may not work): > > baseline01: spec > <version: '0.1-baseline'> > spec > for: #common > do: [ > spec blessing: #baseline. > spec repository: 'filetree://full-filesystempath-to-your-pharo- > subdirectory'. > spec > configuration: 'Stamp' > with: [ > spec > repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; > loads: 'Stamp'; > version: #stable ]. > spec > package: 'MyStompMessaging' with: [ spec requires: #('Stamp') ] ] > > if you get an error then the following should work: > > baseline01: spec > <version: '0.1-baseline'> > spec > for: #common > do: [ > spec blessing: #baseline. > spec repository: 'filetree://full-filesystempath-to-your-pharo- > subdirectory'. > spec > project: 'Stamp-Core' > with: [ > spec > className: > 'ConfigurationOfStamp'; > repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; > loads: 'Stamp'; > version: #stable ]. > spec > package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] > > I've also submitted a metacello bug[1] to cover this issue, although I may > have already fixed the bug in a later version of Metacello, I'm going to > double check wihen I get a chance... > > Finally, I would be interested to know what errors or warnings you might > get from validating your configuration (inspect the result of > MetacelloToolBox class>>validateConfiguration: with your configuration > class as an argument). > > HTH, > > Dale > > [1] https://github.com/dalehenrich/metacello-work/issues/313 > > > On Thu, Nov 13, 2014 at 12:28 PM, Rafael Luque < > rafael.luque.leiva(a)gmail.com> wrote: > >> Thank you for the responses. >> >> I'll try both of them, but in the meantime I found another problem >> because of my lack of experience. >> >> I'm trying to define in the baseline a dependency with another project, >> in particular the Stamp project by Sven Van Caekenberghe [1] in >> Smalltalkhub in the following way: >> >> baseline01: spec >> <version: '0.1-baseline'> >> spec >> for: #common >> do: [ >> spec blessing: #baseline. >> spec repository: 'filetree://full-filesystempath-to-your-pharo- >> subdirectory'. >> spec >> project: 'Stamp-Core' >> with: [ >> spec >> repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; >> loads: 'Stamp'; >> version: #stable ]. >> spec >> package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] >> >> >> When I evaluate the following in a Workspace: >> >> (ConfigurationOfMyPackage project version: '0.1') load. >> >> I get the followin error: >> >> MessageNotUnderstood: receiver of "ensureLoadUsing:" is nil >> >> In the debugger I see that MetacelloMCProjectSpec>>projectPackage is nil. >> >> In an old thread I found that Dale Henrichs suggests to try this: >> >> MetacelloProjectRegistration >> resetRegistry; >> primeRegistryFromImage >> >> But in my case It does not solve the problem. >> >> >> Thank you in advance. >> >> >> [1] http://smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp/packages/Stamp >> [2] >> http://forum.world.st/Sample-metacello-configuration-referencing-a-github-p… >> >> 2014-11-13 19:07 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> >>> Le 13/11/2014 18:21, Rafael Luque a Ã©crit : >>> >>>> Hi all, >>>> >>>> I'm starting with Pharo and playing with the ways to integrate it with >>>> Git. >>>> >>>> I've read the "Git and Pharo" chapter on "Enterprise Pharo" book by >>>> Thierry Goubier and loaded the GitFileTree package. >>>> >>>> I'm working on a project with several microservices, one of them will be >>>> based on Pharo and the other ones in other technologies. The project >>>> repository is based in our own Git server and each microservice maps >>>> with one subdirectory in the repo. >>>> >>>> My question is if it is possible to define a Metacello configuration to >>>> load my packages from an specific subdirectory of a Git repository. I >>>> have tried with the following baseline method, but it fails because does >>>> not understand repoPath: >>>> >>> >>> Yes, it is possible to fix a specific subdirectory, with a gitfiletree: >>> url, via a dir=aRelativePath. >>> >>> baseline01: spec >>> <version: '0.1-baseline'> >>> spec >>> for: #common >>> do: [ >>> spec blessing: #baseline. >>> spec repository: 'gitfiletree://my-git-server/my-project&dir=my-pharo- >>> subdirectory'. >>> spec >>> package: 'MyPackage'. >>> . . . ] >>> >>> You can have a look at the ConfigurationOfAltBrowser in the >>> configuration browser to see how it triggers downloading the GitFileTree >>> support. >>> >>> Thierry >>> >>> >>> baseline01: spec >>>> <version: '0.1-baseline'> >>>> spec >>>> for: #common >>>> do: [ >>>> spec blessing: #baseline. >>>> spec repository: 'git@my-git-server:my-project'. >>>> spec repoPath: 'my-pharo-subdirectory'. >>>> spec >>>> package: 'MyPackage'. >>>> . . . ] >>>> >>>> Thank you in advance. >>>> >>>> >>> >>> >> >

Nov. 13, 2014

Re: [Pharo-users] Metacello configuration based on subdirectory of Git repo

by Dale Henrichs

Rafael, It looks like in your case that you've got a configuration problem ... and here's the proper fix (but depending upon which vesion of Metacello you're using may or may not work): baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'filetree://full-filesystempath-to-your-pharo-subdirectory '. spec configuration: 'Stamp' with: [ spec repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; loads: 'Stamp'; version: #stable ]. spec package: 'MyStompMessaging' with: [ spec requires: #('Stamp') ] ] if you get an error then the following should work: baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'filetree://full-filesystempath-to-your-pharo-subdirectory '. spec project: 'Stamp-Core' with: [ spec className: 'ConfigurationOfStamp'; repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; loads: 'Stamp'; version: #stable ]. spec package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] I've also submitted a metacello bug[1] to cover this issue, although I may have already fixed the bug in a later version of Metacello, I'm going to double check wihen I get a chance... Finally, I would be interested to know what errors or warnings you might get from validating your configuration (inspect the result of MetacelloToolBox class>>validateConfiguration: with your configuration class as an argument). HTH, Dale [1] https://github.com/dalehenrich/metacello-work/issues/313 On Thu, Nov 13, 2014 at 12:28 PM, Rafael Luque <rafael.luque.leiva(a)gmail.com > wrote: > Thank you for the responses. > > I'll try both of them, but in the meantime I found another problem because > of my lack of experience. > > I'm trying to define in the baseline a dependency with another project, in > particular the Stamp project by Sven Van Caekenberghe [1] in Smalltalkhub > in the following way: > > baseline01: spec > <version: '0.1-baseline'> > spec > for: #common > do: [ > spec blessing: #baseline. > spec repository: 'filetree://full-filesystempath-to-your-pharo- > subdirectory'. > spec > project: 'Stamp-Core' > with: [ > spec > repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; > loads: 'Stamp'; > version: #stable ]. > spec > package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] > > > When I evaluate the following in a Workspace: > > (ConfigurationOfMyPackage project version: '0.1') load. > > I get the followin error: > > MessageNotUnderstood: receiver of "ensureLoadUsing:" is nil > > In the debugger I see that MetacelloMCProjectSpec>>projectPackage is nil. > > In an old thread I found that Dale Henrichs suggests to try this: > > MetacelloProjectRegistration > resetRegistry; > primeRegistryFromImage > > But in my case It does not solve the problem. > > > Thank you in advance. > > > [1] http://smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp/packages/Stamp > [2] > http://forum.world.st/Sample-metacello-configuration-referencing-a-github-p… > > 2014-11-13 19:07 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Le 13/11/2014 18:21, Rafael Luque a Ã©crit : >> >>> Hi all, >>> >>> I'm starting with Pharo and playing with the ways to integrate it with >>> Git. >>> >>> I've read the "Git and Pharo" chapter on "Enterprise Pharo" book by >>> Thierry Goubier and loaded the GitFileTree package. >>> >>> I'm working on a project with several microservices, one of them will be >>> based on Pharo and the other ones in other technologies. The project >>> repository is based in our own Git server and each microservice maps >>> with one subdirectory in the repo. >>> >>> My question is if it is possible to define a Metacello configuration to >>> load my packages from an specific subdirectory of a Git repository. I >>> have tried with the following baseline method, but it fails because does >>> not understand repoPath: >>> >> >> Yes, it is possible to fix a specific subdirectory, with a gitfiletree: >> url, via a dir=aRelativePath. >> >> baseline01: spec >> <version: '0.1-baseline'> >> spec >> for: #common >> do: [ >> spec blessing: #baseline. >> spec repository: 'gitfiletree://my-git-server/my-project&dir=my-pharo- >> subdirectory'. >> spec >> package: 'MyPackage'. >> . . . ] >> >> You can have a look at the ConfigurationOfAltBrowser in the configuration >> browser to see how it triggers downloading the GitFileTree support. >> >> Thierry >> >> >> baseline01: spec >>> <version: '0.1-baseline'> >>> spec >>> for: #common >>> do: [ >>> spec blessing: #baseline. >>> spec repository: 'git@my-git-server:my-project'. >>> spec repoPath: 'my-pharo-subdirectory'. >>> spec >>> package: 'MyPackage'. >>> . . . ] >>> >>> Thank you in advance. >>> >>> >> >> >

Nov. 13, 2014

Re: [Pharo-users] Metacello configuration based on subdirectory of Git repo

by Rafael Luque

Thank you for the responses. I'll try both of them, but in the meantime I found another problem because of my lack of experience. I'm trying to define in the baseline a dependency with another project, in particular the Stamp project by Sven Van Caekenberghe [1] in Smalltalkhub in the following way: baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'filetree://full-filesystempath-to-your-pharo-subdirectory '. spec project: 'Stamp-Core' with: [ spec repository: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Stamp/main'; loads: 'Stamp'; version: #stable ]. spec package: 'MyStompMessaging' with: [ spec requires: #('Stamp-Core') ] ] When I evaluate the following in a Workspace: (ConfigurationOfMyPackage project version: '0.1') load. I get the followin error: MessageNotUnderstood: receiver of "ensureLoadUsing:" is nil In the debugger I see that MetacelloMCProjectSpec>>projectPackage is nil. In an old thread I found that Dale Henrichs suggests to try this: MetacelloProjectRegistration resetRegistry; primeRegistryFromImage But in my case It does not solve the problem. Thank you in advance. [1] http://smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp/packages/Stamp [2] http://forum.world.st/Sample-metacello-configuration-referencing-a-github-p… 2014-11-13 19:07 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Le 13/11/2014 18:21, Rafael Luque a Ã©crit : > >> Hi all, >> >> I'm starting with Pharo and playing with the ways to integrate it with >> Git. >> >> I've read the "Git and Pharo" chapter on "Enterprise Pharo" book by >> Thierry Goubier and loaded the GitFileTree package. >> >> I'm working on a project with several microservices, one of them will be >> based on Pharo and the other ones in other technologies. The project >> repository is based in our own Git server and each microservice maps >> with one subdirectory in the repo. >> >> My question is if it is possible to define a Metacello configuration to >> load my packages from an specific subdirectory of a Git repository. I >> have tried with the following baseline method, but it fails because does >> not understand repoPath: >> > > Yes, it is possible to fix a specific subdirectory, with a gitfiletree: > url, via a dir=aRelativePath. > > baseline01: spec > <version: '0.1-baseline'> > spec > for: #common > do: [ > spec blessing: #baseline. > spec repository: 'gitfiletree://my-git-server/my-project&dir=my-pharo- > subdirectory'. > spec > package: 'MyPackage'. > . . . ] > > You can have a look at the ConfigurationOfAltBrowser in the configuration > browser to see how it triggers downloading the GitFileTree support. > > Thierry > > > baseline01: spec >> <version: '0.1-baseline'> >> spec >> for: #common >> do: [ >> spec blessing: #baseline. >> spec repository: 'git@my-git-server:my-project'. >> spec repoPath: 'my-pharo-subdirectory'. >> spec >> package: 'MyPackage'. >> . . . ] >> >> Thank you in advance. >> >> > >

Nov. 13, 2014

Re: [Pharo-users] Opentalk or remoting libraries

by Alain Rastoul

Le 13/11/2014 20:17, Sven Van Caekenberghe a Ã©crit : > Nice. > > It is of course also important to note the security risks involved: the client can execute absolutely anything. > Yes, a problem on open networks. And important to notice > One partial solution is to bind the server only to the localhost. >

Nov. 13, 2014

Re: [Pharo-users] Error when compiling a string with a quote

by Hilaire

Thanks for the tips! Hilaire Le 13/11/2014 19:04, Sven Van Caekenberghe a Ã©crit : > I was too quick to respond, the #storeString conversion is OK: -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Nov. 13, 2014

Re: [Pharo-users] Opentalk or remoting libraries

by Sven Van Caekenberghe

Nice. It is of course also important to note the security risks involved: the client can execute absolutely anything. One partial solution is to bind the server only to the localhost. > On 13 Nov 2014, at 19:17, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > > Hi, > CORBA main focus is about interoperability between systems, languages (don't know about opentalk). > If you want smalltalk only remote execution, you can very easily do your own on Pharo with Zinc http components and Fuel serializer: a small server that reads smalltalk blocks, evaluates them and return the result (see below an example of server and client). > I don't know if Zinc and Fuel run on Squeak, but I guess if not, they are equivalents ones or you could do the same. > Beware that Fuel builds a graph of the objects touched by the object it serializes (the block) and serialize them along the way, that may be a problem if you have references to other big objects of your image. > > " ================================= RPC server" > " start Zn server in background " > ZnServer startDefaultOn: 1701. > ZnServer default delegate: (ZnWebSocketDelegate handler: > ([ :webSocket | > [ [ | serializedRequest request response serializedResponse | > serializedRequest := webSocket readMessage. > request := FLMaterializer materializeFromByteArray: serializedRequest. > "execute block and it's value to response byte array" > response := [ request value ] > on: Exception do: [ :ex | ex resume: 'Exception ',ex class name , ' - ', ex messageText ]. > serializedResponse := FLSerializer serializeToByteArray: response . > webSocket sendMessage: serializedResponse . > ] repeat. > ] > on: ConnectionClosed, ConnectionTimedOut > do: [ self crLog: 'Ignoring connection or timeout' ] > ]) ). > "=========================================" > > " to stop the server" > ZnServer stopDefault . > > > > "========================================= RPC CLIENT" > > " Client call to server: calculate factorial 100 on the other side" > | webSocket | > webSocket := ZnWebSocket to: 'ws://127.0.0.1:1701'. > [ | request serializedRequest serializedResponse response | > request := [ 100 factorial ] . " the request is the block to evaluate" > serializedRequest := FLSerializer serializeToByteArray: request . "serialize the block" > webSocket sendMessage: serializedRequest . "send it" > serializedResponse := webSocket readMessage . " read response" > response := FLMaterializer materializeFromByteArray: serializedResponse. "deserialize to object" > Transcript show: response asString ; cr ] > on: ConnectionClosed > do: [ self crLog: 'Ignoring connection close, done' ] > > > regards, > > Alain > > > Le 12/11/2014 18:17, Annick Fron a Ã©crit : >> Hi, >> >> Are there some libraries in pharo to do remote calls like in Opentalk or Corba ? >> >> Annick >> > > >

Nov. 13, 2014

Re: [Pharo-users] Opentalk or remoting libraries

by Alain Rastoul

Hi, CORBA main focus is about interoperability between systems, languages (don't know about opentalk). If you want smalltalk only remote execution, you can very easily do your own on Pharo with Zinc http components and Fuel serializer: a small server that reads smalltalk blocks, evaluates them and return the result (see below an example of server and client). I don't know if Zinc and Fuel run on Squeak, but I guess if not, they are equivalents ones or you could do the same. Beware that Fuel builds a graph of the objects touched by the object it serializes (the block) and serialize them along the way, that may be a problem if you have references to other big objects of your image. " ================================= RPC server" " start Zn server in background " ZnServer startDefaultOn: 1701. ZnServer default delegate: (ZnWebSocketDelegate handler: ([ :webSocket | [ [ | serializedRequest request response serializedResponse | serializedRequest := webSocket readMessage. request := FLMaterializer materializeFromByteArray: serializedRequest. "execute block and it's value to response byte array" response := [ request value ] on: Exception do: [ :ex | ex resume: 'Exception ',ex class name , ' - ', ex messageText ]. serializedResponse := FLSerializer serializeToByteArray: response . webSocket sendMessage: serializedResponse . ] repeat. ] on: ConnectionClosed, ConnectionTimedOut do: [ self crLog: 'Ignoring connection or timeout' ] ]) ). "=========================================" " to stop the server" ZnServer stopDefault . "========================================= RPC CLIENT" " Client call to server: calculate factorial 100 on the other side" | webSocket | webSocket := ZnWebSocket to: 'ws://127.0.0.1:1701'. [ | request serializedRequest serializedResponse response | request := [ 100 factorial ] . " the request is the block to evaluate" serializedRequest := FLSerializer serializeToByteArray: request . "serialize the block" webSocket sendMessage: serializedRequest . "send it" serializedResponse := webSocket readMessage . " read response" response := FLMaterializer materializeFromByteArray: serializedResponse. "deserialize to object" Transcript show: response asString ; cr ] on: ConnectionClosed do: [ self crLog: 'Ignoring connection close, done' ] regards, Alain Le 12/11/2014 18:17, Annick Fron a Ã©crit : > Hi, > > Are there some libraries in pharo to do remote calls like in Opentalk or Corba ? > > Annick >

Nov. 13, 2014

Re: [Pharo-users] Metacello configuration based on subdirectory of Git repo

by Thierry Goubier

Le 13/11/2014 18:21, Rafael Luque a Ã©crit : > Hi all, > > I'm starting with Pharo and playing with the ways to integrate it with Git. > > I've read the "Git and Pharo" chapter on "Enterprise Pharo" book by > Thierry Goubier and loaded the GitFileTree package. > > I'm working on a project with several microservices, one of them will be > based on Pharo and the other ones in other technologies. The project > repository is based in our own Git server and each microservice maps > with one subdirectory in the repo. > > My question is if it is possible to define a Metacello configuration to > load my packages from an specific subdirectory of a Git repository. I > have tried with the following baseline method, but it fails because does > not understand repoPath: Yes, it is possible to fix a specific subdirectory, with a gitfiletree: url, via a dir=aRelativePath. baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'gitfiletree://my-git-server/my-project&dir=my-pharo-subdirectory'. spec package: 'MyPackage'. . . . ] You can have a look at the ConfigurationOfAltBrowser in the configuration browser to see how it triggers downloading the GitFileTree support. Thierry > baseline01: spec > <version: '0.1-baseline'> > spec > for: #common > do: [ > spec blessing: #baseline. > spec repository: 'git@my-git-server:my-project'. > spec repoPath: 'my-pharo-subdirectory'. > spec > package: 'MyPackage'. > . . . ] > > Thank you in advance. >

Nov. 13, 2014

Re: [Pharo-users] Error when compiling a string with a quote

by Sven Van Caekenberghe

I was too quick to respond, the #storeString conversion is OK: (#( $f $o $o $' $b $a $r) as: String) storeString collect: [ :each | each ] as: Array. => #($' $f $o $o $' $' $b $a $r $') The contract of #storeString is, given a String (well any object), what should it look like when written as a literal constant in source code. That is precisely what you want, no ? but you have to drop adding your own quotes, like stream << 'description' << Character cr << Character tab << $^ << dialog description string storeString. or even (as #printOn: is the same as #storeOn: for String) stream << 'description' << Character cr << Character tab << $^ print: dialog description string. And I would turn this into a cascade, but that is more coding style. stream << 'description'; cr; tab; nextPut: $^; print: dialog description string. > On 13 Nov 2014, at 18:26, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 13/11/2014 18:05, Sven Van Caekenberghe a Ã©crit : >> I think you need to send #storeString to the result of 'dialog description string'. The single quote has to be doubled. > > Yep, I realized it is not double quoted. > I used this message copyWithRegex: '''' matchesReplacedWith: '''''' > > However both #storeString or #printString messages can't do the job. > > 'n''a pas l''e' storeString > -> '''n''''a pas l''''e''' > > ('n''a pas l''e'copyWithRegex: '''' matchesReplacedWith: '''''') > -> 'n''''a pas l''''e' > > > #storeString seems to mess up with the quote, adding superfluous one. > Strange? > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > >

Nov. 13, 2014