17 Nov
2014
17 Nov
'14
5:14 p.m.
Dear All,
i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my
Tool/Project. Today i tried
to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
changed a lot.
Is there a list what has changed/what was removed/what are the
alternatives/...?
Some examples
view := ROMondrianViewBuilder *titled*: 'asdasd'.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
Anther question:
How can i change the line thickness of a Mondrian Node? I find the
default size is to thick.
BW,
Volkert
17 Nov
17 Nov
11:06 p.m.
Tomorrow I will provide a detailed answer.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de wrote:
Dear All,
i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my Tool/Project.
Today i tried
to migrate my work to Roassal2 and found out, that the Interface of RTMondrianViewBuilder
has
changed a lot.
Is there a list what has changed/what was removed/what are the alternatives/...?
Some examples
view := ROMondrianViewBuilder titled: 'asdasd'.
view shape rectangle withText: #shortName; textVerticalPadding: -10; fontSize:
6.
view addMenu: 'Zoom in' callBack: [ :stack | … ].
Anther question:
How can i change the line thickness of a Mondrian Node? I find the default size is to
thick.
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
19 Nov
19 Nov
4:55 p.m.
Alexandre, any hints/advice for me?
BW,
Volkert
Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
Tomorrow I will provide a detailed answer.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
Dear All,
i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in
my Tool/Project. Today i tried
to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
changed a lot.
Is there a list what has changed/what was removed/what are the
alternatives/...?
Some examples
view := ROMondrianViewBuilder *titled*: 'asdasd'.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
Anther question:
How can i change the line thickness of a Mondrian Node? I find the
default size is to thick.
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
6:58 p.m.
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1. However, we are here
to help!
>> view := ROMondrianViewBuilder titled:
'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>> view shape rectangle withText:
#shortName; textVerticalPadding: -10; fontSize: 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go incrementally.
>> view addMenu: 'Zoom in'
callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de wrote:
>
> Alexandre, any hints/advice for me?
>
> BW,
> Volkert
>
> Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
>> Tomorrow I will provide a detailed answer.
>>
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>> On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
>>>
>>> Dear All,
>>>
>>> i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my
Tool/Project. Today i tried
>>> to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
>>> changed a lot.
>>>
>>> Is there a list what has changed/what was removed/what are the
alternatives/...?
>>>
>>> Some examples
>>>
>>> view := ROMondrianViewBuilder titled: 'asdasd'.
>>>
>>> view shape rectangle withText: #shortName; textVerticalPadding: -10;
fontSize: 6.
>>>
>> view addMenu: 'Zoom in'
callBack: [ :stack | … ].
>>
>>> Anther question:
>>>
>>> How can i change the line thickness of a Mondrian Node? I find the default
size is to thick.
>>>
>>> BW,
>>>
>>> Volkert
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>
> --
> www.nivoba.de <http://www.nivoba.de/>
>
> "The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
20 Nov
20 Nov
8:24 p.m.
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1.
However, we are here to help!
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
>> view := ROMondrianViewBuilder *titled*:
'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>> view shape rectangle *withText*:
#shortName; *textVerticalPadding*:
>> -10; *fontSize*: 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go
incrementally.
>>
>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
Alexandre, any hints/advice for me?
BW,
Volkert
Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Tomorrow I will provide a detailed answer.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
Dear All,
i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1
in my Tool/Project. Today i tried
to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
changed a lot.
Is there a list what has changed/what was removed/what are the
alternatives/...?
Some examples
view := ROMondrianViewBuilder *titled*: 'asdasd'.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
Anther question:
How can i change the line thickness of a Mondrian Node? I find the
default size is to thick.
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
8:55 p.m.
Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 20, 2014, at 4:24 PM, volkert(a)nivoba.de wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1. However, we are here
to help!
--
www.nivoba.de <http://www.nivoba.de/>
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> view := ROMondrianViewBuilder
titled: 'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>> view shape rectangle withText:
#shortName; textVerticalPadding: -10; fontSize: 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go incrementally.
>> view addMenu: 'Zoom in'
callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de <mailto:volkert@nivoba.de>
wrote:
>
> Alexandre, any hints/advice for me?
>
> BW,
> Volkert
>
> Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
>> Tomorrow I will provide a detailed answer.
>>
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>> On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
>>>
>>> Dear All,
>>>
>>> i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my
Tool/Project. Today i tried
>>> to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
>>> changed a lot.
>>>
>>> Is there a list what has changed/what was removed/what are the
alternatives/...?
>>>
>>> Some examples
>>>
>>> view := ROMondrianViewBuilder titled: 'asdasd'.
>>>
>>> view shape rectangle withText: #shortName; textVerticalPadding: -10;
fontSize: 6.
>>>
>> view addMenu: 'Zoom in'
callBack: [ :stack | … ].
>>
>>> Anther question:
>>>
>>> How can i change the line thickness of a Mondrian Node? I find the default
size is to thick.
>>>
>>> BW,
>>>
>>> Volkert
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>
> --
> www.nivoba.de <http://www.nivoba.de/>
>
> "The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
22 Nov
22 Nov
5:16 p.m.
Dear Alexandre, i updated Roassal2, but see no changes.
I also started with a fresh Pharo 3.0 Image.
Maybe i made a mistake. See:
Loading ConfigurationOfRoassal2 did not resolve all dependencies to
packages needed
for running Roassal2 in Pharo 3.0. I think it is Glamour, GTPlayground,
GTInspector, ... But i am
not sure, what package to load here, so i tried to load the whole
GTookit. Everything works, but
the GToolkit load Roassal2 by itself (??)
So my question: What package do need to load for a working Roassal2?
May be, the dependencies should be handled in ConfigurationOfRoassal2.
BW,
Volkert
Am 20.11.2014 um 20:55 schrieb Alexandre Bergel:
Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
On Nov 20, 2014, at 4:24 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1.
However, we are here to help!
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> view := ROMondrianViewBuilder
*titled*: 'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>> view shape rectangle *withText*:
#shortName;
>> *textVerticalPadding*: -10; *fontSize*: 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go
incrementally.
>>
>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de
> <mailto:volkert@nivoba.de> wrote:
>
> Alexandre, any hints/advice for me?
>
> BW,
> Volkert
>
> Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
>> Tomorrow I will provide a detailed answer.
>>
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>> On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
>>> <mailto:volkert@nivoba.de> wrote:
>>>
>>> Dear All,
>>>
>>> i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1
>>> in my Tool/Project. Today i tried
>>> to migrate my work to Roassal2 and found out, that the Interface
>>> of RTMondrianViewBuilder has
>>> changed a lot.
>>>
>>> Is there a list what has changed/what was removed/what are the
>>> alternatives/...?
>>>
>>> Some examples
>>>
>>> view := ROMondrianViewBuilder *titled*: 'asdasd'.
>>>
>> view shape rectangle *withText*:
#shortName;
>> *textVerticalPadding*: -10; *fontSize*: 6.
>>
>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>
>>> Anther question:
>>>
>>> How can i change the line thickness of a Mondrian Node? I find
>>> the default size is to thick.
>>>
>>> BW,
>>>
>>> Volkert
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.nivoba.de
>
> "The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 
5:28 p.m.
Hi,
Indeed, we are in a bit of a situation here. The examples of Roassal could
go in a separate package as they are specific to GTInspector Core (the one
that does not depend on Roassal). In Pharo 4, GT Core is part of the
default image, so this won't be an issue anymore, but it is an issue for
Pharo 3.
Cheers,
Doru
On Sat, Nov 22, 2014 at 5:16 PM, volkert(a)nivoba.de <volkert(a)nivoba.de>
wrote:
Dear Alexandre, i updated Roassal2, but see no
changes.
I also started with a fresh Pharo 3.0 Image.
Maybe i made a mistake. See:
Loading ConfigurationOfRoassal2 did not resolve all dependencies to
packages needed
for running Roassal2 in Pharo 3.0. I think it is Glamour, GTPlayground,
GTInspector, ... But i am
not sure, what package to load here, so i tried to load the whole GTookit.
Everything works, but
the GToolkit load Roassal2 by itself (??)
So my question: What package do need to load for a working Roassal2?
May be, the dependencies should be handled in ConfigurationOfRoassal2.
BW,
Volkert
Am 20.11.2014 um 20:55 schrieb Alexandre Bergel:
Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 20, 2014, at 4:24 PM, volkert(a)nivoba.de wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1.
However, we are here to help!
view := ROMondrianViewBuilder *titled*: 'asdasd’.
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go
incrementally.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de wrote:
Alexandre, any hints/advice for me?
BW,
Volkert
Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
Tomorrow I will provide a detailed answer.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de wrote:
Dear All,
i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my
Tool/Project. Today i tried
to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
changed a lot.
Is there a list what has changed/what was removed/what are the
alternatives/...?
Some examples
view := ROMondrianViewBuilder *titled*: 'asdasd'.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
Anther question:
How can i change the line thickness of a Mondrian Node? I find the default
size is to thick.
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
5:34 p.m.
Understand. But what is now the best way to load Roassal2 with all its
depending packages
into a Pharo 3.0 Image?
BW,
Volkert
Am 22.11.2014 um 17:28 schrieb Tudor Girba:
Hi,
Indeed, we are in a bit of a situation here. The examples of Roassal
could go in a separate package as they are specific to GTInspector
Core (the one that does not depend on Roassal). In Pharo 4, GT Core is
part of the default image, so this won't be an issue anymore, but it
is an issue for Pharo 3.
Cheers,
Doru
On Sat, Nov 22, 2014 at 5:16 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> <volkert(a)nivoba.de
<mailto:volkert@nivoba.de>> wrote:
Dear Alexandre, i updated Roassal2, but see no changes.
I also started with a fresh Pharo 3.0 Image.
Maybe i made a mistake. See:
Loading ConfigurationOfRoassal2 did not resolve all dependencies
to packages needed
for running Roassal2 in Pharo 3.0. I think it is Glamour,
GTPlayground, GTInspector, ... But i am
not sure, what package to load here, so i tried to load the whole
GTookit. Everything works, but
the GToolkit load Roassal2 by itself (??)
So my question: What package do need to load for a working Roassal2?
May be, the dependencies should be handled in ConfigurationOfRoassal2.
BW,
Volkert
Am 20.11.2014 um 20:55 schrieb Alexandre Bergel:
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
--
www.nivoba.de <http://www.nivoba.de>
"The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev On Nov 20, 2014, at 4:24 PM,
volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with
Roassal1. However, we are here to help!
>>> view := ROMondrianViewBuilder *titled*: 'asdasd’.
>>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>>> view shape rectangle *withText*: #shortName;
>>> *textVerticalPadding*: -10; *fontSize*: 6.
>>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go
incrementally.
>>>
>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de
> <mailto:volkert@nivoba.de> wrote:
>
> Alexandre, any hints/advice for me?
>
> BW,
> Volkert
>
> Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
>> Tomorrow I will provide a detailed answer.
>>
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>> On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
>>> <mailto:volkert@nivoba.de> wrote:
>>>
>>> Dear All,
>>>
>>> i am using heavily Mondrian (ROMondrianViewBuilder) from
>>> Roassal1 in my Tool/Project. Today i tried
>>> to migrate my work to Roassal2 and found out, that the
>>> Interface of RTMondrianViewBuilder has
>>> changed a lot.
>>>
>>> Is there a list what has changed/what was removed/what are
>>> the alternatives/...?
>>>
>>> Some examples
>>>
>>> view := ROMondrianViewBuilder *titled*: 'asdasd'.
>>>
>>> view shape rectangle *withText*: #shortName;
>>> *textVerticalPadding*: -10; *fontSize*: 6.
>>>
>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>
>>> Anther question:
>>>
>>> How can i change the line thickness of a Mondrian Node? I
>>> find the default size is to thick.
>>>
>>> BW,
>>>
>>> Volkert
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.nivoba.de <http://www.nivoba.de/>
>
> "The more complex an object, the larger the investment in learning to use
it, and the greater the resistance to abandon it.", NW
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.nivoba.de <http://www.nivoba.de/>
"The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5:45 p.m.
You could load the complete GToolkit:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadDevelopment
Not ideal, but it should work. You can also take the ready made image:
https://ci.inria.fr/moose/job/gtoolkit/lastSuccessfulBuild/artifact/gtoolki…
Or you can simply take the Moose image:
https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-…
Cheers,
Doru
On Sat, Nov 22, 2014 at 5:34 PM, volkert(a)nivoba.de <volkert(a)nivoba.de>
wrote:
Understand. But what is now the best way to load
Roassal2 with all its
depending packages
into a Pharo 3.0 Image?
BW,
Volkert
Am 22.11.2014 um 17:28 schrieb Tudor Girba:
Hi,
Indeed, we are in a bit of a situation here. The examples of Roassal
could go in a separate package as they are specific to GTInspector Core
(the one that does not depend on Roassal). In Pharo 4, GT Core is part of
the default image, so this won't be an issue anymore, but it is an issue
for Pharo 3.
Cheers,
Doru
On Sat, Nov 22, 2014 at 5:16 PM, volkert(a)nivoba.de <volkert(a)nivoba.de>
wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
Dear Alexandre, i updated Roassal2, but see no
changes.
I also started with a fresh Pharo 3.0 Image.
Maybe i made a mistake. See:
Loading ConfigurationOfRoassal2 did not resolve all dependencies to
packages needed
for running Roassal2 in Pharo 3.0. I think it is Glamour, GTPlayground,
GTInspector, ... But i am
not sure, what package to load here, so i tried to load the whole
GTookit. Everything works, but
the GToolkit load Roassal2 by itself (??)
So my question: What package do need to load for a working Roassal2?
May be, the dependencies should be handled in ConfigurationOfRoassal2.
BW,
Volkert
Am 20.11.2014 um 20:55 schrieb Alexandre Bergel:
Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 20, 2014, at 4:24 PM, volkert(a)nivoba.de wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1.
However, we are here to help!
view := ROMondrianViewBuilder *titled*: 'asdasd’.
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go
incrementally.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de wrote:
Alexandre, any hints/advice for me?
BW,
Volkert
Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
Tomorrow I will provide a detailed answer.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de wrote:
Dear All,
i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my
Tool/Project. Today i tried
to migrate my work to Roassal2 and found out, that the Interface of
RTMondrianViewBuilder has
changed a lot.
Is there a list what has changed/what was removed/what are the
alternatives/...?
Some examples
view := ROMondrianViewBuilder *titled*: 'asdasd'.
view shape rectangle *withText*: #shortName;
*textVerticalPadding*: -10; *fontSize*: 6.
view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
Anther question:
How can i change the line thickness of a Mondrian Node? I find the
default size is to thick.
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5:48 p.m.
Ok, loading the GToolkit is what i am doing.
Thank you,
Volkert
Am 22.11.2014 um 17:45 schrieb Tudor Girba:
You could load the complete GToolkit:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadDevelopment
Not ideal, but it should work. You can also take the ready made image:
https://ci.inria.fr/moose/job/gtoolkit/lastSuccessfulBuild/artifact/gtoolki…
Or you can simply take the Moose image:
https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-…
Cheers,
Doru
On Sat, Nov 22, 2014 at 5:34 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> <volkert(a)nivoba.de
<mailto:volkert@nivoba.de>> wrote:
Understand. But what is now the best way to load Roassal2 with all
its depending packages
into a Pharo 3.0 Image?
BW,
Volkert
Am 22.11.2014 um 17:28 schrieb Tudor Girba:
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
Hi,
Indeed, we are in a bit of a situation here. The examples of
Roassal could go in a separate package as they are specific to
GTInspector Core (the one that does not depend on Roassal). In
Pharo 4, GT Core is part of the default image, so this won't be
an issue anymore, but it is an issue for Pharo 3.
Cheers,
Doru
On Sat, Nov 22, 2014 at 5:16 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> <volkert(a)nivoba.de
<mailto:volkert@nivoba.de>> wrote:
Dear Alexandre, i updated Roassal2, but see no changes.
I also started with a fresh Pharo 3.0 Image.
Maybe i made a mistake. See:
Loading ConfigurationOfRoassal2 did not resolve all
dependencies to packages needed
for running Roassal2 in Pharo 3.0. I think it is Glamour,
GTPlayground, GTInspector, ... But i am
not sure, what package to load here, so i tried to load the
whole GTookit. Everything works, but
the GToolkit load Roassal2 by itself (??)
So my question: What package do need to load for a working
Roassal2?
May be, the dependencies should be handled in
ConfigurationOfRoassal2.
BW,
Volkert
Am 20.11.2014 um 20:55 schrieb Alexandre Bergel:
--
www.nivoba.de <http://www.nivoba.de>
"The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
--
www.nivoba.de <http://www.nivoba.de>
"The more complex an object, the larger the investment in learning to use
it, and the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev On Nov 20, 2014, at 4:24 PM,
volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
> Hi Volkert,
>
> Sorry for replying late. This is a rather busy time for me.
> As you have noticed, Roassal2 is not fully compatible with
> Roassal1. However, we are here to help!
>
>>>> view := ROMondrianViewBuilder *titled*: 'asdasd’.
>>>>
>
> This now works (you need to update Roassal2):
>
> view := RTMondrianViewBuilder titled: 'asdasd’.
>
>>>> view shape rectangle *withText*: #shortName;
>>>> *textVerticalPadding*: -10; *fontSize*: 6.
>>>>
> Unfortunately, this is not supported yet.
> What you can do is
> view shape rectangle width: 50; text: #shortName; fontSize: 6.
>
> No text padding for now. Is it okay however? The idea is
> to go incrementally.
>>>>
>>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>>
>
> you can do:
>
> view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
>
> Please, report things that are missing. This is very
> important :-)
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>> On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de
>> <mailto:volkert@nivoba.de> wrote:
>>
>> Alexandre, any hints/advice for me?
>>
>> BW,
>> Volkert
>>
>> Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
>>> Tomorrow I will provide a detailed answer.
>>>
>>> Alexandre
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel http://www.bergel.eu
>>> <http://www.bergel.eu/>
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>>> On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
>>>> <mailto:volkert@nivoba.de> wrote:
>>>>
>>>> Dear All,
>>>>
>>>> i am using heavily Mondrian (ROMondrianViewBuilder)
>>>> from Roassal1 in my Tool/Project. Today i tried
>>>> to migrate my work to Roassal2 and found out, that the
>>>> Interface of RTMondrianViewBuilder has
>>>> changed a lot.
>>>>
>>>> Is there a list what has changed/what was removed/what
>>>> are the alternatives/...?
>>>>
>>>> Some examples
>>>>
>>>> view := ROMondrianViewBuilder *titled*: 'asdasd'.
>>>>
>>>> view shape rectangle *withText*: #shortName;
>>>> *textVerticalPadding*: -10; *fontSize*: 6.
>>>>
>>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>>
>>>> Anther question:
>>>>
>>>> How can i change the line thickness of a Mondrian Node?
>>>> I find the default size is to thick.
>>>>
>>>> BW,
>>>>
>>>> Volkert
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.nivoba.de <http://www.nivoba.de/>
>>
>> "The more complex an object, the larger the investment in learning
to use it, and the greater the resistance to abandon it.", NW
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.nivoba.de <http://www.nivoba.de/>
"The more complex an object, the larger the investment in learning to use
it, and the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5:30 p.m.
Sorry, found the changes .... ;-)
But the other point is still valid ;-)
Am 22.11.2014 um 17:16 schrieb volkert(a)nivoba.de:
Dear Alexandre, i updated Roassal2, but see no
changes.
I also started with a fresh Pharo 3.0 Image.
Maybe i made a mistake. See:
Loading ConfigurationOfRoassal2 did not resolve all dependencies to
packages needed
for running Roassal2 in Pharo 3.0. I think it is Glamour,
GTPlayground, GTInspector, ... But i am
not sure, what package to load here, so i tried to load the whole
GTookit. Everything works, but
the GToolkit load Roassal2 by itself (??)
So my question: What package do need to load for a working Roassal2?
May be, the dependencies should be handled in ConfigurationOfRoassal2.
BW,
Volkert
Am 20.11.2014 um 20:55 schrieb Alexandre Bergel:
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
Ok, let us know!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev On Nov 20, 2014, at 4:24 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
No worries. I will have a look tomorrow and give you feedback.
Thank you,
Volkert
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with
Roassal1. However, we are here to help!
>>> view := ROMondrianViewBuilder *titled*: 'asdasd’.
>>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>>> view shape rectangle *withText*: #shortName;
>>> *textVerticalPadding*: -10; *fontSize*: 6.
>>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea is to go
incrementally.
>>>
>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
Please, report things that are missing. This is very important :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Nov 19, 2014, at 12:55 PM, volkert(a)nivoba.de
> <mailto:volkert@nivoba.de> wrote:
>
> Alexandre, any hints/advice for me?
>
> BW,
> Volkert
>
> Am 17.11.2014 um 23:06 schrieb Alexandre Bergel:
>> Tomorrow I will provide a detailed answer.
>>
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>> On Nov 17, 2014, at 1:14 PM, volkert(a)nivoba.de
>>> <mailto:volkert@nivoba.de> wrote:
>>>
>>> Dear All,
>>>
>>> i am using heavily Mondrian (ROMondrianViewBuilder) from
>>> Roassal1 in my Tool/Project. Today i tried
>>> to migrate my work to Roassal2 and found out, that the Interface
>>> of RTMondrianViewBuilder has
>>> changed a lot.
>>>
>>> Is there a list what has changed/what was removed/what are the
>>> alternatives/...?
>>>
>>> Some examples
>>>
>>> view := ROMondrianViewBuilder *titled*: 'asdasd'.
>>>
>>> view shape rectangle *withText*: #shortName;
>>> *textVerticalPadding*: -10; *fontSize*: 6.
>>>
>>> view *addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>>
>>> Anther question:
>>>
>>> How can i change the line thickness of a Mondrian Node? I find
>>> the default size is to thick.
>>>
>>> BW,
>>>
>>> Volkert
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.nivoba.de
>
> "The more complex an object, the larger the investment in learning to use it,
and the greater the resistance to abandon it.", NW
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and
the greater the resistance to abandon it.", NW
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
7:05 p.m.
Dear Alexandre
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
view shape rectangle width: 50; text: #shortName; fontSize: 6.
=> MessageNotUnderstood: RTBox>>text:
Works, but the Menu looks not very appetizing. ;-)
BW,
Volkert
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1.
However, we are here to help!
Works fine.
>> view := ROMondrianViewBuilder *titled*:
'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>> view
shape rectangle *withText*: #shortName; *textVerticalPadding*:
>> -10; *fontSize*: 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The idea
is to go
incrementally.
Make sense, but this is an issue for me. I need a way to give a
node a
title.
Here an example how it currently looks like
>> view
*addMenu*: 'Zoom in' callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
25 Nov
25 Nov
12:48 a.m.
Hi Volkert,
I worked on the shape and title issue.
Update Roassal and try the following:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
b := RTMondrianViewBuilder new.
b shape rectangle withTextAbove.
b nodes: RTShape withAllSubclasses forEach: [:cls |
b shape rectangle color: Color white; size: #numberOfLinesOfCode.
b nodes: cls methods. b gridLayout ].
b flowLayout.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I have the impression this will fulfill your need. Let me know how it goes!
Cheers,
Alexandre
On Nov 22, 2014, at 2:05 PM, volkert(a)nivoba.de wrote:
Dear Alexandre
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
view shape rectangle width: 50; text: #shortName; fontSize: 6.
=> MessageNotUnderstood: RTBox>>text:
Works, but the Menu looks not very appetizing. ;-)
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1. However, we are here
to help!
Works fine.
>> view := ROMondrianViewBuilder
titled: 'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>>
>> view shape rectangle withText: #shortName; textVerticalPadding: -10;
fontSize: 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The
idea is to go incrementally.
Make sense, but this is an issue for me. I need a way
to give a node a title.
Here an example how it currently looks like
<Mail Attachment.png>
>>
>> view addMenu: 'Zoom in' callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
7:21 a.m.
Nice. I will check it.
Many thanks,
Volkert
Am 25.11.2014 um 00:48 schrieb Alexandre Bergel:
Hi Volkert,
I worked on the shape and title issue.
Update Roassal and try the following:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
b := RTMondrianViewBuilder new.
b shape rectangle withTextAbove.
b nodes: RTShape withAllSubclasses forEach: [:cls |
b shape rectangle color: Color white; size: #numberOfLinesOfCode.
b nodes: cls methods. b gridLayout ].
b flowLayout.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I have the impression this will fulfill your need. Let me know how it
goes!
Cheers,
Alexandre
--
www.nivoba.de
"The more complex an object, the larger the investment in learning to use it, and the
greater the resistance to abandon it.", NW
On Nov 22, 2014, at 2:05 PM, volkert(a)nivoba.de
<mailto:volkert@nivoba.de> wrote:
Dear Alexandre
Am 19.11.2014 um 18:58 schrieb Alexandre Bergel:
view shape rectangle width: 50; text: #shortName; fontSize: 6.
=> MessageNotUnderstood: RTBox>>text:
Works, but the Menu looks not very appetizing. ;-)
BW,
Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dieser Nachrichteninhalt wird auf Anfrage komplett heruntergeladen. Hi Volkert,
Sorry for replying late. This is a rather busy time for me.
As you have noticed, Roassal2 is not fully compatible with Roassal1.
However, we are here to help!
Works fine.
>> view := ROMondrianViewBuilder
titled: 'asdasd’.
>>
This now works (you need to update Roassal2):
view := RTMondrianViewBuilder titled: 'asdasd’.
>>
>> view shape
>> rectangle withText: #shortName; textVerticalPadding: -10; fontSize:
>> 6.
>>
Unfortunately, this is not supported yet.
What you can do is
view shape rectangle width: 50; text: #shortName; fontSize: 6.
No text padding for now. Is it okay however? The
idea is to go
incrementally.
Make sense, but this is an issue for me. I need a way to give a
node
a title.
Here an example how it currently looks like
<Mail Attachment.png>
>>
>> view addMenu: 'Zoom in' callBack: [ :stack | … ].
>>
you can do:
view view addMenu: ‘Zoom in’ callback: [ “do your stuff” ]
3904
days inactive
3912
days old
14 comments
3 participants
participants (3)
-
Alexandre Bergel -
Tudor Girba -
volkert＠nivoba.de