- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Capturing stdout

by Max Leske

start pharo from the console? On 28.03.2014, at 12:57, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I want to write a test for an NB Mac system call example (Issue 13147). I can > check the exit code easily, the output goes to stdout of the image. Can I > capture it somehow? thx :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Capturing-stdout-tp4751320.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Tudor Girba

And a last one :). You can find the actual code here: GTImageSetupCommandLineHandler>>installFonts Cheers, Doru On Fri, Mar 28, 2014 at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > And the installation of the font happens like this: > > install > FreeTypeFontProvider current > addFromFileContents: self fontContents > baseName: self originalFileName > > Cheers, > Doru > > > > > On Fri, Mar 28, 2014 at 1:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I am not quite sure this is where the problem comes from given that we >> see half of the letters being well drawn and half not well. >> >> Here is how the font is loaded: >> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' >> 'SourceSansProBold') do: [ :each | >> each asSymbol asClassIfAbsent: [ >> Gofer new >> smalltalkhubUser: 'girba' project: 'FreeFonts'; >> package: each; >> load ]. >> (Smalltalk at: each asSymbol) new install ]. >> FreeTypeSystemSettings loadFt2Library: true. >> FreeTypeFontProvider current updateFromSystem. >> >> StandardFonts >> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' >> pointSize: 10); >> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); >> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: >> 14); >> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); >> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) >> >> Did I miss something? >> >> Cheers, >> Doru >> >> >> >> On Fri, Mar 28, 2014 at 12:44 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> >>> >>> On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> wrote: >>> >>> Hi >>> >>> We found with igor the problems that produced red cross in Moose. >>> The problem is that the system is looking Source Sans Pro and does not >>> find it. >>> >>> The logic in findBestFont: does not find it because there is no such >>> font registered in font manager >>> and the default logic is to return TextStyle defaultFont which is a >>> bitmpa one. >>> >>> So question: >>> - may be we should have a FT font default loaded in the system? >>> >>> - Doru we remember that you loaded font in the system? May be >>> you do not register well the fonts. >>> Could you let us know what you did? >>> >>> >>> can you execute the following >>> -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >>> realFont >>> you should get a freetype font >>> >>> - 1 Disable the freetrype in the setting >>> - 2 Enable again freetype in the setting >>> - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >>> realFont >>> >>> because you should get a strikeFont and this is the bug >>> So it looks like the image level fonts are lost. >>> >>> Stef and Igor. >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Tudor Girba

And the installation of the font happens like this: install FreeTypeFontProvider current addFromFileContents: self fontContents baseName: self originalFileName Cheers, Doru On Fri, Mar 28, 2014 at 1:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I am not quite sure this is where the problem comes from given that we see > half of the letters being well drawn and half not well. > > Here is how the font is loaded: > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBold') do: [ :each | > each asSymbol asClassIfAbsent: [ > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load ]. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > FreeTypeFontProvider current updateFromSystem. > > StandardFonts > setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 10); > haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); > balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) > > Did I miss something? > > Cheers, > Doru > > > > On Fri, Mar 28, 2014 at 12:44 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> >> On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >> Hi >> >> We found with igor the problems that produced red cross in Moose. >> The problem is that the system is looking Source Sans Pro and does not >> find it. >> >> The logic in findBestFont: does not find it because there is no such font >> registered in font manager >> and the default logic is to return TextStyle defaultFont which is a >> bitmpa one. >> >> So question: >> - may be we should have a FT font default loaded in the system? >> >> - Doru we remember that you loaded font in the system? May be you >> do not register well the fonts. >> Could you let us know what you did? >> >> >> can you execute the following >> -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >> realFont >> you should get a freetype font >> >> - 1 Disable the freetrype in the setting >> - 2 Enable again freetype in the setting >> - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >> realFont >> >> because you should get a strikeFont and this is the bug >> So it looks like the image level fonts are lost. >> >> Stef and Igor. >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Tudor Girba

I am not quite sure this is where the problem comes from given that we see half of the letters being well drawn and half not well. Here is how the font is loaded: #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | each asSymbol asClassIfAbsent: [ Gofer new smalltalkhubUser: 'girba' project: 'FreeFonts'; package: each; load ]. (Smalltalk at: each asSymbol) new install ]. FreeTypeSystemSettings loadFt2Library: true. FreeTypeFontProvider current updateFromSystem. StandardFonts setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) Did I miss something? Cheers, Doru On Fri, Mar 28, 2014 at 12:44 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > Hi > > We found with igor the problems that produced red cross in Moose. > The problem is that the system is looking Source Sans Pro and does not > find it. > > The logic in findBestFont: does not find it because there is no such font > registered in font manager > and the default logic is to return TextStyle defaultFont which is a bitmpa > one. > > So question: > - may be we should have a FT font default loaded in the system? > > - Doru we remember that you loaded font in the system? May be you > do not register well the fonts. > Could you let us know what you did? > > > can you execute the following > -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) > realFont > you should get a freetype font > > - 1 Disable the freetrype in the setting > - 2 Enable again freetype in the setting > - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) > realFont > > because you should get a strikeFont and this is the bug > So it looks like the image level fonts are lost. > > Stef and Igor. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] DateAndTime>>#= slow?

by Pharo4Stef

Hi johan Please let us know because I would be in favor of integrating such speed up if your system fully work. stef On 28 Mar 2014, at 09:17, Johan Brichau <johan(a)inceptive.be> wrote: > > On 28 Mar 2014, at 06:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Bugs are errors that prevents the system to run. > > <nagging> > Some performance problems make the system impossible to work with > </nagging> > > Anyway, going to check in Sven's changes today. > > cheers > Johan >

March 28, 2014

Capturing stdout

by Sean P. DeNigris

I want to write a test for an NB Mac system call example (Issue 13147). I can check the exit code easily, the output goes to stdout of the image. Can I capture it somehow? thx :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Capturing-stdout-tp4751320.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Pharo4Stef

On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: Hi We found with igor the problems that produced red cross in Moose. The problem is that the system is looking Source Sans Pro and does not find it. The logic in findBestFont: does not find it because there is no such font registered in font manager and the default logic is to return TextStyle defaultFont which is a bitmpa one. So question: - may be we should have a FT font default loaded in the system? - Doru we remember that you loaded font in the system? May be you do not register well the fonts. Could you let us know what you did? can you execute the following -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) realFont you should get a freetype font - 1 Disable the freetrype in the setting - 2 Enable again freetype in the setting - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) realFont because you should get a strikeFont and this is the bug So it looks like the image level fonts are lost. Stef and Igor. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Esteban Lorenzano

Hi, well.. source sans pro should be loaded (along with source code pro), but: 1) I loaded the wrong font. 2) for some reason, the build fails to use it by default (you need to update âuse freetypeâ in settings, then re-choose). I did not spend too much time on trying to fix that bug (others were more urgent), but for those who want to spend a bit on it (cough, cough, Doru, cough, cough), half of the work is already done :) Esteban On 28 Mar 2014, at 08:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > We found with igor the problems that produced red cross in Moose. > The problem is that the system is looking Source Sans Pro and does not find it. > > The logic in findBestFont: does not find it because there is no such font registered in font manager > and the default logic is to return TextStyle defaultFont which is a bitmpa one. > > So question: > - may be we should have a FT font default loaded in the system? > > - Doru we remember that you loaded font in the system? May be you do not register well the fonts. > Could you let us know what you did? > > Stef and Igor. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

March 28, 2014

Re: [Pharo-dev] Smalltalkhub & API

by phil＠highoctane.be

I just wanted to have my projects repos added to my preferences file. Without an API, it requires scraping the UI and writing code. So, yes, an API would be nice (or some helper to help with the repos registration for a given user/team in Monticello). But the REST thing is good enough at this point. With some NeoJSON, it can be quickly accessed. Phil On Fri, Mar 28, 2014 at 11:00 AM, Nicolas Petton <petton.nicolas(a)gmail.com>wrote: > > Would it be useful if SmalltalkHub provided an API (I mean, something > documented)? > > Nico > > > phil(a)highoctane.be writes: > > > Ah, nice! > > > > Thx > > > > > > > > On Fri, Mar 28, 2014 at 10:44 AM, Nicolas Petton > > <petton.nicolas(a)gmail.com>wrote: > > > >> Hi! > >> > >> You can do: > >> > >> GET http://smalltalkhub.com/hub/projects/{user,team} > >> > >> Cheers, > >> Nico > >> > >> phil(a)highoctane.be writes: > >> > >> > Is there a way to ask for a set of project names under a given > Team/User? > >> > > >> > I don't like maintaining lists like this one: > >> > > >> > #( > >> > 'BitmapCharacterSet' > >> > 'CollectionArithmetic' > >> > 'Coral' > >> > 'EventRecorder' > >> > 'FFICompatibility' > >> > 'FileSystemLegacy' > >> > 'Flotr' > >> > 'Gettext' > >> > 'ImageWorker' > >> > 'JSON' > >> > 'LDAP' > >> > 'LEDMorph' > >> > 'MorphExamplesAndDemos' > >> > 'NBOpenGL' > >> > 'OPAX' > >> > 'OrderPreservingDictionary' > >> > 'Pastell' > >> > 'Phexample' > >> > 'PlotMorph' > >> > 'PostgresV2' > >> > 'Postmark' > >> > 'ProfStef' > >> > 'RFB' > >> > 'ROE' > >> > 'SCouchDBViewServer' > >> > 'SMark' > >> > 'Smacc' > >> > 'Sound' > >> > 'Soup' > >> > 'Spotlight2' > >> > 'Tanker' > >> > 'XMLParser' > >> > 'XMLSupport' > >> > 'XMLWriter' > >> > 'XPath' > >> > 'readline') do: [ :projectName | > >> > MCRepositoryGroup default addRepository: ( > >> > MCSmalltalkhubRepository > >> > owner: 'PharoExtras' > >> > project: projectName) > >> > ]. > >> > > >> > > >> > Phil > >> > >> > >> -- > >> Nicolas Petton > >> http://nicolas-petton.fr > >> > >> > > > -- > Nicolas Petton > http://nicolas-petton.fr > >

March 28, 2014

Re: [Pharo-dev] Smalltalkhub & API

by Nicolas Petton

Would it be useful if SmalltalkHub provided an API (I mean, something documented)? Nico phil(a)highoctane.be writes: > Ah, nice! > > Thx > > > > On Fri, Mar 28, 2014 at 10:44 AM, Nicolas Petton > <petton.nicolas(a)gmail.com>wrote: > >> Hi! >> >> You can do: >> >> GET http://smalltalkhub.com/hub/projects/{user,team} >> >> Cheers, >> Nico >> >> phil(a)highoctane.be writes: >> >> > Is there a way to ask for a set of project names under a given Team/User? >> > >> > I don't like maintaining lists like this one: >> > >> > #( >> > 'BitmapCharacterSet' >> > 'CollectionArithmetic' >> > 'Coral' >> > 'EventRecorder' >> > 'FFICompatibility' >> > 'FileSystemLegacy' >> > 'Flotr' >> > 'Gettext' >> > 'ImageWorker' >> > 'JSON' >> > 'LDAP' >> > 'LEDMorph' >> > 'MorphExamplesAndDemos' >> > 'NBOpenGL' >> > 'OPAX' >> > 'OrderPreservingDictionary' >> > 'Pastell' >> > 'Phexample' >> > 'PlotMorph' >> > 'PostgresV2' >> > 'Postmark' >> > 'ProfStef' >> > 'RFB' >> > 'ROE' >> > 'SCouchDBViewServer' >> > 'SMark' >> > 'Smacc' >> > 'Sound' >> > 'Soup' >> > 'Spotlight2' >> > 'Tanker' >> > 'XMLParser' >> > 'XMLSupport' >> > 'XMLWriter' >> > 'XPath' >> > 'readline') do: [ :projectName | >> > MCRepositoryGroup default addRepository: ( >> > MCSmalltalkhubRepository >> > owner: 'PharoExtras' >> > project: projectName) >> > ]. >> > >> > >> > Phil >> >> >> -- >> Nicolas Petton >> http://nicolas-petton.fr >> >> -- Nicolas Petton http://nicolas-petton.fr

March 28, 2014