Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
July 2015
- 850 messages
Re: [Pharo-dev] About nextPutAll: $(
by Eliot Miranda
On Sat, Jul 25, 2015 at 9:39 AM, Hernán Morales Durand <
hernan.morales(a)gmail.com> wrote:
> In BioSmalltalk I use this pattern a lot:
>
> aStream
> nextPutAll: self name
> between: $[ -> $].
>
> so yes, that would be a nice inclusion for me :)
>
i don't like the allocation here; v slow. why not nextPutAll:between:and: ?
>
> Cheers,
>
> Hernán
>
>
>
>
> 2015-07-24 17:48 GMT-03:00 stepharo <stepharo(a)free.fr>:
>
>> HI
>>
>> while working on a lecture I saw that we have about 75 cases like:
>>
>> aStream nextPut: $(.
>> ....
>> aStream nextPut: $).
>>
>>
>>
>> storeOn: aStream
>> "Store a description of the elements of the complement rather than
>> self."
>>
>> aStream nextPut: $(.
>> absent storeOn: aStream.
>> aStream nextPut: $); space; nextPutAll: #complement.
>>
>>
>> printElementsOn: aStream
>> aStream nextPut: $(.
>> self size > 100
>> ifTrue: [aStream nextPutAll: 'size '.
>> self size printOn: aStream]
>> ifFalse: [self keysSortedSafely
>> do: [:key | aStream print: key;
>> nextPutAll: '->';
>> print: (self at: key);
>> space]].
>> aStream nextPut: $)
>>
>> we have surroundedBy: aString
>>
>> surroundedBy: aString
>> ^ self class streamContents: [ :s|
>> s nextPutAll: aString.
>> s nextPutAll: self.
>> s nextPutAll: aString ].
>>
>> But only working on aString.
>> To me it looks like it ia class for having it on stream.
>>
>> What do you think?
>>
>>
>>
>>
>>
>
--
_,,,^..^,,,_
best, Eliot
July 29, 2015
Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?
by Alexandre Bergel
Pure agile development: the latest version is the one that count.
You need to update two packages: Roassal2 and Trachel.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Jul 29, 2015, at 3:24 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote:
>
> Or a configuration? Which one?
>
> --HH
>
> On 7/29/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote:
>> Thanks for the updated GANTT script.
>>
>> My question was about the version of Roassal to load.
>>
>> Which one?
>> I just go for version 1000?
>>
>> See screenshot.
>>
>> --Hannes
>>
>> On 7/29/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>>> You should load the latest Roassal.
>>>>
>>>> How do I do that? I just loaded Roassal into a fresh Pharo4.0 image
>>>> and RTTimeLine is not included.
>>>
>>> We did some refactoring.
>>> Instead, you should do:
>>>
>>> -=-=-=-=-=-=-=-=
>>> data := #(#(WP1 0 5) #(WP2 5 8) #(WP3 7 10)).
>>>
>>> b := RTTimeline new.
>>>
>>> s := RTTimelineSet new.
>>> s objects: data.
>>> s lineIdentifier: #first.
>>> s start: #second.
>>> s end: #third.
>>> b add: s.
>>>
>>> b axisX
>>> numberOfLabels: 5;
>>> labelRotation: -45;
>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>
>>> d := RTVerticalTickLineDecorator new.
>>> d shape line color: Color white.
>>> b addDecorator: d.
>>> b
>>> -=-=-=-=-=-=-=-=
>>>
>>>
>>>
>>> The class RTTimelineExample contains many examples
>>>
>>> Let us know how it goes
>>>
>>> Alexandre
>>>
>>>>
>>>>
>>>>> Alexandre
>>>>>
>>>>>
>>>>>
>>>>>> Le 9 mai 2015 à 19:06, H. Hirzel <hannes.hirzel(a)gmail.com> a écrit :
>>>>>>
>>>>>> Thank you for the examples, Alexandre!
>>>>>>
>>>>>> I have Pharo 4.0 with Roassal 2.0 installed (AlexandreBergel.718)
>>>>>>
>>>>>> I paste the following into a 'Playground' window and 'do it'.
>>>>>>
>>>>>> b := RTTimeLine new.
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>>>>
>>>>>> b axisX numberOfLabels: 5.
>>>>>> b
>>>>>>
>>>>>> I get the error message that RTTimeLine is not known.
>>>>>>
>>>>>> What am I missing?
>>>>>>
>>>>>> --Hannes
>>>>>>
>>>>>>
>>>>>>> On 5/8/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>>>>> Hi Hannes!
>>>>>>>
>>>>>>> Here is a first shoot paired-programmed with Juraj using Roassal:
>>>>>>>
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>> b := RTTimeLine new.
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b axisX numberOfLabels: 5.
>>>>>>> b
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Here some slightly more elaborated example:
>>>>>>>
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>> âOne color per entry"
>>>>>>> | b d |
>>>>>>> b := RTTimeLine new.
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end:
>>>>>>> 5).
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end:
>>>>>>> 8).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end:
>>>>>>> 5).
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end:
>>>>>>> 8).
>>>>>>>
>>>>>>> d := RTVerticalTickLineDecorator new.
>>>>>>> d shape line color: Color white.
>>>>>>> b addDecorator: d.
>>>>>>> b axisX
>>>>>>> numberOfLabels: 5;
>>>>>>> labelRotation: -45;
>>>>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>>>>
>>>>>>> b shape color: (RTMultiLinearColorForIdentity new objects: b
>>>>>>> entries).
>>>>>>> b
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> One color per timeline
>>>>>>>
>>>>>>>
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>> | b |
>>>>>>> b := RTTimeLine new.
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end:
>>>>>>> 5).
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end:
>>>>>>> 8).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end:
>>>>>>> 5).
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end:
>>>>>>> 10).
>>>>>>>
>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end:
>>>>>>> 8).
>>>>>>>
>>>>>>> d := RTVerticalTickLineDecorator new.
>>>>>>> d shape line color: Color white.
>>>>>>> b addDecorator: d.
>>>>>>> b axisX
>>>>>>> numberOfLabels: 5;
>>>>>>> labelRotation: -45;
>>>>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>>>>
>>>>>>> b shape color: (RTMultiLinearColorForIdentity new command:
>>>>>>> #identifier;
>>>>>>> objects: #(c1 c2 c3 c4 c5)).
>>>>>>> b
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>>
>>>>>>>
>>>>>>> Age of some classes:
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>> | b |
>>>>>>> b := RTTimeLine new.
>>>>>>> b extent: 500 @ 500.
>>>>>>> ((RTShape withAllSubclasses sortedAs: #ageInDaysRounded) select:
>>>>>>> #hasMethods)
>>>>>>> do: [ :cls |
>>>>>>> e := RTTimeLineEntry new.
>>>>>>> e identifier: cls.
>>>>>>> e start: cls computeYoungestMethod ageInDays.
>>>>>>> e end: cls computeOldestMethod ageInDays.
>>>>>>> b addEntry: e ].
>>>>>>> b
>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> All these examples are in the Roassal time line example menu.
>>>>>>>
>>>>>>> This is still an early version. Let us know how it goes!
>>>>>>> https://www.facebook.com/ObjectProfile/posts/840542572699008
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Alexandre
>>>>>>>
>>>>>>> --
>>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>>>> Alexandre Bergel http://www.bergel.eu
>>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On May 7, 2015, at 4:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hello
>>>>>>>>
>>>>>>>> Has somebody done a GANTT chart?
>>>>>>>>
>>>>>>>> GanttChartMorph openOn: aCollectionOfActivities
>>>>>>>>
>>>>>>>> ?
>>>>>>>>
>>>>>>>> Activities have
>>>>>>>> - id
>>>>>>>> - description
>>>>>>>> - start date
>>>>>>>> - end date
>>>>>>>> ?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> Hannes
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>
>>>
>>
> <Roassal2_configurations_Screenshot from 2015-07-29 18:23:50.png>_______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
July 29, 2015
Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?
by H. Hirzel
Or a configuration? Which one?
--HH
On 7/29/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote:
> Thanks for the updated GANTT script.
>
> My question was about the version of Roassal to load.
>
> Which one?
> I just go for version 1000?
>
> See screenshot.
>
> --Hannes
>
> On 7/29/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>> You should load the latest Roassal.
>>>
>>> How do I do that? I just loaded Roassal into a fresh Pharo4.0 image
>>> and RTTimeLine is not included.
>>
>> We did some refactoring.
>> Instead, you should do:
>>
>> -=-=-=-=-=-=-=-=
>> data := #(#(WP1 0 5) #(WP2 5 8) #(WP3 7 10)).
>>
>> b := RTTimeline new.
>>
>> s := RTTimelineSet new.
>> s objects: data.
>> s lineIdentifier: #first.
>> s start: #second.
>> s end: #third.
>> b add: s.
>>
>> b axisX
>> numberOfLabels: 5;
>> labelRotation: -45;
>> labelConversion: [ :v | Date year: 2015 day: v ].
>>
>> d := RTVerticalTickLineDecorator new.
>> d shape line color: Color white.
>> b addDecorator: d.
>> b
>> -=-=-=-=-=-=-=-=
>>
>>
>>
>> The class RTTimelineExample contains many examples
>>
>> Let us know how it goes
>>
>> Alexandre
>>
>>>
>>>
>>>> Alexandre
>>>>
>>>>
>>>>
>>>>> Le 9 mai 2015 à 19:06, H. Hirzel <hannes.hirzel(a)gmail.com> a écrit :
>>>>>
>>>>> Thank you for the examples, Alexandre!
>>>>>
>>>>> I have Pharo 4.0 with Roassal 2.0 installed (AlexandreBergel.718)
>>>>>
>>>>> I paste the following into a 'Playground' window and 'do it'.
>>>>>
>>>>> b := RTTimeLine new.
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>>>
>>>>> b axisX numberOfLabels: 5.
>>>>> b
>>>>>
>>>>> I get the error message that RTTimeLine is not known.
>>>>>
>>>>> What am I missing?
>>>>>
>>>>> --Hannes
>>>>>
>>>>>
>>>>>> On 5/8/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>>>> Hi Hannes!
>>>>>>
>>>>>> Here is a first shoot paired-programmed with Juraj using Roassal:
>>>>>>
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>> b := RTTimeLine new.
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end:
>>>>>> 10).
>>>>>>
>>>>>> b axisX numberOfLabels: 5.
>>>>>> b
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>
>>>>>>
>>>>>>
>>>>>> Here some slightly more elaborated example:
>>>>>>
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>> âOne color per entry"
>>>>>> | b d |
>>>>>> b := RTTimeLine new.
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end:
>>>>>> 5).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end:
>>>>>> 8).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end:
>>>>>> 5).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end:
>>>>>> 10).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end:
>>>>>> 10).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end:
>>>>>> 10).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end:
>>>>>> 8).
>>>>>>
>>>>>> d := RTVerticalTickLineDecorator new.
>>>>>> d shape line color: Color white.
>>>>>> b addDecorator: d.
>>>>>> b axisX
>>>>>> numberOfLabels: 5;
>>>>>> labelRotation: -45;
>>>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>>>
>>>>>> b shape color: (RTMultiLinearColorForIdentity new objects: b
>>>>>> entries).
>>>>>> b
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>
>>>>>>
>>>>>>
>>>>>> One color per timeline
>>>>>>
>>>>>>
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>> | b |
>>>>>> b := RTTimeLine new.
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end:
>>>>>> 5).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end:
>>>>>> 8).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end:
>>>>>> 5).
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end:
>>>>>> 10).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end:
>>>>>> 10).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end:
>>>>>> 10).
>>>>>>
>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end:
>>>>>> 8).
>>>>>>
>>>>>> d := RTVerticalTickLineDecorator new.
>>>>>> d shape line color: Color white.
>>>>>> b addDecorator: d.
>>>>>> b axisX
>>>>>> numberOfLabels: 5;
>>>>>> labelRotation: -45;
>>>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>>>
>>>>>> b shape color: (RTMultiLinearColorForIdentity new command:
>>>>>> #identifier;
>>>>>> objects: #(c1 c2 c3 c4 c5)).
>>>>>> b
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>
>>>>>>
>>>>>> Age of some classes:
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>> | b |
>>>>>> b := RTTimeLine new.
>>>>>> b extent: 500 @ 500.
>>>>>> ((RTShape withAllSubclasses sortedAs: #ageInDaysRounded) select:
>>>>>> #hasMethods)
>>>>>> do: [ :cls |
>>>>>> e := RTTimeLineEntry new.
>>>>>> e identifier: cls.
>>>>>> e start: cls computeYoungestMethod ageInDays.
>>>>>> e end: cls computeOldestMethod ageInDays.
>>>>>> b addEntry: e ].
>>>>>> b
>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>>
>>>>>>
>>>>>>
>>>>>> All these examples are in the Roassal time line example menu.
>>>>>>
>>>>>> This is still an early version. Let us know how it goes!
>>>>>> https://www.facebook.com/ObjectProfile/posts/840542572699008
>>>>>>
>>>>>> Cheers,
>>>>>> Alexandre
>>>>>>
>>>>>> --
>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>>> Alexandre Bergel http://www.bergel.eu
>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On May 7, 2015, at 4:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hello
>>>>>>>
>>>>>>> Has somebody done a GANTT chart?
>>>>>>>
>>>>>>> GanttChartMorph openOn: aCollectionOfActivities
>>>>>>>
>>>>>>> ?
>>>>>>>
>>>>>>> Activities have
>>>>>>> - id
>>>>>>> - description
>>>>>>> - start date
>>>>>>> - end date
>>>>>>> ?
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Hannes
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>>
>
July 29, 2015
Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?
by H. Hirzel
Thanks for the updated GANTT script.
My question was about the version of Roassal to load.
Which one?
I just go for version 1000?
See screenshot.
--Hannes
On 7/29/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>> You should load the latest Roassal.
>>
>> How do I do that? I just loaded Roassal into a fresh Pharo4.0 image
>> and RTTimeLine is not included.
>
> We did some refactoring.
> Instead, you should do:
>
> -=-=-=-=-=-=-=-=
> data := #(#(WP1 0 5) #(WP2 5 8) #(WP3 7 10)).
>
> b := RTTimeline new.
>
> s := RTTimelineSet new.
> s objects: data.
> s lineIdentifier: #first.
> s start: #second.
> s end: #third.
> b add: s.
>
> b axisX
> numberOfLabels: 5;
> labelRotation: -45;
> labelConversion: [ :v | Date year: 2015 day: v ].
>
> d := RTVerticalTickLineDecorator new.
> d shape line color: Color white.
> b addDecorator: d.
> b
> -=-=-=-=-=-=-=-=
>
>
>
> The class RTTimelineExample contains many examples
>
> Let us know how it goes
>
> Alexandre
>
>>
>>
>>> Alexandre
>>>
>>>
>>>
>>>> Le 9 mai 2015 à 19:06, H. Hirzel <hannes.hirzel(a)gmail.com> a écrit :
>>>>
>>>> Thank you for the examples, Alexandre!
>>>>
>>>> I have Pharo 4.0 with Roassal 2.0 installed (AlexandreBergel.718)
>>>>
>>>> I paste the following into a 'Playground' window and 'do it'.
>>>>
>>>> b := RTTimeLine new.
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>>
>>>> b axisX numberOfLabels: 5.
>>>> b
>>>>
>>>> I get the error message that RTTimeLine is not known.
>>>>
>>>> What am I missing?
>>>>
>>>> --Hannes
>>>>
>>>>
>>>>> On 5/8/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>>> Hi Hannes!
>>>>>
>>>>> Here is a first shoot paired-programmed with Juraj using Roassal:
>>>>>
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>> b := RTTimeLine new.
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>>>
>>>>> b axisX numberOfLabels: 5.
>>>>> b
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>
>>>>>
>>>>>
>>>>> Here some slightly more elaborated example:
>>>>>
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>> âOne color per entry"
>>>>> | b d |
>>>>> b := RTTimeLine new.
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end: 5).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end: 8).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end: 5).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end:
>>>>> 10).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end:
>>>>> 10).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end:
>>>>> 10).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end: 8).
>>>>>
>>>>> d := RTVerticalTickLineDecorator new.
>>>>> d shape line color: Color white.
>>>>> b addDecorator: d.
>>>>> b axisX
>>>>> numberOfLabels: 5;
>>>>> labelRotation: -45;
>>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>>
>>>>> b shape color: (RTMultiLinearColorForIdentity new objects: b
>>>>> entries).
>>>>> b
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>
>>>>>
>>>>>
>>>>> One color per timeline
>>>>>
>>>>>
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>> | b |
>>>>> b := RTTimeLine new.
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end: 5).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end: 8).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end: 5).
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end:
>>>>> 10).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end:
>>>>> 10).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end:
>>>>> 10).
>>>>>
>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end: 8).
>>>>>
>>>>> d := RTVerticalTickLineDecorator new.
>>>>> d shape line color: Color white.
>>>>> b addDecorator: d.
>>>>> b axisX
>>>>> numberOfLabels: 5;
>>>>> labelRotation: -45;
>>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>>
>>>>> b shape color: (RTMultiLinearColorForIdentity new command:
>>>>> #identifier;
>>>>> objects: #(c1 c2 c3 c4 c5)).
>>>>> b
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>
>>>>>
>>>>> Age of some classes:
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>> | b |
>>>>> b := RTTimeLine new.
>>>>> b extent: 500 @ 500.
>>>>> ((RTShape withAllSubclasses sortedAs: #ageInDaysRounded) select:
>>>>> #hasMethods)
>>>>> do: [ :cls |
>>>>> e := RTTimeLineEntry new.
>>>>> e identifier: cls.
>>>>> e start: cls computeYoungestMethod ageInDays.
>>>>> e end: cls computeOldestMethod ageInDays.
>>>>> b addEntry: e ].
>>>>> b
>>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>>
>>>>>
>>>>>
>>>>> All these examples are in the Roassal time line example menu.
>>>>>
>>>>> This is still an early version. Let us know how it goes!
>>>>> https://www.facebook.com/ObjectProfile/posts/840542572699008
>>>>>
>>>>> Cheers,
>>>>> Alexandre
>>>>>
>>>>> --
>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>> Alexandre Bergel http://www.bergel.eu
>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>
>>>>>
>>>>>
>>>>>> On May 7, 2015, at 4:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hello
>>>>>>
>>>>>> Has somebody done a GANTT chart?
>>>>>>
>>>>>> GanttChartMorph openOn: aCollectionOfActivities
>>>>>>
>>>>>> ?
>>>>>>
>>>>>> Activities have
>>>>>> - id
>>>>>> - description
>>>>>> - start date
>>>>>> - end date
>>>>>> ?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Hannes
>>>>
>>>> _______________________________________________
>>>> 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
>
>
July 29, 2015
Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?
by Alexandre Bergel
>> You should load the latest Roassal.
>
> How do I do that? I just loaded Roassal into a fresh Pharo4.0 image
> and RTTimeLine is not included.
We did some refactoring.
Instead, you should do:
-=-=-=-=-=-=-=-=
data := #(#(WP1 0 5) #(WP2 5 8) #(WP3 7 10)).
b := RTTimeline new.
s := RTTimelineSet new.
s objects: data.
s lineIdentifier: #first.
s start: #second.
s end: #third.
b add: s.
b axisX
numberOfLabels: 5;
labelRotation: -45;
labelConversion: [ :v | Date year: 2015 day: v ].
d := RTVerticalTickLineDecorator new.
d shape line color: Color white.
b addDecorator: d.
b
-=-=-=-=-=-=-=-=
The class RTTimelineExample contains many examples
Let us know how it goes
Alexandre
>
>
>> Alexandre
>>
>>
>>
>>> Le 9 mai 2015 à 19:06, H. Hirzel <hannes.hirzel(a)gmail.com> a écrit :
>>>
>>> Thank you for the examples, Alexandre!
>>>
>>> I have Pharo 4.0 with Roassal 2.0 installed (AlexandreBergel.718)
>>>
>>> I paste the following into a 'Playground' window and 'do it'.
>>>
>>> b := RTTimeLine new.
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>
>>> b axisX numberOfLabels: 5.
>>> b
>>>
>>> I get the error message that RTTimeLine is not known.
>>>
>>> What am I missing?
>>>
>>> --Hannes
>>>
>>>
>>>> On 5/8/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>> Hi Hannes!
>>>>
>>>> Here is a first shoot paired-programmed with Juraj using Roassal:
>>>>
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>> b := RTTimeLine new.
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>>
>>>> b axisX numberOfLabels: 5.
>>>> b
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>
>>>>
>>>>
>>>> Here some slightly more elaborated example:
>>>>
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>> âOne color per entry"
>>>> | b d |
>>>> b := RTTimeLine new.
>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end: 5).
>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end: 8).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end: 5).
>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end: 10).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end: 10).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end: 10).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end: 8).
>>>>
>>>> d := RTVerticalTickLineDecorator new.
>>>> d shape line color: Color white.
>>>> b addDecorator: d.
>>>> b axisX
>>>> numberOfLabels: 5;
>>>> labelRotation: -45;
>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>
>>>> b shape color: (RTMultiLinearColorForIdentity new objects: b
>>>> entries).
>>>> b
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>
>>>>
>>>>
>>>> One color per timeline
>>>>
>>>>
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>> | b |
>>>> b := RTTimeLine new.
>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end: 5).
>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end: 8).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end: 5).
>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end: 10).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end: 10).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end: 10).
>>>>
>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end: 8).
>>>>
>>>> d := RTVerticalTickLineDecorator new.
>>>> d shape line color: Color white.
>>>> b addDecorator: d.
>>>> b axisX
>>>> numberOfLabels: 5;
>>>> labelRotation: -45;
>>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>>
>>>> b shape color: (RTMultiLinearColorForIdentity new command:
>>>> #identifier;
>>>> objects: #(c1 c2 c3 c4 c5)).
>>>> b
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>
>>>>
>>>> Age of some classes:
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>> | b |
>>>> b := RTTimeLine new.
>>>> b extent: 500 @ 500.
>>>> ((RTShape withAllSubclasses sortedAs: #ageInDaysRounded) select:
>>>> #hasMethods)
>>>> do: [ :cls |
>>>> e := RTTimeLineEntry new.
>>>> e identifier: cls.
>>>> e start: cls computeYoungestMethod ageInDays.
>>>> e end: cls computeOldestMethod ageInDays.
>>>> b addEntry: e ].
>>>> b
>>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>>
>>>>
>>>>
>>>> All these examples are in the Roassal time line example menu.
>>>>
>>>> This is still an early version. Let us know how it goes!
>>>> https://www.facebook.com/ObjectProfile/posts/840542572699008
>>>>
>>>> Cheers,
>>>> Alexandre
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>>> On May 7, 2015, at 4:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote:
>>>>>
>>>>> Hello
>>>>>
>>>>> Has somebody done a GANTT chart?
>>>>>
>>>>> GanttChartMorph openOn: aCollectionOfActivities
>>>>>
>>>>> ?
>>>>>
>>>>> Activities have
>>>>> - id
>>>>> - description
>>>>> - start date
>>>>> - end date
>>>>> ?
>>>>>
>>>>> Regards
>>>>>
>>>>> Hannes
>>>
>>> _______________________________________________
>>> 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
July 29, 2015
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/50198
Home: https://github.com/pharo-project/pharo-core
July 29, 2015
[pharo-project/pharo-core] 7b3c81: 50198
by GitHub
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 7b3c81bb45a3103eed62892087bfc2c1c5c86f76
https://github.com/pharo-project/pharo-core/commit/7b3c81bb45a3103eed628920…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2015-07-29 (Wed, 29 Jul 2015)
Changed paths:
M ProfStef-Core.package/LessonView.class/instance/accessing/sourceTextModel.st
M ProfStef-Core.package/LessonView.class/instance/gui/showLesson_withTitle_.st
A ProfStef-Core.package/LessonView.class/instance/hack/hasBindingOf_.st
A ProfStef-Core.package/LessonView.class/instance/hack/hasBindingThatBeginsWith_.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50197.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50198.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50197.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50198.st
M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M Slot.package/UnlimitedInstanceVariableSlot.class/instance/TODO/todo.st
A Slot.package/UnlimitedInstanceVariableSlot.class/instance/code generation/emitStore_.st
A Slot.package/UnlimitedInstanceVariableSlot.class/instance/code generation/emitValue_.st
Log Message:
-----------
50198
16063 Byte code generation UnlimitedInstanceVariableSlot
https://pharo.fogbugz.com/f/cases/16063
16061 DNU when running ProfStef tests
https://pharo.fogbugz.com/f/cases/16061
http://files.pharo.org/image/50/50198.zip
July 29, 2015
Re: [Pharo-dev] About "compileSilently"
by roberto.minelli@usi.ch
Yeah, I also removed #prepareDebuggerExample from my image...
It is the third time in the last two weeks that this happens to me and I have to spend lot of time to recover the changes from one image to the other.
Cheers,
R
> On 29 Jul 2015, at 11:16, Marcus Denker <marcus.denker(a)inria.fr> wrote:
>
> Not known, but the whole #prepareDebuggerExample method is very strange. We should remove it.
>
>> On 29 Jul 2015, at 16:05, roberto.minelli(a)usi.ch wrote:
>>
>> Hi,
>>
>> I donât know if this is related, but recently happens something super strange to my images.
>>
>> From time to time, in one of my commits the author is suddenly changed to âAutoGenTutorialâ and, if I donât spot this, from now on the Pharo image stops recording my changes.
>>
>> This is very frustrating.. is this a known issue?
>>
>> Thanks a lot,
>> RM
>>
>>
>>> On 30 May 2015, at 06:01, Nicolai Hess <nicolaihess(a)web.de> wrote:
>>>
>>>
>>>
>>> 2015-05-28 21:14 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>:
>>> Le 28/05/2015 20:40, Nicolai Hess a écrit :
>>>
>>>
>>> 2015-05-28 16:55 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com
>>> <mailto:thierry.goubier@gmail.com>>:
>>>
>>>
>>>
>>> 2015-05-28 16:49 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de
>>> <mailto:nicolaihess@web.de>>:
>>>
>>> How silent should "compileSilently" be?
>>>
>>> no trace in the system :
>>> 15314 <https://pharo.fogbugz.com/default.asp?15314>
>>> compileSilently and method history / changes file
>>>
>>> not half silenlty
>>> 13023 <https://pharo.fogbugz.com/default.asp?13023>
>>> Test Cases should not do things half silently
>>>
>>> not "SystemAnnouncer-silent"
>>> 10560 <https://pharo.fogbugz.com/default.asp?10560>
>>> SystemAnnouncer and compileSilently
>>>
>>>
>>> ?
>>>
>>> What do you think, what granularity of "silent" do we need.
>>> I see at least three different use cases:
>>>
>>> - just an ordinary compile
>>>
>>>
>>> ? Silent means that: Core infrastructure is not updated properly
>>> (i.e. RPackage) and tools (Browsers) can end desynchronised with the
>>> methods.
>>>
>>> - compile for tests
>>>
>>>
>>> Probably the one... But I wonder if this is a good idea anyway. I'd
>>> believe most tests using silently are using it wrongly and shouldn't
>>> be using it in the first place.
>>>
>>> - compile autogenerated methods.
>>>
>>>
>>> This one may not be silent. If the auto-generated method will be
>>> visible (saved in a package, can be browsed, etc...) then it
>>> shouldn't be silent.
>>>
>>>
>>>
>>> What about compiled method for which the source did not change?
>>>
>>> Hum. I see what you mean.
>>>
>>> I do silent compilation when I install tracing probes inside methods, to make sure they don't appear as changed in browsers... But I don't create new methods. I guess this will be the same with the MetaLinks Marcus is preparing.
>>>
>>> But, yes, as I said: methods or changes that are not visible then you can make them silent.
>>>
>>> But in a different case, such as compiling a SmaCC parser, you want that code to be visible.
>>>
>>>
>>> For NativeBoost generated methods, I may want to have that code visible too.
>>> I just don't want the code to be marked as "changed" after a recompilation.
>>>
>>> For example, a subclass of NativeBoosts NBExternalStructure or NBExternalArray must be recompiled when used in a new session, or when the structure
>>> changed.
>>>
>>> The compiler installs the generated accessor methods and you may want to see that code - just to make sure the structure change was applied.
>>> But you really don't want this code in a changeset, because whenever you use this code in another image or in a new session it
>>> will be recompiled anyway.
>>>
>>>
>>>
>>> I am interested on this for issue 15315, everytime you open spotter,
>>> you'll get a new
>>>
>>> "method: PharoSyntaxTutorial divideTwoByZero; AutoGenTutorial 5/28/2015
>>> 20:34"
>>>
>>> in you changes file.
>>>
>>> This one makes for some annoying noise in the changes. But as I say below, maybe it doesn't matter.
>>>
>>> Another case are autogenerated methods from NativeBoost.
>>> For example, open a fresh image and execute code that triggers
>>> NativeBoost to install native functions for this session.
>>> (EllipseMorph new openInSceneView)
>>>
>>> And now look at your list of recent changes.
>>> I get about 30 entries for athens/cairo methods.
>>>
>>> One of the thing to consider is what you use the changes for. If it is to recover from crashes, then what you just need to make sure is that replaying all since the last save is ok... even if you have multiple times the same method source saved in it.
>>>
>>> Yes, you are right. It does not hurt to have this in the changes file. (But it does not have any use to be there).
>>>
>>>
>>> True changes management is happening in the packages these days, and most code written in the changes shouldn't be recorded there imho (oh, well, apart for the source pointer, of course).
>>>
>>> And other uses it could have (recording all do its, for example) is reimplemented / duplicated elsewhere in the system anyway.
>>>
>>> Thierry
>>
>
>
July 29, 2015
Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?
by H. Hirzel
On 5/10/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
> You should load the latest Roassal.
How do I do that? I just loaded Roassal into a fresh Pharo4.0 image
and RTTimeLine is not included.
--Hannes
> Alexandre
>
>
>
>> Le 9 mai 2015 à 19:06, H. Hirzel <hannes.hirzel(a)gmail.com> a écrit :
>>
>> Thank you for the examples, Alexandre!
>>
>> I have Pharo 4.0 with Roassal 2.0 installed (AlexandreBergel.718)
>>
>> I paste the following into a 'Playground' window and 'do it'.
>>
>> b := RTTimeLine new.
>>
>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>
>> b axisX numberOfLabels: 5.
>> b
>>
>> I get the error message that RTTimeLine is not known.
>>
>> What am I missing?
>>
>> --Hannes
>>
>>
>>> On 5/8/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>> Hi Hannes!
>>>
>>> Here is a first shoot paired-programmed with Juraj using Roassal:
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>> b := RTTimeLine new.
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; end: 5).
>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; end: 8).
>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; end: 10).
>>>
>>> b axisX numberOfLabels: 5.
>>> b
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>
>>>
>>>
>>> Here some slightly more elaborated example:
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>> âOne color per entry"
>>> | b d |
>>> b := RTTimeLine new.
>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end: 5).
>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end: 8).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end: 5).
>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end: 10).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end: 10).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end: 10).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end: 8).
>>>
>>> d := RTVerticalTickLineDecorator new.
>>> d shape line color: Color white.
>>> b addDecorator: d.
>>> b axisX
>>> numberOfLabels: 5;
>>> labelRotation: -45;
>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>
>>> b shape color: (RTMultiLinearColorForIdentity new objects: b
>>> entries).
>>> b
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>
>>>
>>>
>>> One color per timeline
>>>
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>> | b |
>>> b := RTTimeLine new.
>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; end: 5).
>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; end: 8).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; end: 5).
>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; end: 10).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; end: 10).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; end: 10).
>>>
>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; end: 8).
>>>
>>> d := RTVerticalTickLineDecorator new.
>>> d shape line color: Color white.
>>> b addDecorator: d.
>>> b axisX
>>> numberOfLabels: 5;
>>> labelRotation: -45;
>>> labelConversion: [ :v | Date year: 2015 day: v ].
>>>
>>> b shape color: (RTMultiLinearColorForIdentity new command:
>>> #identifier;
>>> objects: #(c1 c2 c3 c4 c5)).
>>> b
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>
>>>
>>> Age of some classes:
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>> | b |
>>> b := RTTimeLine new.
>>> b extent: 500 @ 500.
>>> ((RTShape withAllSubclasses sortedAs: #ageInDaysRounded) select:
>>> #hasMethods)
>>> do: [ :cls |
>>> e := RTTimeLineEntry new.
>>> e identifier: cls.
>>> e start: cls computeYoungestMethod ageInDays.
>>> e end: cls computeOldestMethod ageInDays.
>>> b addEntry: e ].
>>> b
>>> -=-=-=-=-=-=-=-=-=-=-=-=
>>>
>>>
>>>
>>> All these examples are in the Roassal time line example menu.
>>>
>>> This is still an early version. Let us know how it goes!
>>> https://www.facebook.com/ObjectProfile/posts/840542572699008
>>>
>>> Cheers,
>>> Alexandre
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>>> On May 7, 2015, at 4:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote:
>>>>
>>>> Hello
>>>>
>>>> Has somebody done a GANTT chart?
>>>>
>>>> GanttChartMorph openOn: aCollectionOfActivities
>>>>
>>>> ?
>>>>
>>>> Activities have
>>>> - id
>>>> - description
>>>> - start date
>>>> - end date
>>>> ?
>>>>
>>>> Regards
>>>>
>>>> Hannes
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
July 29, 2015
Re: [Pharo-dev] About "compileSilently"
by Marcus Denker
https://pharo.fogbugz.com/f/cases/16067/remove-prepareDebuggerExample <https://pharo.fogbugz.com/f/cases/16067/remove-prepareDebuggerExample>
> On 29 Jul 2015, at 16:16, Marcus Denker <marcus.denker(a)inria.fr> wrote:
>
> Not known, but the whole #prepareDebuggerExample method is very strange. We should remove it.
>
July 29, 2015