August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Google Code Shutdown

by Dimitris Chloupis

A workaround if you absolutely want to use gitfiletree is to install linux using a VM like virtual box , Ubuntu for example works very well with pharo https://www.virtualbox.org/ This way you avoid booting to another OS , you can also share your git folder to both windows and linux vm. This way you can use gitfiletree without ditching windows. Of course dual boot can work too if you dont need to use Pharo with windoom. VM option works also if you want to install MacOS on your windows pc. On Mon, Aug 3, 2015 at 1:13 PM Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Hi, > > > > Sorry but I am using Windowsâ¦ not because I want to but because I have > to... So the therapy will not work ;) > > Actually, the bugtracker of Moose can be on github, but the git user > experience under Windows has to be improved if we want to use efficiently > the other functionalities of github (pull requests, commit, branches,â¦). > > > > Cheers, > > Vincent > > > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* Peter UhnÃ¡k > *EnvoyÃ© :* lundi 3 aoÃ»t 2015 11:56 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] Google Code Shutdown > > > > As long as nobody on your team is using Windows, git(hub) is quite good. :) > > (And if you have Windows user, then find him a therapy first, or push for > libcgit :)) > > > > On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > Github is indeed appealing. > > Cheers, > Alexandre > > > > > > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > > Tudor Girba-2 wrote > >> Would you like to help us move the moose-technology project? > > > > Sure. What do you have in mind? It seems exporting to GitHub is the > easiest > > option. There are a few limitations, but I've had good experiences... > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. >

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by serge.stinckwich＠gmail.com

Create a repo for moose in order to have a bug tracker, move issues from Google code to this repo :-) Sorry I'm on my phone, I can't help now ;-) Sent from my iPhone > On 3 aoÃ»t 2015, at 13:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I just created this organization: > https://github.com/orgs/moosetechnology/dashboard > > What should I do next? > > Cheers, > Doru > >> On Mon, Aug 3, 2015 at 12:55 PM, <serge.stinckwich(a)gmail.com> wrote: >> Yes but at the moment only the bug tracker will be used I guess. Maybe someone can create a MOOSE org ? >> >> Sent from my iPhone >> >>> On 3 aoÃ»t 2015, at 11:56, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> As long as nobody on your team is using Windows, git(hub) is quite good. :) >>> (And if you have Windows user, then find him a therapy first, or push for libcgit :)) >>> >>>> On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> Github is indeed appealing. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> >>>> > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>>> > >>>> > Tudor Girba-2 wrote >>>> >> Would you like to help us move the moose-technology project? >>>> > >>>> > Sure. What do you have in mind? It seems exporting to GitHub is the easiest >>>> > option. There are a few limitations, but I've had good experiences... >>>> > >>>> > >>>> > >>>> > ----- >>>> > Cheers, >>>> > Sean >>>> > -- >>>> > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html >>>> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>>> > >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Tudor Girba

I just created this organization: https://github.com/orgs/moosetechnology/dashboard What should I do next? Cheers, Doru On Mon, Aug 3, 2015 at 12:55 PM, <serge.stinckwich(a)gmail.com> wrote: > Yes but at the moment only the bug tracker will be used I guess. Maybe > someone can create a MOOSE org ? > > Sent from my iPhone > > On 3 aoÃ»t 2015, at 11:56, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > As long as nobody on your team is using Windows, git(hub) is quite good. :) > (And if you have Windows user, then find him a therapy first, or push for > libcgit :)) > > On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > >> Github is indeed appealing. >> >> Cheers, >> Alexandre >> >> >> >> > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> >> wrote: >> > >> > Tudor Girba-2 wrote >> >> Would you like to help us move the moose-technology project? >> > >> > Sure. What do you have in mind? It seems exporting to GitHub is the >> easiest >> > option. There are a few limitations, but I've had good experiences... >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: >> http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by serge.stinckwich＠gmail.com

Yes but at the moment only the bug tracker will be used I guess. Maybe someone can create a MOOSE org ? Sent from my iPhone > On 3 aoÃ»t 2015, at 11:56, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > As long as nobody on your team is using Windows, git(hub) is quite good. :) > (And if you have Windows user, then find him a therapy first, or push for libcgit :)) > >> On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Github is indeed appealing. >> >> Cheers, >> Alexandre >> >> >> >> > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> > >> > Tudor Girba-2 wrote >> >> Would you like to help us move the moose-technology project? >> > >> > Sure. What do you have in mind? It seems exporting to GitHub is the easiest >> > option. There are a few limitations, but I've had good experiences... >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Peter UhnÃ¡k

> > but the git user experience under Windows has to be improved if we want to > use efficiently the other functionalities of github (pull requests, commit, > branches,â¦). > Well some of the experience can be mitigated with tools like GitHub for Windows, but the main problem is that git with Pharo is incredibly unstable on Windows and crashes constantly. That's our experience with it so my colleague had to switch to pure filetree out of frustration. This however is NOT problem of git, it's problem of OSProcess. But it does render it almost unusable for now. (At least for us.) Peter

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Blondeau Vincent

Hi, Sorry but I am using Windowsâ¦ not because I want to but because I have to... So the therapy will not work ;) Actually, the bugtracker of Moose can be on github, but the git user experience under Windows has to be improved if we want to use efficiently the other functionalities of github (pull requests, commit, branches,â¦). Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Peter UhnÃ¡k EnvoyÃ© : lundi 3 aoÃ»t 2015 11:56 Ã : Pharo Development List Objet : Re: [Pharo-dev] Google Code Shutdown As long as nobody on your team is using Windows, git(hub) is quite good. :) (And if you have Windows user, then find him a therapy first, or push for libcgit :)) On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Github is indeed appealing. Cheers, Alexandre > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > Tudor Girba-2 wrote >> Would you like to help us move the moose-technology project? > > Sure. What do you have in mind? It seems exporting to GitHub is the easiest > option. There are a few limitations, but I've had good experiences... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Peter UhnÃ¡k

As long as nobody on your team is using Windows, git(hub) is quite good. :) (And if you have Windows user, then find him a therapy first, or push for libcgit :)) On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Github is indeed appealing. > > Cheers, > Alexandre > > > > > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > > Tudor Girba-2 wrote > >> Would you like to help us move the moose-technology project? > > > > Sure. What do you have in mind? It seems exporting to GitHub is the > easiest > > option. There are a few limitations, but I've had good experiences... > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Aug. 3, 2015

Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?

by H. Hirzel

This worked fine. The code is very readable and easy to adapt once there is an example. Thank you. --Hannes On 8/1/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Sure, this is easy. Axis supports a method called #labelConversion: [ > :aNumericalValue | â¦ ] > You need to provide a bloc that returns a string. > > For example: > > > > | data b s | > data := #(#(c1 0 5) #(c1 6 8) #(c2 0 5) #(c2 8 10) #(c3 0 10) #(c4 5 10) > #(c5 5 8)). > > b := RTTimeline new. > > s := RTTimelineSet new. > s objects: data. > s lineIdentifier: #first. > s start: #second. > s end: #third. > b add: s. > > b axisY > title: 'Task'. > b axisX > numberOfLabels: 10; > title: 'Week day'; > labelConversion: [ :v | v \\ 7 + 1 ]. > > b build. > ^ b view > > Does this help? > > Cheers, > Alexandre > > > >> On Aug 1, 2015, at 12:48 AM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> The SVG export accessible through the '...' menu works fine. >> >> A new question regarding the labeling of the x-axis. >> >> How do I specify that I want to see months >> >> 8 9 10 11 12 >> >> only? >> >> data := #( #(WP1 8 12) #(WP2 8 10) #(WP3 10 11) >> #(WP4 11 12) >> >> >> >> And is something like this possible? >> >> >> 8 9 10 11 12 1 2 3 4 >> >> >> --Hannes >> >> >> On 7/31/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> The ââ¦â button, top right of a GTInspector that is showing a Roassal >>> visualization. >>> >>> https://dl.dropboxusercontent.com/u/31543901/TMP/Screen%20Shot%202015-07-30… >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Jul 30, 2015, at 2:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> >>>> Which menu? Could you describe it verbally please where to click? The >>>> picture did not come through. >>>> >>>> --Hannes >>>> >>>> On 7/30/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> Simply use the menu: >>>>> >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>>> On Jul 30, 2015, at 11:59 AM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> Alexandre, >>>>>> >>>>>> This is really agile ... version 1005 of Roassal loaded and version >>>>>> 305 of Trachel :-) >>>>>> >>>>>> The GANTT chart works fine, see screen shot. >>>>>> >>>>>> How do I export it as SVG code in Roassal? >>>>>> >>>>>> --Hannes >>>>>> >>>>>> On 7/29/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> <Pharo_Roassal_GANTT_chart_Screenshot from 2015-07-30 14:55:31.png> >>>>> >>>>> >>>> >>> >>> >>> >> <Roassal_timeline_x_axis_question_Screenshot from 2015-08-01.png> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Aug. 3, 2015

Re: [Pharo-dev] Nautilus new buttons not buttons?

by Esteban Lorenzano

I just talked with Franck and we agree on trying to move most of those functionality to a toolbarâ¦ letâs hope this solves our small problem :) Esteban > On 03 Aug 2015, at 01:06, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 01/08/15 13:25, Franck Warlouzet wrote: >> Hello, >> >> Yes it looks a little bit 'lite' but we did not want to have 2 buttons >> with the same look but two different kinds of actions. Hierarchy button >> changes the window itself and variable and scoped open a new menu or >> window. >> >> I agree about the class side button. > > Every button in the Nautilus browser has lots of improvement potential. > > It should be visually clear where a button applies to. Scoped applies to the package pane, Variables to the class pane, Hierarchy/Flat to the class pane, Class side to the methods and methods category pane and comments to the text pane. The location of the buttons could reflect that. > > It should be visually clear if a button represents a direct action, an indirect action, shows a menu, represents a state change action or the current state or opens a menu > > The buttons should have hover texts explaining what the button does and when it is (and not) applicable. > > A button should react to left-click only, not to right-click (or with a menu to right click). > > And then there are also some Rubric widgets in the text pane that behave somewhat like buttons. > > And now for something completely different: > Why are the variables shown in reversed order? I rarely look for > users of DependentFields > > > Stephan > >

Aug. 3, 2015

WhatsUp from: 2015-08-03 until: 2015-08-16

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-08-16 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Aug. 3, 2015