MooseFinder and glamour

List overview All Threads
Download

newer

older

Issue 865 in moose-technology:...

Re: Roassal ROMondrianExamples on...

Fabrizio Perin

13 Nov 2012 13 Nov '12

6:47 p.m.

Hi, I was loading some old code and some of browsers I wrote do not open correctly anymore. Apparently I cannot do something like this anymore: browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: (MooseFinder startOn: a) ]. This because MooseFinder do not understand anymore startOn:. Any suggestions on how can I make this glamour example working again? mooseFinderOnSelectedElement "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: 100)'> | browser | browser := GLMTabulator new. browser column: #functions; column: #finder. browser transmit to: #functions; andShow: [ :a | a list title: 'Functions'; display: [ :each | each ] ]. browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: (MooseFinder startOn: a) ]. ^browser Thanks, Fabrizio

Show replies by date

Andrei Vasile Chis

13 Nov 13 Nov

6:55 p.m.

Hi Fabrizio, Try browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: (MooseFinder new) ]. instead of browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: (MooseFinder startOn: a) ] Cheers, Andrei On Tue, Nov 13, 2012 at 6:47 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com>wrote;wrote:

...

Fabrizio Perin

7:58 p.m.

Tudor Girba

8:15 p.m.

Hi Fabrizio, Could you pass the example around? Cheers, Doru On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote:

...

Hi Andrei, that kind of work in the sense that the browser actually open but I get a SubscriptOutOfBound:1 error message. I think the problem is that I should pass to the MooseFinder the element in the selection port. Any suggestion? Cheers, Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

Fabrizio Perin

9:47 p.m.

Hi Doru, the method that doesn't work is this: (I already adapted the method following the suggestion of Andrei) mooseFinderOnSelectedElement "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: 100)'> | browser | browser := GLMTabulator new. browser column: #functions; column: #finder. browser transmit to: #functions; andShow: [ :a | a list title: 'Functions'; display: [ :each | each ] ]. browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: MooseFinder new ]. ^browser Cheers, Fabrizio 2012/11/13 Tudor Girba <tudor(a)tudorgirba.com>om>:

...

Hi Fabrizio, Could you pass the example around? Cheers, Doru On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote:

-- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Andrei Vasile Chis

11:13 p.m.

Hi Fabrizio, Try "MooseFinder new first noTitle" instead of "MooseFinder new". Cheers, Andrei On Tue, Nov 13, 2012 at 9:47 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com>wrote;wrote:

...

Hi Fabrizio, Could you pass the example around? Cheers, Doru On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com>

wrote:

-- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be

done."

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Fabrizio Perin

14 Nov 14 Nov

2:01 p.m.

Hi, thanks, that automagically worked. Fabrizio 2012/11/13 Andrei Vasile Chis <chisvasileandrei(a)gmail.com>om>:

...

Hi Fabrizio, Try "MooseFinder new first noTitle" instead of "MooseFinder new". Cheers, Andrei On Tue, Nov 13, 2012 at 9:47 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote:

Hi Fabrizio, Could you pass the example around? Cheers, Doru On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote:

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba

2:48 p.m.

Indeed, this part still needs some more care. The issue is like this: I want to move away from the BrowserTemplate because it is a dead thing. For example, beforehand, to embed the MooseFinder, you needed to do "MooseFinder new browser". The goal now would be to use only "MooseFinder new". To achieve this, the current idea is to subclass from GLMCompositePresentation and use the API from this to script the browser in the initialization. Conceptually, this is much nicer because you get an object you can work with at runtime. However, we still have the problem of using in practice. It would be cool to look at this tomorrow. Cheers, Doru On Wed, Nov 14, 2012 at 2:01 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com>wrote;wrote:

...

Hi, thanks, that automagically worked. Fabrizio 2012/11/13 Andrei Vasile Chis <chisvasileandrei(a)gmail.com>om>:

Hi Fabrizio, Try "MooseFinder new first noTitle" instead of "MooseFinder new". Cheers, Andrei On Tue, Nov 13, 2012 at 9:47 PM, Fabrizio Perin <

fabrizio.perin(a)gmail.com>

wrote: > > Hi Doru, > the method that doesn't work is this: (I already adapted the method > following the suggestion of Andrei) > > mooseFinderOnSelectedElement > "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" > <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: > 100)'> > > | browser | > browser := GLMTabulator new. > browser > column: #functions; > column: #finder. > browser transmit > to: #functions; > andShow: [ :a | > a list > title: 'Functions'; > display: [ :each | each ] ]. > browser transmit > to: #finder; > from: #functions port: #selection; > andShow: [ :a | a custom: MooseFinder new ]. > ^browser > > > Cheers, > Fabrizio > > 2012/11/13 Tudor Girba <tudor(a)tudorgirba.com>om>: > > Hi Fabrizio, > > > > Could you pass the example around? > > > > Cheers, > > Doru > > > > > > On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com> > > wrote: > > > >> Hi Andrei, > >> that kind of work in the sense that the browser actually open but I > >> get a SubscriptOutOfBound:1 error message. I think the problem is

that

> >> I should pass to the MooseFinder the element in the selection port. > >> Any suggestion? > >> > >> Cheers, > >> Fabrizio > >> _______________________________________________ > >> Moose-dev mailing list > >> Moose-dev(a)iam.unibe.ch > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "Not knowing how to do something is not an argument for how it cannot

done." _______________________________________________ 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 "Every thing has its own flow"

Fabrizio Perin

2:56 p.m.

2012/11/14 Tudor Girba <tudor(a)tudorgirba.com>om>:

...

Indeed, this part still needs some more care. The issue is like this: I want to move away from the BrowserTemplate

because

...

it is a dead thing. For example, beforehand, to embed the MooseFinder, you needed to do "MooseFinder new browser".

Did you? In the example I posted I simply had to add to a browser the MooseFinder browser started on something: mooseFinderOnSelectedElement "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: 100)'> | browser | browser := GLMTabulator new. browser column: #functions; column: #finder. browser transmit to: #functions; andShow: [ :a | a list title: 'Functions'; display: [ :each | each ] ]. * browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: (MooseFinder startOn: a) ].* ^browser We can investigate this issue during the Moose Dojo. Cheers, Fabrizio The goal now would be to use only

...

"MooseFinder new". To achieve this, the current idea is to subclass from GLMCompositePresentation and use the API from this to script the browser

...

the initialization. Conceptually, this is much nicer because you get an object you can work with at runtime. However, we still have the problem of using in practice. It would be cool to look at this tomorrow. Cheers, Doru On Wed, Nov 14, 2012 at 2:01 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote: > > Hi, > thanks, that automagically worked. > > Fabrizio > > 2012/11/13 Andrei Vasile Chis <chisvasileandrei(a)gmail.com>om>: > > Hi Fabrizio, > > > > Try "MooseFinder new first noTitle" instead of "MooseFinder new". > > > > Cheers, > > Andrei > > > > On Tue, Nov 13, 2012 at 9:47 PM, Fabrizio Perin > > <fabrizio.perin(a)gmail.com> > > wrote: > >> > >> Hi Doru, > >> the method that doesn't work is this: (I already adapted the method > >> following the suggestion of Andrei) > >> > >> mooseFinderOnSelectedElement > >> "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" > >> <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: > >> 100)'> > >> > >> | browser | > >> browser := GLMTabulator new. > >> browser > >> column: #functions; > >> column: #finder. > >> browser transmit > >> to: #functions; > >> andShow: [ :a | > >> a list > >> title: 'Functions'; > >> display: [ :each | each ] ]. > >> browser transmit > >> to: #finder; > >> from: #functions port: #selection; > >> andShow: [ :a | a custom: MooseFinder new ]. > >> ^browser > >> > >> > >> Cheers, > >> Fabrizio > >> > >> 2012/11/13 Tudor Girba <tudor(a)tudorgirba.com>om>: > >> > Hi Fabrizio, > >> > > >> > Could you pass the example around? > >> > > >> > Cheers, > >> > Doru > >> > > >> > > >> > On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com> > >> > wrote: > >> > > >> >> Hi Andrei, > >> >> that kind of work in the sense that the browser actually open but I > >> >> get a SubscriptOutOfBound:1 error message. I think the problem is > >> >> that > >> >> I should pass to the MooseFinder the element in the selection port. > >> >> Any suggestion? > >> >> > >> >> Cheers, > >> >> Fabrizio > >> >> _______________________________________________ > >> >> Moose-dev mailing list > >> >> Moose-dev(a)iam.unibe.ch > >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >> > > >> > -- > >> > www.tudorgirba.com > >> > > >> > "Not knowing how to do something is not an argument for how it

cannot

...

> be > done." > > > _______________________________________________ > 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

_______________________________________________ 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

Tudor Girba

3:43 p.m.

* startOn: is offered by the template :) Doru * On Wed, Nov 14, 2012 at 2:56 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com>wrote;wrote:

...

2012/11/14 Tudor Girba <tudor(a)tudorgirba.com>om>:

Indeed, this part still needs some more care. The issue is like this: I want to move away from the BrowserTemplate

because

it is a dead thing. For example, beforehand, to embed the MooseFinder,

you

needed to do "MooseFinder new browser".

Did you? In the example I posted I simply had to add to a browser the MooseFinder browser started on something: mooseFinderOnSelectedElement "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: 100)'> | browser | browser := GLMTabulator new. browser column: #functions; column: #finder. browser transmit to: #functions; andShow: [ :a | a list title: 'Functions'; display: [ :each | each ] ]. * browser transmit to: #finder; from: #functions port: #selection; andShow: [ :a | a custom: (MooseFinder startOn: a) ]. * ^browser We can investigate this issue during the Moose Dojo. Cheers, Fabrizio The goal now would be to use only

"MooseFinder new". To achieve this, the current idea is to subclass from GLMCompositePresentation and use the API from this to script the browser

the initialization. Conceptually, this is much nicer because you get an object you can work with at runtime. However, we still have the problem

using in practice. It would be cool to look at this tomorrow. Cheers, Doru On Wed, Nov 14, 2012 at 2:01 PM, Fabrizio Perin <

fabrizio.perin(a)gmail.com>

wrote: > > Hi, > thanks, that automagically worked. > > Fabrizio > > 2012/11/13 Andrei Vasile Chis <chisvasileandrei(a)gmail.com>om>: > > Hi Fabrizio, > > > > Try "MooseFinder new first noTitle" instead of "MooseFinder new". > > > > Cheers, > > Andrei > > > > On Tue, Nov 13, 2012 at 9:47 PM, Fabrizio Perin > > <fabrizio.perin(a)gmail.com> > > wrote: > >> > >> Hi Doru, > >> the method that doesn't work is this: (I already adapted the method > >> following the suggestion of Andrei) > >> > >> mooseFinderOnSelectedElement > >> "self new mooseFinderOnSelectedElement openOn: (1 to: 100)" > >> <glmBrowser: 'Open MooseFinder On Selected Element' input: '(1

to:

>> 100)'> >> >> | browser | >> browser := GLMTabulator new. >> browser >> column: #functions; >> column: #finder. >> browser transmit >> to: #functions; >> andShow: [ :a | >> a list >> title: 'Functions'; >> display: [ :each | each ] ]. >> browser transmit >> to: #finder; >> from: #functions port: #selection; >> andShow: [ :a | a custom: MooseFinder new ]. >> ^browser >> >> >> Cheers, >> Fabrizio >> >> 2012/11/13 Tudor Girba <tudor(a)tudorgirba.com>om>: >> > Hi Fabrizio, >> > >> > Could you pass the example around? >> > >> > Cheers, >> > Doru >> > >> > >> > On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin(a)gmail.com

> >> > wrote: > >> > > >> >> Hi Andrei, > >> >> that kind of work in the sense that the browser actually open but

> >> >> get a SubscriptOutOfBound:1 error message. I think the problem is > >> >> that > >> >> I should pass to the MooseFinder the element in the selection

port.

> >> >> Any suggestion? > >> >> > >> >> Cheers, > >> >> Fabrizio > >> >> _______________________________________________ > >> >> Moose-dev mailing list > >> >> Moose-dev(a)iam.unibe.ch > >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >> > > >> > -- > >> > www.tudorgirba.com > >> > > >> > "Not knowing how to do something is not an argument for how it

cannot

> > be > > done." > > > > > > _______________________________________________ > > 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 _______________________________________________ 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 "Every thing has its own flow"

4568

days inactive

4569

days old

moose-dev@list.inf.unibe.ch

Manage subscription

9 comments

3 participants

tags (0)

participants (3)

Andrei Vasile Chis
Fabrizio Perin
Tudor Girba