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

[Pharo-project] [update 2.0] #20469

by Marcus Denker

20469 ----- Issue 7224: Failing test related to RB http://code.google.com/p/pharo/issues/detail?id=7224 Issue 6957: ConfiugrationCommandLineHandler tries to open file on --help in non-headless mode http://code.google.com/p/pharo/issues/detail?id=6957 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-CommandLine-MarcusDenker.69.diff http://ss3.gemstone.com/ss/Pharo20/Refactoring-Tests-Core-MarcusDenker.59.d… http://ss3.gemstone.com/ss/Pharo20/Refactoring-Core-MarcusDenker.169.diff http://ss3.gemstone.com/ss/Pharo20/NativeBoost-Core-MarcusDenker.98.diff http://ss3.gemstone.com/ss/Pharo20/ConfigurationCommandLineHandler-Core-Mar…

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Sven Van Caekenberghe

On 14 Jan 2013, at 09:09, Norbert Hartl <norbert(a)hartl.name> wrote: > Am 14.01.2013 um 07:54 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> Morning, Norbert, >> >> On 14 Jan 2013, at 07:44, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? >>> Using *cello you can use postLoadDoits to tweak stuff. >> >> You mean that, in your opinion, making sure that the #initialize is called in every scenario (new/existing class) can only be done with an explicit action ? > > I think that the primary purpose is to initialize newly created space. In case of shape change this doesn't happen. So taking the example you initialize e.g. an instvar with a collection. Do you want to reinitialize it even if you corrected a typo in the comment of a method? > If I wanted to have control over those things I would on class initialization register a class of mine to the local change notification system in the image. But this isn't easy to do in a cross platform manner. Maybe there are better ways. I'm sure someone will speak up then. Let's make it more concrete. Zinc-Resource-Meta-Core is a package that among other thins contains ZnMimeType. ZnMimeType class>>initialize sets up some constants (lists of known mime types, file extension to mime type mappings, you get the idea). When I add new constants in a new source version, I want them to be added when doing an automated CI build, obviously. Right now, this does *not* happen, probably because the class and #initialize method already exist in the image where it is being load in. Indeed, you would not always want costly initializations to run, but there should at least be a hook to do it, no ? >>> Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>>> Hi, >>>> >>>> For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. >>>> >>>> Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? >>>> >>>> It does not get sent to existing classes being reloaded/overwritten ? >>>> >>>> Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? >>>> >>>> What would be the best practice here ? The most portable one ? >>>> >>>> I want to be able to make sure #initialize is sent when I want it. >>>> >>>> Thx, >>>> >>>> Sven >>>> >>>> PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. >>>> >>>> -- >>>> Sven Van Caekenberghe >>>> http://stfx.eu >>>> Smalltalk is the Red Pill >> >> >

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Norbert Hartl

Am 14.01.2013 um 07:54 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Morning, Norbert, > > On 14 Jan 2013, at 07:44, Norbert Hartl <norbert(a)hartl.name> wrote: > >> As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? >> Using *cello you can use postLoadDoits to tweak stuff. > > You mean that, in your opinion, making sure that the #initialize is called in every scenario (new/existing class) can only be done with an explicit action ? I think that the primary purpose is to initialize newly created space. In case of shape change this doesn't happen. So taking the example you initialize e.g. an instvar with a collection. Do you want to reinitialize it even if you corrected a typo in the comment of a method? If I wanted to have control over those things I would on class initialization register a class of mine to the local change notification system in the image. But this isn't easy to do in a cross platform manner. Maybe there are better ways. I'm sure someone will speak up then. Norbert > Sven > >> Norbert >> >> Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> Hi, >>> >>> For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. >>> >>> Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? >>> >>> It does not get sent to existing classes being reloaded/overwritten ? >>> >>> Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? >>> >>> What would be the best practice here ? The most portable one ? >>> >>> I want to be able to make sure #initialize is sent when I want it. >>> >>> Thx, >>> >>> Sven >>> >>> PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill > >

Jan. 14, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by Geert Claes

The updated stHub looks good! One thing I noticed is that I get to see the new 404-lego-head page quite a lot? In the "Recently created projects" the following projects are not found: Prototype, Odyssey and MukadePM. Maybe it's because these projects are not public? Doing a search for something that doesn't exist also gives the "page not found" page. While browsing around I noticed too that there are projects without "contributors"? Anyhow, just fyi because I know its still a wip and its starting to look pretty nice :) -- View this message in context: http://forum.world.st/SmalltalkHub-upgrade-tp4662977p4663245.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Sven Van Caekenberghe

Morning, Norbert, On 14 Jan 2013, at 07:44, Norbert Hartl <norbert(a)hartl.name> wrote: > As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? > Using *cello you can use postLoadDoits to tweak stuff. You mean that, in your opinion, making sure that the #initialize is called in every scenario (new/existing class) can only be done with an explicit action ? Sven > Norbert > > Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> Hi, >> >> For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. >> >> Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? >> >> It does not get sent to existing classes being reloaded/overwritten ? >> >> Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? >> >> What would be the best practice here ? The most portable one ? >> >> I want to be able to make sure #initialize is sent when I want it. >> >> Thx, >> >> Sven >> >> PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Norbert Hartl

As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? Using *cello you can use postLoadDoits to tweak stuff. Norbert Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi, > > For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. > > Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? > > It does not get sent to existing classes being reloaded/overwritten ? > > Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? > > What would be the best practice here ? The most portable one ? > > I want to be able to make sure #initialize is sent when I want it. > > Thx, > > Sven > > PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Jan. 14, 2013

[Pharo-project] Class initialisation after loading

by Sven Van Caekenberghe

Hi, For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? It does not get sent to existing classes being reloaded/overwritten ? Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? What would be the best practice here ? The most portable one ? I want to be able to make sure #initialize is sent when I want it. Thx, Sven PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Jan. 14, 2013

[Pharo-project] pharo association membership

by Tudor Girba

Hi, I just remembered that I forgot to pay for the membership. I remedied the situations a minute ago. I am sending this message because as a reminder in case other people might have forgotten, too :). For convenience, to get a membership: - go here: http://association.pharo.org/web/members/register - enter your data - login and go to http://association.pharo.org/web/members - press "review my subscription" Cheers, Doru -- www.tudorgirba.com "To utilize feedback, you first have to acquire it."

Jan. 13, 2013

Re: [Pharo-project] Evaluate math expression

by H. Hirzel

PetitParser --Hannes On 1/13/13, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Hello, > > What tools will you use to evaluate math expression writen in algebraic > form as 2*x*cos(5*x+10). > > Thanks > > > Hilaire > > >

Jan. 13, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Camillo Bruni

I added a new jenkins job: https://ci.inria.fr/rmod/job/TxText/ currently inactive/broken, we will dive into it tomorrow ;) On 2013-01-13, at 22:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > thanks denis for pushing that!!!! > > Stef > > >> Hello. >> >> I upload new version of TxText with new TxTextMorph which can show TxTextModel (http://www.smalltalkhub.com/#!/~sig/TxText ). See class side examples. >> >> Implementation details: >> >> TxTextMorph has textLayout instance variable which contains full precomputed information to draw text on screen. TxTextLayout contains collection of TxTextLine. TxTextLine contains collection of span objects (from text model) and offset with extent required for drawing lines (with right align for example). >> There are TxTextLayoutStrategy hierarchy responsible for building specific text layout objects: >> â¢ TxSimpleTextLayoutStrategy build layout with actual text lines which text model contains >> â¢ TxWrapTextStrategy build layout with lines which satisfied preferredExtent (given from text morph bounds) >> When text morph accepts new text model It asks layoutStrategy to build new layout. Then align selector applyed to layout. So text can be placed left to right, centered or right to left. >> >> Morph drawing method very simple: >> >> TxTextMorph>>drawOn: aCanvas >> textLayout drawTextOn: aCanvas at: self position >> >> TxTextLayout>>drawTextOn: aCanvas at: aPoint >> | topOffset linePosition | >> topOffset := 0. >> lines do: [:eachLine | >> linePosition := aPoint x @ (aPoint y + topOffset). >> eachLine drawOn: aCanvas at: linePosition. >> topOffset := topOffset + eachLine height. >> ] >> >> TxTextLine>>drawOn: aCanvas at: aPoint >> >> spans do: [:each | >> each drawOn: aCanvas at: aPoint + offset >> ] >> >> At the end TxCharactersSpan draw contents on canvas: >> >> TxCharactersSpan >>drawOn: aCanvas at: aPoint >> aCanvas >> drawString: characters >> at: aPoint >> font: (self getAttribute: TxFontAttribute) >> color: (self getAttribute: TxColorAttribute) >> >> And with Athens api text attributes can be not hardcoded: >> >> TxCharactersSpan >>drawAthensOn: aCanvas at: aPoint >> attributes applyOn: aCanvas. >> aCanvas pathTransform translateX: aPoint x Y: aPoint y. >> aCanvas drawString: characters >> >> Questions: >> >> Now text alignment (like centering) is property of TxTextMorph. So it global property of full text layout. >> But how such attribute can be applied to specific line? >> >> TxModel is list of spans. And each span object contains characters with same text attributes like font or color. Text alignment can be such attribute too. Do you think it should be attribute of all spans from single line? Or it should be only attribute of TxLineSeparator span? What your idea? >> >> Future: >> >> Next plan: cursor navigation, text selection and editing features. And of course tests, sorry I not start with tests now. >> >> I wait your comments , ideas and questions. Maybe you don't like my approach. I want to know why. >> I really want clean and object solution for text stuff in pharo. >> > >

Jan. 13, 2013