Smalltalk › Frameworks & Tools › Moose

roassal2 support for menus

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Tudor Girba-2

roassal2 support for menus

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.

We either

- add RTInteractionBuilder>>menu: or,

- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

www.tudorgirba.com

"Every thing has its own flow"

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

jfabry

Re: roassal2 support for menus

FWIW, I would prefer putting it in the builder. Putting things in Object always makes me shiver ...

On Sep 29, 2014, at 1:50 AM, Tudor Girba <[hidden email]> wrote:

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.
We either
- add RTInteractionBuilder>>menu: or,
- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

--
www.tudorgirba.com

"Every thing has its own flow"

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

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

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

abergel

Re: roassal2 support for menus

In reply to this post by Tudor Girba-2

I will try to work on this today.

Alexandre

Le 28-09-2014 à 21:50, Tudor Girba <[hidden email]> a écrit :

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.
We either
- add RTInteractionBuilder>>menu: or,
- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

--
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

Tudor Girba-2

Re: roassal2 support for menus

In reply to this post by jfabry

What makes you shiver in this case?

Object already defines its menu.

Cheers,

Doru

On Mon, Sep 29, 2014 at 1:41 PM, Johan Fabry <[hidden email]> wrote:

FWIW, I would prefer putting it in the builder. Putting things in Object always makes me shiver ...

On Sep 29, 2014, at 1:50 AM, Tudor Girba <[hidden email]> wrote:

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.
We either
- add RTInteractionBuilder>>menu: or,
- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

--
www.tudorgirba.com

"Every thing has its own flow"

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

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
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

jfabry

Re: roassal2 support for menus

That makes me shiver as well ;-) In Pharo 3 this luckily is not the case.

I just have the philosophy to try and avoid putting things high in the hierarchy to make things high up as simple as possible (but not simpler ;-) ). This even considering class extensions.

In this case, we can put the responsibility for some Roassal thingy in a Roassal builder so I would put that feature (and the added complexity) there.

On Sep 29, 2014, at 10:23 AM, Tudor Girba <[hidden email]> wrote:

What makes you shiver in this case?

Object already defines its menu.

Cheers,
Doru

On Mon, Sep 29, 2014 at 1:41 PM, Johan Fabry <[hidden email]> wrote:

FWIW, I would prefer putting it in the builder. Putting things in Object always makes me shiver ...

On Sep 29, 2014, at 1:50 AM, Tudor Girba <[hidden email]> wrote:

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.
We either
- add RTInteractionBuilder>>menu: or,
- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

--
www.tudorgirba.com

"Every thing has its own flow"

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

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
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

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

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

Tudor Girba-2

Re: roassal2 support for menus

Hi,

I think you are misunderstanding this issue. This is not high in the hierarchy. In the Moose image, every object can offer a menu of possible actions. Hence, it is an Object responsibility. Just like inspect is the object responsibility.

Cheers,

Doru

On Mon, Sep 29, 2014 at 4:34 PM, Johan Fabry <[hidden email]> wrote:

That makes me shiver as well ;-) In Pharo 3 this luckily is not the case.

I just have the philosophy to try and avoid putting things high in the hierarchy to make things high up as simple as possible (but not simpler ;-) ). This even considering class extensions.

In this case, we can put the responsibility for some Roassal thingy in a Roassal builder so I would put that feature (and the added complexity) there.

On Sep 29, 2014, at 10:23 AM, Tudor Girba <[hidden email]> wrote:

What makes you shiver in this case?

Object already defines its menu.

Cheers,
Doru

On Mon, Sep 29, 2014 at 1:41 PM, Johan Fabry <[hidden email]> wrote:

FWIW, I would prefer putting it in the builder. Putting things in Object always makes me shiver ...

On Sep 29, 2014, at 1:50 AM, Tudor Girba <[hidden email]> wrote:

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.
We either
- add RTInteractionBuilder>>menu: or,
- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

--
www.tudorgirba.com

"Every thing has its own flow"

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

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
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

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
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

jfabry

Re: roassal2 support for menus

OK for Moose I can understand, given its focus on data analysis. But I think that adding a menu for Roassal is too much, as not all use of Moose implies Roassal, and some people (like me) use Roassal stand-alone for showing specific things. So my vote stays with the Roassal builder.

On Sep 29, 2014, at 11:58 AM, Tudor Girba <[hidden email]> wrote:

Hi,

I think you are misunderstanding this issue. This is not high in the hierarchy. In the Moose image, every object can offer a menu of possible actions. Hence, it is an Object responsibility. Just like inspect is the object responsibility.

Cheers,
Doru

On Mon, Sep 29, 2014 at 4:34 PM, Johan Fabry <[hidden email]> wrote:

That makes me shiver as well ;-) In Pharo 3 this luckily is not the case.

I just have the philosophy to try and avoid putting things high in the hierarchy to make things high up as simple as possible (but not simpler ;-) ). This even considering class extensions.

In this case, we can put the responsibility for some Roassal thingy in a Roassal builder so I would put that feature (and the added complexity) there.

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

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

abergel

Re: roassal2 support for menus

In reply to this post by Tudor Girba-2

Hi!

I worked on this:

-=-=-=-=-=-=-=-=-=
b := RTMondrianViewBuilder new.
b interaction menu: #mooseMenuMorph.
b nodes: (1 to: 20).
b build
-=-=-=-=-=-=-=-=-=

Cheers,

Alexandre

On Sep 29, 2014, at 6:23 AM, Tudor Girba <[hidden email]> wrote:

What makes you shiver in this case?

Object already defines its menu.

Cheers,
Doru

On Mon, Sep 29, 2014 at 1:41 PM, Johan Fabry <[hidden email]> wrote:

FWIW, I would prefer putting it in the builder. Putting things in Object always makes me shiver ...

On Sep 29, 2014, at 1:50 AM, Tudor Girba <[hidden email]> wrote:

Hi,

We need a simple way to add the Moose menu to any Roassal element or edge.
We either
- add RTInteractionBuilder>>menu: or,
- add Object>>roassalMenuFor: aBuilder

What do you think?

Doru

--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
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

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

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