22 Nov
2014
22 Nov
'14
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