Hi!
I have worked on the actions available in Glamour during the last few days. I have just added a find icon (glasses icon): Clicking on it open a spotter to look for element in the view. Selecting it move the camera to focus on it. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Hi Alexandre, This example no longer works. Also when I select an element the zooming in the visualization does not work any more. On a related topic we could add something like the following method to RTElement RTElement>>spotterPreviewIn: aComposite <spotterPreview: 10> RTBlink unhighlightElements: self view elements. RTBlink highlight: self. aComposite addBrickBack: self view setUpCanvas buildMorph Now this method is quite a hack but would make it possible to have something in the images from below. The bad part is the method above has a lot of side-effects as it resizes the canvas in the original visualization (if the view is opened somewhere else) and it does not deselect the element when spotter is closed. Cheers, Andrei On Wed, Oct 28, 2015 at 1:16 AM, Alexandre Bergel <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Hi!
I have just tried on the last version of Moose, with the last version of Roassal.
This is interesting. However, I am wondering whether we are not removing something by doing that. The preview then does not show the model. And maybe this is relevant to have. Would it be possible to visually select the kind of preview to have? Maybe with a tab or something? Alexandre
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Hi,
We could have two processors: - one for the elements - one for the model behind the elements The one for the elements would offer the view like Andrei suggested, and the one for models would offer the model preview. What do you think? Cheers, Doru > On Nov 30, 2015, at 3:59 PM, Alexandre Bergel <[hidden email]> wrote: > > Hi! > >> This example no longer works. >> Also when I select an element the zooming in the visualization does not work any more. > > I have just tried on the last version of Moose, with the last version of Roassal. > >> On a related topic we could add something like the following method to RTElement > > This is interesting. However, I am wondering whether we are not removing something by doing that. The preview then does not show the model. And maybe this is relevant to have. > Would it be possible to visually select the kind of preview to have? Maybe with a tab or something? > > Alexandre > >> >> RTElement>>spotterPreviewIn: aComposite >> <spotterPreview: 10> >> RTBlink unhighlightElements: self view elements. >> RTBlink highlight: self. >> aComposite addBrickBack: self view setUpCanvas buildMorph >> >> Now this method is quite a hack but would make it possible to have something in the images from below. >> The bad part is the method above has a lot of side-effects as it resizes the canvas in the original visualization (if the view is opened somewhere else) >> and it does not deselect the element when spotter is closed. >> >> >> <a GTSpotterMorph(116916224)2015-11-30T14-57-48-574342+01-00.png> >> <a GTSpotterMorph(561774592)2015-11-30T14-57-22-207557+01-00.png> >> >> >> Cheers, >> Andrei >> >> >> On Wed, Oct 28, 2015 at 1:16 AM, Alexandre Bergel <[hidden email]> wrote: >> Hi! >> >> I have worked on the actions available in Glamour during the last few days. >> I have just added a find icon (glasses icon): >> <Screen Shot 2015-10-27 at 9.12.41 PM.png> >> >> Clicking on it open a spotter to look for element in the view. Selecting it move the camera to focus on it. >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com "Don't give to get. Just give." _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by abergel
On Mon, Nov 30, 2015 at 3:59 PM, Alexandre Bergel <[hidden email]> wrote:
Ah. I made a slight confusion. If you inspect the code below [1] you will have to search actions: - one for the RTView object - one for the View presentation We should keep just the one for the RTView object. Then we need to add a processor that delegates to the view in RTBuilder for example [2] to work [1] v := RTView new. es := (RTEllipse new size: #yourself) elementsOn: (1 to: 50). v addAll: es. RTRectanglePackLayout on: es. v [2] b:=RTMondrian new. b nodes: (Collection withAllSubclasses). b layout grid. b.
Right now tabs are not supported but Doru's solution could work. Just if we also like to keep the preview the current solution need to be fixed to not break the original view. Cheers, Andrei
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by Tudor Girba-2
Well, is this supported? I have no idea how
Alexandre > Le 30 nov. 2015 à 12:16, Tudor Girba <[hidden email]> a écrit : > > Hi, > > We could have two processors: > - one for the elements > - one for the model behind the elements > > The one for the elements would offer the view like Andrei suggested, and the one for models would offer the model preview. What do you think? > > Cheers, > Doru > > >> On Nov 30, 2015, at 3:59 PM, Alexandre Bergel <[hidden email]> wrote: >> >> Hi! >> >>> This example no longer works. >>> Also when I select an element the zooming in the visualization does not work any more. >> >> I have just tried on the last version of Moose, with the last version of Roassal. >> >>> On a related topic we could add something like the following method to RTElement >> >> This is interesting. However, I am wondering whether we are not removing something by doing that. The preview then does not show the model. And maybe this is relevant to have. >> Would it be possible to visually select the kind of preview to have? Maybe with a tab or something? >> >> Alexandre >> >>> >>> RTElement>>spotterPreviewIn: aComposite >>> <spotterPreview: 10> >>> RTBlink unhighlightElements: self view elements. >>> RTBlink highlight: self. >>> aComposite addBrickBack: self view setUpCanvas buildMorph >>> >>> Now this method is quite a hack but would make it possible to have something in the images from below. >>> The bad part is the method above has a lot of side-effects as it resizes the canvas in the original visualization (if the view is opened somewhere else) >>> and it does not deselect the element when spotter is closed. >>> >>> >>> <a GTSpotterMorph(116916224)2015-11-30T14-57-48-574342+01-00.png> >>> <a GTSpotterMorph(561774592)2015-11-30T14-57-22-207557+01-00.png> >>> >>> >>> Cheers, >>> Andrei >>> >>> >>> On Wed, Oct 28, 2015 at 1:16 AM, Alexandre Bergel <[hidden email]> wrote: >>> Hi! >>> >>> I have worked on the actions available in Glamour during the last few days. >>> I have just added a find icon (glasses icon): >>> <Screen Shot 2015-10-27 at 9.12.41 PM.png> >>> >>> Clicking on it open a spotter to look for element in the view. Selecting it move the camera to focus on it. >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Don't give to get. Just give." > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by Andrei Chis
But at the end, how to implement this?
This is confusing to me. How can I select one processor or another? Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Hi,
Spotter presents you with multiple categories for each search. Each of these categories are produced by a so called (search) processor that is defined through a <spotterOrder:> pragma. For example: RPackage>>spotterClassesFor: aStep <spotterOrder: 20> aStep listProcessor allCandidates: [ self definedClasses sorted: [ :a :b | a name < b name ] ]; title: 'Classes'; filter: GTFilterSubstring So, my proposal was to have two of these in the RTView: - one that lists models - one that lists elements Then, if you would go through the first list, you will see the preview of hte model, if you would go through the second list, you would see the rendering. Cheers, Doru > On Dec 4, 2015, at 2:52 PM, Alexandre Bergel <[hidden email]> wrote: > > But at the end, how to implement this? > This is confusing to me. How can I select one processor or another? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Nov 30, 2015, at 1:05 PM, Andrei Chis <[hidden email]> wrote: >> >> >> >> On Mon, Nov 30, 2015 at 3:59 PM, Alexandre Bergel <[hidden email]> wrote: >> Hi! >> >>> This example no longer works. >>> Also when I select an element the zooming in the visualization does not work any more. >> >> I have just tried on the last version of Moose, with the last version of Roassal. >> >> Ah. I made a slight confusion. >> If you inspect the code below [1] you will have to search actions: >> - one for the RTView object >> - one for the View presentation >> We should keep just the one for the RTView object. >> Then we need to add a processor that delegates to the view in RTBuilder for example [2] to work >> >> [1] >> v := RTView new. >> es := (RTEllipse new size: #yourself) elementsOn: (1 to: 50). >> v addAll: es. >> RTRectanglePackLayout on: es. >> v >> >> [2] >> b:=RTMondrian new. >> b nodes: (Collection withAllSubclasses). >> b layout grid. >> b. >> >> >>> On a related topic we could add something like the following method to RTElement >> >> This is interesting. However, I am wondering whether we are not removing something by doing that. The preview then does not show the model. And maybe this is relevant to have. >> Would it be possible to visually select the kind of preview to have? Maybe with a tab or something? >> >> Right now tabs are not supported but Doru's solution could work. >> Just if we also like to keep the preview the current solution need to be fixed to not break the original view. >> >> Cheers, >> Andrei >> >> >> >> Alexandre >> >>> >>> RTElement>>spotterPreviewIn: aComposite >>> <spotterPreview: 10> >>> RTBlink unhighlightElements: self view elements. >>> RTBlink highlight: self. >>> aComposite addBrickBack: self view setUpCanvas buildMorph >>> >>> Now this method is quite a hack but would make it possible to have something in the images from below. >>> The bad part is the method above has a lot of side-effects as it resizes the canvas in the original visualization (if the view is opened somewhere else) >>> and it does not deselect the element when spotter is closed. >>> >>> >>> <a GTSpotterMorph(116916224)2015-11-30T14-57-48-574342+01-00.png> >>> <a GTSpotterMorph(561774592)2015-11-30T14-57-22-207557+01-00.png> >>> >>> >>> Cheers, >>> Andrei >>> >>> >>> On Wed, Oct 28, 2015 at 1:16 AM, Alexandre Bergel <[hidden email]> wrote: >>> Hi! >>> >>> I have worked on the actions available in Glamour during the last few days. >>> I have just added a find icon (glasses icon): >>> <Screen Shot 2015-10-27 at 9.12.41 PM.png> >>> >>> Clicking on it open a spotter to look for element in the view. Selecting it move the camera to focus on it. >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com "What is more important: To be happy, or to make happy?" _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Free forum by Nabble | Edit this page |