February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo contribution CI: Email on failed build

by Norbert Hartl

Am 25.02.2014 um 16:48 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > guten Tag Nortbert, > > I am sure you know more about Jenkins than I do, but yes you can (and I do use this feature): > > https://ci.inria.fr/pharo-contribution/job/ZTimestamp/configure > > <Screen Shot 2014-02-25 at 16.45.19.png> > > You do have to log in of course. > I was logged in but as this is a foreign service I forgot that I can configure it myself and assumed the opposite :) Just another embarrassing moment. thanks, Norbert > Regards, > > Sven > > On 25 Feb 2014, at 16:42, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Is it possible to receive an email when the build of the project I registered turns to unstable? >> >> Norbert >

Feb. 25, 2014

Re: [Pharo-dev] Pharo contribution CI: Email on failed build

by Sven Van Caekenberghe

guten Tag Nortbert, I am sure you know more about Jenkins than I do, but yes you can (and I do use this feature): https://ci.inria.fr/pharo-contribution/job/ZTimestamp/configure You do have to log in of course. Regards, Sven On 25 Feb 2014, at 16:42, Norbert Hartl <norbert(a)hartl.name> wrote: > Is it possible to receive an email when the build of the project I registered turns to unstable? > > Norbert

Feb. 25, 2014

Pharo contribution CI: Email on failed build

by Norbert Hartl

Is it possible to receive an email when the build of the project I registered turns to unstable? Norbert

Feb. 25, 2014

Re: [Pharo-dev] Fwd: [Moose-dev] Text Displaying issue with Roassal

by Alexandre Bergel

Indeed cool keyboard! Alexandre On Feb 25, 2014, at 12:13 PM, J.F. Rick <self(a)je77.com> wrote: > Thanks, but the keyboard design is basically ripping off iOS and Android. Once it works, I'll share. > > Cheers, > > Jeff > > > On Tue, Feb 25, 2014 at 3:52 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This is a beautiful looking keyboard :) > > Doru > > > On Tue, Feb 25, 2014 at 2:45 PM, J.F. Rick <self(a)je77.com> wrote: > Here's an updated bug for this: > https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug > > Cheers, > > Jeff > > > On Tue, Feb 25, 2014 at 2:33 PM, Vincent Blondeau <vincent.blondeau(a)polytech-lille.net> wrote: > Hi Pharoers, > > We are encounter a problem with text displaying under Roassal. > Roassal is a Moose tool to make some graphics visualisations, principally graphs. > Some visualisations are displaying some text, like : > > - ROMondrianExample new centeredText > - ROMondrianExample new temporaryEdges > - ROMondrianExample new labeledRectangle > > They use AthensCanvas to render. > > Since the beginning of February, we experiment very strange problems with font displaying. See by yourself : > > What we expect : > <Mail Attachment.png> > What we have : > <Mail Attachment.png> > You can see that the letters in each word are not of the same size. > (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh Moose image : https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-…) > > We thought it was a font problem. So we updated the fonts to use this one : > LogicalFont familyName: StandardFonts defaultFont familyName pointSize: aSize > which is the default system font. (The fonts are located in ROFontOrganizerAthens). > > But the problem was not solved. > > After some searches, we saw that Roassal (via the ROAthensCanvas) uses AthensCairoCanvas and this class has been changed begin February to use native boost. > The closed issue related is : > > 12765 Athens font rendering missing letters and missizing others > https://pharo.fogbugz.com/f/cases/12765 > > That should resolve the problem instead of created one ;) > > > So if we load the older packages of Athens-Core and Athens-Cairo (before the issue resolution): > > Name: Athens-Core-MarcusDenker.34 > Author: MarcusDenker > Time: 5 July 2013, 10:59:47.206954 am > UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 > Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 > > Name: Athens-Cairo-MarcusDenker.51 > Author: MarcusDenker > Time: 26 August 2013, 4:03:06.190096 pm > UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 > Ancestors: Athens-Cairo-SebastianTleye.50 > > we have no problem of font displaying ! > > The question is : > What we should adapt in Roassal to support this new implementation of Athens ? Or is Athens (by the native boost primitives) broken ? > > Thanks in advance ! > > > Vincent BLONDEAU > > > > > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2014

Re: [Pharo-dev] Q: Restart the image

by ClÃ©ment Bera

Hello, One possibility is to save, then open again the current image with OSProcess, lastly close the first image. This would work for sure. The code would look like: Smalltalk snapshot: true andQuit: false. OSProcess executeInCommandLine: './pharo myImage.image'. Smalltalk snapshot: false andQuit: true. I do not remember how OSProcess works. I also do not remember how to get the path of the current image and VM to generate the proper command line instruction... But it should work. 2014-02-25 15:24 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > Out of curiosity: > > Is it possible to restart the image from within the > image itself - that means end the ST session and start > the VM with the same image again? > > Thx > T. > >

Feb. 25, 2014

Re: [Pharo-dev] Fwd: [Moose-dev] Text Displaying issue with Roassal

by Tudor Girba

Sure. It's just nice to see beautiful looking things like that rendered with Pharo :). Doru On Tue, Feb 25, 2014 at 4:13 PM, J.F. Rick <self(a)je77.com> wrote: > Thanks, but the keyboard design is basically ripping off iOS and Android. > Once it works, I'll share. > > Cheers, > > Jeff > > > On Tue, Feb 25, 2014 at 3:52 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> This is a beautiful looking keyboard :) >> >> Doru >> >> >> On Tue, Feb 25, 2014 at 2:45 PM, J.F. Rick <self(a)je77.com> wrote: >> >>> Here's an updated bug for this: >>> https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug >>> >>> Cheers, >>> >>> Jeff >>> >>> >>> On Tue, Feb 25, 2014 at 2:33 PM, Vincent Blondeau < >>> vincent.blondeau(a)polytech-lille.net> wrote: >>> >>>> Hi Pharoers, >>>> >>>> We are encounter a problem with text displaying under Roassal. >>>> Roassal is a Moose tool to make some graphics visualisations, >>>> principally graphs. >>>> Some visualisations are displaying some text, like : >>>> >>>> - ROMondrianExample new centeredText >>>> - ROMondrianExample new temporaryEdges >>>> - ROMondrianExample new labeledRectangle >>>> >>>> They use AthensCanvas to render. >>>> >>>> Since the beginning of February, we experiment very strange problems >>>> with font displaying. See by yourself : >>>> >>>> What we expect : >>>> >>>> What we have : >>>> >>>> You can see that the letters in each word are not of the same size. >>>> (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh >>>> Moose image : >>>> https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… >>>> ) >>>> >>>> We thought it was a font problem. So we updated the fonts to use this >>>> one : >>>> LogicalFont familyName: StandardFonts defaultFont familyName pointSize: >>>> aSize >>>> which is the default system font. (The fonts are located in >>>> ROFontOrganizerAthens). >>>> >>>> But the problem was not solved. >>>> >>>> After some searches, we saw that Roassal (via the ROAthensCanvas) uses >>>> AthensCairoCanvas and this class has been changed begin February to use >>>> native boost. >>>> The closed issue related is : >>>> >>>> 12765 Athens font rendering missing letters and missizing others >>>> https://pharo.fogbugz.com/f/cases/12765 >>>> >>>> That should resolve the problem instead of created one ;) >>>> >>>> >>>> So if we load the older packages of Athens-Core and Athens-Cairo >>>> (before the issue resolution): >>>> >>>> Name: Athens-Core-MarcusDenker.34 >>>> Author: MarcusDenker >>>> Time: 5 July 2013, 10:59:47.206954 am >>>> UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 >>>> Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 >>>> >>>> Name: Athens-Cairo-MarcusDenker.51 >>>> Author: MarcusDenker >>>> Time: 26 August 2013, 4:03:06.190096 pm >>>> UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 >>>> Ancestors: Athens-Cairo-SebastianTleye.50 >>>> >>>> we have no problem of font displaying ! >>>> >>>> The question is : >>>> What we should adapt in Roassal to support this new implementation of >>>> Athens ? Or is Athens (by the native boost primitives) broken ? >>>> >>>> Thanks in advance ! >>>> >>>> >>>> Vincent BLONDEAU >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Jochen "Jeff" Rick, Ph.D. >>> http://www.je77.com/ >>> Skype ID: jochenrick >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 25, 2014

Re: [Pharo-dev] Fwd: [Moose-dev] Text Displaying issue with Roassal

by J.F. Rick

Thanks, but the keyboard design is basically ripping off iOS and Android. Once it works, I'll share. Cheers, Jeff On Tue, Feb 25, 2014 at 3:52 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This is a beautiful looking keyboard :) > > Doru > > > On Tue, Feb 25, 2014 at 2:45 PM, J.F. Rick <self(a)je77.com> wrote: > >> Here's an updated bug for this: >> https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug >> >> Cheers, >> >> Jeff >> >> >> On Tue, Feb 25, 2014 at 2:33 PM, Vincent Blondeau < >> vincent.blondeau(a)polytech-lille.net> wrote: >> >>> Hi Pharoers, >>> >>> We are encounter a problem with text displaying under Roassal. >>> Roassal is a Moose tool to make some graphics visualisations, >>> principally graphs. >>> Some visualisations are displaying some text, like : >>> >>> - ROMondrianExample new centeredText >>> - ROMondrianExample new temporaryEdges >>> - ROMondrianExample new labeledRectangle >>> >>> They use AthensCanvas to render. >>> >>> Since the beginning of February, we experiment very strange problems >>> with font displaying. See by yourself : >>> >>> What we expect : >>> >>> What we have : >>> >>> You can see that the letters in each word are not of the same size. >>> (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh >>> Moose image : >>> https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… >>> ) >>> >>> We thought it was a font problem. So we updated the fonts to use this >>> one : >>> LogicalFont familyName: StandardFonts defaultFont familyName pointSize: >>> aSize >>> which is the default system font. (The fonts are located in >>> ROFontOrganizerAthens). >>> >>> But the problem was not solved. >>> >>> After some searches, we saw that Roassal (via the ROAthensCanvas) uses >>> AthensCairoCanvas and this class has been changed begin February to use >>> native boost. >>> The closed issue related is : >>> >>> 12765 Athens font rendering missing letters and missizing others >>> https://pharo.fogbugz.com/f/cases/12765 >>> >>> That should resolve the problem instead of created one ;) >>> >>> >>> So if we load the older packages of Athens-Core and Athens-Cairo (before >>> the issue resolution): >>> >>> Name: Athens-Core-MarcusDenker.34 >>> Author: MarcusDenker >>> Time: 5 July 2013, 10:59:47.206954 am >>> UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 >>> Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 >>> >>> Name: Athens-Cairo-MarcusDenker.51 >>> Author: MarcusDenker >>> Time: 26 August 2013, 4:03:06.190096 pm >>> UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 >>> Ancestors: Athens-Cairo-SebastianTleye.50 >>> >>> we have no problem of font displaying ! >>> >>> The question is : >>> What we should adapt in Roassal to support this new implementation of >>> Athens ? Or is Athens (by the native boost primitives) broken ? >>> >>> Thanks in advance ! >>> >>> >>> Vincent BLONDEAU >>> >>> >>> >>> >> >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Feb. 25, 2014

Re: [Pharo-dev] Fwd: [Moose-dev] Text Displaying issue with Roassal

by Tudor Girba

This is a beautiful looking keyboard :) Doru On Tue, Feb 25, 2014 at 2:45 PM, J.F. Rick <self(a)je77.com> wrote: > Here's an updated bug for this: > https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug > > Cheers, > > Jeff > > > On Tue, Feb 25, 2014 at 2:33 PM, Vincent Blondeau < > vincent.blondeau(a)polytech-lille.net> wrote: > >> Hi Pharoers, >> >> We are encounter a problem with text displaying under Roassal. >> Roassal is a Moose tool to make some graphics visualisations, principally >> graphs. >> Some visualisations are displaying some text, like : >> >> - ROMondrianExample new centeredText >> - ROMondrianExample new temporaryEdges >> - ROMondrianExample new labeledRectangle >> >> They use AthensCanvas to render. >> >> Since the beginning of February, we experiment very strange problems with >> font displaying. See by yourself : >> >> What we expect : >> >> What we have : >> >> You can see that the letters in each word are not of the same size. >> (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh >> Moose image : >> https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… >> ) >> >> We thought it was a font problem. So we updated the fonts to use this >> one : >> LogicalFont familyName: StandardFonts defaultFont familyName pointSize: >> aSize >> which is the default system font. (The fonts are located in >> ROFontOrganizerAthens). >> >> But the problem was not solved. >> >> After some searches, we saw that Roassal (via the ROAthensCanvas) uses >> AthensCairoCanvas and this class has been changed begin February to use >> native boost. >> The closed issue related is : >> >> 12765 Athens font rendering missing letters and missizing others >> https://pharo.fogbugz.com/f/cases/12765 >> >> That should resolve the problem instead of created one ;) >> >> >> So if we load the older packages of Athens-Core and Athens-Cairo (before >> the issue resolution): >> >> Name: Athens-Core-MarcusDenker.34 >> Author: MarcusDenker >> Time: 5 July 2013, 10:59:47.206954 am >> UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 >> Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 >> >> Name: Athens-Cairo-MarcusDenker.51 >> Author: MarcusDenker >> Time: 26 August 2013, 4:03:06.190096 pm >> UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 >> Ancestors: Athens-Cairo-SebastianTleye.50 >> >> we have no problem of font displaying ! >> >> The question is : >> What we should adapt in Roassal to support this new implementation of >> Athens ? Or is Athens (by the native boost primitives) broken ? >> >> Thanks in advance ! >> >> >> Vincent BLONDEAU >> >> >> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 25, 2014

Re: [Pharo-dev] Path>>parentUpTo: aParentDirName

by Sebastian Sastre

thanks for explaining Sven, donât be sorry for me, be sorry for the less abundant contributions the community main artifact gets. I get what you mean Iâm all for automation My point is that we deserve (and should aim?) to get the best of both worlds: 1. easy to provide (read: low friction) bug reports / contributions 2. easy to digest (even automated) bug reports / contributions While I understand that we are in a trade off now, I continue with the impression of unnecessary friction and a bit worried about the less chances of getting more valuable contributions How to make things easy for those both publics is the âsomething to think aboutâ Iâm mentioning It would be interesting to hear what ideas come from that because lowering that friction has chances to be a breakthrough On Feb 25, 2014, at 11:12 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 25 Feb 2014, at 15:01, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Okay, Iâll take a look later (donât know when) >> >> and >> >> I keep the impression of unnecessary friction to receive contributions >> >> Something to think about > > I am sorry it feels that way, but it is not. > > It is the difference between sending an actual git pull request on the source code and an email with some partial, copied code. The first is more work for you, but can be used in automated systems like our CI, can be merged with one operation and will serve as a historic record. The latter pushes all the work to the integrators, who are already overloaded. > > Making a slice is not more work that using Monticello, which you are probably doing every day. > >> On Feb 25, 2014, at 10:40 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 25 Feb 2014, at 14:36, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >>> >>>> Would this be okay? >>>> >>>> https://pharo.fogbugz.com/f/cases/12991/navigation-enhancement-Path-parentU… >>> >>> Well, not yet, you should learn how to make a actual slice... >>> >>> http://www.pharo-project.org/community/issue-tracking >>> >>> there are 2 movies and there is an explanation. >>> >>> Sven >>> >>> >>> >> > >

Feb. 25, 2014

Q: Restart the image

by Torsten Bergmann

Out of curiosity: Is it possible to restart the image from within the image itself - that means end the ST session and start the VM with the same image again? Thx T.

Feb. 25, 2014