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.blond...@worldline.com> wrote: > > > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de >> Serge Stinckwich >> Envoyé : vendredi 2 septembre 2016 16:44 >> À : Pharo Development List >> Cc : scismallt...@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.blond...@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/
