Charter for external view
Locked
 
|
Hi, I need to use Charter Builder to build a chart in an external view. According to the builder chapter, any builder should override #renderIn:, and so it should be possible to do “builder renderIn: myView”. But RTCharterBuilder does not override this method. Can I build charts in my view in some other way?
Uko _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Have you tried to set the view right after the creation of the builder by using #view: ?
Alexandre > Le 23-09-2014 à 6:48, Yuriy Tymchuk <[hidden email]> a écrit : > > Hi, I need to use Charter Builder to build a chart in an external view. According to the builder chapter, any builder should override #renderIn:, and so it should be possible to do “builder renderIn: myView”. But RTCharterBuilder does not override this method. Can I build charts in my view in some other way? > > Uko > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Oh, yes, it works. Thanks. But is this a new API? Because I really liked the idea that everything was based on #renderIn: so you can refer on the same way to all builders. It it going to be use also, or builders will move to #view:?
Uko > On 23 Sep 2014, at 14:18, Alexandre Bergel <[hidden email]> wrote: > > Have you tried to set the view right after the creation of the builder by using #view: ? > > Alexandre > >> Le 23-09-2014 à 6:48, Yuriy Tymchuk <[hidden email]> a écrit : >> >> Hi, I need to use Charter Builder to build a chart in an external view. According to the builder chapter, any builder should override #renderIn:, and so it should be possible to do “builder renderIn: myView”. But RTCharterBuilder does not override this method. Can I build charts in my view in some other way? >> >> Uko >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
> Oh, yes, it works. Thanks. But is this a new API? Because I really liked the idea that everything was based on #renderIn: so you can refer on the same way to all builders. It it going to be use also, or builders will move to #view:?
I see your point and you are perfectly right. #renderIn: is called when you call #build, to build the visualization. It often happens that the view is required _before_ you actually build it. For example, RTCharterBuilder>>points: uses the view variable. I have the impression this is not a big deal. Having #renderIn: is not that necessary. Probably, that in the future we will need a way to define input of a builder. Something like: RTBuilder>>buildWithArguments: arguments In that case, it would be like using a builder as a super-composite-shape. Do you my point? Cheers, Alexandre > >> On 23 Sep 2014, at 14:18, Alexandre Bergel <[hidden email]> wrote: >> >> Have you tried to set the view right after the creation of the builder by using #view: ? >> >> Alexandre >> >>> Le 23-09-2014 à 6:48, Yuriy Tymchuk <[hidden email]> a écrit : >>> >>> Hi, I need to use Charter Builder to build a chart in an external view. According to the builder chapter, any builder should override #renderIn:, and so it should be possible to do “builder renderIn: myView”. But RTCharterBuilder does not override this method. Can I build charts in my view in some other way? >>> >>> Uko >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Yes, thanks.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by abergel
One more thing that I want to state in favour of #renderIn:
Today I’ve discovered that shape builder of Charter has to be used before you set #points:. Now when you follow #renderIn: strategy, it’s harder to develop the builder itself but it’s easier to use, because you just set up builder and then make it run. The way Charter is implemented now makes me find out and memorise the sequence of set up that I have to use to make it work (first view, then shapes, then points, then line…). These are just my 2 cents, but personally of me it’s usability issue that I wanted to share. Uko > On 23 Sep 2014, at 20:26, Alexandre Bergel <[hidden email]> wrote: > >> Oh, yes, it works. Thanks. But is this a new API? Because I really liked the idea that everything was based on #renderIn: so you can refer on the same way to all builders. It it going to be use also, or builders will move to #view:? > > I see your point and you are perfectly right. #renderIn: is called when you call #build, to build the visualization. It often happens that the view is required _before_ you actually build it. > > For example, RTCharterBuilder>>points: uses the view variable. > I have the impression this is not a big deal. Having #renderIn: is not that necessary. Probably, that in the future we will need a way to define input of a builder. Something like: > RTBuilder>>buildWithArguments: arguments > > In that case, it would be like using a builder as a super-composite-shape. Do you my point? > > Cheers, > Alexandre > >> >>> On 23 Sep 2014, at 14:18, Alexandre Bergel <[hidden email]> wrote: >>> >>> Have you tried to set the view right after the creation of the builder by using #view: ? >>> >>> Alexandre >>> >>>> Le 23-09-2014 à 6:48, Yuriy Tymchuk <[hidden email]> a écrit : >>>> >>>> Hi, I need to use Charter Builder to build a chart in an external view. According to the builder chapter, any builder should override #renderIn:, and so it should be possible to do “builder renderIn: myView”. But RTCharterBuilder does not override this method. Can I build charts in my view in some other way? >>>> >>>> Uko >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ 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 |