Using MouseEnter events from a Mondrian presentation in Glamour
Locked
Using MouseEnter events from a Mondrian presentation in Glamour
 
|
I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation.
I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. It seems like I could perhaps read from the #status port? My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. (rambling from esug) -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Good idea, would be of use for AspectMaps. So +1 on that question! On 14 Sep 2010, at 11:28, Simon Denier wrote: > I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation. > > I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. > It seems like I could perhaps read from the #status port? > > My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. > > For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. > I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. > > (rambling from esug) > > -- > Simon > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Johan Fabry [hidden email] - http://dcc.uchile.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 |
Re: Using MouseEnter events from a Mondrian presentation in Glamour
|
|
Hi,
browser := GLMTabulator new. browser column: #complexity; column: #source. browser transmit to: #complexity; andShow: [:a | a mondrian painting: [:view :group | group viewSystemComplexityOn: view ]]. browser transmit to: #source; from: #complexity->#status; andShow: [:a | a text display: [:class | class sourceText ]; when: [:class | class isKindOf: FAMIXClass ]]. browser openOn: MooseModel root allModels first allModelClasses) Doru On 14 Sep 2010, at 19:13, Johan Fabry wrote: > > Good idea, would be of use for AspectMaps. So +1 on that question! > > On 14 Sep 2010, at 11:28, Simon Denier wrote: > >> I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation. >> >> I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. >> It seems like I could perhaps read from the #status port? >> >> My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. >> >> For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. >> I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. >> >> (rambling from esug) >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Johan Fabry > [hidden email] - http://dcc.uchile.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 "Problem solving should be focused on describing the problem in a way that makes the solution obvious." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Using MouseEnter events from a Mondrian presentation in Glamour
|
|
Thank you very much Doru! Works great. On 15 sept. 2010, at 11:20, Tudor Girba wrote: > Hi, > > browser := GLMTabulator new. > browser column: #complexity; column: #source. > browser transmit to: #complexity; andShow: [:a | > a mondrian > painting: [:view :group | group viewSystemComplexityOn: view ]]. > browser transmit to: #source; from: #complexity->#status; andShow: [:a | > a text > display: [:class | class sourceText ]; > when: [:class | class isKindOf: FAMIXClass ]]. > browser openOn: MooseModel root allModels first allModelClasses) > > Doru > > > On 14 Sep 2010, at 19:13, Johan Fabry wrote: > >> >> Good idea, would be of use for AspectMaps. So +1 on that question! >> >> On 14 Sep 2010, at 11:28, Simon Denier wrote: >> >>> I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation. >>> >>> I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. >>> It seems like I could perhaps read from the #status port? >>> >>> My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. >>> >>> For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. >>> I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. >>> >>> (rambling from esug) >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> Johan Fabry >> [hidden email] - http://dcc.uchile.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 > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Using MouseEnter events from a Mondrian presentation in Glamour
|
|
If there is anything I can do on this, let me know.
Alexandre On 15 Sep 2010, at 11:50, Simon Denier wrote: > > Thank you very much Doru! Works great. > > > On 15 sept. 2010, at 11:20, Tudor Girba wrote: > >> Hi, >> >> browser := GLMTabulator new. >> browser column: #complexity; column: #source. >> browser transmit to: #complexity; andShow: [:a | >> a mondrian >> painting: [:view :group | group viewSystemComplexityOn: view ]]. >> browser transmit to: #source; from: #complexity->#status; andShow: [:a | >> a text >> display: [:class | class sourceText ]; >> when: [:class | class isKindOf: FAMIXClass ]]. >> browser openOn: MooseModel root allModels first allModelClasses) >> >> Doru >> >> >> On 14 Sep 2010, at 19:13, Johan Fabry wrote: >> >>> >>> Good idea, would be of use for AspectMaps. So +1 on that question! >>> >>> On 14 Sep 2010, at 11:28, Simon Denier wrote: >>> >>>> I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation. >>>> >>>> I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. >>>> It seems like I could perhaps read from the #status port? >>>> >>>> My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. >>>> >>>> For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. >>>> I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. >>>> >>>> (rambling from esug) >>>> >>>> -- >>>> Simon >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> Johan Fabry >>> [hidden email] - http://dcc.uchile.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 >> >> "Problem solving should be focused on describing >> the problem in a way that makes the solution obvious." >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > > _______________________________________________ > 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 |
|
|
In reply to this post by Simon Denier-3
+1 on this as well :-) Cant test it now, taking a plane back home today, but I trust Simon's judgement ;-) On 15 Sep 2010, at 05:50, Simon Denier wrote: > > Thank you very much Doru! Works great. > > > On 15 sept. 2010, at 11:20, Tudor Girba wrote: > >> Hi, >> >> browser := GLMTabulator new. >> browser column: #complexity; column: #source. >> browser transmit to: #complexity; andShow: [:a | >> a mondrian >> painting: [:view :group | group viewSystemComplexityOn: view ]]. >> browser transmit to: #source; from: #complexity->#status; andShow: [:a | >> a text >> display: [:class | class sourceText ]; >> when: [:class | class isKindOf: FAMIXClass ]]. >> browser openOn: MooseModel root allModels first allModelClasses) >> >> Doru >> >> >> On 14 Sep 2010, at 19:13, Johan Fabry wrote: >> >>> >>> Good idea, would be of use for AspectMaps. So +1 on that question! >>> >>> On 14 Sep 2010, at 11:28, Simon Denier wrote: >>> >>>> I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation. >>>> >>>> I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. >>>> It seems like I could perhaps read from the #status port? >>>> >>>> My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. >>>> >>>> For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. >>>> I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. >>>> >>>> (rambling from esug) >>>> >>>> -- >>>> Simon >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> Johan Fabry >>> [hidden email] - http://dcc.uchile.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 >> >> "Problem solving should be focused on describing >> the problem in a way that makes the solution obvious." >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Johan Fabry [hidden email] - http://dcc.uchile.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 |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |