roassal in the world menu

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

roassal in the world menu

Tudor Girba-2
Hi,

Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.

In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.

In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).

Alex, what do you say?

Cheers,
Doru


--
www.tudorgirba.com

"Yesterday is a fact.
 Tomorrow is a possibility.
 Today is a challenge."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

abergel
Yes, I can move the default roassal easel accessible from the Tools menu. I've just committed.

Another point.
What is the language supported by the glamour roassal easel? Currently, it uses the low API. A valid script is:

-=-=-=-=-=-=-=-=-=
| b |
b := ROMondrianViewBuilder view: view.
b nodes: (1 to: 20).
b applyLayout.
-=-=-=-=-=-=-=-=-=

shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?

Cheers,
Alexandre

On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:

> Hi,
>
> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>
> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>
> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>
> Alex, what do you say?
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

Tudor Girba-2
Hi,

On 2 Jun 2012, at 00:08, Alexandre Bergel wrote:

> Yes, I can move the default roassal easel accessible from the Tools menu. I've just committed.

Great, thanks.

> Another point.
> What is the language supported by the glamour roassal easel? Currently, it uses the low API. A valid script is:
>
> -=-=-=-=-=-=-=-=-=
> | b |
> b := ROMondrianViewBuilder view: view.
> b nodes: (1 to: 20).
> b applyLayout.
> -=-=-=-=-=-=-=-=-=

Indeed, this is the current case.

> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?

I think not. My idea was that the GLMMondrianEasel will be switched to the ROMondrianViewBuilder when it will work. Like this we can edit at both levels.

Or maybe we find another solution? Maybe we can just offer both view variables in the same Easel?

Cheers,
Doru



> Cheers,
> Alexandre
>
> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>
>> Hi,
>>
>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>
>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>
>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>
>> Alex, what do you say?
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Yesterday is a fact.
>> Tomorrow is a possibility.
>> Today is a challenge."
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"We can create beautiful models in a vacuum.
But, to get them effective we have to deal with the inconvenience of reality."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

abergel
>> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?
>
> I think not. My idea was that the GLMMondrianEasel will be switched to the ROMondrianViewBuilder when it will work. Like this we can edit at both levels.
>
> Or maybe we find another solution? Maybe we can just offer both view variables in the same Easel?

Maybe having view and roView. What would be a good name for the instance of ROView?

Alexandre

>
>
>
>> Cheers,
>> Alexandre
>>
>> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>>
>>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>>
>>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>>
>>> Alex, what do you say?
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Yesterday is a fact.
>>> Tomorrow is a possibility.
>>> Today is a challenge."
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "We can create beautiful models in a vacuum.
> But, to get them effective we have to deal with the inconvenience of reality."
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

Tudor Girba-2
Hi,


On 2 Jun 2012, at 00:24, Alexandre Bergel wrote:

>>> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?
>>
>> I think not. My idea was that the GLMMondrianEasel will be switched to the ROMondrianViewBuilder when it will work. Like this we can edit at both levels.
>>
>> Or maybe we find another solution? Maybe we can just offer both view variables in the same Easel?
>
> Maybe having view and roView. What would be a good name for the instance of ROView?

How about view and rawView?

Doru


> Alexandre
>
>>
>>
>>
>>> Cheers,
>>> Alexandre
>>>
>>> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>>>
>>>> Hi,
>>>>
>>>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>>>
>>>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>>>
>>>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>>>
>>>> Alex, what do you say?
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "We can create beautiful models in a vacuum.
>> But, to get them effective we have to deal with the inconvenience of reality."
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing should have the right to be different."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

Tudor Girba-2
Just a note:
When we accept something in the Easel, we tell the view variable to render.

If we get two variables, we need to get them to affect the same low level model, such that we can tell the rawView to render. This means that the ROMondrianViewBuilder should be changed to offer a reference to the underlying ROView.

Doru


On 2 Jun 2012, at 00:37, Tudor Girba wrote:

> Hi,
>
>
> On 2 Jun 2012, at 00:24, Alexandre Bergel wrote:
>
>>>> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?
>>>
>>> I think not. My idea was that the GLMMondrianEasel will be switched to the ROMondrianViewBuilder when it will work. Like this we can edit at both levels.
>>>
>>> Or maybe we find another solution? Maybe we can just offer both view variables in the same Easel?
>>
>> Maybe having view and roView. What would be a good name for the instance of ROView?
>
> How about view and rawView?
>
> Doru
>
>
>> Alexandre
>>
>>>
>>>
>>>
>>>> Cheers,
>>>> Alexandre
>>>>
>>>> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>>>>
>>>>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>>>>
>>>>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>>>>
>>>>> Alex, what do you say?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "Yesterday is a fact.
>>>>> Tomorrow is a possibility.
>>>>> Today is a challenge."
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel  http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "We can create beautiful models in a vacuum.
>>> But, to get them effective we have to deal with the inconvenience of reality."
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Every thing should have the right to be different."
>
>
>

--
www.tudorgirba.com

Innovation comes in least expected form.
That is, if it is expected, it already happened.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

abergel
Yep, easy:

view := ROMondrianViewBuilder new.
rawView := view container.

Here is an example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Preambule. It includes the initialization. "
| view rawView |
view := ROMondrianViewBuilder new.
rawView := view container.
"enter your script below"
"-------------"
"-------------"

rawView add: ROElement sprite.
view nodes: (1 to: 20).

"-------------"
"-------------"
"Below is the initiation of the menu and opening the visualization"
ROEaselMorphic new populateMenuOn: view.
view open
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Cheers,
Alexandre


On Jun 2, 2012, at 12:47 AM, Tudor Girba wrote:

> Just a note:
> When we accept something in the Easel, we tell the view variable to render.
>
> If we get two variables, we need to get them to affect the same low level model, such that we can tell the rawView to render. This means that the ROMondrianViewBuilder should be changed to offer a reference to the underlying ROView.
>
> Doru
>
>
> On 2 Jun 2012, at 00:37, Tudor Girba wrote:
>
>> Hi,
>>
>>
>> On 2 Jun 2012, at 00:24, Alexandre Bergel wrote:
>>
>>>>> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?
>>>>
>>>> I think not. My idea was that the GLMMondrianEasel will be switched to the ROMondrianViewBuilder when it will work. Like this we can edit at both levels.
>>>>
>>>> Or maybe we find another solution? Maybe we can just offer both view variables in the same Easel?
>>>
>>> Maybe having view and roView. What would be a good name for the instance of ROView?
>>
>> How about view and rawView?
>>
>> Doru
>>
>>
>>> Alexandre
>>>
>>>>
>>>>
>>>>
>>>>> Cheers,
>>>>> Alexandre
>>>>>
>>>>> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>>>>>
>>>>>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>>>>>
>>>>>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>>>>>
>>>>>> Alex, what do you say?
>>>>>>
>>>>>> Cheers,
>>>>>> Doru
>>>>>>
>>>>>>
>>>>>> --
>>>>>> www.tudorgirba.com
>>>>>>
>>>>>> "Yesterday is a fact.
>>>>>> Tomorrow is a possibility.
>>>>>> Today is a challenge."
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>> --
>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>> Alexandre Bergel  http://www.bergel.eu
>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "We can create beautiful models in a vacuum.
>>>> But, to get them effective we have to deal with the inconvenience of reality."
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing should have the right to be different."
>>
>>
>>
>
> --
> www.tudorgirba.com
>
> Innovation comes in least expected form.
> That is, if it is expected, it already happened.
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

Tudor Girba-2
Excellent. In this case, we actually do not even need two variables :). We just start from the MondrianViewBuilder and if someone wants the raw one, it can just access it from there.

Doru


On 4 Jun 2012, at 20:06, Alexandre Bergel wrote:

> Yep, easy:
>
> view := ROMondrianViewBuilder new.
> rawView := view container.
>
> Here is an example:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> "Preambule. It includes the initialization. "
> | view rawView |
> view := ROMondrianViewBuilder new.
> rawView := view container.
> "enter your script below"
> "-------------"
> "-------------"
>
> rawView add: ROElement sprite.
> view nodes: (1 to: 20).
>
> "-------------"
> "-------------"
> "Below is the initiation of the menu and opening the visualization"
> ROEaselMorphic new populateMenuOn: view.
> view open
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> Cheers,
> Alexandre
>
>
> On Jun 2, 2012, at 12:47 AM, Tudor Girba wrote:
>
>> Just a note:
>> When we accept something in the Easel, we tell the view variable to render.
>>
>> If we get two variables, we need to get them to affect the same low level model, such that we can tell the rawView to render. This means that the ROMondrianViewBuilder should be changed to offer a reference to the underlying ROView.
>>
>> Doru
>>
>>
>> On 2 Jun 2012, at 00:37, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>>
>>> On 2 Jun 2012, at 00:24, Alexandre Bergel wrote:
>>>
>>>>>> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?
>>>>>
>>>>> I think not. My idea was that the GLMMondrianEasel will be switched to the ROMondrianViewBuilder when it will work. Like this we can edit at both levels.
>>>>>
>>>>> Or maybe we find another solution? Maybe we can just offer both view variables in the same Easel?
>>>>
>>>> Maybe having view and roView. What would be a good name for the instance of ROView?
>>>
>>> How about view and rawView?
>>>
>>> Doru
>>>
>>>
>>>> Alexandre
>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Cheers,
>>>>>> Alexandre
>>>>>>
>>>>>> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>>>>>>
>>>>>>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>>>>>>
>>>>>>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>>>>>>
>>>>>>> Alex, what do you say?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Doru
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> www.tudorgirba.com
>>>>>>>
>>>>>>> "Yesterday is a fact.
>>>>>>> Tomorrow is a possibility.
>>>>>>> Today is a challenge."
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Moose-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>> --
>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>>> Alexandre Bergel  http://www.bergel.eu
>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "We can create beautiful models in a vacuum.
>>>>> But, to get them effective we have to deal with the inconvenience of reality."
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel  http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing should have the right to be different."
>>>
>>>
>>>
>>
>> --
>> www.tudorgirba.com
>>
>> Innovation comes in least expected form.
>> That is, if it is expected, it already happened.
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Value is always contextual."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

Ben Coman
In reply to this post by abergel
Following up from a while a go...

In yesterday's Moose 4.7 I see that Roassal Easel is at the top of the Tools menu - right where I always go to get the Finder.
Perhaps Roassal Easel could be moved down next to Modrian Easel ?

cheer -ben


Alexandre Bergel wrote:
Yes, I can move the default roassal easel accessible from the Tools menu. I've just committed.

Another point.
What is the language supported by the glamour roassal easel? Currently, it uses the low API. A valid script is:

-=-=-=-=-=-=-=-=-=
| b |
b := ROMondrianViewBuilder view: view.
b nodes: (1 to: 20).
b applyLayout.
-=-=-=-=-=-=-=-=-=

shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?

Cheers,
Alexandre

On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:

  
Hi,

Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.

In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.

In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).

Alex, what do you say?

Cheers,
Doru


--
www.tudorgirba.com

"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."

_______________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

abergel
I have now added it below the Finder menu.
I actually like to have it at the top of the menu.
Can someone else give his opinion.

Cheers,
Alexandre


On Jun 17, 2012, at 4:47 AM, Ben Coman wrote:

> Following up from a while a go...
>
> In yesterday's Moose 4.7 I see that Roassal Easel is at the top of the Tools menu - right where I always go to get the Finder.
> Perhaps Roassal Easel could be moved down next to Modrian Easel ?
>
> cheer -ben
>
>
> Alexandre Bergel wrote:
>> Yes, I can move the default roassal easel accessible from the Tools menu. I've just committed.
>>
>> Another point.
>> What is the language supported by the glamour roassal easel? Currently, it uses the low API. A valid script is:
>>
>> -=-=-=-=-=-=-=-=-=
>> | b |
>> b := ROMondrianViewBuilder view: view.
>> b nodes: (1 to: 20).
>> b applyLayout.
>> -=-=-=-=-=-=-=-=-=
>>
>> shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?
>>
>> Cheers,
>> Alexandre
>>
>> On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:
>>
>>  
>>
>>> Hi,
>>>
>>> Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
>>>
>>> In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
>>>
>>> In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
>>>
>>> Alex, what do you say?
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> --
>>>
>>> www.tudorgirba.com
>>>
>>>
>>> "Yesterday is a fact.
>>> Tomorrow is a possibility.
>>> Today is a challenge."
>>>
>>> _______________________________________________
>>> 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

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: roassal in the world menu

Ben Coman
You would have got used to it there. 
I doubly appreciate the change then.

Alexandre Bergel wrote:
I have now added it below the Finder menu.
I actually like to have it at the top of the menu. 
Can someone else give his opinion.

Cheers,
Alexandre


On Jun 17, 2012, at 4:47 AM, Ben Coman wrote:

  
Following up from a while a go...

In yesterday's Moose 4.7 I see that Roassal Easel is at the top of the Tools menu - right where I always go to get the Finder.
Perhaps Roassal Easel could be moved down next to Modrian Easel ?

cheer -ben


Alexandre Bergel wrote:
    
Yes, I can move the default roassal easel accessible from the Tools menu. I've just committed.

Another point.
What is the language supported by the glamour roassal easel? Currently, it uses the low API. A valid script is:

-=-=-=-=-=-=-=-=-=
| b |
b := ROMondrianViewBuilder view: view.
b nodes: (1 to: 20).
b applyLayout.
-=-=-=-=-=-=-=-=-=

shouldn't view be bound to an instance of ROMondrianViewBuilder rather than to ROView?

Cheers,
Alexandre

On Jun 1, 2012, at 10:04 PM, Tudor Girba wrote:

  

      
Hi,

Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.

In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.

In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).

Alex, what do you say?

Cheers,
Doru


--

www.tudorgirba.com


"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."

_______________________________________________
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
    

  


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