August 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Debug it from browser, menu consistency, merged Inspector
by Janko MivÅ¡ek Aug. 8, 2011

Aug. 8, 2011

Hi guys, I just noticed that there is no 'Debug it' in browser's right-click menu, but it is on Workspace. It would be nice to be there too, and there is a place for it. But not need to add Profile it and Watch it in browser's one. Debug it is important for "through debugger" development style .. :) Second usability suggestion: please put Cut/Copy/Paste/Undo section consistently on the same place, or always on the top, or always somewhere else. Not on the bottom as is in context menu in Workspace while in browser it is on top. Same goes with DoIt/PrintIt/DebugIt block. Third: how is the state with merging Inspector and Explorer? Wasn't there already a nice tree-view Inspector in some older Pharo? Best regards Janko -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

4 4

[Pharo-project] [update 1.4] #14078
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

14078 ----- - add ensureCr for vmmaker compatibility to Transcript -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Growl in Pharo
by StÃ©phane Ducasse Aug. 8, 2011

Aug. 8, 2011

Hi I was brainstorming for an example to illustrate announcements and I wanted to have a Growl feature. So I looked at Snarl from Tony Garnock-Jones and I redesigned a simpler Morph. It could be more generic with better default handled default. I do not understand why the color of the text is ignored but I can not want to spend more time on it now. Apparently the first time the text is read and when the background or the color of the border are set the blue get propagated. :( GrowlMorph openWithLabel: 'The time' contents: (TimeStamp now)) If somebody would like to glue together Growl and the available announcements it would be fun to check. Gofer new squeaksource: 'Growl'; package: 'Growl'; load GrowlMorph openWithLabel: 'The time' contents: (TimeStamp now) Stef Something changed between 14042 and 14077 because I do not have the same alpha for the handle but I do not have the time to check. I do not understand why round corners are not taken into account.

2 4

Re: [Pharo-project] Releasing 1.3: TODOs
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

On Aug 8, 2011, at 10:39 AM, Tudor Girba wrote: > Great! As soon as you release 1.3, we will release Moose 4.6 based on it, so I hope it will be soon :) > It will be this week... maybe tomorrow? I only need to figure out the VM story... Marcus > Cheers, > Doru > > > On 8 Aug 2011, at 08:51, Marcus Denker wrote: > >> TODOs to get 1.3 released: >> >> 1) store a 1.3Core on gforge build with an old vm. Double check it works with old VM. >> >> It is likely that, again, I did not think about this for some of the images on gforge... it might >> mean that we need to re-generate images and re-build the Full image based on that. >> I should again stress that this situation is sucking the live out of people (at least me) and >> we need to *simplify* our story *considerably*. This is *not* sustainable like this. >> >> 2) store a 1.3 on gforge (take form Hudson). double check with old vm >> >> 3) update the one-click with reasonable Vms. Which ones? I am confused wrt to VMs, so I need help here. >> >> 4) update the website. >> - especially regarding VMs >> >> >> For 1.4, we should *really* *really* make sure that we auto-generate the *final* *unchanged* release artefact... >> and *one* *defined* family of VMs, with the one-click (and just one one-click, not two) build from the latest VM. >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > -- > www.tudorgirba.com > > "No matter how many recipes we know, we still value a chef." > > > > > > > -- Marcus Denker -- http://marcusdenker.de

3 2

[Pharo-project] Writing an object graph into a no-sql database [WAS] Re: [Seaside] ESUG SummerTalk - Fuel, binary object serializer
by Mariano Martinez Peck Aug. 8, 2011

Aug. 8, 2011

> > I am looking at using Riak ( http://wiki.basho.com/ ) with Pharo. When > storing a âbusiness objectâ you have two choices: > > - Store a binary BLOB representing your object graph. > - Store the object graph as JSON data. > > The last option essentially means you must do something similar to OR > mapping, so I would prefer the first option. With Riak, you will soon > be able to store additional indexed properties, which you later will > be able to query. So you store your whole business object as a BLOB, > together with those properties you need to query. > > Hi guys. Sorry to come back with this old post, but now I am interested ;) Right now, I have a requirement where I need to write a graph into a file. I am using Fuel for that. Each graph, has its own file. In the image side I just store the filename, When I need to load it it reads such file and materialize it with Fuel. I was thinking going a step forward and use a key/value (a.k.a no-sql) database. With Fuel, I can take a graph, and serialize directly into a ByteArray, hence I can take a graph to swap, I assign an ID, and and save it into the database. In the image side, I keep that ID. Then, when needed, I search it in the database and then after with that ByteArray found, I materialize it with Fuel. So...first question is, do you think that could be faster/better than directly writing into a file as I am doing now? Now, which are the available Pharo wrappers for no-sql databases that let me do that? I would appreciate any link or documentation about them. What do I need to use such databases from Pharo? FFI and a library installed in my machine? are there binaries for Mac OS? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

4 4

[Pharo-project] Releasing 1.3: TODOs
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

TODOs to get 1.3 released: 1) store a 1.3Core on gforge build with an old vm. Double check it works with old VM. It is likely that, again, I did not think about this for some of the images on gforge... it might mean that we need to re-generate images and re-build the Full image based on that. I should again stress that this situation is sucking the live out of people (at least me) and we need to *simplify* our story *considerably*. This is *not* sustainable like this. 2) store a 1.3 on gforge (take form Hudson). double check with old vm 3) update the one-click with reasonable Vms. Which ones? I am confused wrt to VMs, so I need help here. 4) update the website. - especially regarding VMs For 1.4, we should *really* *really* make sure that we auto-generate the *final* *unchanged* release artefact... and *one* *defined* family of VMs, with the one-click (and just one one-click, not two) build from the latest VM. Marcus -- Marcus Denker -- http://marcusdenker.de

2 2

[Pharo-project] Thoughts about software refactoring
by StÃ©phane Ducasse Aug. 8, 2011

Aug. 8, 2011

Hi guys What is cool with software refactoring is that we have tests, and even if we break it to death, them we can undo... This morning I was trying to open wood boxes of my old bow window and this is another story. No debugger, no test, no undo. Just think before, try to guess right and do it slowly to avoid to break for real. Stef

3 2

[Pharo-project] [ANN] Presenty UI framework
by Denis Kudriashov Aug. 8, 2011

Aug. 8, 2011

Hello. I am glad to announce Presenty - new user interface framework for Pharo (with MIT license). I publish my current version on http://www.squeaksource.com/Presenty.htmland write first articles about Presenty on blog http://smalltalk-presenty.blogspot.com There are some problems with current implementation. But step-by-step I fix it and improved it. And I have many ideas about Presenty future. Main goal of Presenty is platform independent programming of user interface: Pharo can run your application on any OS. Presenty can present your application on any OS. With Presenty you can easilly write UI applications which can be configured for all "user" platforms: mobile phones, tablets, desktop computers and others. Presenty is based on Morphic and I think morphic can simulate every platform appearance and behavior. And I think simulation is easest then supporting native backends. I have two commercial applications for my company which based on Presenty. So it is really usable although many common UI stuff absent and some bugs exist. One is touch screen oriented application (for basic computer, not mobile device) and second is basic desktop application (driven by mouse and keyboard). It is different applications for different kind of users but its use same components of tasks and domain objects. So when we implement new logic of user interraction it appears on both applications but user takes it with different look and feel. There is problem with speed of presenty application. For my case cog performance solve it. So I don't worry about it. But problem relates to #veryDeepCopy method of morphs. It is very very slow. This method is used for view creation from prototype morph object. I have fix with special methods for copy prototype morph. But I don't use it yet. Now I prepare presentation for ESUG. So I can take into account of all your comments and questions. Best regards, Denis

3 11

[Pharo-project] Hudson build became unstable: Pharo 1.3 #249
by marcus.denker＠inria.fr Aug. 7, 2011

Aug. 7, 2011

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/249/>

1 1

[Pharo-project] cleaning/completing ConfigurationOfPetitParser
by Damien Pollet Aug. 7, 2011

Aug. 7, 2011

Hi, I'm looking at ConfigurationOfPetitParser and wondering if #minimal: and #default: are really needed. Shouldn't those be groups in the baseline, or symbolicVersions loading subsets of packages ? Also, there are dependencies missing. For instance PetitSmalltalk depends on AST-Core, and IMHO this is the responsibility of ConfigurationOfPetitParser to declare that, even if PetitSmalltalk is not loaded by a ConfigurationOfPetitParser load. Also, why are there less class methods than on other ConfigurationOf... ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 3