January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to display an image from an external PNG/JPG file in a Morph?

by StÃ©phane Ducasse

Hi dimitry Do not hesitate to ask questions, we love them because we are all learning from the. This is the trick :) Stef On Jan 10, 2011, at 11:36 AM, Dimitry Golubovsky wrote: > Hi, > > Thanks Alain, this worked for me. > > Alain Plantec wrote: > >> (ImageReadWriter formFromFileNamed: 'pharoLogo.jpg') asMorph openInWorld >> works also > > PS Before asking on the list I tried to google on the topic, nothing > relevant returned. At least now googling for "pharo display png file" > yields this mailing list thread in the first page among other not so > relevant results: someone like me will find the answer faster. > > Thanks again. > > -- > Dimitry Golubovsky > > Anywhere on the Web >

Jan. 10, 2011

Re: [Pharo-project] aligning morphs

by Gary Chambers

Indeed... trying to catch up with work at the moment after nice extended Christmas break! Aside, as for EventHandlerPlus, that should be upwardly integrated to the superclass. (since Google went for unified account it is cumbersome to switch from work to personal account!) Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, January 10, 2011 5:08 PM Subject: Re: [Pharo-project] aligning morphs Thanks gary we should really organize again a coding session at london or lille together so that we continue to clean the UI level. It was fun to pair program last time. Stef On Jan 10, 2011, at 4:50 PM, Gary Chambers wrote: > I may get time later in the week to have a go with GeneralScrollPane to > support the feature you desire... ;-) > > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Cc: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, January 10, 2011 2:23 PM > Subject: Re: [Pharo-project] aligning morphs > > > Hi Gary, > > Thanks for the reply. > > So, what would be required for scrollbars to work with spaceFill? I would > really need this feature, but I do not know how to go about it. > > Could you or anyone else provide some hints? Of course code would be even > better. But at this moment hi ts would be helpful, too :) > > Cheers, > Doru > > > > On Jan 10, 2011, at 13:04, "Gary Chambers" <gazzaguru2(a)btinternet.com> > wrote: > >> Hi Doru, >> >> #spaceFill constraints are typically only used by table layouts. >> ScrollPane is designed for fixed size contents, at present. >> Might be nice to extend it to honour any #spaceFill of its single target >> morph. >> This would simplify usage of scrollers quite a bit! >> >> Regards, Gary >> >> ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> >> To: "Pharo-project(a)lists.gforge.inria.fr Development" >> <pharo-project(a)lists.gforge.inria.fr> >> Sent: Saturday, January 08, 2011 1:22 AM >> Subject: [Pharo-project] aligning morphs >> >> >> >> Hi, >> >> I would need help with understanding the magic behind alignment in >> Morphic. >> >> Take the example from below. Could anyone help me with what I should do >> to have the morph stretch all the way horizontally? >> >> | scroll window morph | >> scroll := ScrollPane new. >> scroll >> fillStyle: (SolidFillStyle color: Color blue); >> vResizing: #spaceFill; >> hResizing: #spaceFill. >> morph := PanelMorph new. >> morph >> fillStyle: (SolidFillStyle color: Color yellow); >> changeTableLayout; >> listDirection: #topToBottom; >> vResizing: #shrinkWrap; >> hResizing: #spaceFill; >> layoutInset: 10. >> morph addMorphBack: (SimpleButtonMorph new width: 200; height: 200). >> scroll scroller addMorph: morph. >> window := SystemWindow new. >> window addMorph: scroll fullFrame: (LayoutFrame fractions: (0 @ 0 corner: >> 1 @ 1)). >> window openInWorld >> >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing should have the right to be different." >> >> >> >> >> > >

Jan. 10, 2011

Re: [Pharo-project] Issue 3525 in pharo: Compiler>>parserClass is broken and does not querying the class for providing the parser class

by Eliot Miranda

On Mon, Jan 10, 2011 at 9:46 AM, <pharo(a)googlecode.com> wrote: > Status: Accepted > Owner: siguctua > > New issue 3525 by siguctua: Compiler>>parserClass is broken and does not > querying the class for providing the parser class > http://code.google.com/p/pharo/issues/detail?id=3525 > > In the following: > > Compiler>>parserClass > > ^parser ifNil: [self class parserClass] ifNotNil: [parser class] > Who writes this stuff ?? ;) <blush> I suggest the attached: parserClass ^parser ifNil: [(class ifNil: [self class]) parserClass] ifNotNil: [parser class] > > > 'self class' should actually be 'class parserClass' > > So, any class could override the default parser by own. In that way a > default parser class is answered by Behavior, not by Compiler. > A Compiler class>>parserClass is useless. > > > But even more than that, due to initializing 'parser' ivar in > Compiler>>new, > it never gets to that code, and evaluating 'parser class' > So, a class can't specify a custom parser class to compiler. > > > > >

Jan. 10, 2011

Re: [Pharo-project] Origins [poll]

by Gabriel HernÃ¡n Barbuto

Jan. 10, 2011

Re: [Pharo-project] additional font size?

by Alexandre Bergel

Ok, I will check. Cheers, Alexandre On 10 Jan 2011, at 13:57, Sven Van Caekenberghe wrote: > > On 10 Jan 2011, at 11:26, Alexandre Bergel wrote: > >> Hi! >> >> Apparently, the 1.2 image contains only the size 7, 9 and 12 for Bitmap DejaVu Sans. Can we get additional font sizes? Are there a vectorial font police supported in Pharo? I would like to be able to give any arbitrary font size. >> >> Cheers, >> Alexandre > > You could load 'DejaVuBitmapFonts' from SqueakSource 'DejaVu'. > You then get size 8,9,10,11,12,14,17 and 22. > These also work on Cog. > > Sven > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 10, 2011

Re: [Pharo-project] Issue 3525 in pharo: Compiler>>parserClass is broken and does not querying the class for providing the parser class

by pharo＠googlecode.com

Comment #4 on issue 3525 by siguctua: Compiler>>parserClass is broken and does not querying the class for providing the parser class http://code.google.com/p/pharo/issues/detail?id=3525 For example, OMeta using custom parser/compiler for own source code. So, custom parsers for parsing methods in fact are common.

Jan. 10, 2011

[Pharo-project] Issue 3526 in pharo: Update bug reporting instructions now that new issues are automatically posted to mailing list

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3526 by sean.p.denigris: Update bug reporting instructions now that new issues are automatically posted to mailing list http://code.google.com/p/pharo/issues/detail?id=3526 The final instruction at http://pharo-project.org/community/issue-tracking reads: "After having submitted an issue: Send a mail to the mailing list with the link and a short description." This now happens automatically and should be removed.

Jan. 10, 2011

Re: [Pharo-project] Issue 3525 in pharo: Compiler>>parserClass is broken and does not querying the class for providing the parser class

by pharo＠googlecode.com

Comment #3 on issue 3525 by siguctua: Compiler>>parserClass is broken and does not querying the class for providing the parser class http://code.google.com/p/pharo/issues/detail?id=3525 > Default is Smalltalk and for any other syntax you can use Default is 'Parser' :) a pragma: foo >>> <language: 'JavaScript'> before you get there, you should use some kind of parser to parse the pragma, and i don't see why it should be prohibited from changing a default parser for source code. It should be possible to instruct the compiler to use different parser for parsing a source code of my class methods, so a method's source code could look like: <xml> <method name="foo"> <return> <message><receiver><self/></receiver> <selector value="foo"/> </message> </return> </method> </xml> :)

Jan. 10, 2011

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by pharo＠googlecode.com

Comment #1 on issue 3506 by sean.p.denigris: TextMorph's #autoFit: and #wrapFlag: are confusing http://code.google.com/p/pharo/issues/detail?id=3506 Fix in inbox SLICE-Issue-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1 Added comments for TextMorph's #autoFit: and #wrapFlag:

Jan. 10, 2011

Re: [Pharo-project] Issue 3525 in pharo: Compiler>>parserClass is broken and does not querying the class for providing the parser class

by pharo＠googlecode.com

Comment #2 on issue 3525 by siguctua: Compiler>>parserClass is broken and does not querying the class for providing the parser class http://code.google.com/p/pharo/issues/detail?id=3525 Here the test case, which covers this issue Attachments: CustomParserTest.1.cs 1005 bytes

Jan. 10, 2011