- Pharo-dev - lists.pharo.org

Last modified method in nautilus does not show the recently modified

by stepharo

Hi guys I'm trying to do a video (I will not show the feature) but Last modified method in nautilus does not show the recently modified Stef

March 8, 2016

Re: [Pharo-dev] [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-dev] strange array instance

by Eliot Miranda

Hi Pavel, On Tue, Mar 8, 2016 at 1:40 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > there is a strange array of size 1024 in the Pharo image that is not eaten > by garbage collector even if no object points to it. I guess it is related > to Spur. > > ((Array allInstances select: [ :i | i size = 1024 ]) > select: [ :a | a second = SmallInteger ]) pointersTo > > What is it and is it accessible somehow? > It is indeed the first class table page. It looks like an old bug. The oldest Spur image I can start up has the problem. The way that class table pages are hidden is that they have a class index which is not that of Array. Array is at index 52 in the class table (51 zero-relative, Array identityHash = 51), but it is also at index 17 (16 zero-relative). Array allInstances looks for objects whose class index is 51, hence not seeing the class table pages, which all (but the first) have class index 16. Luckily we can fix the problem easily, and we can fix another problem at the same time, which is that SmallFloat64 has the wrong hash. The class table is two-level; a (hidden) array of Arrays. Classes are in the class table at their identityHashes (so that to instantiate a class one copies the class's identity hash into the classIndex of the new instance instead of having to search the class table). But when SmallFloat64 was created in the 32-bit image I forgot to give it the right hash and store it in the class table. (there are no SmallFloat64 instances in a 32-bit image, only in 64-bits). So we can first change SmallFloat64's hash to 3, which is what the Spur 64-bit VM and image require, and enter it into the first class table page, and then we can make the first class table page disappear. | firstClassTablePage clone | "The first class table page is the first Array instance. Of course this is a bug." firstClassTablePage := Array someInstance. "It should contain only nil and classes." self assert: (firstClassTablePage allSatisfy: [:e| e == nil or: [e isBehavior]]). "And its first 17 elements should only be the immediate classes and Array, since Array is used as the class pun for class table pages, with index 17 (16 zero-relative)" self assert: (firstClassTablePage first: 17) asSet = {nil. SmallInteger. Character. Array} asSet. "It just so happens that the second Array is the specialSelectors" self assert: Array someInstance nextInstance == Smalltalk specialSelectors. "Store SmallFloat64 in the first class table page at index 4 (3 zero-relative)." firstClassTablePage at: 4 put: SmallFloat64. "Use the secret set identity hash primitive to set SmallFloat64's identityHash to 3." SmallFloat64 tryPrimitive: 161 withArgs: #(3). "Now create an object that looks like Array class, but has identityHash 16." "Take a shallow copy of Array class." clone := Array shallowCopy. "Change it into an Array." Array adoptInstance: clone. "Set its identityHash to 16." clone tryPrimitive: 161 withArgs: #(16). "Use the adoptInstance: primitive to ``set the class of the firstClassTablePage to the cone''. or, more accurately, to set the firstClassTablePage's class index to 16." clone tryPrimitive: 160 withArgs: {firstClassTablePage} With the above done, we can check that everything is ok." self assert: SmallFloat64 identityHash = 3. self assert: Array someInstance == Smalltalk specialSelectors. "A class table page is 1024 slots, contains only nil or behaviours, and contains at least one behaviour (is not all nils). There shouldn't be any that we can find." self assert: (self systemNavigation allObjects select: [:o| o isArray and: [o size = 1024 and: [(o allSatisfy: [:e| e == nil or: [e isBehavior]]) and: [o anySatisfy: [:e| e isBehavior]]]]]) size = 0 I recommend you create an update map. Then create a version of kernel with a post-load action, written something like this: (Array someInstance size = 1014 and: [(Array someInstance allSatisfy: [:e| e == nil or: [e isBehavior]]) and: [(firstClassTablePage first: 17) asSet = {nil. SmallInteger. Character. Array} asSet]]) ifTrue: [| firstClassTablePage clone | firstClassTablePage := Array someInstance. self assert: (firstClassTablePage allSatisfy: [:e| e == nil or: [e isBehavior]]). self assert: (firstClassTablePage first: 17) asSet = {nil. SmallInteger. Character. Array} asSet. firstClassTablePage at: 4 put: SmallFloat64. SmallFloat64 tryPrimitive: 161 withArgs: #(3). clone := Array shallowCopy. Array adoptInstance: clone. clone tryPrimitive: 161 withArgs: #(16). clone tryPrimitive: 160 withArgs: {Array someInstance} self assert: SmallFloat64 identityHash = 3. self assert: (Array someInstance first: 4) = {nil. SmallInteger. Character. SmallFloat64}] Then create a second update map to ensure that that version of Kernel is loaded. I will do this for Squeak immediately. Apologies. P.S. Interestingly enough, it shows what a horrible security hole the debugger primitives tryPrimitive:withArgs: and tryNamedPrimitive:withArgs: are. Cheers, > -- Pavel > _,,,^..^,,,_ best, Eliot

March 8, 2016

Re: [Pharo-dev] strange array instance

by Eliot Miranda

> On Mar 8, 2016, at 2:13 AM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > >> Le 8 mars 2016 Ã 10:57, Guille Polito <guillermopolito(a)gmail.com> a Ã©crit : >> >> It smells like the first page of the class table, yes, but it shouldn't be visible from the image side (as far as I understood) > > Yes, it is the first page of the Spur class table. > It means than #allInstances is able to reach this instance but not #garbageCollect. Eliot is it the desired behavior or does #allInstances need to be updated to hide the class table pages? Ugh, that's a bug. The class table pages should not be visible. Objects in Sour contain class indices, not class pointers. One can arrange that a class is in the class table at more than one index. allInstances searches for objects with a particular class index. So the class table pages should use a "false index" (I call these "class puns"), and hence not show up in allInstances (or allObjects). I'll investigate.

March 8, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50632 Home: https://github.com/pharo-project/pharo-core

March 8, 2016

[pharo-project/pharo-core] ec187b: 50632

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ec187b5b9722b87bb9cf893a00ce2d9c95b5b9ea https://github.com/pharo-project/pharo-core/commit/ec187b5b9722b87bb9cf893a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-08 (Tue, 08 Mar 2016) Changed paths: R Collections-Sequenceable.package/Array.class/instance/private/refersToLiteral_.st R Kernel.package/AdditionalMethodState.class/instance/testing/refersToLiteral_.st R Kernel.package/Behavior.class/instance/testing/isEphemeronClass.st R Kernel.package/Behavior.class/instance/testing/isImmediateClass.st M Kernel.package/CompiledMethod.class/instance/literals/refersToLiteral_.st R Kernel.package/Object.class/instance/pointing to/refersToLiteral_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50631.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50632.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50631.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50632.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50632 16368 refersToLiteral: should (for now) just call hasLiteralThorough: https://pharo.fogbugz.com/f/cases/16368 17768 remove again isEphemeronClass and isImmediateClass https://pharo.fogbugz.com/f/cases/17768 http://files.pharo.org/image/50/50632.zip

March 8, 2016

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Call for action for Roassal

by Johan Fabry

Excellent, thanks a lot! I will take a look at that tomorrow. > On Mar 7, 2016, at 11:34, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi Johan, > > I've just commited RTAnchorConstraint to latest Roassal, see class-side example there. > > I've been using it for my class diagrams where it works quite well, however class diagrams are usually orthogonal-ish, which makes it a bit nicer. > <uml.png> > > The Anchor will avoid intersecting it's own line, and one of the end shapes (it should both but apparently I have a bug there...). > It doesn't look at other lines, however you can specify on which side it should be. > > (You can also put the node label inside the circle with `el @ (RTLabelled new center)` but you probably know that.) > <anchor.png> > â > I have also a global edge labeling layout which produces good placementâ¦ but it's slow as hellâ¦ I need to write a fast flow alogrithmâ¦ > > Also the Anchor currently doesn't work with self-edges. On the other hand Roassal doesn't have self-edges yet so it shouldn't be a problem. :) > > Peter > > > On Mon, Mar 7, 2016 at 2:34 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > > Better late than never :-) (working on the holidays backlog) > > I only have one request: better positioning on labels of nodes and edges. For example see the image: three of the four labels are badly positioned because the bounding box of their text is intersected by one or more edges. > > <Screen Shot 2016-03-07 at 10.31.24.png> > I know that to solve this generally is hard, but for simple cases like this it should be possible. > > Ah, and it should work well with animations and dragging of course ;-) > >> On Feb 24, 2016, at 05:51, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Dear community, >> >> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com <http://agilevisualization.com/> will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >> >> What are the 3 aspects you would like to see improved in Roassal? >> >> You can answer publicly or by sending private messages. >> >> Kind regards, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >> https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> >> > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

March 8, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50631 Home: https://github.com/pharo-project/pharo-core

March 8, 2016

[pharo-project/pharo-core] e8b5c6: 50631

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e8b5c6249e646b6a982b6eda9d21a2d744b49c07 https://github.com/pharo-project/pharo-core/commit/e8b5c6249e646b6a982b6eda… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-08 (Tue, 08 Mar 2016) Changed paths: R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/README.md R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/definition.st R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/instance/utilities/assert_familyName_pointSize_.st R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/instance/utilities/saveStandardSystemFontsDuring_.st M Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsFloatPoint.st M Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsIntegerPoint.st A Graphics-Tests.package/PointTest.class/instance/tests-truncation and roundoff/testIsFloatPoint.st A Kernel.package/Behavior.class/instance/testing/isEphemeronClass.st A Kernel.package/Behavior.class/instance/testing/isImmediateClass.st M Kernel.package/Point.class/instance/converting/asFloatPoint.st M Kernel.package/Point.class/instance/converting/asIntegerPoint.st A Kernel.package/Point.class/instance/testing/isFloatPoint.st M Kernel.package/Point.class/instance/testing/isIntegerPoint.st M Kernel.package/Rectangle.class/instance/rectangle functions/areasOutside_.st M Kernel.package/Rectangle.class/instance/transforming/centeredBeneath_.st M Kernel.package/Rectangle.class/instance/truncation and roundoff/ceiling.st M Kernel.package/Rectangle.class/instance/truncation and roundoff/floor.st M Kernel.package/Rectangle.class/instance/truncation and roundoff/isIntegerRectangle.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50630.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50631.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50630.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50631.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-SessionManager.package/StartupUIManager.class/instance/error handling/handleError_log_.st Log Message: ----------- 50631 17766 StandardSystemFontsTest is either unfinised or obsolete https://pharo.fogbugz.com/f/cases/17766 17736 Growl raise debugger instead of a popup at startup https://pharo.fogbugz.com/f/cases/17736 17758 Rectangle>>#areasOutside: inconsistent return value https://pharo.fogbugz.com/f/cases/17758 17752 Point>>#asFloatPoint and Point>>#asIntegerPoint should not create new instances all the time. Add Point>>#isFloatPoint https://pharo.fogbugz.com/f/cases/17752 http://files.pharo.org/image/50/50631.zip

March 8, 2016

Re: [Pharo-dev] strange array instance

by Guille Polito

But of course it should not be collected :) it is the class table. And the VM uses it as root for the GC AFAIK (check setHiddenRoot:). -------- Original Message -------- >> Le 8 mars 2016 Ã 10:57, Guille Polito <guillermopolito(a)gmail.com> a Ã©crit : >> >> It smells like the first page of the class table, yes, but it shouldn't be visible from the image side (as far as I understood) > Yes, it is the first page of the Spur class table. > It means than #allInstances is able to reach this instance but not #garbageCollect. Eliot is it the desired behavior or does #allInstances need to be updated to hide the class table pages? > >

March 8, 2016