Re: [Pharo-users] Machine learning in Pharo

You have also Natural Smalltalk from hernan. It sounds like a good basis. Stef Le 1/5/16 à 18:50, Evan Donahue a écrit : Hello, I added a "MachineLearning" repository to Smalltalkhub a while back, but I got sidetracked before adding anything beyond a naive KNN classifier, which was

Re: [Pharo-users] Machine learning in Pharo

for NLP Olivier started to work on Phonetix Now there is https://github.com/mark-watson/nlp_smalltalk But the lince is GPL3.0 and it looks simple... not sure it is worth to polute your life with such license. Stef Le 1/5/16 à 18:50, Evan Donahue a écrit : Hello, I added a

Re: [Pharo-users] Machine learning in Pharo

Hi Even, let us know! This is highly exciting! Alexandre > On May 1, 2016, at 1:50 PM, Evan Donahue wrote: > > Hello, > > I added a "MachineLearning" repository to Smalltalkhub a while back, but I > got sidetracked before adding anything beyond a naive KNN classifier,

Re: [Pharo-users] Machine learning in Pharo

Hello, I added a "MachineLearning" repository to Smalltalkhub a while back, but I got sidetracked before adding anything beyond a naive KNN classifier, which was really just to help prototype the testing framework. That said, my plans involve expanding the library extensively this summer in

Re: [Pharo-users] #ast vs. #parseTree

marcus may be we should slowly deprecated ast into cachedParseTree or something like that. Le 30/4/16 à 22:25, Sean P. DeNigris a écrit : Why does CompiledMethod understand both? They are in the same protocol, produce the same kindOf result, and neither has a method comment! :/ (Pharo 4.0)

Re: [Pharo-users] Create BaselineOf from ConfigurationOf

Thierry Goubier wrote > Oh, that's why you were asking for #ast versus #parseTree. You caught me! - Cheers, Sean -- View this message in context: http://forum.world.st/Create-BaselineOf-from-ConfigurationOf-tp4893076p4893147.html Sent from the Pharo Smalltalk Users mailing list archive at

Re: [Pharo-users] #ast vs. #parseTree

Marcus Denker-4 wrote > #ast returns a result from the cache, while #parseTree always gets a new > one… Ah, okay. What is the difference? That is, how/when is the cache updated? Marcus Denker-4 wrote > Yes, it could be better. Like always. :) - Cheers, Sean -- View this message in

Re: [Pharo-users] RT export to PDF

On 01/05/16 04:00, Arturo Zambrano wrote: Hi, I'm using RT on top of pharo5. As I need to export to pdf, I also installed RTPDFExporter and Artefact development versions Exporting to pdf fails with MNU RTPDFVisitor>>visitMapShape: any hint regarding this? The PDF exporter has its last

Re: [Pharo-users] Pharo 3 / Pharo3 Dark Theme names

is for historical reasons… there is no actual reason to not rename them :) > On 01 May 2016, at 11:06, Marcus Denker wrote: > > yes… I am thinking that always when I happen to see it in the setting. >> On 30 Apr 2016, at 18:35, Peter Uhnák wrote: >>

Re: [Pharo-users] Pharo 3 / Pharo3 Dark Theme names

yes… I am thinking that always when I happen to see it in the setting. > On 30 Apr 2016, at 18:35, Peter Uhnák wrote: > > Hi, > > is there some reason why the theme is called "Pharo 3" and "Pharo3 Dark"… I > mean we are about to start Pharo 6 so maybe it should just be

Re: [Pharo-users] #ast vs. #parseTree

#ast returns a result from the cache, while #parseTree always gets a new one… yes, it could be documented. Yes, it could be better. Like always. Marcus > On 30 Apr 2016, at 22:25, Sean P. DeNigris wrote: > > Why does CompiledMethod understand both? They are in

Re: [Pharo-users] Create BaselineOf from ConfigurationOf

Le 30/04/2016 23:28, Sean P. DeNigris a écrit : I got tired of manually converting Configs into Baselines, so I wrote a little script. You pass it the selector of a #baselineXyz: method, and it converts it (i.e. changes the pragma, removes the blessing and repo, etc) Hopefully you will find it