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

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 #1 on issue 3525 by Torsten....(a)astares.de: 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 But that would ONLY associate A CLASS with its own parser/compiler. But wouldnt it make more sense on the method level. Default is Smalltalk and for any other syntax you can use a pragma: foo <language: 'JavaScript'> alert('hi'); bar <language: 'C'> _export(...) You could return a script for Seaside or store an XML in a method, write VMMaker in C in the ST browser, ... I think VW has something similar since I've seen this once in a VW browser. Smalltalk/X too since you can write C directly in the ST browser. Depending on the pragma you could do syntax highligting, provide tools, ...

Jan. 10, 2011

[Pharo-project] Custom Parser class

by Igor Stasenko

Hello, i stumbled upon weird thing. In my own class i wanted to define own custom parser class, by implementing MyClass class>>parserClass and it seems works only for parsing during source code highlighting, but completely does not taken into account when compiling methods of my class. Is this done by intent, so to specify custom parser, first i need to provide a custom compiler , which providing custom parser? And if not, this should be fixed. See http://code.google.com/p/pharo/issues/detail?id=3525 for details. -- Best regards, Igor Stasenko AKA sig.

Jan. 10, 2011

[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

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] '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 Dale Henrichs

Jan. 10, 2011

Re: [Pharo-project] aligning morphs

by StÃ©phane Ducasse

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 3523 in pharo: Nested comments

by pharo＠googlecode.com

Comment #5 on issue 3523 by renggli: Nested comments http://code.google.com/p/pharo/issues/detail?id=3523 Fist of all, C/C++/Java/C#/JavaScript comments go like this: /* some comment */ In any case, introducing that into Smalltalk doesn't work because both #/* and #/* are valid binary selectors and it would be highly ambiguous to parse something like this: 12 /* some comment */ a A combination with the double-quotes $" could work and would avoid the ambiguity: "* some comment "* some nesting *" *" Otherwise, I am afraid there is no other character to introduce nested comments.

Jan. 10, 2011

Re: [Pharo-project] additional font size?

by Sven Van Caekenberghe

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

Jan. 10, 2011

Re: [Pharo-project] Why Sets need to be rehashed when loading them from an ImageSegment?

by Lukas Renggli

Any object that uses an identity hash anywhere in its #hash might change its hash, thus the rehashing. Lukas On Monday, 10 January 2011, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi. I was almost sure that Set instancesÂ that were written in an ImageSegment,Â needed to be rehashed once they are swap in. And I even thought I was understanding why. But now, I don't understand at all why is that. I would really appreciate anyway that can give me a hint. > > So...ImageSegment rehashes all Set instances (at loading time) that were written in an ImageSegment, and then exported with ReferenceStream. Notice that this rehash is finally called from ImageSegment >> comeFullyUpOnReload: smartRefStream. > When you export an ImageSegment with a reference stream, you also serializer the "outPointers" array. This is usually the case when you want to load the object subgraph in another image or when do it backups so that to start with a clean image.Â Notice that the Set rehash only occurs in this case. If we use ImageSegment just to swap out / in, there is no Set rehash. > So...I think that this has something to do about WHY Set instances need to be rehashed. > > For each object ImageSegment write into the file, it writes both: object header + slots.Â Â So....the hash (12 bits in the object header) is copied. When the object is loaded back, it continues to have the same hash. It doesn't change. > So...if hash doesn't change, why Set instances need to be rehashes when they come back from an ImageSegment? > > Thanks in advance, > > Mariano > -- Lukas Renggli www.lukas-renggli.ch

Jan. 10, 2011

Re: [Pharo-project] aligning morphs

by Gary Chambers

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 3516 in pharo: Failing tests in MetaCello

by pharo＠googlecode.com

Updates: Status: Closed Comment #5 on issue 3516 by marianopeck: Failing tests in MetaCello http://code.google.com/p/pharo/issues/detail?id=3516 thanks dale. I close the issue then :)

Jan. 10, 2011