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

Pharo tutorials
by Goubier Thierry April 11, 2014

April 11, 2014

Is that just me, or... The pharo tutorials are read-only in 30782, and therefore I can't open a menu and 'do it (d)' ? 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

5 4

Nicer scrollbars [was RE: Fixing inconsistent buttons look in PharoUI]
by Philippe Back April 11, 2014

April 11, 2014

And while I was at it, I made the scrollbars nicer. https://pharo.fogbugz.com/default.asp?13136 All of this made me notice that there are quite a number of little glitches all over. Especially when using larger fonts. Phil From: Philippe Back [mailto:phil@highoctane.be] Sent: mercredi 26 mars 2014 10:51 To: 'pharo-dev(a)lists.pharo.org' Subject: Fixing inconsistent buttons look in PharoUI I've made a pass at fixing the buttons look (border in some places, no border in others). Spec-generated buttons are using the ButtonModel and MorphicButtonAdapter but the defaultSpec fo the the ButtonModel is asking the borderWidth and borderColor from the model, which is all nice but should be looking like the standard PluggableButtonMorphs, which do have a border. So, aligned now. https://pharo.fogbugz.com/default.asp?13135 Slice in inbox: SLICE-Issue-13135-Inconsistent-look-of-buttons-across-tools-Border-no-border -PhilippeBack.1 Phil --- Ce courrier Ã©lectronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. http://www.avast.com

7 13

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there
by Blondeau Vincent April 4, 2014

April 4, 2014

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:30 Ã : Moose-related development Cc : Pharo Development List Objet : [Moose-dev] Re: [Pharo-dev] Re: Re: Fwd: Font problem is still there On 28 Mar 2014, at 14:55, Tudor Girba <tudor(a)tudorgirba.com<mailto:tudor@tudorgirba.com>> wrote: In the Moose image, the fonts are already set to free type fonts. yes but if you uncheck and recheck freetype the embedded fonts are lost -> substition -> substitution failed. -> get a strike font and boum. I confirm ! [cid:image001.png@01CF4A9B.F64977F0] [cid:image002.png@01CF4A9B.F64977F0] And if you can see under the A character, there is a square that should not be here... (under w7) Vincent Doru On Fri, Mar 28, 2014 at 2:50 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: No, I did not change the Free type in the pharo settings. But if I do it under Moose, I got : <image001.png> De : moose-dev-bounces(a)iam.unibe.ch<mailto:moose-dev-bounces@iam.unibe.ch> [mailto:moose-dev-bounces@iam.unibe.ch<mailto:moose-dev-bounces@iam.unibe.ch>] De la part de StÃ©phane Ducasse EnvoyÃ© : vendredi 28 mars 2014 14:44 Ã : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there vincent Did you changed the freetype settings? Setf On 28 Mar 2014, at 14:36, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: +1. So, I did on a fresh Moose 5.0 Image under W7: Gofer new smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; loadDevelopment. 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. -- www.tudorgirba.com<http://www.tudorgirba.com/> "Every thing has its own flow" _______________________________________________ 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 ________________________________ 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.

8 22

Two fixes for review
by Ben Coman April 3, 2014

April 3, 2014

1 1

<quote author="Sean P. DeNigris"> I think the tree nodes should be based on name-matching and not only per-package. For example: </quote> In 4.0, let's query the Metacello configurations to find out exactly what packages belong to which project and categorize from there, but until then, I think this is already an improvement:
by Sean DeNigris April 3, 2014

April 3, 2014

> I think the tree nodes should be based on name-matching and not only per-package I should've appended: "as a compromise for the time being"... In 4.0, imagine this killer combination: - Declare high-level logical categories a la AltBrowser (e.g. UI). This really nails the 7+/-2 sweet spot - For external projects, query the Metacello configurations to find out exactly what packages belong to which project and group accordingly; they could also declare AltBrowser categories But until then, I think this is already an improvement: The screenshot is of two overlapping Nautilus browsers. The one on the left is the current implementation. The one on the right adds top-level categories. The key thing to notice is the scroll bar: almost 10 pages to deal with currently vs. 3-4 with top level categories. Notice also that the icons make it clear what is an actual package. The other important thing to remember is that power users are most likely going to use Spotlight or the filter bar. This is really more for exploration and education. Cheers, Sean

4 5

[Spec] whenSelectedItemsChanged: on TreeModel
by Roberto Minelli April 2, 2014

April 2, 2014

Hi, I am experiencing problems with #whenSelectedItemsChanged: on a TreeModel. In particular, the block (i.e., argument of #whenSelectedItemsChanged: gets randomly executed a couple of times (3/4) the second time that the selection happens. The first time is fine. It looks like the registration of the âeventâ or âannouncementâ is done multiple times. Any hint? Cheers, R

5 4

Font problem identified
by Pharo4Stef April 2, 2014

April 2, 2014

Hi guys I found the problem now I will think about the solution. https://pharo.fogbugz.com/default.asp?13149 Stef

4 9

Strange left-over in 30804
by Goubier Thierry April 2, 2014

April 2, 2014

Hi All, has anybody noticed a strange new RPackage in 30804 named: FloatArray-dot.st ? I can't miss it with AltBrowser, and it's visible in Nautilus, but not in Browser. 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

2 3

Fwd: FogBugz (Case [Issue]13154) Pharo VM - BitBlt bug in alphaSourceBlendBits8
by Nicolai Hess April 2, 2014

April 2, 2014

Thank you Nicolas, I verified the fix, it works. I took nicolas' change and build a windows pharo vm. changing the bit depth to 8bit littleendian (-8) works now. But there are two more issues (not related to this fix). 1. Changing Display depth to 4/8/16 shows horrible rendering artifacts (those do not occur on squeak) 2. Since refactoring some parts out of DisplayScreen into MorphicUIManager you can not change the depth from -XX to XX Display newDepth:8 has no effect if current display depth is -8. (This happens on squeak too, verified in Squeak 4.4/Squeak 4.5). BTW found this change for alphaSourceBlendBits8 its way into squeaks vm? I took the lates 4.5 allinone and the bug is still there. regards Nicolai ---------- Forwarded message ---------- From: Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> Date: 2014-03-30 15:49 GMT+02:00 Subject: FogBugz (Case [Issue]13154) Pharo VM - BitBlt bug in alphaSourceBlendBits8 To: "nicolaihess(a)web.de" <nicolaihess(a)web.de> [image: avatar] *Ulysse The Galactic Monkey From Outer Space* edited *Case 13154*: BitBlt bug in alphaSourceBlendBits8 <https://pharo.fogbugz.com/default.asp?13154>: *Bug* in [image: Project:] Pharo VM: 2. External * You are subscribed to this case Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/14726//artifact/val… Errors: 1 | *Status* changed: Resolved (Monkey is checking) [image: changed to] Work Needed [image: Priority] *Priority*: 5 - Fix If Time [image: Status] *Status*: Work Needed [image: Assigned To] *Assigned to*: Nicolas Cellier [image: Milestone] *Milestone*: Pharo3.0 Go to Case <https://pharo.fogbugz.com/default.asp?13154> No longer need updates? Unsubscribe from this case.<https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&comma…> Don't want FogBugz notifications anymore? Update your preferences.<https://pharo.fogbugz.com/default.asp?pg=pgPrefs> [image: FogBugz] A FogBugz case was edited by Ulysse The Galactic Monkey >From Outer Space. Case ID: 13154 Title: BitBlt bug in alphaSourceBlendBits8 Status: Work Needed Category: Bug Project: Pharo VM Area: 2. External Priority: 5 - Fix If Time Milestone: Pharo3.0: 30/03/2014 (Today) Assigned To: Nicolas Cellier URL: https://pharo.fogbugz.com/default.asp?13154 Changes: Status changed from 'Resolved (Monkey is checking)' to 'Work Needed'. Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/14726//artifact/val… Errors: 1 | You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&comma…) from this case.

2 2

Spec and forms
by Norbert Hartl April 1, 2014

April 1, 2014

Is there anything that might help in order to create a form like UI in spec? Any descriptive way? slot based? magritte? Norbert

5 14