- Pharo-dev - lists.pharo.org

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

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

by StÃ©phane Ducasse

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

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

by StÃ©phane Ducasse

Igor do not think that because our tools do not use anything, we do not need good text support. Moose is struggling with the limits of the current textmodel. We should offer solutions to people not just to edit methods. Stef On Jan 13, 2013, at 9:51 PM, Igor Stasenko wrote: > Wow.. > this is a huge progress! > Sorry i was busy with other stuff and had no time to look at your code. > > > On 13 January 2013 20:54, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> 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? >> > > Well, there is two approaches: a per-line attribute can be a special > span at the beginning at > line, or it can be an attribute. Both has pros and cons, however. > In case of span, it needs to be dealt properly with text editing/navigation. > In case of attribute(s), this attribute is really per line (or better > to say, per paragraph) > and putting it into each span seems like superfluous. > > IMO, i would go for a simplest model: the capability like text > alignment (left/center/right) > per line, is kind of overkill for our little world. > I mean, it would be nice to have, but look at our tools: where are > they used? Nowhere. > So i would not focus on it right now, and having a global attribute > seems like a good solution right now. > >> Future: >> >> Next plan: cursor navigation, text selection and editing features. And of >> course tests, sorry I not start with tests now. >> > don't forget about tests. > We started writing a model by implementing tests first, because we > didn't wanted > an implementation to dictate how things should be used. > >> 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. >> > > > > -- > Best regards, > Igor Stasenko. >

Jan. 13, 2013

Re: [Pharo-project] About fluidSynth

by StÃ©phane Ducasse

> Dear StÃ©phane Ducasse san, and Pharo guys all. > > thank you for interesting "FluidSynth goes to Pharo 2.0." work in > progress. it is still unfinishedâ¦ orz keep us posted! This sounds like an exciting project. > > "description begin" > 'FluidSynth goes to Pharo 2.0.' packages are plugin for FluidSynth and > GUI and others. > FluidSynth is a real-time software synthesizer based on the SoundFont > 2 specifications. > http://sourceforge.net/apps/trac/fluidsynth/ > > 'FluidSynth goes to Pharo 2.0.' packages will be a sub-package of the > Khoros package handling audio and midi. > requires other MIDI packages (events, files, objects, playing process, etc) *1. > *1: FluidSynth has own midi file player. but this packages don't use it. > "description end" > > digressing: > first, Squeak has a useful SimpleMIDIPort, but we can't use any > software synthesizer with/through it.ãThere is no CoreMIDI. so i made > a PortMidiPlugin(++) for Squeak (OSX). after it, "There's Something > About Pharo 2.0". > thereafter i wanted a handy midiport without any external software > synthesizer, and found FluidSynth. If you need help for having a build server, we will have a new jenkins server :) > > i only wanted handy and 'simple' midiport for playback or testing, but > FluidSynth profound. for example, it supports microtonal. we can use > just intonation, meantone temperament, or other alternative tunings... > > ... this package became huge across expectation. 46 classes (4 traits) > have instance methods 832, class method 327 (selectors counting). but > the simplest use requires one FluidSynthInterface class only. of > course fluidsynth library and FluidSynthPlugin must be placed for VM. :) > widgets: > well, there is no special widgets. VolumeKnobMorph is a subclass of > PluggableSliderMorph simply. morph of VU meter is a subclass of > AlignmentMorph with custom drawOn:, drived by a model descendant of > ComposableModel. Still if you want to propose some simple subclasses to improve the ones in Pharo feel free. > after all or as an interim report, it may be that i'll commit to > public code-repository, such as umezawa san's SqueakSourceJ > (http://squeaksource.blueplane.jp/) ss3, sh, or so. Ok just pay attention that GPL is not a smalltalk friendly license. > PortMidiPlugin and FluidSynthPlugin have no platform sources. > (PortMidiPlugin++ is for OSX only) > > > -p.s.- > > will Pharo 2.0 official come with new clean changes? > Pharo-20468.image: 29.1 MB > Pharo-20468.changes: 31.1 MB We added a lot like new AST/Refactoring engine, metacello, so 2.0 will be probably a bit bigger than what we would like. What we need is - to manage pharo fully with metacello - get hazelnuts as the core Plus - a fast deployment and loading mechanism (Tanker/fuel) and we could really get a small kernel but with all the packages around in good shape. Right now we have problems to maintain all the packages that we want and keep them outside the image. Stef > 2013/1/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Dear Nishihara Satoshi >> >> I saw a tweet on fluidsynth and it that it is running on Pharo. It looks really nice. >> We would like to have a a news on it on the pharo web site. >> >> Could you provide a little text? >> >> BTW if you are creating widget that you think that missing in Pharo you can offer them to Pharo >> under MIT and we will maintain them and enhance them when we are building the new UI builder. >> Stef >> >> >> Begin forwarded message: >> >>> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Subject: [Pharo-project] About fluidSynth >>> Date: January 12, 2013 11:00:26 PM GMT+01:00 >>> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> >>> Reply-To: Pharo-project(a)lists.gforge.inria.fr >>> >>> Hi guys >>> >>> I aw a tweet on fluidSynth on Pharo2.0 and I **want** a news for the Pharo web site. >>> So what is FluidSynth :) >>> I want more than http://sourceforge.net/apps/trac/fluidsynth/ :) >>> Stef >>> >> >>> >>> >>> >> >> > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

Jan. 13, 2013

[Pharo-project] Evaluate math expression

by Hilaire Fernandes

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