September 2016 - Pharo-users

Re: [Pharo-users] What are the best practices for an open source project with Pharo?

by stepharo

Le 14/9/16 Ã 15:22, julius a Ã©crit : > I'm new to Smalltalk, welcome :) > I did the Inria MOOC and really like the way of how to > construct applications. Tx > Still I wonder how development teams approach > development with Pharo. > Currently I'm thinking of implementing a small idea of mine with Pharo since > Seaside felt quite nice when I experimented a bit. The project would need to > be open source because I want to apply for funding at a initiative that only > supports open source projects. But then I don't have the feeling that the > Monticello approach is the most inviting way to get funding or contributors > considering everyone is used to Github. Start by building something then you will see if people comes. Moose and Seaside are large open-source projects are people developed using Monticello without problem. By the end of the year we will migrate everything to github. And by that time you can benefit from it. > I found now the guide to Git with Pharo by Peter Uhnak (thanks for writing > that post!) so maybe this would be a good solution... > > Searching for best practices I read about some projects that make sure > developers always get a new image every day, how could that be implemented > without too much hassle of needing a server with some kind of build system. You can request an account on our Jenkins server and you create a job and you can donwload it using the pharolauncher. You contributors can then take the latest version commit changes and updtae the configuration and the job will cretae automatically a new image for the next cycle. > *tl;dr*: how could and should I approach the development of an open source > project with Pharo, considering acceptance of Monticello usage and sharing > of pharo images? You provide a configurationOf and people can take an image like the seaside one and load your code using the configurationOf and they can commit to your repo. You can either have a readonly repo and an inbox and you do the merging. the inbox acts as a pull request. This is how we manage Pharo and pharo reasonably complex :) > > > > -- > View this message in context: http://forum.world.st/What-are-the-best-practices-for-an-open-source-projec… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 14, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Serge Stinckwich

Always same error message ... ExternalAddress loadSymbol: 'Rf_initEmbeddedR' from: RLibrary returns FailedPrimitive On Wed, Sep 14, 2016 at 3:55 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > >> -----Message d'origine----- >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de >> Serge Stinckwich >> EnvoyÃ© : mercredi 14 septembre 2016 15:09 >> Ã : Any question about pharo is welcome >> Cc : scismalltalk(a)googlegroups.com; Pharo Development List >> Objet : Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1 >> >> Hi Vincent, >> > Hi Serge, > > >> Ok I try again with the latest Pharo 6.0. >> >> When I evaluate: >> >> Gofer it smalltalkhubUser: 'VincentBlondeau' project: >> 'RProjectConnector'; configuration; loadStable There is an error : could not >> resolve Rconnector. Apparently there is a problem with the package name, >> because this vincentBlondeau and not VincentBlondeau (Uppercase). Did you >> already try your configuration in an empty Pharo 6.0 image ? :-) > > Not really for this one ... I corrected and it should work now ;) >> >> I was able to load RConnector-vincentBlondeau.72 directly from Monticello >> repo. >> I modify the RLibrary>>macModuleName path name to >> /usr/local/Cellar/r/3.3.1_2/R.framework/Versions/3.3/Resources/lib/libR.dyl >> ib >> When I relaunch my image, I have an error: the R session is not well >> initialized at startup. >> >> In RSession>>isExistsRf_initEmbeddedR I still see a reference to Alien class. >> You are still using Alien ? >> > > Because I didn't found something better before. But, I just looked at it and changed to ExternalAddress method. > > Can you try again with version 73 ? > > Thanks, > Vincent > >> >> >> On Tue, Sep 13, 2016 at 6:25 PM, Blondeau Vincent >> <vincent.blondeau(a)worldline.com> wrote: >> > >> > >> > >> >> -----Message d'origine----- >> >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part >> >> de Serge Stinckwich EnvoyÃ© : vendredi 2 septembre 2016 16:44 Ã : >> >> Pharo Development List Cc : scismalltalk(a)googlegroups.com; Any >> >> question about pharo is welcome Objet : Re: [Pharo-dev] [ANN] >> >> RProjectConnector V2.1 >> >> >> >> Great job Vincent ! >> >> >> > It will be great when it will work on OS X ;) >> > >> >> There is some problems on Mac OS X: >> >> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on: >> >> RObjectArray class>>initElementType: >> >> I was able to load the package after a while by loading directly the >> >> package with the Monticello Browser >> > >> > Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 >> image (it should work under Pharo 5.0 too) and that version 14 of >> ConfigurationOfRProjectConnector and version 71 of the RConnector >> packages are loaded. >> > >> >> - Apparently there is still some methods using NB like: RSession >> >> class>>checkSession or RSession class>>initEmbeddedR: >> > >> > Should not, it is modified ... >> > >> >> >> >> I try to move the R dll close to my Pharo VM and also inside the >> >> Plugins directory but without success ... >> > >> > It should be at the same location that libcairo.2.dylib >> > >> >> Is there a way to say where are the R dll instead of copying them ? >> >> >> > Didn't think so .. Maybe the VM developers knows ? >> > >> > >> > Thanks! >> > >> > Vincent >> > >> > >> >> Thank you. >> >> >> >> >> >> >> >> >> >> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent >> >> <vincent.blondeau(a)worldline.com> wrote: >> >> > Hello everyone, >> >> > >> >> > >> >> > >> >> > I am glad to announce the release of version 2.1 of the >> RProjectConnector. >> >> > >> >> > The binding between Pharo and R (https://www.r-project.org/) is now >> >> > translated to UFFI and so to Pharo 6.0. >> >> > >> >> > >> >> > >> >> > You can call directly your R methods from Pharo. For example, with >> >> > the famous iris clustering example: >> >> > >> >> > >> >> > >> >> > iris := 'eval' asREval: {RObject findVar: 'iris'}. >> >> > >> >> > 'plot' >> >> > >> >> > asREval: >> >> > >> >> > {(iris at: 'Petal.Length'). >> >> > >> >> > (iris at: 'Petal.Width'). >> >> > >> >> > (#pch -> 21). >> >> > >> >> > (#xlab -> 'length'). >> >> > >> >> > (#ylab -> 'Width'). >> >> > >> >> > (#bg ->((iris at: 'Species') collect: >> >> > [ :value | {'red'. 'green3'. 'blue'} at: value ])). >> >> > >> >> > (#main -> 'Edgar Anderson''s Iris Data')}. >> >> > >> >> > iris inspect. >> >> > >> >> > >> >> > >> >> > To use it, you should install R and copy the R libraries near the >> >> > Pharo VM (see the documentation on SmalltalkHub >> >> > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for >> >> > how to proceed). >> >> > >> >> > >> >> > >> >> > Donât forget to relaunch Pharo after the installation to be able to >> >> > use the connector. >> >> > >> >> > >> >> > >> >> > Only basic features are implemented yet, but you can participate to >> >> > its extension! >> >> > >> >> > >> >> > >> >> > Cheers, >> >> > >> >> > Vincent Blondeau >> >> > >> >> > >> >> > >> >> >> !!!************************************************************ >> >> ******* >> >> > ****************** "Ce message et les piÃ¨ces jointes sont >> >> > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. >> >> > Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous >> >> > recevez ce message par erreur, merci d'en avertir immÃ©diatement >> >> > l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant >> >> > Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra >> >> > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les >> >> > meilleurs efforts soient faits pour maintenir cette transmission >> >> > exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet >> >> > Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout >> >> > dommage rÃ©sultant d'un virus transmis. >> >> > >> >> > This e-mail and the documents attached are confidential and >> >> > intended solely for the addressee; it may also be privileged. If >> >> > you receive this e-mail in error, please notify the sender >> >> > immediately and destroy it. As its integrity cannot be secured on >> >> > the Internet, the Worldline liability cannot be triggered for the >> >> > message content. Although the sender endeavours to maintain a >> >> > computer virus-free network, the sender does not warrant that this >> >> > transmission is virus-free and will not be liable for any damages resulting >> from any virus transmitted.!!!" >> >> >> >> >> >> >> >> -- >> >> Serge Stinckwich >> >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> >> Every DSL ends up being Smalltalk >> >> http://www.doesnotunderstand.org/ >> > >> > >> > >> !!!************************************************************ >> ******* >> > ****************** "Ce message et les piÃ¨ces jointes sont >> > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut >> Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce >> message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le >> dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la >> responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de >> ce message. Bien que les meilleurs efforts soient faits pour maintenir cette >> transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã >> cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage >> rÃ©sultant d'un virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this e-mail >> in error, please notify the sender immediately and destroy it. As its integrity >> cannot be secured on the Internet, the Worldline liability cannot be triggered >> for the message content. Although the sender endeavours to maintain a >> computer virus-free network, the sender does not warrant that this >> transmission is virus-free and will not be liable for any damages resulting >> from any virus transmitted.!!!" >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 14, 2016

Re: [Pharo-users] Pharo users count / estimate ?

by Alexandre Bergel

I think we have many reliable numbers for the Pharo MOOC. Alexandre > On Sep 14, 2016, at 12:15 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi all, > > for some silly report that I need to write I wanted to add an estimate of how many people worldwide use Pharo. I tried to find number of downloads of e.g. Pharo 5 to use that as a basis for estimation but I could not find this info online. Does the Pharo team have any usable statistics that can be shared ? > > TIA > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >

Sept. 14, 2016

Pharo users count / estimate ?

by Johan Fabry

Hi all, for some silly report that I need to write I wanted to add an estimate of how many people worldwide use Pharo. I tried to find number of downloads of e.g. Pharo 5 to use that as a basis for estimation but I could not find this info online. Does the Pharo team have any usable statistics that can be shared ? TIA -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Sept. 14, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Blondeau Vincent

> -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > Serge Stinckwich > EnvoyÃ© : mercredi 14 septembre 2016 15:09 > Ã : Any question about pharo is welcome > Cc : scismalltalk(a)googlegroups.com; Pharo Development List > Objet : Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1 > > Hi Vincent, > Hi Serge, > Ok I try again with the latest Pharo 6.0. > > When I evaluate: > > Gofer it smalltalkhubUser: 'VincentBlondeau' project: > 'RProjectConnector'; configuration; loadStable There is an error : could not > resolve Rconnector. Apparently there is a problem with the package name, > because this vincentBlondeau and not VincentBlondeau (Uppercase). Did you > already try your configuration in an empty Pharo 6.0 image ? :-) Not really for this one ... I corrected and it should work now ;) > > I was able to load RConnector-vincentBlondeau.72 directly from Monticello > repo. > I modify the RLibrary>>macModuleName path name to > /usr/local/Cellar/r/3.3.1_2/R.framework/Versions/3.3/Resources/lib/libR.dyl > ib > When I relaunch my image, I have an error: the R session is not well > initialized at startup. > > In RSession>>isExistsRf_initEmbeddedR I still see a reference to Alien class. > You are still using Alien ? > Because I didn't found something better before. But, I just looked at it and changed to ExternalAddress method. Can you try again with version 73 ? Thanks, Vincent > > > On Tue, Sep 13, 2016 at 6:25 PM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > > > > > >> -----Message d'origine----- > >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > >> de Serge Stinckwich EnvoyÃ© : vendredi 2 septembre 2016 16:44 Ã : > >> Pharo Development List Cc : scismalltalk(a)googlegroups.com; Any > >> question about pharo is welcome Objet : Re: [Pharo-dev] [ANN] > >> RProjectConnector V2.1 > >> > >> Great job Vincent ! > >> > > It will be great when it will work on OS X ;) > > > >> There is some problems on Mac OS X: > >> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on: > >> RObjectArray class>>initElementType: > >> I was able to load the package after a while by loading directly the > >> package with the Monticello Browser > > > > Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 > image (it should work under Pharo 5.0 too) and that version 14 of > ConfigurationOfRProjectConnector and version 71 of the RConnector > packages are loaded. > > > >> - Apparently there is still some methods using NB like: RSession > >> class>>checkSession or RSession class>>initEmbeddedR: > > > > Should not, it is modified ... > > > >> > >> I try to move the R dll close to my Pharo VM and also inside the > >> Plugins directory but without success ... > > > > It should be at the same location that libcairo.2.dylib > > > >> Is there a way to say where are the R dll instead of copying them ? > >> > > Didn't think so .. Maybe the VM developers knows ? > > > > > > Thanks! > > > > Vincent > > > > > >> Thank you. > >> > >> > >> > >> > >> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent > >> <vincent.blondeau(a)worldline.com> wrote: > >> > Hello everyone, > >> > > >> > > >> > > >> > I am glad to announce the release of version 2.1 of the > RProjectConnector. > >> > > >> > The binding between Pharo and R (https://www.r-project.org/) is now > >> > translated to UFFI and so to Pharo 6.0. > >> > > >> > > >> > > >> > You can call directly your R methods from Pharo. For example, with > >> > the famous iris clustering example: > >> > > >> > > >> > > >> > iris := 'eval' asREval: {RObject findVar: 'iris'}. > >> > > >> > 'plot' > >> > > >> > asREval: > >> > > >> > {(iris at: 'Petal.Length'). > >> > > >> > (iris at: 'Petal.Width'). > >> > > >> > (#pch -> 21). > >> > > >> > (#xlab -> 'length'). > >> > > >> > (#ylab -> 'Width'). > >> > > >> > (#bg ->((iris at: 'Species') collect: > >> > [ :value | {'red'. 'green3'. 'blue'} at: value ])). > >> > > >> > (#main -> 'Edgar Anderson''s Iris Data')}. > >> > > >> > iris inspect. > >> > > >> > > >> > > >> > To use it, you should install R and copy the R libraries near the > >> > Pharo VM (see the documentation on SmalltalkHub > >> > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for > >> > how to proceed). > >> > > >> > > >> > > >> > Donât forget to relaunch Pharo after the installation to be able to > >> > use the connector. > >> > > >> > > >> > > >> > Only basic features are implemented yet, but you can participate to > >> > its extension! > >> > > >> > > >> > > >> > Cheers, > >> > > >> > Vincent Blondeau > >> > > >> > > >> > > >> > !!!************************************************************ > >> ******* > >> > ****************** "Ce message et les piÃ¨ces jointes sont > >> > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. > >> > Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous > >> > recevez ce message par erreur, merci d'en avertir immÃ©diatement > >> > l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant > >> > Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > >> > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les > >> > meilleurs efforts soient faits pour maintenir cette transmission > >> > exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet > >> > Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout > >> > dommage rÃ©sultant d'un virus transmis. > >> > > >> > This e-mail and the documents attached are confidential and > >> > intended solely for the addressee; it may also be privileged. If > >> > you receive this e-mail in error, please notify the sender > >> > immediately and destroy it. As its integrity cannot be secured on > >> > the Internet, the Worldline liability cannot be triggered for the > >> > message content. Although the sender endeavours to maintain a > >> > computer virus-free network, the sender does not warrant that this > >> > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted.!!!" > >> > >> > >> > >> -- > >> Serge Stinckwich > >> UCBN & UMI UMMISCO 209 (IRD/UPMC) > >> Every DSL ends up being Smalltalk > >> http://www.doesnotunderstand.org/ > > > > > > > !!!************************************************************ > ******* > > ****************** "Ce message et les piÃ¨ces jointes sont > > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut > Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce > message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le > dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la > responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de > ce message. Bien que les meilleurs efforts soient faits pour maintenir cette > transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã > cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage > rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted.!!!" > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Sept. 14, 2016

What are the best practices for an open source project with Pharo?

by julius

I'm new to Smalltalk, I did the Inria MOOC and really like the way of how to construct applications. Still I wonder how development teams approach development with Pharo. Currently I'm thinking of implementing a small idea of mine with Pharo since Seaside felt quite nice when I experimented a bit. The project would need to be open source because I want to apply for funding at a initiative that only supports open source projects. But then I don't have the feeling that the Monticello approach is the most inviting way to get funding or contributors considering everyone is used to Github. I found now the guide to Git with Pharo by Peter Uhnak (thanks for writing that post!) so maybe this would be a good solution... Searching for best practices I read about some projects that make sure developers always get a new image every day, how could that be implemented without too much hassle of needing a server with some kind of build system. *tl;dr*: how could and should I approach the development of an open source project with Pharo, considering acceptance of Monticello usage and sharing of pharo images? -- View this message in context: http://forum.world.st/What-are-the-best-practices-for-an-open-source-projec… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 14, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Serge Stinckwich

Hi Vincent, Ok I try again with the latest Pharo 6.0. When I evaluate: Gofer it smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector'; configuration; loadStable There is an error : could not resolve Rconnector. Apparently there is a problem with the package name, because this vincentBlondeau and not VincentBlondeau (Uppercase). Did you already try your configuration in an empty Pharo 6.0 image ? :-) I was able to load RConnector-vincentBlondeau.72 directly from Monticello repo. I modify the RLibrary>>macModuleName path name to /usr/local/Cellar/r/3.3.1_2/R.framework/Versions/3.3/Resources/lib/libR.dylib When I relaunch my image, I have an error: the R session is not well initialized at startup. In RSession>>isExistsRf_initEmbeddedR I still see a reference to Alien class. You are still using Alien ? On Tue, Sep 13, 2016 at 6:25 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> Serge Stinckwich >> EnvoyÃ© : vendredi 2 septembre 2016 16:44 >> Ã : Pharo Development List >> Cc : scismalltalk(a)googlegroups.com; Any question about pharo is welcome >> Objet : Re: [Pharo-dev] [ANN] RProjectConnector V2.1 >> >> Great job Vincent ! >> > It will be great when it will work on OS X ;) > >> There is some problems on Mac OS X: >> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on: >> RObjectArray class>>initElementType: >> I was able to load the package after a while by loading directly the package >> with the Monticello Browser > > Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 image (it should work under Pharo 5.0 too) and that version 14 of ConfigurationOfRProjectConnector and version 71 of the RConnector packages are loaded. > >> - Apparently there is still some methods using NB like: RSession >> class>>checkSession or RSession class>>initEmbeddedR: > > Should not, it is modified ... > >> >> I try to move the R dll close to my Pharo VM and also inside the Plugins >> directory but without success ... > > It should be at the same location that libcairo.2.dylib > >> Is there a way to say where are the R dll instead of copying them ? >> > Didn't think so .. Maybe the VM developers knows ? > > > Thanks! > > Vincent > > >> Thank you. >> >> >> >> >> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent >> <vincent.blondeau(a)worldline.com> wrote: >> > Hello everyone, >> > >> > >> > >> > I am glad to announce the release of version 2.1 of the RProjectConnector. >> > >> > The binding between Pharo and R (https://www.r-project.org/) is now >> > translated to UFFI and so to Pharo 6.0. >> > >> > >> > >> > You can call directly your R methods from Pharo. For example, with the >> > famous iris clustering example: >> > >> > >> > >> > iris := 'eval' asREval: {RObject findVar: 'iris'}. >> > >> > 'plot' >> > >> > asREval: >> > >> > {(iris at: 'Petal.Length'). >> > >> > (iris at: 'Petal.Width'). >> > >> > (#pch -> 21). >> > >> > (#xlab -> 'length'). >> > >> > (#ylab -> 'Width'). >> > >> > (#bg ->((iris at: 'Species') collect: >> > [ :value | {'red'. 'green3'. 'blue'} at: value ])). >> > >> > (#main -> 'Edgar Anderson''s Iris Data')}. >> > >> > iris inspect. >> > >> > >> > >> > To use it, you should install R and copy the R libraries near the >> > Pharo VM (see the documentation on SmalltalkHub >> > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for >> > how to proceed). >> > >> > >> > >> > Donât forget to relaunch Pharo after the installation to be able to >> > use the connector. >> > >> > >> > >> > Only basic features are implemented yet, but you can participate to >> > its extension! >> > >> > >> > >> > Cheers, >> > >> > Vincent Blondeau >> > >> > >> > >> !!!************************************************************ >> ******* >> > ****************** "Ce message et les piÃ¨ces jointes sont >> > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il >> > peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous >> > recevez ce message par erreur, merci d'en avertir immÃ©diatement >> > l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre >> > assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre >> > recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> > efforts soient faits pour maintenir cette transmission exempte de tout >> > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >> > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >> > d'un virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> > solely for the addressee; it may also be privileged. If you receive >> > this e-mail in error, please notify the sender immediately and destroy >> > it. As its integrity cannot be secured on the Internet, the Worldline >> > liability cannot be triggered for the message content. Although the >> > sender endeavours to maintain a computer virus-free network, the >> > sender does not warrant that this transmission is virus-free and will >> > not be liable for any damages resulting from any virus transmitted.!!!" >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 14, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Blondeau Vincent

Hi, I implemented the FFILibrary way in the latest dev version. Maybe you have to modify the code to point to your library (see RLibrary methods). Donât hesitate to commit your code, the project is open. Thanks, Cheers, Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Esteban Lorenzano EnvoyÃ© : mercredi 14 septembre 2016 14:23 Ã : Any question about pharo is welcome Objet : Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1 Hi, On 14 Sep 2016, at 12:19, Ben Coman <btc(a)openInWorld.com<mailto:btc@openinworld.com>> wrote: On Wed, Sep 14, 2016 at 4:21 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: I try to move the R dll close to my Pharo VM and also inside the Plugins directory but without success ... It should be at the same location that libcairo.2.dylib Is there a way to say where are the R dll instead of copying them ? Are you using the system to do the library path resolution? Or finding the library file in Pharo and then passing an absolute path to FFI? no, it doesnâtâ¦ you need to pass a path to the library (e.g. '/opt/local/lib/libR.soâ) I think that the system that do the resolution: I defined in a trait: ffiLibraryName ^ #R And the library is named R.dll (under windows). Maybe I should do like CairoLibrary? My limited understanding is that #ffiLibraryName should return a class rather than a symbol. Thus... MyClass class >> ffiLibraryName ^ R R >> win32ModuleName ^ 'libr.N.dll'. "or whatever is the actual dll filenameâ wellâ¦ it can answer a class (a child of FFILibrary, like LibC) or a String with a fixed path: âlibr.N.dllâ of course, 2nd way is limited because you hardcode the library path :S cheers, Esteban cheers -ben !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Sept. 14, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Esteban Lorenzano

Hi, > On 14 Sep 2016, at 12:19, Ben Coman <btc(a)openInWorld.com> wrote: > > On Wed, Sep 14, 2016 at 4:21 PM, Blondeau Vincent > <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: >>>> >>>>> >>>>> I try to move the R dll close to my Pharo VM and also inside the >>>>> Plugins directory but without success ... >>>> >>>> It should be at the same location that libcairo.2.dylib >>>> >>>>> Is there a way to say where are the R dll instead of copying them ? >>> >>> Are you using the system to do the library path resolution? Or finding the >>> library file in Pharo and then passing an absolute path to FFI? no, it doesnâtâ¦ you need to pass a path to the library (e.g. '/opt/local/lib/libR.soâ) >> >> I think that the system that do the resolution: >> I defined in a trait: >> ffiLibraryName >> ^ #R >> And the library is named R.dll (under windows). >> >> Maybe I should do like CairoLibrary? > > > My limited understanding is that #ffiLibraryName should return a class > rather than a symbol. Thus... > > MyClass class >> ffiLibraryName > ^ R > > R >> win32ModuleName > ^ 'libr.N.dll'. "or whatever is the actual dll filenameâ wellâ¦ it can answer a class (a child of FFILibrary, like LibC) or a String with a fixed path: âlibr.N.dllâ of course, 2nd way is limited because you hardcode the library path :S cheers, Esteban > > > cheers -ben

Sept. 14, 2016

Re: [Pharo-users] Problem cleaning up image

by Vitor Medina Cruz

Thanks for the answers! On Tue, Sep 13, 2016 at 2:46 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 13 Sep 2016, at 18:54, Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > > > > I understand. I thought it did more stuff, like remove necessary > development tools or executing processes, > > It does call #cleanUpForRelease, but this we call at *every* update on the > CI, too. This calls the #cleanUp method of all classes > and does some more (rehashing all dictionaries, restarting all? methods > holding on to blocksâ¦). > > > I don't know, but considering its implementation it should affect only > the image size, right? > > > Yes. Of course right now Cog is not compacting the somewhat empty > allocated memory regions, so e.g. the > 47 MB image should be around 15 MB empty space and the cleanup will not > shrink it. > > But when this is fixed, you should see a change. A saved image is too a > large extend methods and literals they > point to (especially for things like Tutorials). In the past the normal > image was ca. 25MB, while the shrieked one > after cleanup for deployment maybe 15? I do not remember. > > But that was already a bit of âmoored lawâ time ago ;-) > > Marcus > > >

Sept. 14, 2016