- Pharo-dev - lists.pharo.org

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 17, 2013

Oct. 17, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… 1 regressions found. KernelTests.Classes.BehaviorTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 17, 2013

Oct. 17, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… 1 regressions found. KernelTests.Classes.BehaviorTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 17, 2013

Oct. 17, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 2 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits Zinc.Tests.ZnServerTests.testEntityTooLarge

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 17, 2013

Oct. 17, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

1 0

Fogbugz workflow
by Ben Coman Oct. 17, 2013

Oct. 17, 2013

A further query on workflow with FogBugz. It seems the Galactic Monkey From Outer Space picks up Cases with status 'Resolved (Fix Review Needed)'. When that is succcessful, what is the next step? Should I being changing the status to 'Resolved (Fix To Include)' myself or is further human review required? Referring to https://pharo.fogbugz.com/default.asp?11835 this Case now doesn't appear in any of the Work Needed, Integration nor Review filters. Hence my query about the next step. cheers -ben

3 4

Spec error
by Sean P. DeNigris Oct. 17, 2013

Oct. 17, 2013

When I tried to open my Spec UI (previously working in latest 2.0) in 3.0, I got ByteSymbol DNU specWidget:. What changed and how do I port? And if it's an intended change, we should have at least documentation for non-backward-compatible kernel changes... Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-error-tp4714069.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 7

[ann] system attraction view
by Tudor Girba Oct. 17, 2013

Oct. 17, 2013

Hi, I built a new visualization that has two goals: 1. show how the architecture of a system is fluid rather than rigid. 2. look good and serve as advertisement device for Moose, Roassal and Pharo. A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/ I already used it as a splash screen for a couple of presentations, and it catches the eye. The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups). Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

6 15

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: default monospaced code font
by Goubier Thierry Oct. 17, 2013

Oct. 17, 2013

Once the correct fonts are installed, the pdf looks very different :) Revised judgement: Source code pro is not bad for a monospaced font. Source sans pro is impressive of density (9), and has this additional readability on DejaVu sans for the $l. I'll take Source Sans Pro, then. But Pharo is not seeing it in the dialog. Is that because I did a user specific install of the fonts (and not system wide) and Pharo is not checking the user-specific fonts? Thierry Le 17/10/2013 11:11, Goubier Thierry a Ã©crit : > I'll do like you because... > > I only managed to install the source code pro font so far (no default > install in ubuntu) and Pharo doesn't see it (LibreOffice does). I'll > look for the source sans pro download as well. > > (May explain the pdf issues if the fonts are not embedded in the pdf > document). > > Thierry > > Le 17/10/2013 10:57, Igor Stasenko a Ã©crit : >> ok i looked at .xlxslsx file >> at least, in google preview it looks more or less close to the truth :) >> >> and i can say that Source Sans Pro is a winner ( to my taste ). >> I like that for 'i' in it don't closes together as in 'it', comparing to >> dejavu , where it does. >> It reads very clear yet compact. >> >> On 17 October 2013 10:43, Igor Stasenko <siguctua(a)gmail.com >> <mailto:siguctua@gmail.com>> wrote: >> >> >> >> >> On 17 October 2013 10:47, Goubier Thierry <thierry.goubier(a)cea.fr >> <mailto:thierry.goubier@cea.fr>> wrote: >> >> >> >> Le 17/10/2013 10:29, Igor Stasenko a Ã©crit : >> >> hmm.. i have suspicion that it is actually adobe who can't >> handle the >> font properly.. >> because in some examples for source code pro font, the >> adjacent letters >> jump onto each other. >> i don't believe it is that bad (see attached)Inline images 1 >> >> >> Adobe or the viewer? I used evince to view it, not acrobat >> reader. It may point to incorrect spacing information in Source >> Sans Pro (I have not the errors you see in Source Code Pro). >> >> Who is in charge of the Source Pro font? Which typographer? Oh, >> Adobe apparently. If they can't handle it properly... >> >> i am far from blaming adobe, just wanted to say that in my viewer it >> does not shows things >> properly, because when rendered in pharo it don't have such problems. >> >> so i cannot have decent comparison.. >> >> Thierry >> >> >> >> On 17 October 2013 09:28, Goubier Thierry >> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr> >> <mailto:thierry.goubier@cea.fr >> <mailto:thierry.goubier@cea.fr>__>> wrote: >> >> Excellent, I like the comparison a lot! Thanks! >> >> My take is: >> - Unable to like Source Code Pro 9 (and it's so wide); >> - Source Sans Pro 9 has spacing issues (16r, the r is >> too close) and >> reading issues (it's the worse for the lL|i characters) >> - Source sans Pro 10 is better than 9 (but what with >> the 2x space?) >> >> Overall, I'd stay with DejaVu Sans 9 based on this >> sample. In my >> opinion, the best compromise density / readability. >> >> Thierry >> >> Le 16/10/2013 19:56, btc(a)openinworld.com >> <mailto:btc@openinworld.com> >> <mailto:btc@openinworld.com >> <mailto:btc@openinworld.com>> a Ã©crit : >> >> >> Goubier Thierry wrote: >> >> I'd be more impressed if the argument was >> helping me distinguish >> between | and l. >> >> >> Yes. It is designed to do that. Some common >> failings of >> monospaced fonts >> are noted [1] and dealt with. There comment section >> is also >> interesting. >> >> The attached PDFs are the result of getting the >> urge to compare >> a broad >> coverage of code examples (taken from "Terse Guide >> to Squeak") >> against >> three fonts: >> * DejaVu Sans 9 point >> * Source Code Pro [1] [2] 9 point >> * Source Sans Pro [3] [4] 9 point & 10 point, since >> the width of >> 10 was >> the same as the others at 9. >> Also attached is the source excel file. >> >> cheers -ben >> >> [1] >> >> http://blogs.adobe.com/____typblography/2012/09/source-____code-pro.html >> >> <http://blogs.adobe.com/__typblography/2012/09/source-__code-pro.html> >> >> >> <http://blogs.adobe.com/__typblography/2012/09/source-__code-pro.html >> >> <http://blogs.adobe.com/typblography/2012/09/source-code-pro.html>> >> [2] >> >> http://sourceforge.net/____projects/sourcecodepro.adobe/____files/ >> >> <http://sourceforge.net/__projects/sourcecodepro.adobe/__files/> >> >> >> <http://sourceforge.net/__projects/sourcecodepro.adobe/__files/ >> <http://sourceforge.net/projects/sourcecodepro.adobe/files/>> >> [3] >> >> http://blogs.adobe.com/____typblography/2012/08/source-____sans-pro.html >> >> <http://blogs.adobe.com/__typblography/2012/08/source-__sans-pro.html> >> >> >> <http://blogs.adobe.com/__typblography/2012/08/source-__sans-pro.html >> >> <http://blogs.adobe.com/typblography/2012/08/source-sans-pro.html>> >> [4] >> >> http://sourceforge.net/____projects/sourcesans.adobe/____postdownload?sourc… >> >> >> <http://sourceforge.net/__projects/sourcesans.adobe/__postdownload?source=dlp> >> >> >> >> >> <http://sourceforge.net/__projects/sourcesans.adobe/__postdownload?source=dlp >> >> >> <http://sourceforge.net/projects/sourcesans.adobe/postdownload?source=dlp>> >> >> >> >> I'l let you try, then :) >> >> Thierry >> >> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el >> EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

4 4

[pharo-project/pharo-core]
by GitHub Oct. 17, 2013

Oct. 17, 2013

Branch: refs/tags/30495 Home: https://github.com/pharo-project/pharo-core

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 17, 2013

Oct. 17, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 3 regressions found. RPackage.Tests.RPackageReadOnlyCompleteSetupTest.testAddTag RPackage.Tests.RPackageReadOnlyCompleteSetupTest.testAddTagNames RPackage.Tests.RPackageSetTest.testPolymorphicWithPackageInfo

1 0