Hi!
Here are some links that I found via twitter:
- Journalism in the age of data: http://datajournalism.stanford.edu/
I like chapter 3, titled: Telling "Data Stories". I think some of you may like the title
One of the videos gives the following paper: "Narrative Visualization: Telling Stories with Data" : http://vis.stanford.edu/files/2010-Narrative-InfoVis.pdf
Chapter 7 gives a number of web-tools to visualize data
- How to build good graphical DSLs?
http://www.metacase.com/blogs/stevek/blogView?showComments=true&entry=34757…
Nothing ground bracking in my opinion. However, it gives some elementary references that are useful for me (e.g., "Visual-Semantic Congruence", "Perceptual Immediacy", "Mimetic Symbols", "Visual Monosyllabism", "Visual Saturation", "Principle of Cognitive Fit"
- Data-Driven Documents:
http://mbostock.github.com/d3/
It gives a nice javascript library to do exciting 8 visualizations
It would be gorgeous to have a Moose exporter for this libraries
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Begin forwarded message:
> From: "Fron, Annick" <afron(a)cincom.com>
> Date: March 1, 2011 2:31:03 PM GMT+01:00
> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Subject: RE: SCG
>
> Y a –til une limite au nombre de fichiers ?
>
>
>
> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> Sent: mardi 1 mars 2011 13:56
> To: Moose-related development
> Cc: Fron, Annick
> Subject: Fwd: SCG
>
> can somebody try to help annik
> apparently moose does not work on windows.
>
>
> Je n'ai pas trop le temps de m'abonner à la liste et bla bla
>
> En gros j'ai mis mon app sous d:\apps et il pense être sous mon root directory c'est-à-dire :
> C:\users etc....
> En plus sous Windows 7 le home directory n'est plus sous settings mais sous users ...
> Donc il faut au moins changer les properties du .link
>
>
>
> Begin forwarded message:
>
>
> From: "Fron, Annick" <afron(a)cincom.com>
> Date: March 1, 2011 1:50:15 PM GMT+01:00
> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Subject: RE: SCG
>
>
> J'obtiens ceci , et en plus pas moyen de trouver la commande pour lancer Moose
>
>
>
> -----Original Message-----
> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> Sent: mardi 1 mars 2011 13:41
> To: Fron, Annick
> Subject: Re: SCG
>
>
> > Non pas sous Windaube
>
> bizarre est ce que tu peux remonter cela a la moose-dev car c'est le meme setup que seaside.
> la one-clique contient 3 vms
>
> Stef
>
> >
> >
> > -----Original Message-----
> > From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> > Sent: mardi 1 mars 2011 13:34
> > To: Fron, Annick
> > Subject: Re: SCG
> >
> >
> > On Mar 1, 2011, at 1:25 PM, Fron, Annick wrote:
> >
> >> Ben il faudrait dire de downloader pharo pour moose
> >
> > non :)
> > car c'est deja dans le bundle moose.
> >
> > tu cliques
> > dlown
> > dezippe
> > et click et ca marche.
> >
> > Stef
> >
> >>
> >> -----Original Message-----
> >> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> >> Sent: mardi 1 mars 2011 13:25
> >> To: Fron, Annick
> >> Subject: Re: SCG
> >>
> >> utilise la one click image sur le site.
> >> Tu dls, cliques et cela marche.
> >>
> >> Squeak n'est pas pharo!!!
> >> Pharo n'est pas squeak!!!
> >>
> >> Sef
> >>
> >> On Mar 1, 2011, at 1:23 PM, Fron, Annick wrote:
> >>
> >>> Faut il charger pharo ou squeak ? Le site ne le dit pas
> >>>
> >>> -----Original Message-----
> >>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> >>> Sent: mardi 1 mars 2011 12:51
> >>> To: Fron, Annick
> >>> Subject: Re: SCG
> >>>
> >>>
> >>> On Mar 1, 2011, at 10:46 AM, Fron, Annick wrote:
> >>>
> >>>> Bonjour Stephane,
> >>>>
> >>>> Désolée de ne pas être plus réactive pour la compil, mais souvent sous-traiter demande autant de boulot que faire ...
> >>>> Par contre je bosse pour Cincom sur un portage de C vers Stk, et je ne suis plus au fait des outils SCG utilisables : CodeCrawler et la clique ...
> >>>>
> >>>> Aurais-tu des pointeurs récents ?
> >>>
> >>> tu veux nos outils :)
> >>> www.moose-technology.org
> >>>
> >>> dans pharo moose on peut analyser du c et creer des cartes maintenant il faut surement adapter cela.
> >>>
> >>>
> >>>>
> >>>> Bonne journée
> >>>> Annick
> >>>
> >>
> >
>
>
Begin forwarded message:
> From: "Fron, Annick" <afron(a)cincom.com>
> Date: March 1, 2011 1:59:21 PM GMT+01:00
> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Subject: RE: SCG
>
> The shortcut to Moose on Windows does not seem to be correct :
> On windows it points to c: \documents and settings\username and assumes the app should be in the home directory, which is seldom the case.
> Besides on windows 7 the home directory is under c: \ users
>
> When you finally launch the image, you get a bug telling you your are missing the sources
> And when you import a file structure from disk D:, it sticks to disk C: ....
>
>
> -----Original Message-----
> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> Sent: mardi 1 mars 2011 13:56
> To: Fron, Annick
> Subject: Re: SCG
>
> donne moi au moins une description en anglais de ce que tu as fait
> sinon j'ai pas de windows sous la main pour tester.
>
> Stef
>
> On Mar 1, 2011, at 1:43 PM, Fron, Annick wrote:
>
>> Je n'ai pas trop le temps de m'abonner à la liste et bla bla
>>
>> En gros j'ai mis mon app sous d:\apps et il pense être sous mon root directory c'est-à-dire :
>> C:\users etc....
>> En plus sous Windows 7 le home directory n'est plus sous settings mais sous users ...
>> Donc il faut au moins changer les properties du .link
>>
>>
>> -----Original Message-----
>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>> Sent: mardi 1 mars 2011 13:41
>> To: Fron, Annick
>> Subject: Re: SCG
>>
>>
>>> Non pas sous Windaube
>>
>> bizarre est ce que tu peux remonter cela a la moose-dev car c'est le meme setup que seaside.
>> la one-clique contient 3 vms
>>
>> Stef
>>
>>>
>>>
>>> -----Original Message-----
>>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>>> Sent: mardi 1 mars 2011 13:34
>>> To: Fron, Annick
>>> Subject: Re: SCG
>>>
>>>
>>> On Mar 1, 2011, at 1:25 PM, Fron, Annick wrote:
>>>
>>>> Ben il faudrait dire de downloader pharo pour moose
>>>
>>> non :)
>>> car c'est deja dans le bundle moose.
>>>
>>> tu cliques
>>> dlown
>>> dezippe
>>> et click et ca marche.
>>>
>>> Stef
>>>
>>>>
>>>> -----Original Message-----
>>>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>>>> Sent: mardi 1 mars 2011 13:25
>>>> To: Fron, Annick
>>>> Subject: Re: SCG
>>>>
>>>> utilise la one click image sur le site.
>>>> Tu dls, cliques et cela marche.
>>>>
>>>> Squeak n'est pas pharo!!!
>>>> Pharo n'est pas squeak!!!
>>>>
>>>> Sef
>>>>
>>>> On Mar 1, 2011, at 1:23 PM, Fron, Annick wrote:
>>>>
>>>>> Faut il charger pharo ou squeak ? Le site ne le dit pas
>>>>>
>>>>> -----Original Message-----
>>>>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>>>>> Sent: mardi 1 mars 2011 12:51
>>>>> To: Fron, Annick
>>>>> Subject: Re: SCG
>>>>>
>>>>>
>>>>> On Mar 1, 2011, at 10:46 AM, Fron, Annick wrote:
>>>>>
>>>>>> Bonjour Stephane,
>>>>>>
>>>>>> Désolée de ne pas être plus réactive pour la compil, mais souvent sous-traiter demande autant de boulot que faire ...
>>>>>> Par contre je bosse pour Cincom sur un portage de C vers Stk, et je ne suis plus au fait des outils SCG utilisables : CodeCrawler et la clique ...
>>>>>>
>>>>>> Aurais-tu des pointeurs récents ?
>>>>>
>>>>> tu veux nos outils :)
>>>>> www.moose-technology.org
>>>>>
>>>>> dans pharo moose on peut analyser du c et creer des cartes maintenant il faut surement adapter cela.
>>>>>
>>>>>
>>>>>>
>>>>>> Bonne journée
>>>>>> Annick
>>>>>
>>>>
>>>
>>
>
Hi,
C import does not come out of the box with Moose, and you have to rely on extra projects to do achieve it.
You have two options.
1. CAnalyzer. This is a plugin that depends on another external project one called srcML. scrML is used from the command line to produce XML files out of the C (not C++) files, and those can be afterwards loaded through the Moose Panel.
Steps:
- download srcML: http://www.sdml.info/projects/srcml/
- run it on your system
- download CAnalyzer by executing:
Gofer new
squeaksource: 'CAnalyzer';
package: 'ConfigurationOfCAnalyzer';
load.
(Smalltalk at: #ConfigurationOfCAnalyzer) perform: #loadDefault.
- load the XMLs through Moose Panel
2. The other option is to use inFusion:
http://www.moosetechnology.org/docs/faq/importCandCPPWithinFusion
Cheers,
Doru
On 1 Mar 2011, at 14:32, Fron, Annick wrote:
> Thanks
>
> Where is the tutorial to import C code ?
> Annick
>
> From: Tudor Girba [mailto:tudor.girba@gmail.com]
> Sent: mardi 1 mars 2011 14:32
> To: Fron, Annick
> Cc: Moose-dev Moose Dev
> Subject: Fwd: Moose-dev post from stephane.ducasse(a)inria.fr requires approval
>
> Hi,
>
> Thanks for reporting.
>
> Indeed, it looks like the link is broken. We will have to fix that.
>
> Until then, please
> - run manually: Contents/Resources/Moose.image
> - with: Contents/Windows/Squeak.exe
>
> Cheers,
> Doru
>
>
>
>
>
> Begin forwarded message:
>
>
>
> From: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Date: 1 March 2011 13:56:15 CET
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Cc: Annick Fron <afron(a)cincom.com>
> Subject: Fwd: SCG
>
>
> can somebody try to help annik
> apparently moose does not work on windows.
>
>
> Je n'ai pas trop le temps de m'abonner à la liste et bla bla
>
> En gros j'ai mis mon app sous d:\apps et il pense être sous mon root directory c'est-à-dire :
> C:\users etc....
> En plus sous Windows 7 le home directory n'est plus sous settings mais sous users ...
> Donc il faut au moins changer les properties du .link
>
>
>
> Begin forwarded message:
>
>
> From: "Fron, Annick" <afron(a)cincom.com>
> Date: March 1, 2011 1:50:15 PM GMT+01:00
> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Subject: RE: SCG
>
>
> J'obtiens ceci , et en plus pas moyen de trouver la commande pour lancer Moose
>
--
www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Hi,
Thanks for reporting.
Indeed, it looks like the link is broken. We will have to fix that.
Until then, please
- run manually: Contents/Resources/Moose.image
- with: Contents/Windows/Squeak.exe
Cheers,
Doru
Begin forwarded message:
>
> From: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Date: 1 March 2011 13:56:15 CET
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Cc: Annick Fron <afron(a)cincom.com>
> Subject: Fwd: SCG
>
>
> can somebody try to help annik
> apparently moose does not work on windows.
>
>>
>> Je n'ai pas trop le temps de m'abonner à la liste et bla bla
>>
>> En gros j'ai mis mon app sous d:\apps et il pense être sous mon root directory c'est-à-dire :
>> C:\users etc....
>> En plus sous Windows 7 le home directory n'est plus sous settings mais sous users ...
>> Donc il faut au moins changer les properties du .link
>
>
>
> Begin forwarded message:
>
>> From: "Fron, Annick" <afron(a)cincom.com>
>> Date: March 1, 2011 1:50:15 PM GMT+01:00
>> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
>> Subject: RE: SCG
>>
>> J'obtiens ceci , et en plus pas moyen de trouver la commande pour lancer Moose
>>
>>
>>
>> -----Original Message-----
>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>> Sent: mardi 1 mars 2011 13:41
>> To: Fron, Annick
>> Subject: Re: SCG
>>
>>
>> > Non pas sous Windaube
>>
>> bizarre est ce que tu peux remonter cela a la moose-dev car c'est le meme setup que seaside.
>> la one-clique contient 3 vms
>>
>> Stef
>>
>> >
>> >
>> > -----Original Message-----
>> > From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>> > Sent: mardi 1 mars 2011 13:34
>> > To: Fron, Annick
>> > Subject: Re: SCG
>> >
>> >
>> > On Mar 1, 2011, at 1:25 PM, Fron, Annick wrote:
>> >
>> >> Ben il faudrait dire de downloader pharo pour moose
>> >
>> > non :)
>> > car c'est deja dans le bundle moose.
>> >
>> > tu cliques
>> > dlown
>> > dezippe
>> > et click et ca marche.
>> >
>> > Stef
>> >
>> >>
>> >> -----Original Message-----
>> >> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>> >> Sent: mardi 1 mars 2011 13:25
>> >> To: Fron, Annick
>> >> Subject: Re: SCG
>> >>
>> >> utilise la one click image sur le site.
>> >> Tu dls, cliques et cela marche.
>> >>
>> >> Squeak n'est pas pharo!!!
>> >> Pharo n'est pas squeak!!!
>> >>
>> >> Sef
>> >>
>> >> On Mar 1, 2011, at 1:23 PM, Fron, Annick wrote:
>> >>
>> >>> Faut il charger pharo ou squeak ? Le site ne le dit pas
>> >>>
>> >>> -----Original Message-----
>> >>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
>> >>> Sent: mardi 1 mars 2011 12:51
>> >>> To: Fron, Annick
>> >>> Subject: Re: SCG
>> >>>
>> >>>
>> >>> On Mar 1, 2011, at 10:46 AM, Fron, Annick wrote:
>> >>>
>> >>>> Bonjour Stephane,
>> >>>>
>> >>>> Désolée de ne pas être plus réactive pour la compil, mais souvent sous-traiter demande autant de boulot que faire ...
>> >>>> Par contre je bosse pour Cincom sur un portage de C vers Stk, et je ne suis plus au fait des outils SCG utilisables : CodeCrawler et la clique ...
>> >>>>
>> >>>> Aurais-tu des pointeurs récents ?
>> >>>
>> >>> tu veux nos outils :)
>> >>> www.moose-technology.org
>> >>>
>> >>> dans pharo moose on peut analyser du c et creer des cartes maintenant il faut surement adapter cela.
>> >>>
>> >>>
>> >>>>
>> >>>> Bonne journée
>> >>>> Annick
>> >>>
>> >>
>> >
>>
>
>
>
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
can somebody try to help annik
apparently moose does not work on windows.
>
> Je n'ai pas trop le temps de m'abonner à la liste et bla bla
>
> En gros j'ai mis mon app sous d:\apps et il pense être sous mon root directory c'est-à-dire :
> C:\users etc....
> En plus sous Windows 7 le home directory n'est plus sous settings mais sous users ...
> Donc il faut au moins changer les properties du .link
Begin forwarded message:
> From: "Fron, Annick" <afron(a)cincom.com>
> Date: March 1, 2011 1:50:15 PM GMT+01:00
> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Subject: RE: SCG
>
> J'obtiens ceci , et en plus pas moyen de trouver la commande pour lancer Moose
>
>
>
> -----Original Message-----
> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> Sent: mardi 1 mars 2011 13:41
> To: Fron, Annick
> Subject: Re: SCG
>
>
> > Non pas sous Windaube
>
> bizarre est ce que tu peux remonter cela a la moose-dev car c'est le meme setup que seaside.
> la one-clique contient 3 vms
>
> Stef
>
> >
> >
> > -----Original Message-----
> > From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> > Sent: mardi 1 mars 2011 13:34
> > To: Fron, Annick
> > Subject: Re: SCG
> >
> >
> > On Mar 1, 2011, at 1:25 PM, Fron, Annick wrote:
> >
> >> Ben il faudrait dire de downloader pharo pour moose
> >
> > non :)
> > car c'est deja dans le bundle moose.
> >
> > tu cliques
> > dlown
> > dezippe
> > et click et ca marche.
> >
> > Stef
> >
> >>
> >> -----Original Message-----
> >> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> >> Sent: mardi 1 mars 2011 13:25
> >> To: Fron, Annick
> >> Subject: Re: SCG
> >>
> >> utilise la one click image sur le site.
> >> Tu dls, cliques et cela marche.
> >>
> >> Squeak n'est pas pharo!!!
> >> Pharo n'est pas squeak!!!
> >>
> >> Sef
> >>
> >> On Mar 1, 2011, at 1:23 PM, Fron, Annick wrote:
> >>
> >>> Faut il charger pharo ou squeak ? Le site ne le dit pas
> >>>
> >>> -----Original Message-----
> >>> From: Stéphane Ducasse [mailto:stephane.ducasse@inria.fr]
> >>> Sent: mardi 1 mars 2011 12:51
> >>> To: Fron, Annick
> >>> Subject: Re: SCG
> >>>
> >>>
> >>> On Mar 1, 2011, at 10:46 AM, Fron, Annick wrote:
> >>>
> >>>> Bonjour Stephane,
> >>>>
> >>>> Désolée de ne pas être plus réactive pour la compil, mais souvent sous-traiter demande autant de boulot que faire ...
> >>>> Par contre je bosse pour Cincom sur un portage de C vers Stk, et je ne suis plus au fait des outils SCG utilisables : CodeCrawler et la clique ...
> >>>>
> >>>> Aurais-tu des pointeurs récents ?
> >>>
> >>> tu veux nos outils :)
> >>> www.moose-technology.org
> >>>
> >>> dans pharo moose on peut analyser du c et creer des cartes maintenant il faut surement adapter cela.
> >>>
> >>>
> >>>>
> >>>> Bonne journée
> >>>> Annick
> >>>
> >>
> >
>
Hi,
I marked as broken the 4.3* versions from ConfigurationOfMoose and 2.* versions of SmallDude, and now the default version of ConfigurationOfMoose loads fine again.
While this fixes the situation now, we still have to fix the overall problem of properly packaging of projects.
So, to this end, I propose to keep ConfigurationOfMoose only load the Core of Moose + the generic engines, and create a ConfigurationOfMooseSuite that will include all the other tools that extend FAMIX like SmallDude and DSM.
Also, we will have to take a look at factoring out the generic parts of the DSM and SmallDude engines and make a clear separation from the FAMIX specific code. In DSM this happens quite well already, but we need to look into it again and probably move the CycleTable & co to MooseAlgos.
Cheers,
Doru
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
Hi,
I just installed latest glamour in a pharo 1.2.
I creating a browser with a magritte presenter, and the magritte component doesn't fill the panel. This is the code:
buildBrowser
| browser |
browser := GLMTabulator new
title: 'Builder';
row: #navigation;
row: #edition;
yourself.
browser transmit
to: #navigation;
andShow: [ :presenter |
presenter finder
show: [ :eachPresenter |
eachPresenter list
title: [ :each | each asString ];
when: [ :each | each respondsTo: #allParticipants ];
display: #allParticipants.
eachPresenter label
when: [ :each | (each respondsTo: #allParticipants) not ] ] ].
browser transmit
from: #navigation;
to: #edition;
andShow: [ :presenter |
presenter magritte
title: [ :each | each asString ] ].
^browser
A screenshot of the result:
Any idea?
Cheers,
Esteban
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Glamour
New issue 546 by tudor.gi...(a)gmail.com: Searching in a Glamour list should
offer a progressbar
http://code.google.com/p/moose-technology/issues/detail?id=546
It should be easy to add a progressbar in the selection block.
Hi
Is the dot matrix visualization for duplication available somewhere?
If not, can someone provide a small Mondrian script to start with?
--
Simon Denier
Hi Veronica,
I saw you added allowAllNil. Cool.
Just, please add tests for it :). It is affecting the core of Glamour, and should be covered by tests.
Cheers,
Doru
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Hi!
Today we have 4 yellow test methods:
- MOEaselTest.testExamplesAreOkay is entirely my fault and the situation is fixed by now
- MooseFinderTest.testMenuEntriesForClasses is due to the missing dep in configurationOfMoose. the method #allDuplications is invoked on a FAMIXClassGroup. But, how comes that the menu of famix classes contains a smalldude action? Apparently, the small dude actions are defined outside smalldude. The method viewDuplicationComplexity is defined in Moose-MondrianPainting. Shall I move this method to the SmallDude-Moose package?
- MooseFinderTest.testMenuEntriesForPackages revealed that the method #viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present. According to a few days old version of moose, this class belongs to the package Moose-CycleTable. Doru, an idea what happened here?
- MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference to 'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use core packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
Cheers,
Alexandre
On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
CC: georgega...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-ExternalTools
New issue 545 by tudor.gi...(a)gmail.com: inFusion should nest namespaces and
packages
http://code.google.com/p/moose-technology/issues/detail?id=545
Namespaces should be nested using parentScope.
Packages should be nested using parentPackage.
Hi!
The last hudson version does not have the open panel?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I am working on using MetacelloBrowser for Moose. The goal is to make explicit all the versions of Moose and keep a record of them. Each new commit of one of the Moose package or each new version of a dependent library should produce a new version of Moose. I guess we all want that. I use this for Mondrian and I am quite happy.
I propose to use a simple version numbering. Something like 4.3.X where X will increment at each new commit made in one of the packages of Moose.
I have produced version 4.3.1. It loads in the latest Pharo 1.2. However, it contains a bit of hack. I believe that a Configuration version should not depend on the default baseline.
It still contains:
spec
project: 'MooseAlgos for Moose' with: '2.2';
project: 'PetitParser for Moose' with: 'default';
project: 'DSM for Moose' with: 'default';
project: 'Glamour for Moose' with: '2.1';
project: 'Mondrian for Moose' with: 'default';
project: 'SmallDude for Moose' with: 'default';
project: 'Merlin' with: '1.0';
project: 'RPackage' with: 'default'.
If you agree with this, I can produce a fix version for each of these package. Does it goes in the right direction? I already produce Version 2.1 of Glamour.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
i did try to install the sample models using the proper menu entry into the Moose Panel but apparently it doesn't work. Should i open an issue?
Cheers,
Fabrizio
Hi,
I am glad to announce that I incorporated Eduardo's work into Mondrian. He implemented FADE.
FADE is a force directly algorithm (also called spring algorithm or spring layout) invented by Aaron Quigley (http://www.cs.st-andrews.ac.uk/~aquigley/?Research:Past_Projects:FADE). FADE is faster than MOForceBasedLayout when more than 350 edges and 350 nodes have to be layouted.
On my machine:
[| view |
view := MOViewRenderer new.
view shape rectangle withText.
view nodes: Collection withAllSubclasses.
view nodes: Morph withAllSubclasses.
view edgesFrom: #superclass.
view XXXXX.
view root applyLayout ] timeToRun
For XXX = fadeLayout, it takes 12204 ms to compute
For XXX = forceBasedLayout, it takes 17604ms
In version 2.51 of Mondrian
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
No, it should not be rewritten.
The problem is due to me removing DSM and SmallDude from the default configuration because of Metacello problems. I hope to restart working on it next week.
Cheers,
Doru
On 22 Feb 2011, at 10:56, Cyrille Delaunay wrote:
> MooseSqueakClassPackageImporterTest>>#testCategoryImporter is looking for all packages matching ''Moose-TestResources-Dsm*'', but there is no packages like that in the image. I guess the test should be re-written?
>
> 2011/2/22 <admin(a)moosetechnology.org>
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
>
>
>
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."
Hi,
I would like to remind you that this Saturday, February 26, we organize a Sprint at SCG, University of Berne, Switzerland (room 107):
http://scg.unibe.ch/contact/maps
Further details can be found below. Please let us know by mail if you plan to attend and what you would wish to work on (see below).
Cheers,
Doru
Begin forwarded message:
> From: Tudor Girba <tudor.girba(a)gmail.com>
> Date: 1 February 2011 16:38:30 CET
> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr>
> Cc: Adrian Lienhard <alienhard(a)netstyle.ch>
> Subject: [ANN] pharo focused sprint - bern, feb 26
>
> Hi,
>
> We would like to organize a Pharo Sprint on Saturday, February 26 at SCG, University of Berne, Switzerland (room 107):
> http://scg.unibe.ch/contact/maps
>
> Unlike other sprints, this would not be about fixing things from the tracker, but about building something new and reviewing the situation around one central topic. For this one, the main topic will be Morphic and the IDE. Why? Because it is time to rethink our day-to-day tools and bring them closer to this century (ok, maybe decade :)). It is Ok if you are not a specialist. It is more important to want to participate and learn. The rest will come in time.
>
> ***** Please let us know by mail if you plan to attend and what you would wish to work on (see below).
>
> Proposed tasks (other tasks are possible in the same area):
> - Enhancements of Morphic widgets:
> --- TabGroupMorph with lazy pages, closable tabs, overflow handling and toolbars (a start exists in Glamour)
> --- High level support for collapsable panes (based on the input of Gary)
> --- SearchMorph with multiple groups of items (like in Spotlight)
> --- MorphTreeMorph integrated with GeneralScrollPane to allow for space filling
> --- BreadcrumbMorph
> --- Hyperlinks in TextMorphs
> - Test and enhance the current IDE
> - Evaluate TextMorphs: NewTextMorph, PluggableTextMorph, SMxPluggableTextMorph etc
> - Prototype a new ToolSet solution
> - Enhancements of Glamour and of the Glamorous Toolkit
> --- Debugger
> --- Coder
> --- Multipage Workspace
> --- CodeBubbles
> - Develop WeakAnnouncement (start from the implementation of Lukas)
> - Evaluate the various keybinding implementations
> - Evaluate ToolBuilder
> - Evaluate the path to adopt SimpleMorphic
>
> A second working topic is getting Monticello faster, but this will only be tackled if there are enough people for the first one.
>
> Cheers,
> Adrian and Doru
>
>
>
> --
> www.tudorgirba.com
>
> "Be rather willing to give than demanding to get."
>
>
>
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
Hi guys
I have a question about XMLWriter. I have cards and group of cards.
Each class know how to serialize itself.
For card I have xmlOn: (one of my methods) that describes the card attributes
Card>>xmlOn: aWriter
"write a description of the receiver properties as xml uing aWriter, an instance of XMLWriter"
aWriter tag
name: #card;
with: [self xmlInstVarOn: aWriter]
Group>>xmlOn: aWriter
"write a description of the receiver properties as xml uing aWriter, an instance of XMLWriter"
| cardWriter |
cardWriter := XMLWriter new.
cards do: [:each | each xmlOn: cardWriter].
aWriter tag
name: #group;
with: [
aWriter tag: #groupName with: self groupName.
aWriter tag: #cards with: [ aWriter raw: cardWriter contents]]
And I'm not really happy. Because I would like to avoid to use raw: and instantiate a new writer.
I would like to know how I could use the write to pass the results of the iteration over cards
I wanted to write something like
aWriter tag
name: #group;
with: [
aWriter tag: #groupName with: self groupName.
aWriter tag: #cards with: [self cards do: [:each | each xmlOn: aWriter]]
Hi,
It seems that I am the only one working on 4.3 :). So the plan is to release it in 10 days, on February 20.
Please let me know if you are interested in giving a hand. It can be as small as testing or writing some piece of documentation or a blog post.
Cheers,
Doru
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
We are happy to announce the Moose Suite version 4.3:
*http://moosetechnology.org/download*
What is new:
- New look and feel
- New and flexible API to browse FAMIX models
- Extensible Moose Finder
- Enhanced Glamour engine to deal with complex actions
- Enhanced FAMIX support for Java systems
- Enhanced Glamour rendering for Morphic
- Enhanced meta browser
- Enhanced documentation of Mondrian
- Enhanced XMLSupport
- Enhanced Smalltalk importer
A list of issues addressed in this release can be found at:
*http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%20milestone=4.3*
Have fun,
The Moose Team
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.3
New issue 539 by tudor.gi...(a)gmail.com: Introduce SourceLanguage as an
explicit entity
http://code.google.com/p/moose-technology/issues/detail?id=539
Currently, sourceLanguage is modeled with a symbol stored in the Model.
This is suboptimal due to at least two things:
- the only way to decide strategies of what highlighting to use when
displaying text is with an if
- there is no possibility of having multiple languages in the same model
I would like to introduce FAMIXSourceLanguage as an explicit entity that
can be linked to any FAMIXEntity.
If an entity does not have a FAMIXEntity, it will fallback to the
mooseModel sourceLanguage.
The overall MooseModel sourceLanguage will be decided based on the
FAMIXSourceLanguage object that has no attached entities.