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

Re: [Pharo-dev] problems with the default font

by Esteban Lorenzano

no, I do not confirm (that the defaults are DejaVu): it is a bug. what actually happens is an effect of the infamous âfont bugâ that is around. in fact, if you have that effect with a latest image you should not need to reload fonts, just saving image will fix it. > On 12 Mar 2016, at 14:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > It looks to me as if in the latest Pharo, the default font is rendered with the DejaVu bitmap font instead of Source Sans Pro. > > Here is how the font looks like in Nautilus (look at the fonts in the top part): > <Screen Shot 2016-03-12 at 1.58.46 PM.png> > When I look in Settings, it says that it uses Source Sans Pro. > > However, if I reload the fonts and set it again to Source Sans Pro, I get this picture with the correct rendering (look at the category name âannouncing"): > > <Screen Shot 2016-03-12 at 2.18.09 PM.png> > > Interestingly, the code font looks the same in both situations. Can you confirm this effect? > > Cheers, > Doru > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > www.feenk.com > > "From an abstract enough point of view, any two things are similar." > > > >

March 12, 2016

problems with the default font

by Tudor Girba

Hi, It looks to me as if in the latest Pharo, the default font is rendered with the DejaVu bitmap font instead of Source Sans Pro. Here is how the font looks like in Nautilus (look at the fonts in the top part): When I look in Settings, it says that it uses Source Sans Pro. However, if I reload the fonts and set it again to Source Sans Pro, I get this picture with the correct rendering (look at the category name âannouncing"): Interestingly, the code font looks the same in both situations. Can you confirm this effect? Cheers, Doru -- www.tudorgirba.com www.feenk.com "From an abstract enough point of view, any two things are similar."

March 12, 2016

Fwd: Really usability fix for Versionner

by stepharo

-------- Message transfÃ©rÃ© -------- Sujet : Really usability fix for Versionner Date : Sat, 12 Mar 2016 13:25:43 +0100 De : stepharo <stepharo(a)free.fr> Pour : Pharo Development List <pharo-dev(a)lists.pharo.org> Hi I checked with christophe and it is IMPOSSIBLE to use Versionner for managing projects like SciSmalltalk. First I cannot even reach the ok or cancel button (check the png - this is not fun) Second and more important, Metacello gives warning on projects I do not have any control. So based on the feedback of Christophe I introduced a setting to disable/enable the check. https://pharo.fogbugz.com/f/cases/17806/Make-Metacello-rules-optional-in-Ve… It is important to have it in Pharo 50 else we will not be able to use Versionner or we will have load this fix each time we want to manage large project and I'm fed to spend my life updating configuration of more than 30 packages by hand. Versionner is cool but without this fix the system kills my productivity. I do not have much time to improve Sci and I would like to prefer to use it on real issues and not just spending time updating stupidly numbers. Stef

March 12, 2016

Re: [Pharo-dev] Status of pharo Android and Pharo ios ?

by stepharo

Le 12/3/16 09:44, jannik laval a Ã©crit : > Hi pharoers, > > What is the status of pharo for android and pharo for iOS ? For android not much changes. I was pushing but nothing came out. I'm sorry. Stef > > Thank you for the answer > > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me > d'Information > IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re > laboratoire DISP > http://www.jannik-laval.eu > http://www.phratch.com > http://www.approchealpes.info

March 12, 2016

Status of pharo Android and Pharo ios ?

by jannik laval

Hi pharoers, What is the status of pharo for android and pharo for iOS ? Thank you for the answer -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re laboratoire DISP http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

March 12, 2016

Re: [Pharo-dev] Doc tutorial about uFFI

by Dimitris Chloupis

here https://github.com/SquareBracketAssociates/PharoInProgress On Sat, Mar 12, 2016 at 10:10 AM stepharo <stepharo(a)free.fr> wrote: > Hi esteban > > Where did you publish the doc/tutorial of uFFI? > > Stef > > > >

March 12, 2016

Doc tutorial about uFFI

by stepharo

Hi esteban Where did you publish the doc/tutorial of uFFI? Stef

March 12, 2016

Re: [Pharo-dev] Improving doc of XMLParser

by stepharo

Monty What would be really gorgeous is to revisite the method comments with the idea that people do not know SAX. characters: aString "This call corresponds to the Java SAX call characters(char[] ch, int start, int length)." was not really useful to me. I got no idea about it. So I started to redefine all the methods and put break put in them.... It was not really welcoming. I think that Pharo internal documentation should really improve because we cannot rely on Stack Overflow. And this means that people in that case prefer to develop in a language where they can find solutions instead of crawling. This is why the example effort should be also pushed further. Stef

March 12, 2016

Re: [Pharo-dev] Improving doc of XMLParser

by stepharo

Le 11/3/16 15:36, monty a Ã©crit : > The class comment (and other) could be better; it assumes you already know SAX-style parsing. I will improve it. > > I have been working on a tutorial that shows the usage of XMLParser and related libs (like XPath or XMLParserStAX). EXCELLENT!!!!!!!! > It is being structured like a chapter and formatted with Pillar, so it could go in one of your books (but not PBE, it's too specific for it). Superb. Yes there will be other books :) It would fit perfectly with the PullParser chapter Could you publish that in the squarebraket github repo? In PharoProgress for example Where can I read it? I'm eager to read it because I want to help this person. I produced a PullXMLParser out of Hernan blog I should add missing examples. https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/XMLP… > > Also, instead of: > >> h := MySAXHandler new >> on: FileSystem workingDirectory / 'FILMS.XML'. >> h parseDocument. > You just want: > > result := MySAXHandler parseFileNamed: 'FILMS.XML'. > > or if you want to configure it before parsing, you can use an on*: constructor + parseDocument: > > result := > (MySAXHandler onFileNamed: 'FILMS.XML') > "...configure the instance here.." > parseDocument. Yes I did it like that because I had to change the onFileNamed: because I do not know why but in the moose version I used there was a DNU related to asXMLHandleFile or something like that. > >> Sent: Friday, March 11, 2016 at 7:55 AM >> From: stepharo <stepharo(a)free.fr> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Subject: [Pharo-dev] Improving doc of XMLParser >> >> Hi monty >> >> Yesterday one student ask me to import in Moose an XML document. >> I spent more than 15 min trying.... >> >> What would have really help is the following (could you add it into the >> class comment): >> Many of the comment do not help because are scarce and not precise enough. >> >> To use a SaxHandler subclass it >> >> >> >> SAXHandler subclass: #MySAXHandler >> instanceVariableNames: '' >> classVariableNames: '' >> category: 'MyXMLImporter' >> >> and redefine the method corresponding the notification you want for example: >> >> MySAXHandler>>startElement: aQualifiedName attributes: aDictionary >> >> self halt. >> >> Then to use it simply do >> >> | h | >> h := MySAXHandler new >> on: FileSystem workingDirectory / 'FILMS.XML'. >> h parseDocument. >> ^ h >> >> Your method startElement: aQualifiedName attributes: aDictionary should >> get invoked. >> >> >> I really think that having a tutorial on XML parser ***use*** is cruelly >> needed. >> >> >> >> Stef >> >> >> >> >> >> >> >

March 12, 2016

Re: [Pharo-dev] feedback from yet another student presentation

by stepharo

Thanks for the proposition. Stef Le 11/3/16 09:22, philippe.back(a)highoctane.be a Ã©crit : > > And that woukd be a nice thing to hack on during PharoDays. > > On Mar 11, 2016 9:22 AM, "philippe.back(a)highoctane.be > <mailto:philippe.back@highoctane.be>" <philippe.back(a)gmail.com > <mailto:philippe.back@gmail.com>> wrote: > > STH can be fixed. This is more like some data problem. > > Who can look at the system to identify issues? Is this a Mongo issue? > > Phil > > On Mar 11, 2016 8:17 AM, "Serge Stinckwich" > <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> > wrote: > > On Fri, Mar 11, 2016 at 8:08 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > > > > Le 10/3/16 22:14, Alexandre Bergel a Ã©crit : > >>> > >>> - it was reallllly hard to register a project on > smalltalkhub just after > >>> we created an account. > >>> This already happened to me during the open-devs. > >>> So this is a really big show stopper for the mooc. Because > people will > >>> gave up just after the first lecture :( > >> > >> The situation will be much easier I hope once git is well > supportedâ¦ > > > > > > But will we have to answer 100 of problems during the mooc? > > And if people drop after just because they cannot save their > code as we say > > it :( > > Yes this is real annoying problem ... Maybe you can ask > Gemstone to > support the MOOC > with a dedicated ss3 instance (or use ss3). > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

March 12, 2016