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

View a class with inherited variables/methods

by Esteban A. Maringolo

Is there a way to view a class with all the inherited instance variables and/or methods? I'm trying to understand some code, and because the inheritance tree is not shallow, I'd like to see all the variables it has (both own and inherited). Regards! Esteban A. Maringolo

March 8, 2016

Re: [Pharo-users] [Pillar] Ascii doc

by Yann Dubois

AsciiDoc is an exporter like Pillar, you can export you asciidoc file to pdf or something else. For the moment, this format allows generate files in format that Pillar can't know. I hope I answer your question

March 8, 2016

Re: [Pharo-users] Call about Numerical Methods in Pharo :)

by Alexandre Bergel

Vincent, can you tell a bit more what this binding is about? how can I try? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 3, 2016, at 6:43 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > That's a very good idea. > For now, I use a Pharo-R binding to make the statistics, but it is better if it is directly in the image. > > For my part, it should be nice to have: > - Principal Component Analysis > - Time series > - Correlation with several variables (Correlation matrix) + significance tests (pearson, spearman...) > - Standard statistical tests: normality, variance, mean, distribution > - And the more important is to have nice tools to visualize the data (Box plot, histogram, scatterplots, PCA ones) with a simple API for standard things but that we can customize. The best is that we are able to draw regression lines on them. But I think that is more a Roassal part. > > Thanks for the initiative, > > Cheers, > Vincent > >> -----Message d'origine----- >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de >> stepharo >> EnvoyÃ© : mercredi 2 mars 2016 14:17 >> Ã : Pharo Development List; Any question about pharo is welcome; Didier >> Besset; Souissi Sami >> Objet : [Pharo-users] Call about Numerical Methods in Pharo :) >> >> Hi guys >> >> I met Didier Besset and we had a great hacking session and discussions with >> Serge Stinckwich. >> Didier would like to help Pharo and the numerical part of it. ***Big >> thanks*** Didier. >> >> We would like to do several things: >> >> - Work on "Hows to" >> The numerical methods in Pharo is good but the gap between us and the >> math is too large :) >> so the idea is to have a series of "how to ..." >> - histomgram (simple, based on distribution) >> >> - Improve the SciPharo/NumPha (previously SciSmalltalk) library >> This morning we started to implement a >> ComponentPrincipalDecomposition by combining two of the >> objects available in SciPharo. >> Then we started to enhance the distributions to make sure that we can >> plug other distribution for having >> controlled random number. >> >> - Do a public call to know what is missing for you: this is this mail :) >> Didier would like to work on concrete cases. I love that attitude >> So tell us :) >> >> Hernan ?? >> Alex: ?? pvalue? better distribution? >> Vincent: covariance? CPA? >> Philippe: times series >> Serge R frames? >> Sami: Better random number and various distributions? >> >> - Organise a two day lectures with practices on concrete case in September >> with a recording session. >> Either at IRD Bondy or Lille. >> >> - Make sure that the Numerical Method book will get on lulu :) with a >> better cover and title :) >> >> >> Stef >> > > > !!!************************************************************************************* > "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.!!!"

March 8, 2016

Re: [Pharo-users] Voyage, Magritte descriptions, and nil exceptions

by Sabine Manaa

I don't think it is a bug, there is missing the description of the relationship between one and two: If I define the following method, it works. Thomasso, do you know this documentation? https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/ws/book-resu… One class>>mongoLink <mongoDescription> ^ VOMongoToOneDescription new attributeName: 'link'; kind: Two; yourself regards Sabine 2016-03-08 16:31 GMT+01:00 EstebanLM [via Smalltalk] < ml-node+s1294792n4883253h38(a)n4.nabble.com>: > Hi Tommaso, > > that might be a bugâ¦ which version are you using? > if latest, can you fill a bug here: > https://github.com/estebanlm/voyage/issues (so I do not forget it)? > > thanks, > Esteban > > On 08 Mar 2016, at 16:25, Tommaso Dal Sasso <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4883253&i=0>> wrote: > > Hi, > > thanks for your answer, I also tried with One>>mongoContainer, but sadly > that does not solve the issue. > I think it works in your case because you have the One object cached from > the previous query, but if you inspect the "link" field, it should be nil. > > If you reset the repository connection, it should give the exception again. > > I'll keep trying :-) > Tommaso > > > > On 07/03/16 14:07, Sabine Manaa wrote: > > Hi Tommaso, > > you did not define a One>>mongoContainer. I defined it and then it seems > to work. > > Regards > > 2016-03-06 1:42 GMT+01:00 Tommaso DS [via Smalltalk] <<a > moz-do-not-send="true" > href="x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=0" > target="_top" rel="nofollow" link="external" class="">[hidden email]>: > >> Hi, >> >> I am having troubles with Voyage and Mongo. >> I have some Classes that I save in Mongo, say "One", "Two", and "Three". >> All three classes and are voyage roots, so the objects from each class >> are stored in different collections. >> One objects has a reference to Two or Three objects. >> >> The problem arises when I use a Magritte description and define a Mongo >> container to optimize the storage: since each class is stored in its own >> collection, there is no point in storing the #instanceOf attribute as >> well. >> >> Two>>mongoContainer >> <mongoContainer> >> >> ^ VOMongoContainer new >> kind: Two; >> yourself >> >> If I add this method, when I try to load an object One, I get the >> exception: "KeyNotFound: key #nil not found in SystemDictionary". >> It looks like Voyage is not able to understand the type of the objects >> stored in the collection Two, when loaded from a reference. >> >> Am I missing something? Do I need to specify something more to make it >> work? >> >> I reproduced the scenario in an image that can be downloaded here: >> https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip >> >> Do you have any idea? Should I report this on the issue tracker? >> >> Thanks! >> Tommaso >> >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… >> To start a new topic under Pharo Smalltalk Users, email <a >> moz-do-not-send="true" >> href="x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=1" >> target="_top" rel="nofollow" link="external" class="">[hidden email] >> To unsubscribe from Pharo Smalltalk Users, click here. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> > > > ------------------------------ > View this message in context: Re: Voyage, Magritte descriptions, and nil > exceptions > <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com > <http://nabble.com>. > > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 8, 2016

Re: [Pharo-users] Call about Numerical Methods in Pharo :)

by Werner Kassens

Hi Vincent, it would perhaps be helpful if you could specify your proposal "Standard statistical tests: normality, variance, mean, distribution" a bit, because eventually some of these are already implemented and would just need a wrapper to be easily usable. perhaps it would be enough if one would know which R-functions you use or so, and what kind of return you'd expect. werner On 03/03/2016 10:43 AM, Blondeau Vincent wrote: > Hi, > > That's a very good idea. > For now, I use a Pharo-R binding to make the statistics, but it is better if it is directly in the image. > > For my part, it should be nice to have: > - Principal Component Analysis > - Time series > - Correlation with several variables (Correlation matrix) + significance tests (pearson, spearman...) > - Standard statistical tests: normality, variance, mean, distribution > - And the more important is to have nice tools to visualize the data (Box plot, histogram, scatterplots, PCA ones) with a simple API for standard things but that we can customize. The best is that we are able to draw regression lines on them. But I think that is more a Roassal part. > > Thanks for the initiative, > > Cheers, > Vincent > >> -----Message d'origine----- >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de >> stepharo >> EnvoyÃ© : mercredi 2 mars 2016 14:17 >> Ã : Pharo Development List; Any question about pharo is welcome; Didier >> Besset; Souissi Sami >> Objet : [Pharo-users] Call about Numerical Methods in Pharo :) >> >> Hi guys >> >> I met Didier Besset and we had a great hacking session and discussions with >> Serge Stinckwich. >> Didier would like to help Pharo and the numerical part of it. ***Big >> thanks*** Didier. >> >> We would like to do several things: >> >> - Work on "Hows to" >> The numerical methods in Pharo is good but the gap between us and the >> math is too large :) >> so the idea is to have a series of "how to ..." >> - histomgram (simple, based on distribution) >> >> - Improve the SciPharo/NumPha (previously SciSmalltalk) library >> This morning we started to implement a >> ComponentPrincipalDecomposition by combining two of the >> objects available in SciPharo. >> Then we started to enhance the distributions to make sure that we can >> plug other distribution for having >> controlled random number. >> >> - Do a public call to know what is missing for you: this is this mail :) >> Didier would like to work on concrete cases. I love that attitude >> So tell us :) >> >> Hernan ?? >> Alex: ?? pvalue? better distribution? >> Vincent: covariance? CPA? >> Philippe: times series >> Serge R frames? >> Sami: Better random number and various distributions? >> >> - Organise a two day lectures with practices on concrete case in September >> with a recording session. >> Either at IRD Bondy or Lille. >> >> - Make sure that the Numerical Method book will get on lulu :) with a >> better cover and title :) >> >> >> Stef >> > > > !!!************************************************************************************* > "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.!!!" >

March 8, 2016

Re: [Pharo-users] Voyage, Magritte descriptions, and nil exceptions

by Esteban Lorenzano

Hi Tommaso, that might be a bugâ¦ which version are you using? if latest, can you fill a bug here: https://github.com/estebanlm/voyage/issues (so I do not forget it)? thanks, Esteban > On 08 Mar 2016, at 16:25, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: > > Hi, > > thanks for your answer, I also tried with One>>mongoContainer, but sadly that does not solve the issue. > I think it works in your case because you have the One object cached from the previous query, but if you inspect the "link" field, it should be nil. > > If you reset the repository connection, it should give the exception again. > > I'll keep trying :-) > Tommaso > > > > On 07/03/16 14:07, Sabine Manaa wrote: >> Hi Tommaso, >> >> you did not define a One>>mongoContainer. I defined it and then it seems to work. >> >> Regards >> >> 2016-03-06 1:42 GMT+01:00 Tommaso DS [via Smalltalk] <[hidden email] <x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=0>>: >> Hi, >> >> I am having troubles with Voyage and Mongo. >> I have some Classes that I save in Mongo, say "One", "Two", and "Three". >> All three classes and are voyage roots, so the objects from each class >> are stored in different collections. >> One objects has a reference to Two or Three objects. >> >> The problem arises when I use a Magritte description and define a Mongo >> container to optimize the storage: since each class is stored in its own >> collection, there is no point in storing the #instanceOf attribute as well. >> >> Two>>mongoContainer >> <mongoContainer> >> >> ^ VOMongoContainer new >> kind: Two; >> yourself >> >> If I add this method, when I try to load an object One, I get the >> exception: "KeyNotFound: key #nil not found in SystemDictionary". >> It looks like Voyage is not able to understand the type of the objects >> stored in the collection Two, when loaded from a reference. >> >> Am I missing something? Do I need to specify something more to make it work? >> >> I reproduced the scenario in an image that can be downloaded here: >> https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip <https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip> >> >> Do you have any idea? Should I report this on the issue tracker? >> >> Thanks! >> Tommaso >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> >> To start a new topic under Pharo Smalltalk Users, email [hidden email] <x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here <applewebdata://F53A575C-598C-4B5D-B41C-A90723498F14>. >> NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> >> View this message in context: Re: Voyage, Magritte descriptions, and nil exceptions <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> >> Sent from the Pharo Smalltalk Users mailing list archive <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >

March 8, 2016

Re: [Pharo-users] [ANN] SelectEntity, a new widget for Spec

by Stephan Eggermont

On 08-03-16 13:52, Johan Fabry wrote: > That looks very cool, how about adding it to the standard distribution? That is definitely the goal. Now is the time to point out stupid names, bad design decisions, missed use cases and ugly layout. I would welcome feedback. While building it, I found out I don't like the way an EntryCompletion is connected to its PluggableTextFieldMorph. It makes it difficult to deal with objects that are not strings. PluggableTextFieldMorph>>entryCompletion: anEntryCompletion entryCompletion := anEntryCompletion. entryCompletion ifNotNil: [ entryCompletion chooseBlock isNil ifTrue: [entryCompletion chooseBlock: [:v | self setText: v. self acceptTextInModel ]] ifFalse: [ | blk | blk := entryCompletion chooseBlock. entryCompletion chooseBlock: [:v | self setText: v. self acceptTextInModel. blk value: v]]]. In the demo code it also is clear that the ListModel is incomplete, I couldn't find ho wto open a selected item with the keyboard (unless I implement click on the item, but that then does not have enough context to actually know what to do). Stephan

March 8, 2016

Re: [Pharo-users] [Ann] DemoFFI

by Stephan Eggermont

On 08-03-16 15:20, Pierce Ng wrote: > I wrote these to figure out how to port NBSQLite3 from NativeBoost to the new > FFI. I hope others will find them helpful too. Thanks, Pierce. I find this kind of demos very helpful. Stephan

March 8, 2016

Re: [Pharo-users] Voyage, Magritte descriptions, and nil exceptions

by Tommaso Dal Sasso

Hi, thanks for your answer, I also tried with One>>mongoContainer, but sadly that does not solve the issue. I think it works in your case because you have the One object cached from the previous query, but if you inspect the "link" field, it should be nil. If you reset the repository connection, it should give the exception again. I'll keep trying :-) Tommaso On 07/03/16 14:07, Sabine Manaa wrote: > Hi Tommaso, > > you did not define a One>>mongoContainer. I defined it and then it > seems to work. > > Regards > > 2016-03-06 1:42 GMT+01:00 Tommaso DS [via Smalltalk] <[hidden email] > </user/SendEmail.jtp?type=node&node=4882948&i=0>>: > > Hi, > > I am having troubles with Voyage and Mongo. > I have some Classes that I save in Mongo, say "One", "Two", and > "Three". > All three classes and are voyage roots, so the objects from each > class > are stored in different collections. > One objects has a reference to Two or Three objects. > > The problem arises when I use a Magritte description and define a > Mongo > container to optimize the storage: since each class is stored in > its own > collection, there is no point in storing the #instanceOf attribute > as well. > > Two>>mongoContainer > <mongoContainer> > > ^ VOMongoContainer new > kind: Two; > yourself > > If I add this method, when I try to load an object One, I get the > exception: "KeyNotFound: key #nil not found in SystemDictionary". > It looks like Voyage is not able to understand the type of the > objects > stored in the collection Two, when loaded from a reference. > > Am I missing something? Do I need to specify something more to > make it work? > > I reproduced the scenario in an image that can be downloaded here: > https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip > > Do you have any idea? Should I report this on the issue tracker? > > Thanks! > Tommaso > > > > ------------------------------------------------------------------------ > If you reply to this email, your message will be added to the > discussion below: > http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… > > To start a new topic under Pharo Smalltalk Users, email [hidden > email] </user/SendEmail.jtp?type=node&node=4882948&i=1> > To unsubscribe from Pharo Smalltalk Users, click here. > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > > > > > ------------------------------------------------------------------------ > View this message in context: Re: Voyage, Magritte descriptions, and > nil exceptions > <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com.

March 8, 2016

[Ann] DemoFFI

by Pierce Ng

Hi all, I've published libffidemo on Github, https://github.com/PierceNg/libffidemo, and DemoFFI on STH, http://smalltalkhub.com/#!/~PierceNg/DemoFFI. Together, they show how to use Pharo 5's Unified FFI to obtain an "opaque" pointer to a C-level struct, in the two usual styles: passing in a pointer pointer as a parameter, and via a pointer returned by a C function. They also show how to retrieve an integer through the opaque pointer in two usual styles: passing in a pointer to integer as a parameter, which involves creating an integer value holder on the Smalltalk side, and via an integer returned by a C function. Apart from that, the library does nothing. :-) To compile libffidemo for Pharo's use: $ gcc -shared -m32 -o libffidemo.so libffidemo.c I wrote these to figure out how to port NBSQLite3 from NativeBoost to the new FFI. I hope others will find them helpful too. Pierce

March 8, 2016