- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fuel - a fast object deployment tool
by Martin Dias Dec. 10, 2010

Dec. 10, 2010

Hi Colin Another thing to consider are the clusters. I think they are good because they avoid a lot of overhead. Following the example used in the slides, for serializing N rectangles, it writes: - in vertexes section: 'Rectangle' 'origin' 'corner' N - in edges section: 2*N indexes (references to the origin and corner points) Without clustering, I think each rectangle stored should have some header to say that its an instance of Rectangle. Martin On Fri, Dec 10, 2010 at 11:03 AM, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > >> Hi Martin, >> >> Looks very interesting. Reading the material you posted, the question >> that jumps out at me is this: from the benchmarks, it's clear that >> materializing is faster than serializing, but it's not clear why. How >> does separating the nodes from the edges of the object graph make >> materializing faster? >> >> Thanks, >> >> Colin > > Hi! > > Separate the nodes from the edges of the object permit during the > serialization > to pass only one time on the byte code. > So first we pass on the node so we recreate the objects/nodes and second > when > we pass on the edges we recreate the links between the objects. > > I hope I answered your question :) > > Tristan >

1 0

[Pharo-project] Why was the old Editor Functionality Removed?
by Lukas Renggli Dec. 10, 2010

Dec. 10, 2010

I wonder why the old editor functionality was removed instead of being deprecated until the next release like this is normally done? It is extremely difficult to get any GUI related stuff ported, because the packages cannot simply be loaded. One has to fix part of the package in the old image, and part of the package in the new image. One wrong method, and everything blows up irreversibly. I spent the whole afternoon trying to get OB, Shout and eCompletion working. OB and Shout kind of work (thanks to the preparations in the PharoTaskForces), but they are still subtly broken. eCompletion is very hard to get working. The idea of making completion part of the ToolSet doesn't help at all, the patch now just moved from Morphic to the StandardToolSet class. I am frustrated and give up, I revert back to Pharo 1.1. Lukas -- Lukas Renggli www.lukas-renggli.ch

8 15

[Pharo-project] about cloud in pharo
by stephane ducasse Dec. 10, 2010

Dec. 10, 2010

Hi guys When I see that. I would really like to see how we can create something around the cloud. We have a lot of assets. Does anybody have some interest bootstrapping a business around that? Today http://heroku.com/ were bought by Salesforce for over 200 million (http://techcrunch.com/2010/12/08/breaking-salesforce-buys-heroku-for-212-mi…) Stef

9 10

[Pharo-project] Cog+NativeBoost @ Mac OS
by Igor Stasenko Dec. 10, 2010

Dec. 10, 2010

Hello, since recently i got access to macs, i were finally able to add NB support for Mac OS. I built the Cog VM with NativeBoost plugin , which you can download at NativeBoost project page [1]. At image side you just load NativeBoost-Installer package and then evaluate: NBInstaller install. Should i also build Squeak VM with NB plugin, or i could stick with Cog? :) [1] http://code.google.com/p/nativeboost/downloads/list -- Best regards, Igor Stasenko AKA sig.

3 6

[Pharo-project] Some Tests failing in 1.2
by Luc Fabresse Dec. 10, 2010

Dec. 10, 2010

Hi all, 6 tests in SystemNavigationTest and SystemNavigationOnNewlyCreatedEnvironementTest are failing in 1.2 This is because of the introduction of SourcedMethodReference. I already speak about this problem here: http://forum.world.st/About-SourcedMethodReference-td3035187.html SourcedMethodReference>>= must not be based on identity (==) because it prevents to have multiple SourcedMethodReference pointing to the same CompiledMethod. And we need that because each tools will use different SourcedMethodReference. IMHO, SourcedMethodReference are just proxies and we don't care of their identity. I made these 6 tests pass by: -replacing MethodReference by SourcedMethodReference in SystemNavigationTest and al... -modifying the equality method of SourcedMethodReference: SourcedMethodReference>>= anotherMethodReference ^ (super = anotherMethodReference) and: [ (self timeStamp = self timeStamp) and: [ self sourceCode = self sourceCode ]] I have no idea of the impact of this change for the SourcedMethodReference stuff point of view. Written here: http://code.google.com/p/pharo/issues/detail?id=3398 #Luc

1 0

Re: [Pharo-project] Fuel - a fast object deployment tool
by tr.bourgois Dec. 10, 2010

Dec. 10, 2010

Hi Martin, Looks very interesting. Reading the material you posted, the question that jumps out at me is this: from the benchmarks, it's clear that materializing is faster than serializing, but it's not clear why. How does separating the nodes from the edges of the object graph make materializing faster? Thanks, Colin Hi! Separate the nodes from the edges of the object permit during the serialization to pass only one time on the byte code. So first we pass on the node so we recreate the objects/nodes and second when we pass on the edges we recreate the links between the objects. I hope I answered your question :) Tristan Une messagerie gratuite, garantie Ã vie et des services en plus, Ã§a vous tente ? Je crÃ©e ma boÃ®te mail www.laposte.net

1 0

[Pharo-project] [update 1.2] #12274
by Marcus Denker Dec. 10, 2010

Dec. 10, 2010

12274 ----- Issue 3394: Adopt disappeared from Monticello Browser Issue 3395: Capitalization of Author -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3395 in pharo: Capitalization of Author
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Status: Accepted Owner: ---- Labels: Difficulty-Easy Type-ToDo Milestone-1.2 New issue 3395 by renggli: Capitalization of Author http://code.google.com/p/pharo/issues/detail?id=3395 The author initials are automatically capitalized, this is extremely annoying! Not everybody is following the PharoCore people conventions.

1 3

[Pharo-project] Issue 3394 in pharo: Adopt disappeared from Monticello Browser
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Status: Accepted Owner: ---- Labels: Milestone-1.2 Difficulty-Easy New issue 3394 by renggli: Adopt disappeared from Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3394 The adopt button disappeared, which is a sensible change. The adopt functionality should still be available from the menu, because it is a common operation when integrating.

1 3

[Pharo-project] Time lapses
by Diogenes Moreira Dec. 9, 2010

Dec. 9, 2010

may not be more in the core image of Pharo time lapses message, by example year or month??? with the follow code i get MNU SmallInteger>>year "aDate - otherDate = 1 year." If not, where I could find. Best Regards

2 1