I downloaded the second moose image (the one with the moose logo) and gives me an error when I try to loadBleedingEdge as before

Could not Resolve : Moose-Algos-Kotractor

I would paste the stack but I see no such feature in the debugger.

On Tue, Apr 22, 2014 at 12:58 PM, Tudor Girba tudor@tudorgirba.com wrote:

Hi,

You should use the Moose image.

I just tried and it works. As far as I can see the goal is to produce a visual tool for software assessment. It looks pretty good. I will take a look at the code later.

Keep it up.

Doru

On Tue, Apr 22, 2014 at 11:43 AM, kilon alios kilon.alios@gmail.comwrote:

...

I tried your code but I am getting errors. I downloaded your Configuration and I did ConfigurationOfTelescope loadBleedingEdge.

Try the first sample gives me

MNU>>receiver of "new" is nil

UndefinedObject(Object)>>doesNotUnderstand: #new TLVizuBuilder>>kontract: TLVizuBuilder>>render in Block: [ :c | ... Array(SequenceableCollection)>>do: TLVizuBuilder>>render TLVizuBuilder>>open TLTelescope>>open UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [ :morph | morph doIt ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: KMCategoryBinding>>completeMatch:buffer: KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l completeMatch: self buffer: aBuffer ] Array(SequenceableCollection)>>do: KMKeymap>>notifyCompleteMatchTo:buffer: KMKeymap>>onMatchWith:notify:andDo: KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry onMatchWith: anEventBuffer notify...etc... Set>>do: KMCategory>>onMatchWith:notify:andDo: KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: KMDispatcher>>dispatch: in Block: [ :aTarget | ...

second sample gives me another error

CharacterSet class(Object)>>doesNotUnderstand: #numberOfLinesOfCode UndefinedObject>>DoIt in Block: [ :class | class numberOfLinesOfCode > 30 ] BlockClosure>>rtValue: TLVizuBuilder>>onElements:containers:properties: in Block: [ :element | ... OrderedCollection>>do: TLVizuBuilder>>onElements:containers:properties: TLTelescope>>onElements:containers:properties: UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [ :morph | morph doIt ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: KMCategoryBinding>>completeMatch:buffer: KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l completeMatch: self buffer: aBuffer ] Array(SequenceableCollection)>>do: KMKeymap>>notifyCompleteMatchTo:buffer: KMKeymap>>onMatchWith:notify:andDo: KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry onMatchWith: anEventBuffer notify...etc... Set>>do: KMCategory>>onMatchWith:notify:andDo: KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: KMDispatcher>>dispatch: in Block: [ :aTarget | ...

I am huge fun of astronomy, I am definitely interested in working as a beta tester for your code and learn more about Roassal :) I am actually learning Roassal and Mondrian during my easter vacations .

On Tue, Apr 22, 2014 at 12:20 PM, Leo Perard leo.perard@gmail.comwrote:

...

Hi everybody,

I'm working on vizualisation with Roassal2 and I would like to have some feedbacks on my work. You can vizualise some elements in their containers and test a property on the elements. You have the legend build with the property and a menu (not a lot of features in the menu but it will come). Edges are not available yet, but I'm working on it.

The repository :

MCHttpRepository location: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main' user: '' password: ''

To load the project : ConfigurationOfTelescope load

To play with it you can follow this example :

| telescope | telescope := TLTelescope new onContainers: Collection withAllSubclasses elements: #authors properties: #yourself. telescope numberOfColors: 9. "optional" telescope open

or

| telescope | telescope := TLTelescope new onElements: Collection withAllSubclasses containers: #package properties: [ :class | class numberOfLinesOfCode > 30 ]. telescope numberOfColors: 9. "optional" telescope open

If you have any ideas, or find somes bugs do not hesitate to report to me.

Thanks.

-- Leo Perard

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

got the image from moose website directly this time , I get the same exact error, in this case I have full access to the default pharo debugger so here is the stack

MetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: GTMetacelloPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray:

On Tue, Apr 22, 2014 at 1:42 PM, kilon alios kilon.alios@gmail.com wrote:

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios kilon.alios@gmail.comwrote:

...

I downloaded the second moose image (the one with the moose logo) and gives me an error when I try to loadBleedingEdge as before

Could not Resolve : Moose-Algos-Kotractor

I would paste the stack but I see no such feature in the debugger.

On Tue, Apr 22, 2014 at 12:58 PM, Tudor Girba tudor@tudorgirba.comwrote:

...

Hi,

You should use the Moose image.

I just tried and it works. As far as I can see the goal is to produce a visual tool for software assessment. It looks pretty good. I will take a look at the code later.

Keep it up.

Doru

On Tue, Apr 22, 2014 at 11:43 AM, kilon alios kilon.alios@gmail.comwrote:

...

I tried your code but I am getting errors. I downloaded your Configuration and I did ConfigurationOfTelescope loadBleedingEdge.

Try the first sample gives me

MNU>>receiver of "new" is nil

UndefinedObject(Object)>>doesNotUnderstand: #new TLVizuBuilder>>kontract: TLVizuBuilder>>render in Block: [ :c | ... Array(SequenceableCollection)>>do: TLVizuBuilder>>render TLVizuBuilder>>open TLTelescope>>open UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [ :morph | morph doIt ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: KMCategoryBinding>>completeMatch:buffer: KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l completeMatch: self buffer: aBuffer ] Array(SequenceableCollection)>>do: KMKeymap>>notifyCompleteMatchTo:buffer: KMKeymap>>onMatchWith:notify:andDo: KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry onMatchWith: anEventBuffer notify...etc... Set>>do: KMCategory>>onMatchWith:notify:andDo: KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: KMDispatcher>>dispatch: in Block: [ :aTarget | ...

second sample gives me another error

CharacterSet class(Object)>>doesNotUnderstand: #numberOfLinesOfCode UndefinedObject>>DoIt in Block: [ :class | class numberOfLinesOfCode > 30 ] BlockClosure>>rtValue: TLVizuBuilder>>onElements:containers:properties: in Block: [ :element | ... OrderedCollection>>do: TLVizuBuilder>>onElements:containers:properties: TLTelescope>>onElements:containers:properties: UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [ :morph | morph doIt ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: KMCategoryBinding>>completeMatch:buffer: KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l completeMatch: self buffer: aBuffer ] Array(SequenceableCollection)>>do: KMKeymap>>notifyCompleteMatchTo:buffer: KMKeymap>>onMatchWith:notify:andDo: KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry onMatchWith: anEventBuffer notify...etc... Set>>do: KMCategory>>onMatchWith:notify:andDo: KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: KMDispatcher>>dispatch: in Block: [ :aTarget | ...

I am huge fun of astronomy, I am definitely interested in working as a beta tester for your code and learn more about Roassal :) I am actually learning Roassal and Mondrian during my easter vacations .

On Tue, Apr 22, 2014 at 12:20 PM, Leo Perard leo.perard@gmail.comwrote:

...

Hi everybody,

I'm working on vizualisation with Roassal2 and I would like to have some feedbacks on my work. You can vizualise some elements in their containers and test a property on the elements. You have the legend build with the property and a menu (not a lot of features in the menu but it will come). Edges are not available yet, but I'm working on it.

The repository :

MCHttpRepository location: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main' user: '' password: ''

To load the project : ConfigurationOfTelescope load

To play with it you can follow this example :

| telescope | telescope := TLTelescope new onContainers: Collection withAllSubclasses elements: #authors properties: #yourself. telescope numberOfColors: 9. "optional" telescope open

or

| telescope | telescope := TLTelescope new onElements: Collection withAllSubclasses containers: #package properties: [ :class | class numberOfLinesOfCode > 30 ]. telescope numberOfColors: 9. "optional" telescope open

If you have any ideas, or find somes bugs do not hesitate to report to me.

Thanks.

-- Leo Perard

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

downloaded 5.0 image from your link, same problem, same error :(

On Tue, Apr 22, 2014 at 1:57 PM, Tudor Girba tudor@tudorgirba.com wrote:

Which image?

You should download the 5.0 image: http://www.moosetechnology.org/download/5.0

Doru

On Tue, Apr 22, 2014 at 12:50 PM, kilon alios kilon.alios@gmail.comwrote:

...

got the image from moose website directly this time , I get the same exact error, in this case I have full access to the default pharo debugger so here is the stack

MetacelloFetchingMCSpecLoader(Object)>>error:

MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: GTMetacelloPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do:

MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray:

On Tue, Apr 22, 2014 at 1:42 PM, kilon alios kilon.alios@gmail.comwrote:

...

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios kilon.alios@gmail.comwrote:

...

I downloaded the second moose image (the one with the moose logo) and gives me an error when I try to loadBleedingEdge as before

Could not Resolve : Moose-Algos-Kotractor

I would paste the stack but I see no such feature in the debugger.

On Tue, Apr 22, 2014 at 12:58 PM, Tudor Girba tudor@tudorgirba.comwrote:

...

Hi,

You should use the Moose image.

I just tried and it works. As far as I can see the goal is to produce a visual tool for software assessment. It looks pretty good. I will take a look at the code later.

Keep it up.

Doru

On Tue, Apr 22, 2014 at 11:43 AM, kilon alios kilon.alios@gmail.comwrote:

...

I tried your code but I am getting errors. I downloaded your Configuration and I did ConfigurationOfTelescope loadBleedingEdge.

Try the first sample gives me

MNU>>receiver of "new" is nil

UndefinedObject(Object)>>doesNotUnderstand: #new TLVizuBuilder>>kontract: TLVizuBuilder>>render in Block: [ :c | ... Array(SequenceableCollection)>>do: TLVizuBuilder>>render TLVizuBuilder>>open TLTelescope>>open UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [ :morph | morph doIt ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: KMCategoryBinding>>completeMatch:buffer: KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l completeMatch: self buffer: aBuffer ] Array(SequenceableCollection)>>do: KMKeymap>>notifyCompleteMatchTo:buffer: KMKeymap>>onMatchWith:notify:andDo: KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry onMatchWith: anEventBuffer notify...etc... Set>>do: KMCategory>>onMatchWith:notify:andDo: KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: KMDispatcher>>dispatch: in Block: [ :aTarget | ...

second sample gives me another error

CharacterSet class(Object)>>doesNotUnderstand: #numberOfLinesOfCode UndefinedObject>>DoIt in Block: [ :class | class numberOfLinesOfCode > 30 ] BlockClosure>>rtValue: TLVizuBuilder>>onElements:containers:properties: in Block: [ :element | ... OrderedCollection>>do: TLVizuBuilder>>onElements:containers:properties: TLTelescope>>onElements:containers:properties: UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [ :morph | morph doIt ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: KMCategoryBinding>>completeMatch:buffer: KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l completeMatch: self buffer: aBuffer ] Array(SequenceableCollection)>>do: KMKeymap>>notifyCompleteMatchTo:buffer: KMKeymap>>onMatchWith:notify:andDo: KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry onMatchWith: anEventBuffer notify...etc... Set>>do: KMCategory>>onMatchWith:notify:andDo: KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: KMDispatcher>>dispatch: in Block: [ :aTarget | ...

I am huge fun of astronomy, I am definitely interested in working as a beta tester for your code and learn more about Roassal :) I am actually learning Roassal and Mondrian during my easter vacations .

On Tue, Apr 22, 2014 at 12:20 PM, Leo Perard leo.perard@gmail.comwrote:

> Hi everybody, > > I'm working on vizualisation with Roassal2 and I would like to have > some feedbacks on my work. > You can vizualise some elements in their containers and test a > property on the elements. > You have the legend build with the property and a menu (not a lot of > features in the menu but it will come). > Edges are not available yet, but I'm working on it. > > The repository : > > MCHttpRepository > location: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main' > user: '' > password: '' > > To load the project : ConfigurationOfTelescope load > > To play with it you can follow this example : > > | telescope | > telescope := TLTelescope new onContainers: Collection > withAllSubclasses elements: #authors properties: #yourself. > telescope numberOfColors: 9. "optional" > telescope open > > or > > | telescope | > telescope := TLTelescope new onElements: Collection > withAllSubclasses containers: #package properties: [ :class | class > numberOfLinesOfCode > 30 ]. > telescope numberOfColors: 9. "optional" > telescope open > > > If you have any ideas, or find somes bugs do not hesitate to report > to me. > > Thanks. > > -- > Leo Perard > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

For me it worked well:

1) I downloaded the image Doru said: http://www.moosetechnology.org/download/5.0

then,

2) Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load.

3) ConfigurationOfTelescope load

On Tue, Apr 22, 2014 at 1:05 PM, kilon alios kilon.alios@gmail.com wrote:

downloaded 5.0 image from your link, same problem, same error :(

On Tue, Apr 22, 2014 at 1:57 PM, Tudor Girba tudor@tudorgirba.com wrote:

...

Which image?

You should download the 5.0 image: http://www.moosetechnology.org/download/5.0

Doru

On Tue, Apr 22, 2014 at 12:50 PM, kilon alios kilon.alios@gmail.comwrote:

...

got the image from moose website directly this time , I get the same exact error, in this case I have full access to the default pharo debugger so here is the stack

MetacelloFetchingMCSpecLoader(Object)>>error:

MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: GTMetacelloPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do:

MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray:

On Tue, Apr 22, 2014 at 1:42 PM, kilon alios kilon.alios@gmail.comwrote:

...

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios kilon.alios@gmail.comwrote:

...

I downloaded the second moose image (the one with the moose logo) and gives me an error when I try to loadBleedingEdge as before

Could not Resolve : Moose-Algos-Kotractor

I would paste the stack but I see no such feature in the debugger.

On Tue, Apr 22, 2014 at 12:58 PM, Tudor Girba tudor@tudorgirba.comwrote:

...

Hi,

You should use the Moose image.

I just tried and it works. As far as I can see the goal is to produce a visual tool for software assessment. It looks pretty good. I will take a look at the code later.

Keep it up.

Doru

On Tue, Apr 22, 2014 at 11:43 AM, kilon alios kilon.alios@gmail.comwrote:

> I tried your code but I am getting errors. I downloaded your > Configuration and I did ConfigurationOfTelescope loadBleedingEdge. > > Try the first sample gives me > > MNU>>receiver of "new" is nil > > UndefinedObject(Object)>>doesNotUnderstand: #new > TLVizuBuilder>>kontract: > TLVizuBuilder>>render in Block: [ :c | ... > Array(SequenceableCollection)>>do: > TLVizuBuilder>>render > TLVizuBuilder>>open > TLTelescope>>open > UndefinedObject>>DoIt > OpalCompiler>>evaluate > SmalltalkEditor>>evaluateSelectionAndDo: > SmalltalkEditor>>evaluateSelection > PluggableTextMorph>>doIt in Block: [ textMorph editor > evaluateSelection ] > PluggableTextMorph>>handleEdit: in Block: [ result := editBlock > value ] > TextMorphForEditView(TextMorph)>>handleEdit: > PluggableTextMorph>>handleEdit: > PluggableTextMorph>>doIt > SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: > [ :morph | morph doIt ] > BlockClosure>>cull: > BlockClosure>>cull:cull: > BlockClosure>>cull:cull:cull: > KMCategoryBinding>>completeMatch:buffer: > KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l > completeMatch: self buffer: aBuffer ] > Array(SequenceableCollection)>>do: > KMKeymap>>notifyCompleteMatchTo:buffer: > KMKeymap>>onMatchWith:notify:andDo: > KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry > onMatchWith: anEventBuffer notify...etc... > Set>>do: > KMCategory>>onMatchWith:notify:andDo: > KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: > KMDispatcher>>dispatch: in Block: [ :aTarget | ... > > second sample gives me another error > > CharacterSet class(Object)>>doesNotUnderstand: #numberOfLinesOfCode > UndefinedObject>>DoIt in Block: [ :class | class numberOfLinesOfCode > > 30 ] > BlockClosure>>rtValue: > TLVizuBuilder>>onElements:containers:properties: in Block: [ > :element | ... > OrderedCollection>>do: > TLVizuBuilder>>onElements:containers:properties: > TLTelescope>>onElements:containers:properties: > UndefinedObject>>DoIt > OpalCompiler>>evaluate > SmalltalkEditor>>evaluateSelectionAndDo: > SmalltalkEditor>>evaluateSelection > PluggableTextMorph>>doIt in Block: [ textMorph editor > evaluateSelection ] > PluggableTextMorph>>handleEdit: in Block: [ result := editBlock > value ] > TextMorphForEditView(TextMorph)>>handleEdit: > PluggableTextMorph>>handleEdit: > PluggableTextMorph>>doIt > SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: > [ :morph | morph doIt ] > BlockClosure>>cull: > BlockClosure>>cull:cull: > BlockClosure>>cull:cull:cull: > KMCategoryBinding>>completeMatch:buffer: > KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l > completeMatch: self buffer: aBuffer ] > Array(SequenceableCollection)>>do: > KMKeymap>>notifyCompleteMatchTo:buffer: > KMKeymap>>onMatchWith:notify:andDo: > KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry > onMatchWith: anEventBuffer notify...etc... > Set>>do: > KMCategory>>onMatchWith:notify:andDo: > KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: > KMDispatcher>>dispatch: in Block: [ :aTarget | ... > > I am huge fun of astronomy, I am definitely interested in working as > a beta tester for your code and learn more about Roassal :) I am actually > learning Roassal and Mondrian during my easter vacations . > > > On Tue, Apr 22, 2014 at 12:20 PM, Leo Perard leo.perard@gmail.comwrote: > >> Hi everybody, >> >> I'm working on vizualisation with Roassal2 and I would like to have >> some feedbacks on my work. >> You can vizualise some elements in their containers and test a >> property on the elements. >> You have the legend build with the property and a menu (not a lot >> of features in the menu but it will come). >> Edges are not available yet, but I'm working on it. >> >> The repository : >> >> MCHttpRepository >> location: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main' >> user: '' >> password: '' >> >> To load the project : ConfigurationOfTelescope load >> >> To play with it you can follow this example : >> >> | telescope | >> telescope := TLTelescope new onContainers: Collection >> withAllSubclasses elements: #authors properties: #yourself. >> telescope numberOfColors: 9. "optional" >> telescope open >> >> or >> >> | telescope | >> telescope := TLTelescope new onElements: Collection >> withAllSubclasses containers: #package properties: [ :class | class >> numberOfLinesOfCode > 30 ]. >> telescope numberOfColors: 9. "optional" >> telescope open >> >> >> If you have any ideas, or find somes bugs do not hesitate to report >> to me. >> >> Thanks. >> >> -- >> Leo Perard >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev@iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

ah thanks it works now . I use bleeding edge to get most recent code. Now studying your code.

On 4/22/14, Leo Perard leo.perard@gmail.com wrote:

You load with loadBleedingEdge ? You should just load like that : ConfigurationOfTelescope load

On Tue, Apr 22, 2014 at 1:05 PM, kilon alios kilon.alios@gmail.com wrote:

...

downloaded 5.0 image from your link, same problem, same error :(

On Tue, Apr 22, 2014 at 1:57 PM, Tudor Girba tudor@tudorgirba.com wrote:

...

Which image?

You should download the 5.0 image: http://www.moosetechnology.org/download/5.0

Doru

On Tue, Apr 22, 2014 at 12:50 PM, kilon alios kilon.alios@gmail.comwrote:

...

got the image from moose website directly this time , I get the same exact error, in this case I have full access to the default pharo debugger so here is the stack

MetacelloFetchingMCSpecLoader(Object)>>error:

MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: GTMetacelloPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do:

MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray:

On Tue, Apr 22, 2014 at 1:42 PM, kilon alios kilon.alios@gmail.comwrote:

...

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios kilon.alios@gmail.comwrote:

...

I downloaded the second moose image (the one with the moose logo) and gives me an error when I try to loadBleedingEdge as before

Could not Resolve : Moose-Algos-Kotractor

I would paste the stack but I see no such feature in the debugger.

On Tue, Apr 22, 2014 at 12:58 PM, Tudor Girba tudor@tudorgirba.comwrote:

> Hi, > > You should use the Moose image. > > I just tried and it works. As far as I can see the goal is to > produce > a visual tool for software assessment. It looks pretty good. I will > take a > look at the code later. > > Keep it up. > > Doru > > > On Tue, Apr 22, 2014 at 11:43 AM, kilon alios > kilon.alios@gmail.comwrote: > >> I tried your code but I am getting errors. I downloaded your >> Configuration and I did ConfigurationOfTelescope loadBleedingEdge. >> >> Try the first sample gives me >> >> MNU>>receiver of "new" is nil >> >> UndefinedObject(Object)>>doesNotUnderstand: #new >> TLVizuBuilder>>kontract: >> TLVizuBuilder>>render in Block: [ :c | ... >> Array(SequenceableCollection)>>do: >> TLVizuBuilder>>render >> TLVizuBuilder>>open >> TLTelescope>>open >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> SmalltalkEditor>>evaluateSelectionAndDo: >> SmalltalkEditor>>evaluateSelection >> PluggableTextMorph>>doIt in Block: [ textMorph editor >> evaluateSelection ] >> PluggableTextMorph>>handleEdit: in Block: [ result := editBlock >> value ] >> TextMorphForEditView(TextMorph)>>handleEdit: >> PluggableTextMorph>>handleEdit: >> PluggableTextMorph>>doIt >> SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: >> [ :morph | morph doIt ] >> BlockClosure>>cull: >> BlockClosure>>cull:cull: >> BlockClosure>>cull:cull:cull: >> KMCategoryBinding>>completeMatch:buffer: >> KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l >> completeMatch: self buffer: aBuffer ] >> Array(SequenceableCollection)>>do: >> KMKeymap>>notifyCompleteMatchTo:buffer: >> KMKeymap>>onMatchWith:notify:andDo: >> KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry >> onMatchWith: anEventBuffer notify...etc... >> Set>>do: >> KMCategory>>onMatchWith:notify:andDo: >> KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: >> KMDispatcher>>dispatch: in Block: [ :aTarget | ... >> >> second sample gives me another error >> >> CharacterSet class(Object)>>doesNotUnderstand: #numberOfLinesOfCode >> UndefinedObject>>DoIt in Block: [ :class | class >> numberOfLinesOfCode >> > 30 ] >> BlockClosure>>rtValue: >> TLVizuBuilder>>onElements:containers:properties: in Block: [ >> :element | ... >> OrderedCollection>>do: >> TLVizuBuilder>>onElements:containers:properties: >> TLTelescope>>onElements:containers:properties: >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> SmalltalkEditor>>evaluateSelectionAndDo: >> SmalltalkEditor>>evaluateSelection >> PluggableTextMorph>>doIt in Block: [ textMorph editor >> evaluateSelection ] >> PluggableTextMorph>>handleEdit: in Block: [ result := editBlock >> value ] >> TextMorphForEditView(TextMorph)>>handleEdit: >> PluggableTextMorph>>handleEdit: >> PluggableTextMorph>>doIt >> SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: >> [ :morph | morph doIt ] >> BlockClosure>>cull: >> BlockClosure>>cull:cull: >> BlockClosure>>cull:cull:cull: >> KMCategoryBinding>>completeMatch:buffer: >> KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [ :l | l >> completeMatch: self buffer: aBuffer ] >> Array(SequenceableCollection)>>do: >> KMKeymap>>notifyCompleteMatchTo:buffer: >> KMKeymap>>onMatchWith:notify:andDo: >> KMCategory>>onMatchWith:notify:andDo: in Block: [ :entry | entry >> onMatchWith: anEventBuffer notify...etc... >> Set>>do: >> KMCategory>>onMatchWith:notify:andDo: >> KMCategoryBinding>>verifyMatchWith:notifying:thenDoing: >> KMDispatcher>>dispatch: in Block: [ :aTarget | ... >> >> I am huge fun of astronomy, I am definitely interested in working >> as >> a beta tester for your code and learn more about Roassal :) I am >> actually >> learning Roassal and Mondrian during my easter vacations . >> >> >> On Tue, Apr 22, 2014 at 12:20 PM, Leo Perard >> leo.perard@gmail.comwrote: >> >>> Hi everybody, >>> >>> I'm working on vizualisation with Roassal2 and I would like to >>> have >>> some feedbacks on my work. >>> You can vizualise some elements in their containers and test a >>> property on the elements. >>> You have the legend build with the property and a menu (not a lot >>> of features in the menu but it will come). >>> Edges are not available yet, but I'm working on it. >>> >>> The repository : >>> >>> MCHttpRepository >>> location: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main' >>> user: '' >>> password: '' >>> >>> To load the project : ConfigurationOfTelescope load >>> >>> To play with it you can follow this example : >>> >>> | telescope | >>> telescope := TLTelescope new onContainers: Collection >>> withAllSubclasses elements: #authors properties: #yourself. >>> telescope numberOfColors: 9. "optional" >>> telescope open >>> >>> or >>> >>> | telescope | >>> telescope := TLTelescope new onElements: Collection >>> withAllSubclasses containers: #package properties: [ :class | >>> class >>> numberOfLinesOfCode > 30 ]. >>> telescope numberOfColors: 9. "optional" >>> telescope open >>> >>> >>> If you have any ideas, or find somes bugs do not hesitate to >>> report >>> to me. >>> >>> Thanks. >>> >>> -- >>> Leo Perard >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev@iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev@iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Leo Perard

Hi,

I add a new vizualisation to the project. To test it, reload the configuration of the project and this message : TLTelescope class>>#onElement:withEdgesProperty:

Here an example :

| telescope | telescope := TLTelescope onElement: Collection withEdgesProperty: #subclasses. telescope open

This vizualisation is really dynamic and I like it, but as it's dynamic there are some bugs. The layout on right click on an element dont' work yet. I will try to fix them first. I like the idea of getting something really dynamic with Roassal2. Once you write your code to generate the graph you do not have to write lines again.

If you have ideas to improve this vizualisation, let me know them ;-)

On Tue, Apr 22, 2014 at 7:32 PM, Leo Perard leo.perard@gmail.com wrote:

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel <alexandre.bergel@me.com

...

wrote:

...

Cool animations!!!

We start to have a real and nice infrastructure. This is cool! Make a video and compete to the Roassal contest!

I will think about that !

...

If you have distribution map, why do you propose the tree layout since there is no edges?

Just experimentations. I'm working on edges and I don't know yet how the menu will evoluate.

...

Alexandre

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

-- Leo Perard

Something like that is ok ?

Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load.

ConfigurationOfTelescope load

On Thu, Apr 24, 2014 at 11:33 AM, Tudor Girba tudor@tudorgirba.com wrote:

Please provide an easy Gofer script for loading your package.

Doru

On Thu, Apr 24, 2014 at 11:28 AM, Leo Perard leo.perard@gmail.com wrote:

...

Hi,

I add a new vizualisation to the project. To test it, reload the configuration of the project and this message : TLTelescope class>>#onElement:withEdgesProperty:

Here an example :

| telescope | telescope := TLTelescope onElement: Collection withEdgesProperty: #subclasses. telescope open

This vizualisation is really dynamic and I like it, but as it's dynamic there are some bugs. The layout on right click on an element dont' work yet. I will try to fix them first. I like the idea of getting something really dynamic with Roassal2. Once you write your code to generate the graph you do not have to write lines again.

If you have ideas to improve this vizualisation, let me know them ;-)

On Tue, Apr 22, 2014 at 7:32 PM, Leo Perard leo.perard@gmail.com wrote:

...

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel < alexandre.bergel@me.com> wrote:

...

Cool animations!!!

We start to have a real and nice infrastructure. This is cool! Make a video and compete to the Roassal contest!

I will think about that !

...

If you have distribution map, why do you propose the tree layout since there is no edges?

Just experimentations. I'm working on edges and I don't know yet how the menu will evoluate.

...

Alexandre

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

-- Leo Perard

-- Leo Perard

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Yes I saw it, but I didn't use it because it works with stack as Mondrian and I do not want somthing like that.

On Thu, Apr 24, 2014 at 3:45 PM, Alexandre Bergel alexandre.bergel@me.comwrote:

Hi Leo,

Looks good!

Sergio, in Cc:, is working on a new kind of interaction to achieve similar effect. Sergio, how stable is your expand interaction?

@ Leo: in a couple of hours I will meet Sergio. We will try to include his interaction in Roassal.

Alexandre

_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Apr 24, 2014, at 7:37 AM, Leo Perard leo.perard@gmail.com wrote:

...

Something like that is ok ?

Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load.

ConfigurationOfTelescope load

On Thu, Apr 24, 2014 at 11:33 AM, Tudor Girba tudor@tudorgirba.com

wrote:

...

Please provide an easy Gofer script for loading your package.

Doru

On Thu, Apr 24, 2014 at 11:28 AM, Leo Perard leo.perard@gmail.com

wrote:

...

Hi,

I add a new vizualisation to the project. To test it, reload the configuration of the project and this message : TLTelescope class>>#onElement:withEdgesProperty:

Here an example :

| telescope | telescope := TLTelescope onElement: Collection withEdgesProperty:

#subclasses.

...

telescope open

This vizualisation is really dynamic and I like it, but as it's dynamic

there are some bugs. The layout on right click on an element dont' work yet. I will try to fix them first. I like the idea of getting something really dynamic with Roassal2. Once you write your code to generate the graph you do not have to write lines again.

...

If you have ideas to improve this vizualisation, let me know them ;-)

On Tue, Apr 22, 2014 at 7:32 PM, Leo Perard leo.perard@gmail.com

wrote:

...

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel <

alexandre.bergel@me.com> wrote:

...

Cool animations!!!

We start to have a real and nice infrastructure. This is cool! Make a video and compete to the Roassal contest!

I will think about that !

If you have distribution map, why do you propose the tree layout since

there is no edges?

...

Just experimentations. I'm working on edges and I don't know yet how the

menu will evoluate.

...

Alexandre

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

-- Leo Perard

-- Leo Perard

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Leo Perard _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi!

I am not sure how to load your tool.

ConfigurationOfTelescope load

=> does not work. ‘… Explicitely not defined …’

I’ve tried with #loadDevelopment but I get the following error:

Warning: This package depends on the following classes: TLCustomAction You must resolve these dependencies before you will be able to load these definitions: initialize

Cheers, Alexandre

On Apr 30, 2014, at 12:41 PM, Leo Perard leo.perard@gmail.com wrote:

Hi all,

some new features have been added, especially in the butterfly vizualisation.

To load the project Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load. ConfigurationOfTelescope load

To play with it, you can check the examples in the class side of TLTelescope but here some features you can test.

• for distribution map vizualisation

numberOfColors: let you set the number of items in the legend (the default item is not counted)

• for butterfly vizualisation

expandToRank: expand the graph before opening the view (you don't have the root node alone)

• for both of them

actionOnEntity:title: let you add an action on the entity with a menu on right click (actionOnEntity: [ :e | e inspect ] title: 'Inspect' let you inspect the entity for example) actionOnNode:title: let you add an action on the node with a menu on right click ( actionOnNode: [ :n | n trachelShape color: Color random. n view canvas signalUpdate ] title: 'Change color' let you change the color of the node for example)

Full example | telescope | telescope := TLTelescope. telescope distributionMap onContainers: Collection withAllSubclasses elements: #authors properties: #yourself; numberOfColors: 5; actionOnNode: [ :n | n trachelShape color: Color blue. n view canvas signalUpdate ] title: 'Color'; open. telescope butterfly root: Collection withProperty: #subclasses; expandToRank: 3; actionOnEntity: [ :e | e inspect ] title: 'Inspect'; open As you can see you can open several vizualisation in the same time.

I am sure that there is a lot of features for this dynamic vizualisations so if you have some ideas let me know :-)

Some screenshot

<butterfly.png>

<distribution-map.png> ​ ​

On Thu, Apr 24, 2014 at 4:32 PM, Leo Perard leo.perard@gmail.com wrote: Yes I saw it, but I didn't use it because it works with stack as Mondrian and I do not want somthing like that.

On Thu, Apr 24, 2014 at 3:45 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi Leo,

Looks good!

Sergio, in Cc:, is working on a new kind of interaction to achieve similar effect. Sergio, how stable is your expand interaction?

@ Leo: in a couple of hours I will meet Sergio. We will try to include his interaction in Roassal.

Alexandre

_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Apr 24, 2014, at 7:37 AM, Leo Perard leo.perard@gmail.com wrote:

...

Something like that is ok ?

Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load.

ConfigurationOfTelescope load

On Thu, Apr 24, 2014 at 11:33 AM, Tudor Girba tudor@tudorgirba.com wrote: Please provide an easy Gofer script for loading your package.

Doru

On Thu, Apr 24, 2014 at 11:28 AM, Leo Perard leo.perard@gmail.com wrote: Hi,

I add a new vizualisation to the project. To test it, reload the configuration of the project and this message : TLTelescope class>>#onElement:withEdgesProperty:

Here an example :

| telescope | telescope := TLTelescope onElement: Collection withEdgesProperty: #subclasses. telescope open

This vizualisation is really dynamic and I like it, but as it's dynamic there are some bugs. The layout on right click on an element dont' work yet. I will try to fix them first. I like the idea of getting something really dynamic with Roassal2. Once you write your code to generate the graph you do not have to write lines again.

If you have ideas to improve this vizualisation, let me know them ;-)

On Tue, Apr 22, 2014 at 7:32 PM, Leo Perard leo.perard@gmail.com wrote: On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Cool animations!!!

We start to have a real and nice infrastructure. This is cool! Make a video and compete to the Roassal contest!

I will think about that !

If you have distribution map, why do you propose the tree layout since there is no edges?

Just experimentations. I'm working on edges and I don't know yet how the menu will evoluate.

Alexandre

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

-- Leo Perard

-- Leo Perard

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Leo Perard _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Leo Perard

-- Cheers, Leo Perard University of Lille 1 _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

It should be fix

On Thu, May 1, 2014 at 10:13 PM, Alexandre Bergel alexandre.bergel@me.comwrote:

Hi!

I am not sure how to load your tool.

...

ConfigurationOfTelescope load

=> does not work. ‘… Explicitely not defined …’

I’ve tried with #loadDevelopment but I get the following error:

Warning: This package depends on the following classes: TLCustomAction You must resolve these dependencies before you will be able to load these definitions: initialize

Cheers, Alexandre

On Apr 30, 2014, at 12:41 PM, Leo Perard leo.perard@gmail.com wrote:

...

Hi all,

some new features have been added, especially in the butterfly

vizualisation.

...

To load the project Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load. ConfigurationOfTelescope load

To play with it, you can check the examples in the class side of

TLTelescope but here some features you can test.

...

• for distribution map vizualisation

numberOfColors: let you set the number of items in the legend (the

default item is not counted)

...

• for butterfly vizualisation

expandToRank: expand the graph before opening the view (you don't have

the root node alone)

...

• for both of them

actionOnEntity:title: let you add an action on the entity with a menu on

right click (actionOnEntity: [ :e | e inspect ] title: 'Inspect' let you inspect the entity for example)

...

actionOnNode:title: let you add an action on the node with a menu on

right click ( actionOnNode: [ :n | n trachelShape color: Color random. n view canvas signalUpdate ] title: 'Change color' let you change the color of the node for example)

...

Full example | telescope | telescope := TLTelescope. telescope distributionMap onContainers: Collection withAllSubclasses elements: #authors properties: #yourself; numberOfColors: 5; actionOnNode: [ :n | n trachelShape color: Color blue. n view

canvas signalUpdate ] title: 'Color';

...

  open.

telescope butterfly root: Collection withProperty: #subclasses; expandToRank: 3; actionOnEntity: [ :e | e inspect ] title: 'Inspect'; open As you can see you can open several vizualisation in the same time.

I am sure that there is a lot of features for this dynamic

vizualisations so if you have some ideas let me know :-)

...

Some screenshot

<butterfly.png>

<distribution-map.png> ​ ​

On Thu, Apr 24, 2014 at 4:32 PM, Leo Perard leo.perard@gmail.com

wrote:

...

Yes I saw it, but I didn't use it because it works with stack as

Mondrian and I do not want somthing like that.

...

On Thu, Apr 24, 2014 at 3:45 PM, Alexandre Bergel <

alexandre.bergel@me.com> wrote:

...

Hi Leo,

Looks good!

Sergio, in Cc:, is working on a new kind of interaction to achieve

similar effect.

...

Sergio, how stable is your expand interaction?

@ Leo: in a couple of hours I will meet Sergio. We will try to include

his interaction in Roassal.

...

Alexandre

_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Apr 24, 2014, at 7:37 AM, Leo Perard leo.perard@gmail.com wrote:

...

Something like that is ok ?

Gofer new url: 'http://smalltalkhub.com/mc/LeoPerard/Telescope/main'; package: 'ConfigurationOfTelescope'; load.

ConfigurationOfTelescope load

On Thu, Apr 24, 2014 at 11:33 AM, Tudor Girba tudor@tudorgirba.com

wrote:

...

...

Please provide an easy Gofer script for loading your package.

Doru

On Thu, Apr 24, 2014 at 11:28 AM, Leo Perard leo.perard@gmail.com

wrote:

...

...

Hi,

I add a new vizualisation to the project. To test it, reload the configuration of the project and this message : TLTelescope class>>#onElement:withEdgesProperty:

Here an example :

| telescope | telescope := TLTelescope onElement: Collection withEdgesProperty:

#subclasses.

...

...

telescope open

This vizualisation is really dynamic and I like it, but as it's

dynamic there are some bugs. The layout on right click on an element dont' work yet. I will try to fix them first. I like the idea of getting something really dynamic with Roassal2. Once you write your code to generate the graph you do not have to write lines again.

...

...

If you have ideas to improve this vizualisation, let me know them ;-)

On Tue, Apr 22, 2014 at 7:32 PM, Leo Perard leo.perard@gmail.com

wrote:

...

...

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel <

alexandre.bergel@me.com> wrote:

...

...

Cool animations!!!

We start to have a real and nice infrastructure. This is cool! Make a video and compete to the Roassal contest!

I will think about that !

If you have distribution map, why do you propose the tree layout since

there is no edges?

...

...

Just experimentations. I'm working on edges and I don't know yet how

the menu will evoluate.

...

...

Alexandre

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

-- Leo Perard

-- Leo Perard

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Leo Perard _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Leo Perard

-- Cheers, Leo Perard University of Lille 1 _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev