[Moose-dev] Re: RTCalendarBuilder

Hi Markus, Milton worked on the issue. With the last version of Roassal, can you try the following code? -=-=-=-=-=-= | b | Week startDay: #Monday. b := RTCalendarBuilder new. b dateShape composite: [ :com | com add: (RTEllipse new color: [ :d | d = Date today ifTrue: [ Color blue trans ] ifFalse: [Color transparent] ]; size: 18). com add: (RTLabel new text: [:d| d dayOfMonth]; color: [:d | (d dayOfWeek = 1) ifTrue: [Color red] ifFalse: [ Color black ] ]) ]. b showDayNames. b yearShape composite: [ :comp | comp add: (RTLabel new text: [ :d | d year ]; height: 20 ). comp add: (RTBox new color: [ Color blue alpha: 0.1 ]). ] . b dates: Year current. b build. ^ b view -=-=-=-=-=-= It produces: Let us know how it goes Cheers, Milton & Alexandre On Apr 21, 2017, at 1:58 PM, Markus Böhm <markus.boehm(a)gmail.com> wrote: May I ask: Roassal and Pharo are really fantastic. I’m trying to get a grip on it and use it. What makes me think: In the introduction of the superb “Agile Visualization” book it is stated, that the Roassal OO approach allows for visualizations that are “easily extensible”. I guess compared to hand-crafted, imperative visualizations. Let’s take an example: RTCalendarBuilder I noticed that present visualization of week days start with Sunday as first day of week. E.g. in Europe/Germany weeks start on Monday (according ISO8601). We are visually so used to it, that other schemes make us think (not intuitive). How could I modify this? P.S.: Especially in calendrical visualizations there will be many (local) variations. So maybe it’s a good example to understand how to easily extend Roassal in above and similar topics as an interested user. BR Mike _______________________________________________ Moose-dev mailing list Moose-dev(a)list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev