Your first option does not work :-( portNamed: is not implemented. So
I tried the following variant, intending the #mpanel to update itself but nothing happens :-( browser transmit to: #buttons; andShow:[ :a | (a actionList) act: [:p :entity | entity dooFooTransform. (p pane port: #mpanel) value: entity ] entitled: 'DoFooTransform'; ... On 21 Jan 2010, at 04:29, Tudor Girba wrote: > Hi, > > The first parameter of an action is the presentation. And the > presentation has access to its pane. So, the preferred way is for > the presentation to only talk with its pane and then let > transmissions deal with links between panes. So, you can do: > > a somePresentation > act: [:p :entity | (p pane portNamed: #somePort) value: entity > something] on: $x entitled: 'Update' > > or shorter: > > a somePresentation > update: #somePort on: $x entitled: 'Update' with: [:p :entity | > entity something] > > So, I guess that the buttons in your case are part of an ActionList > that is placed in one pane. So, you could populate 6 different ports > in that pane and then have one transmission from all ports to the > mondrian pane (entity port). > > Is this better? > > Cheers, > Doru -- 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 |
Hi Johan,
On 22 Jan 2010, at 19:28, Johan Fabry wrote: > Your first option does not work :-( portNamed: is not implemented. Indeed, it is port:, not portNamed: > So I tried the following variant, intending the #mpanel to update > itself but nothing happens :-( Wait, #mpanel is the name of the port that you just updated. You need to have a transmission that origins in that port, and if you have it, it should trigger. Does it not happen like that? Cheers, Doru > browser transmit to: #buttons; > andShow:[ :a | > (a actionList) > act: [:p :entity | entity dooFooTransform. (p pane port: #mpanel) > value: entity ] entitled: 'DoFooTransform'; > ... > > > On 21 Jan 2010, at 04:29, Tudor Girba wrote: > >> Hi, >> >> The first parameter of an action is the presentation. And the >> presentation has access to its pane. So, the preferred way is for >> the presentation to only talk with its pane and then let >> transmissions deal with links between panes. So, you can do: >> >> a somePresentation >> act: [:p :entity | (p pane portNamed: #somePort) value: entity >> something] on: $x entitled: 'Update' >> >> or shorter: >> >> a somePresentation >> update: #somePort on: $x entitled: 'Update' with: [:p :entity | >> entity something] >> >> So, I guess that the buttons in your case are part of an ActionList >> that is placed in one pane. So, you could populate 6 different >> ports in that pane and then have one transmission from all ports to >> the mondrian pane (entity port). >> >> Is this better? >> >> Cheers, >> Doru > > -- > 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 "Not knowing how to do something is not an argument for how it cannot be done." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |