12 Mar
2013
12 Mar
'13
10:12 a.m.
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not
get a minimap when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour.
can you have a look?
Here's a simple browser with a roassal visualization (adapted from one of
ben's mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn:
x) + ROLabel + ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
12 Mar
12 Mar
10:30 a.m.
I do not understand the issue, but that is probably because I did not yet
see the mini map. How does it work?
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote;wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not
get a minimap when pressing m key.
It might be something to do with how keystrokes are interpreted in
Glamour. can you have a look?
Here's a simple browser with a roassal visualization (adapted from one of
ben's mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn:
x) + ROLabel + ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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"
10:51 a.m.
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably
because I did not yet
see the mini map. How does it work?
Roassal allows minimaps for large visualizations, see this example in
Roassal: ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups
when one presses 'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't
work. Here's a shorter example of a browser that shows the visu of the
example in a browser but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote;wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do
not get a minimap when pressing m key.
It might be something to do with how keystrokes are interpreted in
Glamour. can you have a look?
Here's a simple browser with a roassal visualization (adapted from one of
ben's mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement
spriteOn: x) + ROLabel + ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:45 p.m.
Ok, I see.
The bug is indeed probably due to key handling in Glamour.
In any case, the MiniMap should not hardcode the key with which it gets triggered.
Please open a bug report.
Cheers,
Doru
On Mar 12, 2013, at 10:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel +
ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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.tudorgirba.com
"Value is always contextual."
13 Mar
13 Mar
3:30 a.m.
For people wondering what the minimap is all about, consider the following script:
| view eltos |
view := ROView new.
view @ RODraggable.
view on: ROMouseRightClick
do: [ :event | ROZoomInMove new on: view ].
view on: ROMouseLeftClick
do: [ :event | ROZoomOutMove new on: view ].
eltos := ROElement spritesOn: (1 to: 400).
eltos do: [:el | el + ROLabel ].
view addAll: eltos.
ROGridLayout new on: eltos.
"Mini map opens by pressing m"
view @ ROMiniMap.
view open.
Pressing the "m" key open a navigation map which gives something like:
Cheers,
Vanessa and Alexandre
On Mar 12, 2013, at 5:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel +
ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
4:21 a.m.
Hi,
I'm sorry, but I don't understand, how the MiniMap should not hardcore
the key with which it is opened? I have a value of the symbol saved,
yes, because I thought it should have one, at least by default. However,
the communication between the ROMorph and the view is done by using events.
Is there a cleaner way?
Thanks,
Vanessa.
On 03/12/2013 05:45 PM, Tudor Girba wrote:
Ok, I see.
The bug is indeed probably due to key handling in Glamour.
In any case, the MiniMap should not hardcode the key with which it gets triggered.
Please open a bug report.
Cheers,
Doru
On Mar 12, 2013, at 10:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel
+ ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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.tudorgirba.com
"Value is always contextual."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
6:24 a.m.
Hi,
Right now, ROMiniMap hardcodes $m, and there is no way to customize it.
Furthermore:
- there is no easy way to spawn a MiniMap programmatically (without the relying on the
$m). You can invoke openMiniMapFor: but you need to initialize the MiniMap carefully
before hand.
- there is no way to get the MiniMap on a different morph than the bulky-gray window.
- there is no way to get the view without having the zoom-in, zoom-out buttons.
All these make it hard to integrate it into a different workflow like Glamour.
Cheers,
Doru
On Mar 13, 2013, at 4:21 AM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote:
Hi,
I'm sorry, but I don't understand, how the MiniMap should not hardcore the key
with which it is opened? I have a value of the symbol saved, yes, because I thought it
should have one, at least by default. However, the communication between the ROMorph and
the view is done by using events.
Is there a cleaner way?
Thanks,
Vanessa.
On 03/12/2013 05:45 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting is the right
one."
Ok, I see.
The bug is indeed probably due to key handling in Glamour.
In any case, the MiniMap should not hardcode the key with which it gets triggered.
Please open a bug report.
Cheers,
Doru
On Mar 12, 2013, at 10:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel +
ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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.tudorgirba.com
"Value is always contextual."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
6:25 a.m.
It's nice.
Note: we have to communicate features like this better, especially given that we have
discussed precisely this topic and agreed that it is critical.
Cheers,
Doru
On Mar 13, 2013, at 3:30 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
For people wondering what the minimap is all about,
consider the following script:
| view eltos |
view := ROView new.
view @ RODraggable.
view on: ROMouseRightClick
do: [ :event | ROZoomInMove new on: view ].
view on: ROMouseLeftClick
do: [ :event | ROZoomOutMove new on: view ].
eltos := ROElement spritesOn: (1 to: 400).
eltos do: [:el | el + ROLabel ].
view addAll: eltos.
ROGridLayout new on: eltos.
"Mini map opens by pressing m"
view @ ROMiniMap.
view open.
Pressing the "m" key open a navigation map which gives something like:
<Screen Shot 2013-03-12 at 10.28.28 PM.png>
Cheers,
Vanessa and Alexandre
On Mar 12, 2013, at 5:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
--
www.tudorgirba.com
"Things happen when they happen,
not when you talk about them happening."
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel +
ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
1:03 p.m.
Thanks for this. We will work on this, probably today or tomorrow.
Alexandre
On Mar 13, 2013, at 1:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
Right now, ROMiniMap hardcodes $m, and there is no way to customize it.
Furthermore:
- there is no easy way to spawn a MiniMap programmatically (without the relying on the
$m). You can invoke openMiniMapFor: but you need to initialize the MiniMap carefully
before hand.
- there is no way to get the MiniMap on a different morph than the bulky-gray window.
- there is no way to get the view without having the zoom-in, zoom-out buttons.
All these make it hard to integrate it into a different workflow like Glamour.
Cheers,
Doru
On Mar 13, 2013, at 4:21 AM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I'm sorry, but I don't understand, how the MiniMap should not hardcore the key
with which it is opened? I have a value of the symbol saved, yes, because I thought it
should have one, at least by default. However, the communication between the ROMorph and
the view is done by using events.
Is there a cleaner way?
Thanks,
Vanessa.
On 03/12/2013 05:45 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting is the
right one."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Ok, I see.
The bug is indeed probably due to key handling in Glamour.
In any case, the MiniMap should not hardcode the key with which it gets triggered.
Please open a bug report.
Cheers,
Doru
On Mar 12, 2013, at 10:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel +
ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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.tudorgirba.com
"Value is always contextual."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
1:07 p.m.
We could have for example.
view @ (ROMiniMap new
keystrocke: $w).
and should be able to support something like this:
element on: ROMouseClick do: [ :event | ROMiniMap openOn: view ].
We can have a look at this today.
Alexandre
On Mar 12, 2013, at 11:21 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote:
Hi,
I'm sorry, but I don't understand, how the MiniMap should not hardcore the key
with which it is opened? I have a value of the symbol saved, yes, because I thought it
should have one, at least by default. However, the communication between the ROMorph and
the view is done by using events.
Is there a cleaner way?
Thanks,
Vanessa.
On 03/12/2013 05:45 PM, Tudor Girba wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Ok, I see.
The bug is indeed probably due to key handling in Glamour.
In any case, the MiniMap should not hardcode the key with which it gets triggered.
Please open a bug report.
Cheers,
Doru
On Mar 12, 2013, at 10:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel +
ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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.tudorgirba.com
"Value is always contextual."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:11 p.m.
Thank you :)
Vanessa.
On 03/13/2013 01:24 AM, Tudor Girba wrote:
Hi,
Right now, ROMiniMap hardcodes $m, and there is no way to customize it.
Furthermore:
- there is no easy way to spawn a MiniMap programmatically (without the relying on the
$m). You can invoke openMiniMapFor: but you need to initialize the MiniMap carefully
before hand.
- there is no way to get the MiniMap on a different morph than the bulky-gray window.
- there is no way to get the view without having the zoom-in, zoom-out buttons.
All these make it hard to integrate it into a different workflow like Glamour.
Cheers,
Doru
On Mar 13, 2013, at 4:21 AM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote:
Hi,
I'm sorry, but I don't understand, how the MiniMap should not hardcore the key
with which it is opened? I have a value of the symbol saved, yes, because I thought it
should have one, at least by default. However, the communication between the ROMorph and
the view is done by using events.
Is there a cleaner way?
Thanks,
Vanessa.
On 03/12/2013 05:45 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting is the
right one."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Ok, I see.
The bug is indeed probably due to key handling in Glamour.
In any case, the MiniMap should not hardcode the key with which it gets triggered.
Please open a bug report.
Cheers,
Doru
On Mar 12, 2013, at 10:51 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Tue, Mar 12, 2013 at 10:30 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
I do not understand the issue, but that is probably because I did not yet see the mini
map. How does it work?
Roassal allows minimaps for large visualizations, see this example in Roassal:
ROMondrianExample >>miniMap.
So the idea is that any visualization allowing minimap, a minimap popups when one presses
'm'.
However, when roassal visu is embedded in a glamour browser, it doesn't work.
Here's a shorter example of a browser that shows the visu of the example in a browser
but there's no miniMap when 'm' is pressed.
| browser |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
ROMondrianExample new miniMapOn: moview.
] ].
browser openOn: #(1 2 3 4 5 6).
Doru
On Tue, Mar 12, 2013 at 10:12 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap
when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour. can you have
a look?
Here's a simple browser with a roassal visualization (adapted from one of ben's
mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel
+ ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
_______________________________________________
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 list
Moose-dev(a)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.tudorgirba.com
"Value is always contextual."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
19 Feb
19 Feb
1:48 p.m.
Hello,
I'm currently working with Martin (Dias) in the migration of Torch to Pharo
3.
In this tool, we now have a Glamour window and a Roassal visualization
inside, in which we can interact with mouse click events. In one of the
interactions, the user moves the mouse over a node and a popup window is
supposed to show with further informations. But no popup is shown, although
the body of the popupView: method is executed.
I was talking to Usman and he showed me this thread (with small example)
http://forum.world.st/minimap-in-Glamour-Roassal-td4676258.html
in which Roassal and Glamour do not communicate well with this kind of
event.
Is there some progress or workarounds with this issue?
Cheers
--
Gustavo Santos
--
View this message in context:
http://forum.world.st/minimap-in-Glamour-Roassal-tp4676258p4744833.html
Sent from the Moose mailing list archive at Nabble.com.
2:15 p.m.
Hi,
The minimap and popup are not the same thing. The popup is entirely handled
by Roassal, and it should work.
Could you provide a minimal example to reproduce the problem?
Cheers,
Doru
On Wed, Feb 19, 2014 at 1:48 PM, Gustavo Santos <gugajansen(a)gmail.com>wrote;wrote:
Hello,
I'm currently working with Martin (Dias) in the migration of Torch to Pharo
3.
In this tool, we now have a Glamour window and a Roassal visualization
inside, in which we can interact with mouse click events. In one of the
interactions, the user moves the mouse over a node and a popup window is
supposed to show with further informations. But no popup is shown, although
the body of the popupView: method is executed.
I was talking to Usman and he showed me this thread (with small example)
http://forum.world.st/minimap-in-Glamour-Roassal-td4676258.html
in which Roassal and Glamour do not communicate well with this kind of
event.
Is there some progress or workarounds with this issue?
Cheers
--
Gustavo Santos
--
View this message in context:
http://forum.world.st/minimap-in-Glamour-Roassal-tp4676258p4744833.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
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"
2:37 p.m.
Yes. I took the example of Usman to get a Glamour window outside.
The code inside #painting: works in a single Roassal visualization
I don't know if I can do this thing inside the block, so please correct me
if I'm terribly wrong.
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a |
a roassal painting: [ :roview :collection |
roview interaction popupView: [ :el :popupView |
popupView shape rectangle fillColor: Color yellow.
popupView node: 20 forIt: [
popupView shape rectangle size: 70; fillColor: Color
green.
popupView node: 30
].
popupView horizontalLineLayout.
popupView applyLayout
].
roview shape rectangle size: 40.
roview node: 10.
viewHack := roview view.
]
].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:[ :x |
| targetElement foundElements |
viewHack elements do: [ :el | el @ ROLightlyHighlightable ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
(targetElement color: Color red) @ ROLightlyHighlightable.
viewHack signalUpdate
].
browser openOn: #(1).
On Wed, Feb 19, 2014 at 2:15 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
The minimap and popup are not the same thing. The popup is entirely
handled by Roassal, and it should work.
Could you provide a minimal example to reproduce the problem?
Cheers,
Doru
On Wed, Feb 19, 2014 at 1:48 PM, Gustavo Santos <gugajansen(a)gmail.com>wrote;wrote:
--
Gustavo Santos
Hello,
I'm currently working with Martin (Dias) in the migration of Torch to
Pharo
3.
In this tool, we now have a Glamour window and a Roassal visualization
inside, in which we can interact with mouse click events. In one of the
interactions, the user moves the mouse over a node and a popup window is
supposed to show with further informations. But no popup is shown,
although
the body of the popupView: method is executed.
I was talking to Usman and he showed me this thread (with small example)
http://forum.world.st/minimap-in-Glamour-Roassal-td4676258.html
in which Roassal and Glamour do not communicate well with this kind of
event.
Is there some progress or workarounds with this issue?
Cheers
--
Gustavo Santos
--
View this message in context:
http://forum.world.st/minimap-in-Glamour-Roassal-tp4676258p4744833.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
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 list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
4080
days inactive
4424
days old
13 comments
6 participants
participants (6)
-
Alexandre Bergel -
Gustavo Jansen -
Gustavo Santos
-
Tudor Girba -
Usman Bhatti -
Vanessa Peña Araya