March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] looking for media to illustrate one important idea :)

by Esteban A. Maringolo

2013/3/25 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > or do you know how Egyptians created their obelisks? Hundreds of them > were sitting in a pit and were beating again and again with small > stones for moths and years, millimetre by millimetre I don't think that helps in the methaphor of a lot of people making small contributions to produce a greater outcome because... egyptians were slaves who died doing those obelisks. Are Igor, Camillo, Esteban, Sven, etc. going to die? I hope not. :) I don't know why Stephane needs that, but I understood what he wants to communicate. I'm trying to imagine something that represents that and then look for a picture of it online. Stephane: Does it need to be shown as a picture? It can be in words as long as it takes less than 1000 words... :) Regards, Esteban A. Maringolo

March 25, 2013

Re: [Pharo-project] looking for media to illustrate one important idea :)

by Pavel Krivanek

http://www.youtube.com/watch?v=FtqV58CbhXw or do you know how Egyptians created their obelisks? Hundreds of them were sitting in a pit and were beating again and again with small stones for moths and years, millimetre by millimetre http://www.pbs.org/wgbh/nova/egypt/dispatches/images/990316n02.jpeg http://upload.wikimedia.org/wikipedia/commons/0/03/Aswan_obelisk_-_how_it_w… http://bepic.net/public_files/pics/20111006190413.jpg -- Pavel On Mon, Mar 25, 2013 at 6:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I'm looking for a video, slidesâ¦ to convey one key point: > making pharo requires thousands of tiny, annoying, tedious tasks (like tagging a bug, checking a bug in the vm, â¦). > > I would like to be able to explain that these steps are not happening magically, but that some guys > are doing them and that we all benefit from them. So if you have an idea of media that I could use. > I was thinking for example to all the steps that you should do to verify your equipment before a long trip in > moutain but this is not really good enough. > > Stef > > > >

March 25, 2013

Re: [Pharo-project] Spec documentation and examples

by stephane ducasse

thnkas daniela we should update the spec tutorial and turn it into a chapter. Probably during the 14 hours train to the pharo conf we will give a try to fix it. Stef > Hi: > > I'm starting to develop with pharo using spec. I really like the spec approach. I already review some examples that come with spec but I only get UIs with a bad aspect by following the examples. > I would like to find more documentation and examples about how to write the defaultSpec. Documentation about how to use the spec structure to develop a nice and usable UI. > > Thanks in advance, > Daniela Meneses

March 25, 2013

Re: [Pharo-project] Roassal is on SmalltalkHub

by stephane ducasse

thanks alex! On Mar 25, 2013, at 5:06 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > We've just completed the migration of Roassal to SmalltalkHub. > > -=-=-=-=-=-=-=-=-=-=-=-= > Gofer new > smalltalkhubUser: 'ObjectProfile' project: 'Roassal'; > package: 'ConfigurationOfRoassal'; > load. > (Smalltalk at: #ConfigurationOfRoassal) project lastVersion load. > -=-=-=-=-=-=-=-=-=-=-=-= > > Interestingly, I have a folder weighting 152Mb of all the versions of Roassal. Hard to believe it weights so much :-) space is so cheap that it is not worth to think about delta :) > > Doru, we haven't changed yet the #development tag. I would like to know first whether there is an impact on the way we develop (especially with Versionner). > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

March 25, 2013

Re: [Pharo-project] [3.0] 9 issues need reviews

by Marcus Denker

On Mar 24, 2013, at 7:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Even with the integrations of saturday, there was a lot done that need > attention: > > > https://pharo.fogbugz.com/f/filters/22/3-0-Integration > > 6 are ready to be integrated, > 9 need a code review. > now 15 issues need a review. Marcus

March 25, 2013

Re: [Pharo-project] looking for media to illustrate one important idea :)

by Marcus Denker

On Mar 25, 2013, at 6:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I'm looking for a video, slidesâ¦ to convey one key point: > making pharo requires thousands of tiny, annoying, tedious tasks (like tagging a bug, checking a bug in the vm, â¦). > http://en.wikipedia.org/wiki/HeinzelmÃ¤nnchen ;-) Marcus

March 25, 2013

Re: [Pharo-project] Reproducible VM crash when loading FFI

by Eliot Miranda

Hi Guille, thanks for this. The problem is that Pharo's recreateSpecialObjectsArray uses newCompactClassesArray to recreate the compact classes array and on Cog that is not supported. Cog caches the compactClassesArray (specialObjectsArray at: 29) in every jitted method prolog to reduce the time taken to derive the receiver's class in message lookup. The Pharo 2.0 code for recreating the specialObjectsArray can therefore create a dangling pointer where the only reference to the old compactClassesArray is in machine code, and the machine code GC doesn't cope with there being roots in machine code. Note that Cog also caches the characterTable and class SmallInteger in machine code. There are two solutions to this. One would be to reuse the compactClassesArray (my recommendation). So that recreateSpecialObjectsArray looks like ... "An array of the 255 Characters in ascii order. Cog inlines table into machine code at: prim so do not regenerate it." newArray at: 25 put: Character characterTable. ... "A 32-element array with up to 32 classes that have compact instances. Cog inlines table into machine code class lookup so do not regenerate it." newArray at: 29 put: self compactClassesArray. ... where compactClassesArray, like Character characterTable, answers the existing object. The second solution (rather hackish) is to void all machine code on installing the new specialObjectsArray. e.g. recreateSpecialObjectsArray "Smalltalk recreateSpecialObjectsArray" "To external package developers: **** DO NOT OVERRIDE THIS METHOD. ***** If you are writing a plugin and need additional special object(s) for your own use, use addGCRoot() function and use own, separate special objects registry " "The Special Objects Array is an array of objects used by the Squeak virtual machine. Its contents are critical and accesses to it by the VM are unchecked, so don't even think of playing here unless you know what you are doing." "Replace the interpreter's reference in one atomic operation. Void machine code to avoid crashing Cog." | newSpecialObjectsArray | newSpecialObjectsArray := self newSpecialObjectsArray. self specialObjectsArray becomeForward: newSpecialObjectsArray. Smalltalk vm voidCogVMState this is my fault for not ensuring recreateSpecialObjectsArray was properly commented. I had commented the inlining of Character table, but not the inlining of the CompactClasses array. Apologies. HTH, Eliot On Sat, Mar 23, 2013 at 10:19 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Hi! > > In my quest to crash the vm, i've found an ugly common case :(. > I am trying to port the opendbx driver to 2.0, but I'm getting vm crashes > when my configuration loads FFI :(. I updated my configuration to load > version 1.7 of FFI (which I assume is the latest). > > I tried to do it in Pharo 2.0 with latest pharovm, and with eliot's Cog > 2701 from his website, failing in both cases. > The snippet of code that gets a sistematic crash is: > > Gofer it > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; > package: 'ConfigurationOfOpenDBXDriver'; > load. > ((Smalltalk at: #ConfigurationOfOpenDBXDriver) project version:#stable) > load > > > This snippet crashes always with a segmentation fault (at least the > fifteen times i tried :), with several different output in the console... > > Surprisingly, if I load FFI alone and not from the OpenDBXDriver > configuration, it loads well... :/ > > So I'm deferring the OpenDBX port a bit longer :( > > Thanks! > Guille > -- best, Eliot

March 25, 2013

[Pharo-project] looking for media to illustrate one important idea :)

by StÃ©phane Ducasse

Hi guys I'm looking for a video, slidesâ¦ to convey one key point: making pharo requires thousands of tiny, annoying, tedious tasks (like tagging a bug, checking a bug in the vm, â¦). I would like to be able to explain that these steps are not happening magically, but that some guys are doing them and that we all benefit from them. So if you have an idea of media that I could use. I was thinking for example to all the steps that you should do to verify your equipment before a long trip in moutain but this is not really good enough. Stef

March 25, 2013

Re: [Pharo-project] Spec documentation and examples

by ClÃ©ment Bera

Hello, I have no documentation but examples. Basically either : - you choose to write the default spec with row and columns, you can precise height or row of some elements. With this method it is easier to get what you want but quite slow sometimes. ex : (Inspector UI) defaultSpec <spec> ^ SpecLayout composed newColumn: [:c | c newRow: [:row | row add: #list width: 135; add: #description ]; newRow: [:row2 | row2 add: #text ] height: 75 ]; yourself - write down directly the position and size of elements ex : (debugger UI) defaultSpec <spec: #default> ^ SpecLayout composed add: #contextStackList origin: 0@0 corner: 1(a)0.30; add: #debuggerToolBar origin: 0(a)0.30 corner: 1(a)0.30 offsetOrigin: 0(a)(-12.5) offsetCorner: 0(a)(12.5); add: #currentMethodText origin: 0(a)0.30 corner: 1(a)0.70 offsetOrigin: 0(a)12.5offsetCorner: 0@0 ; add: #receiverInspector origin: 0(a)0.70 corner: 0.5@1 offsetOrigin: 0@4offsetCorner: 0@0 ; add: #contextVariableInspector origin: 0.5(a)0.70 corner: 1@1 offsetOrigin: 4@4 offsetCorner: 0@0; yourself The elements (for example #contextStackList) have to be both instance variables of the object and be initialized in initializedWidgets. ex : initializeWidgets self instantiateModels: #( contextStackList ListComposableModel debuggerToolBar DebuggerToolBar currentMethodText TextModel receiverInspector EyeInspector contextVariableInspector EyeInspector). You can see the example I showed you on smalltalkhub : user: ClementBera project: eye class: EyeInspector ex: 'Class ogle' or user: mate project: AST-interpreter Class: ASTDebuggerUI ex: run ASTDebuggerTest>>#testAsSymbol I hope I was able to help you, Clement 2013/3/25 Daniela Meneses <daniela11290(a)gmail.com> > Hi: > > I'm starting to develop with pharo using spec. I really like the spec > approach. I already review some examples that come with spec but I only get > UIs with a bad aspect by following the examples. > I would like to find more documentation and examples about how to write > the defaultSpec. Documentation about how to use the spec structure to > develop a nice and usable UI. > > Thanks in advance, > Daniela Meneses >

March 25, 2013

Re: [Pharo-project] NB additions

by Esteban Lorenzano

this is a consequence on how we do the integration: by merging packages (to prevent ugly overrides)... so, each time I integrate a change, it creates a new monticello package, who is allocated on the Pharo20 repository. It does not matters if the resulting package is equal to the original one (in fact, that what should happen most of the time)... but yes, version number and commiter name will change. Esteban On Mar 25, 2013, at 4:56 PM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > Pharo 2.0 has "NativeBoost-Core-EstebanLorenzano.116" which is in > http://ss3.gemstone.com/ss/Pharo20 since NB is now in Pharo 2.0 > > The same version is not in the old squeaksource/NativeBoost repo > and also not in the new SmalltalkHub native boost project. > > When having additions to NB where should I place them? > > >

March 25, 2013