April 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Mondrian: present and future

by Mariano Martinez Peck

On Thu, Apr 1, 2010 at 11:15 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi All, > > Just to give some news about Mondrian. Together with colleagues from Bern, > Lille and Santiago, I have been working on this visualization engine for > quite some times. Although it contains some important bugs (e.g., popupView) > it is fairly stable and usable. The current version is 2.0-beta.7. > > Mondrian is slowly maturing. A short summary of the discussion I had with > Doru and StÃ©phane today. > Some of the features I would like to see in for Version 3.0 are: > - scalable spring layout (also known as force based layout): this is a > very simple and nice layout that produces amazing results > - add layers: embedding a rendering or a part of it in a layer. Layers > could then be iteratively activated and desactivared. The idea is to enable > the construction of scripts in a very iterative and incremental way. > - having a small core embeddable in your application > I would really love to have this. A very small runtime kernel for Mondrian. For example, I would like to add the "UML Diagram" to OB but withoput needing to load all Mondrian in the image. Cheers mariano

April 1, 2010

[Pharo-project] Mondrian: present and future

by Alexandre Bergel

Hi All, Just to give some news about Mondrian. Together with colleagues from Bern, Lille and Santiago, I have been working on this visualization engine for quite some times. Although it contains some important bugs (e.g., popupView) it is fairly stable and usable. The current version is 2.0-beta.7. Mondrian is slowly maturing. A short summary of the discussion I had with Doru and StÃ©phane today. Some of the features I would like to see in for Version 3.0 are: - scalable spring layout (also known as force based layout): this is a very simple and nice layout that produces amazing results - add layers: embedding a rendering or a part of it in a layer. Layers could then be iteratively activated and desactivared. The idea is to enable the construction of scripts in a very iterative and incremental way. - having a small core embeddable in your application - making Mondrian load graphiz scripts - having a better help system (Ã la ProfStef) - dedicated chapter for Pharo By Example Volume 2 - exporting as PDF - anti-aliasing This probably will not happen today or tomorrow, but I just feel necessary to share this roadmap with you. Some other features are wanted. Using Rome is one. Open GL is another. There are plenty of rooms for a very cool visualization engine. Probably during the holiday period I will consolidate the current version by fixing remaining bugs and produce 2.0. Bug tracker: http://code.google.com/p/moose-technology/ Web page: http://www.moosetechnology.org/tools/mondrian Let's render our dream! Cheers, Alexandre NB: sorry for this cross mailing list post. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 1, 2010

Re: [Pharo-project] serializing a class

by Schwab,Wilhelm K

Stef, Dolphin's solution is to use proxies. Rather than serializing the class itself, one might prefer to serialize a proxy that knows enough to find the appropriate object once it "wakes up" in the new image. In the case of a class, it should be enough to know the name, so the proxy would have that one aspect and it would resolve itself by looking for it in the system dictionary. There is a little more to it, but that is the basic idea. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Thursday, April 01, 2010 3:03 PM To: Pharo-project(a)lists.gforge.inria.fr Development Subject: [Pharo-project] serializing a class Hi I would like to do a little experiment. I need to save a class (not the instances) in a binary format and I was wondering if somebody got experience with that. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 1, 2010

Re: [Pharo-project] [Moose-dev] Re: Mondrian: present and future

by Tudor Girba

>> Hi All, >> >> Just to give some news about Mondrian. Together with colleagues >> from Bern, Lille and Santiago, I have been working on this >> visualization engine for quite some times. Although it contains >> some important bugs (e.g., popupView) it is fairly stable and >> usable. The current version is 2.0-beta.7. >> >> Mondrian is slowly maturing. A short summary of the discussion I >> had with Doru and StÃ©phane today. >> Some of the features I would like to see in for Version 3.0 are: >> - scalable spring layout (also known as force based layout): this >> is a very simple and nice layout that produces amazing results >> - add layers: embedding a rendering or a part of it in a layer. >> Layers could then be iteratively activated and desactivared. The >> idea is to enable the construction of scripts in a very iterative >> and incremental way. > this is a nice idea Thanks :) >> - having a small core embeddable in your application >> - making Mondrian load graphiz scripts >> - having a better help system (Ã la ProfStef) >> - dedicated chapter for Pharo By Example Volume 2 >> - exporting as PDF >> - anti-aliasing >> >> This probably will not happen today or tomorrow, but I just feel >> necessary to share this roadmap with you. Some other features are >> wanted. Using Rome is one. Open GL is another. There are plenty of >> rooms for a very cool visualization engine. >> >> Probably during the holiday period I will consolidate the current >> version by fixing remaining bugs and produce 2.0. >> >> Bug tracker: http://code.google.com/p/moose-technology/ >> Web page: http://www.moosetechnology.org/tools/mondrian >> >> Let's render our dream! > > :) > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

April 1, 2010

Re: [Pharo-project] Mondrian: present and future

by StÃ©phane Ducasse

On Apr 1, 2010, at 11:15 PM, Alexandre Bergel wrote: > Hi All, > > Just to give some news about Mondrian. Together with colleagues from Bern, Lille and Santiago, I have been working on this visualization engine for quite some times. Although it contains some important bugs (e.g., popupView) it is fairly stable and usable. The current version is 2.0-beta.7. > > Mondrian is slowly maturing. A short summary of the discussion I had with Doru and StÃ©phane today. > Some of the features I would like to see in for Version 3.0 are: > - scalable spring layout (also known as force based layout): this is a very simple and nice layout that produces amazing results > - add layers: embedding a rendering or a part of it in a layer. Layers could then be iteratively activated and desactivared. The idea is to enable the construction of scripts in a very iterative and incremental way. this is a nice idea > - having a small core embeddable in your application > - making Mondrian load graphiz scripts > - having a better help system (Ã la ProfStef) > - dedicated chapter for Pharo By Example Volume 2 > - exporting as PDF > - anti-aliasing > > This probably will not happen today or tomorrow, but I just feel necessary to share this roadmap with you. Some other features are wanted. Using Rome is one. Open GL is another. There are plenty of rooms for a very cool visualization engine. > > Probably during the holiday period I will consolidate the current version by fixing remaining bugs and produce 2.0. > > Bug tracker: http://code.google.com/p/moose-technology/ > Web page: http://www.moosetechnology.org/tools/mondrian > > Let's render our dream! :)

April 1, 2010

[Pharo-project] about Compiled method and trailer

by StÃ©phane Ducasse

Hi CompiledMethod newBytes: size trailerBytes: CompiledMethodTrailer empty nArgs: nbArgs nTemps: nbTmp nStack: 0 nLits: nbLit primitive: 0. is is the equivalent as the old? CompiledMethod newBytes: size trailerBytes: #(0 0 0 0) nArgs: nbArgs nTemps: nbTmp nStack: 0 nLits: nbLit primitive: 0. Thanks. Stef

April 1, 2010

[Pharo-project] Cassandra database and Pharo

by Miguel Enrique CobÃ¡ Martinez

If you're interested in NoSQL databases in general and Cassandra in particular, I wrote a little tutorial for accessing a Cassandra server from Pharo. http://miguel.leugim.com.mx/index.php/2010/03/31/accessing-cassandra-from-p… Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

April 1, 2010

Re: [Pharo-project] Registering a tool in the world menu

by Marcus Denker

On Apr 1, 2010, at 6:26 PM, HernÃ¡n Morales Durand wrote: > > > IIRC in Squeak people is using the #registerOpenCommand: message, is > there a standard way to avoid the platform or version specific > Deprecation Warnings in Pharo? (please see the attachment) > > I do not want to check > > Smalltalk version isSqueak ifTrue: [ ... ] ifFalse: [ Smalltalk > version isPharo ifFalse: [ ... isCuis ] etc. We could remove the deprecation for now and just do nothing. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010

[Pharo-project] serializing a class

by StÃ©phane Ducasse

Hi I would like to do a little experiment. I need to save a class (not the instances) in a binary format and I was wondering if somebody got experience with that. Stef

April 1, 2010

Re: [Pharo-project] Registering a tool in the world menu

by HernÃ¡n Morales Durand

2010/3/31 Alain Plantec <alain.plantec(a)free.fr>: > Marcus Denker a Ã©crit : >> >> On Mar 31, 2010, at 8:28 AM, HernÃ¡n Morales Durand wrote: >> >> >>> >>> Hi list, >>> Â I'm using PharoCore 1.1 #11301. Now I want to adapt some tools to >>> use the new menu registration mechanism. When I evaluate: >>> >>> menuCommandOn: aBuilder >>> Â Â Â Â <worldMenu> >>> Â Â Â Â (aBuilder item: #'Dependency Browser') >>> Â Â Â Â Â Â Â Â parent: #Tools; >>> Â Â Â Â Â Â Â Â action:[self open]; >>> Â Â Â Â Â Â Â Â icon: Â UITheme current windowMenuForm. >>> >>> the world menu is modified including only the Dependency Browser item >>> and all remaining items were removed. Did I miss something? >>> >>> >> >> You need to execute >> >> Â Â Â Â World resetWorldMenu >> >> This gathers all the methods with the worldMenu tag and executes them. >> > > normally you don't need to execute 'World resetWorldMenu'. > The world menu is automatically rebuilt each time > a method containing a <worldMenu> pragma is compiled. > Alain > Thank you Alain and Marcus. I have not access to the imagen with the problem now, but it should be weird because I cannot reproduce the bug again. IIRC in Squeak people is using the #registerOpenCommand: message, is there a standard way to avoid the platform or version specific Deprecation Warnings in Pharo? (please see the attachment) I do not want to check Smalltalk version isSqueak ifTrue: [ ... ] ifFalse: [ Smalltalk version isPharo ifFalse: [ ... isCuis ] etc. Cheers, HernÃ¡n

April 1, 2010