* startOn: is offered by the template :)
Doru *
On Wed, Nov 14, 2012 at 2:56 PM, Fabrizio Perin fabrizio.perin@gmail.comwrote:
2012/11/14 Tudor Girba tudor@tudorgirba.com:
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
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@gmail.com>
wrote:
Hi, thanks, that automagically worked.
Fabrizio
2012/11/13 Andrei Vasile Chis chisvasileandrei@gmail.com:
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@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 ]. ^browserCheers, Fabrizio
2012/11/13 Tudor Girba tudor@tudorgirba.com:
Hi Fabrizio,
Could you pass the example around?
Cheers, Doru
On 13 Nov 2012, at 19:58, Fabrizio Perin <fabrizio.perin@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@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev