Telescope - Vizualisation using Roassal2

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
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 <[hidden email]> wrote:

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

forgot to add that I used PharoLauncher to download the image

On Tue, Apr 22, 2014 at 1:41 PM, kilon alios <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> wrote:

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 <[hidden email]> wrote:

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel <[hidden email]> 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

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 <[hidden email]> wrote:

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Please provide an easy Gofer script for loading your package.

Doru

On Thu, Apr 24, 2014 at 11:28 AM, Leo Perard <[hidden email]> 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 <[hidden email]> wrote:

On Tue, Apr 22, 2014 at 7:05 PM, Alexandre Bergel <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev