- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New website about Spec - http://spec.st

by Sven Van Caekenberghe

Super nice, very professional, congratulations to everybody who working on this! On 28 Mar 2014, at 14:18, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Hi guys :) > > I am glad to announce (even if Philippe already let the cat out :P) a website dedicated to Spec: http://spec.st. > You can find a quick introduction, documentation (mainly what is now in the Pharo For The Enterprise book), and > a news feed where I will explain the API changes, the news widgets introduce etc. > > The website contents can be found here (https://github.com/spec-framework/website) so if you want to contribute > you are welcome :) > > Ben > > PS: I would like to thank Johan Fabry who helped me a lot writing the documentation, > Sean P. DeNigris who fixed my english a couple of times and Nicolas Petton who > helped me on the website look and feel

March 28, 2014

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

by Johan Brichau

Hi all, With Sven's fixes loaded, our model unit tests are all running fine. The benchmarks indicate the same speed as in 1.4. This is really great! I'm still running the entire suite of tests but that will take a while to complete. But essential datetime bugs should have been spotted already. Great work Sven! I think it's worth integrating. If not, we will definitely work with this patched version. Johan On 28 Mar 2014, at 13:36, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > 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

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Igor Stasenko

Ookkayy.. so, current status: - finally we got an agreement that big red square because of font loading issues and font rendering artifacts is two separate issues. Thanks! - i am not going to address font-loading issue here and now.. (because we spent time on it earlier today with Stef already and you should have the report on it in separate mail). - we seem to be agreed that it is best to use same (up-to-date version) of software when reporting issues to work on them. Thanks again. :) - while on linux and mac things seem to be working fine, i can confirm that there is rendering artifacts (same as reported by Vincent) on Windows. so i going to explore what causing this problem.. -- Best regards, Igor Stasenko.

March 28, 2014

Re: [Pharo-dev] Capturing stdout

by Max Leske

On 28.03.2014, at 15:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Max Leske wrote >> Forget what I saidâ¦ Just ramblingâ¦ > > Ha ha, I was doing the confused-puppy-head-tilt (see > http://da0cb6511396a92928c7-488d28a6573db6ac4a247063b638fcb9.r77.cf2.rackcd…) :p > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Capturing-stdout-tp4751320p4751409.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 28, 2014

Re: [Pharo-dev] Release Mode

by Marcus Denker

On 28 Mar 2014, at 15:52, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > While I was on holiday, it seems my dear friends have gone feature crazy... > almost as bad as me in the run up to the 2.0 release, ha ha. > > As cool as they are, are: > - changing the look of Nautilus buttons > - evaluate arbitrary expressions in Spotlight > - etc, etc > showstopping bugs?! > > This beta time is reserved specifically for finding the bugs that may > inevitably be introduced with these enhancements. We really may be creating > a mess, as end users find them in our "stable" release instead. > Yes, it was wrongâ¦ maybe we should revert. Marcus

March 28, 2014

Re: [Pharo-dev] Capturing stdout

by Sean P. DeNigris

Max Leske wrote > Forget what I saidâ¦ Just ramblingâ¦ Ha ha, I was doing the confused-puppy-head-tilt (see http://da0cb6511396a92928c7-488d28a6573db6ac4a247063b638fcb9.r77.cf2.rackcd…) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Capturing-stdout-tp4751320p4751409.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Release Mode

by Sean P. DeNigris

While I was on holiday, it seems my dear friends have gone feature crazy... almost as bad as me in the run up to the 2.0 release, ha ha. As cool as they are, are: - changing the look of Nautilus buttons - evaluate arbitrary expressions in Spotlight - etc, etc showstopping bugs?! This beta time is reserved specifically for finding the bugs that may inevitably be introduced with these enhancements. We really may be creating a mess, as end users find them in our "stable" release instead. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Release-Mode-tp4751408.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] someone using Magritte-Morph?

by Sean P. DeNigris

EstebanLM wrote > should instead be... Without an image handy, your change looks like good. IIRC I did the display string stuff after I implemented the relation morphs and probably forgot to change it there. ----- Cheers, Sean -- View this message in context: http://forum.world.st/someone-using-Magritte-Morph-tp4751095p4751404.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Fwd: Font problem is still there

by Tudor Girba

Yes, I can confirm. But, this is a known issue that in practice has little impact, and it was not related to the issue of rendering in Athens. So, from my point of you, the critical issue is now solved. Thanks! :) Doru On Fri, Mar 28, 2014 at 3:33 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > yes but if you uncheck and recheck freetype > the embedded fonts are lost > -> substition > -> substitution failed. > -> get a strike font and boum. > > Can you confirm? > > On 28 Mar 2014, at 15:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Excellent. > > I confirm the same result in the latest Moose image (which no longer loads > anything related to Athens). > > It works out of the box without any resetting of the fonts (by using the > already installed Source Sans Pro. > > Cheers, > Doru > > > <a WorldMorph(511705088) [wo.png> > > > On Fri, Mar 28, 2014 at 3:15 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> >> On 28 March 2014 15:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> I added the code in the mail precisely to leave out any ambiguities :). >>> >>> The first part of the snippet (as also listed by Vincent) loads the very >>> latest development version of Athens configuration. So, yes, I think I >>> loaded the latest code. >>> >>> Doru >>> >> >> and that code snippet works only if you have FreeSans font in your >> system.. which not exists on Mac OS (at least in my installation).. >> >> i took the latest pharo 3.0 image: >> >> curl get.pharo.org/30 | bash >> % Total % Received % Xferd Average Speed Time Time Time >> Current >> Dload Upload Total Spent Left >> Speed >> 100 2587 100 2587 0 0 70999 0 --:--:-- --:--:-- --:--:-- >> 421k >> Downloading the latest 30 Image: >> http://files.pharo.org/image/30/latest.zip >> Pharo.image >> 193-51-236-207:pharo sig$ ./pharo-ui Pharo.image >> >> - went to font settings and updated the font list from system. >> >> >> And then evaluated: >> >> AthensSceneView new scene: [ :canvas | |s| >> canvas setFont: (LogicalFont familyName: 'Arial' >> pointSize: 20). >> s:= String newFrom: ($A to: $Z),($a to: $z), ($0 to: $9). >> >> canvas pathTransform restoreAfter: [ >> canvas pathTransform translateX: 0 Y: 50. >> canvas setPaint: Color black. >> canvas drawString:s ] >> >> ];openInWindow >> >> And here's what i got: >> <Screen Shot 2014-03-28 at 3.11.25 PM.png> >> >> And the screenshot you given cannot be true, because 20 points font size >> should be much larger than 10 point (the font used for label above with >> zoom/pan metrics). >> >> Note, i did not loaded anything into pharo image.. just evaluated the >> above snippet.. >> on my machine, which is: 10.8.3 mac os >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > 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] [Moose-dev] Re: Re: Fwd: Font problem is still there

by Blondeau Vincent

De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de StÃ©phane Ducasse EnvoyÃ© : vendredi 28 mars 2014 15:39 Ã : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there In Pharo 3.0 this is is normal because FreeSans does not exist. I think that we should embed a default FT font and use is as default. Isn't the StandardFonts defaultFont ? Vincent Now since embedded fonts are lost when reloading Freetrype fonts. The reloading of FreeType should be fixed. Stef And : AthensSceneView new scene: [ :canvas | |s| canvas setFont: (LogicalFont familyName: 'FreeSans' pointSize: 20). s:= String newFrom: ($A to: $Z),($a to: $z), ($0 to: $9). canvas pathTransform restoreAfter: [ canvas pathTransform translateX: 0 Y: 50. canvas setPaint: Color black. canvas drawString:s ] ];openInWindow And I got : <image001.png> <image002.png> And under a fresh Pharo 3.0 : <image003.png> Vincent De : moose-dev-bounces(a)iam.unibe.ch<mailto:moose-dev-bounces@iam.unibe.ch> [mailto:moose-dev-bounces@iam.unibe.ch] De la part de Tudor Girba EnvoyÃ© : vendredi 28 mars 2014 14:28 Ã : Moose-related development Objet : [Moose-dev] Re: Fwd: [Pharo-dev] Font problem is still there Hi, This was discussed before both on the Moose and on the Pharo mailing list. We are loading explicitly an older version of Athens because we could not work at all with the one that came from Pharo, and nobody reacted at the time to the font issue: GTImageSetupCommandLineHandler>>loadOlderAthensPackagesToCorrectTheFontCachingProblem " This is a workaround fir the bug described here: https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug " Gofer new smalltalkhubUser: 'Pharo' project: 'Pharo30'; package: 'Athens-Cairo' constraint: [ :version | version author = 'MarcusDenker' and: [ version versionNumber = 51 ] ]; package: 'Athens-Core' constraint: [ :version | version author = 'MarcusDenker' and: [ version versionNumber = 34 ] ]; load Now it's great that you are looking at it. So, I now removed it from the setup and the image is now relying on the latest Pharo 3.0. The build is running now: https://ci.inria.fr/moose/job/moose-5.0/1008/ Cheers, Doru On Fri, Mar 28, 2014 at 2:18 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: Hi guys. This is strange that moose is using a so old version of Athens. Stef Begin forwarded message: From: Igor Stasenko <siguctua(a)gmail.com<mailto:siguctua@gmail.com>> Subject: Re: [Pharo-dev] Font problem is still there Date: 28 Mar 2014 14:03:17 GMT+1 To: Pharo Development List <pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org>> Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org>> so, i checked both in 4.9 and 5.0 Moose images on linux... got weird results and sometimes crashes. in 5.0 image the version is: Athens-Cairo-MarcusDenker.51 - this one uses pretty old code, which renders text using 'toy' cairo api for text rendering. in my working image, where i work every day it is: Athens-Cairo-SvenVanCaekenberghe.64 and there's also couple important fixes since .51 as well as different font rendering code which no longer using toy api.. so, guys, if you want me to continue, please try using latest versions and report problems about it, because it makes no sense to find a fix in something which outdated and thrown away many months ago. Load the latest dev version of Athens from smalltalkhub (it is version 2.5) ConfigurationOfAthens loadDevelopment. try it out. Here's what i got on latest fresh vanilla out of the box Pharo 3.0 image on linux system: <image004.jpg> P.S. i am not saying that it is *impossible* that there is problems in new version, just asking you to report problems with that version, not one which year(s) old. -- Best regards, Igor Stasenko. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch<mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com<http://www.tudorgirba.com/> "Every thing has its own flow" ________________________________ 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. ________________________________ 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.

March 28, 2014