- Pharo-dev - lists.pharo.org

[Pharo-project] ProtoObject basicNew :)
by StÃ©phane Ducasse Nov. 29, 2011

Nov. 29, 2011

Hi I would like to know the methods that I should define in a subclass of ProtoObject so that I can use basicNew. Does any of you have an idea? Stef

5 15

[Pharo-project] [COTDC] 85 - HashedCollection
by Sean P. DeNigris Nov. 29, 2011

Nov. 29, 2011

Today: HashedCollection Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest -- View this message in context: http://forum.world.st/COTDC-85-HashedCollection-tp4115592p4115592.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 4

[Pharo-project] Toolbar for haltOnce etc?
by Stefan Marr Nov. 29, 2011

Nov. 29, 2011

Hi: Is there anything floating around that I could load into a Pharo image that gives me some small tools like for instance 'Object setHaltOnce' to arm haltOnce? There are probably more useful things in the image I haven't noticed yet. In case anyone has something like a toolbar with such things, I would appreciate a pointer. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

1 0

Re: [Pharo-project] Athens work in progress: couple screenshots
by Fernando Olivero Nov. 29, 2011

Nov. 29, 2011

I get the point now, something like the brushes in seaside. Thanks for the explanation. Regarding the protocol, did you consider reusing the same idea, but one step before, as in the following: pathTransform := canvas transformDescribedBy: 'path'. pathTransform scaleBy: 0.5. imageTransform := canvas transformDescribedBy: 'image'. imageTransform scaleBy: 0.5. Maybe add the following for documentation: AthensCairo>>availableTransforms ^ #('path'. 'image'. ) AthensOpenGL>>availableTransforms ^ #('modelView'. 'projection'. ) This would unify the canvas protocol, for all the available rendering engines. Fernando On Mon, Nov 28, 2011 at 6:43 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 28 November 2011 16:04, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: >> Don't know, but in case we cant modify Athens, we can always rename >> the project and start fresh, given that Igor rewrote most of it >> right?. >> >> Fernando >> >> On Fri, Nov 25, 2011 at 12:58 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> On Nov 25, 2011, at 10:35 AM, Fernando Olivero wrote: >>> >>>> Ok, i will try to do so from now on! >>>> >>>> Igor, thanks for detailed response, i see now there's no real need for >>>> caching the glyphs, even though i didn't consider rotation as an >>>> available affine transformation. >>>> >>>> Just a question on the protocol of the canvas, i found it better to >>>> use the following convenience methods, instead of exposing the >>>> transformation (or canvas state) directly to the sender: >>>> >>>> drawOn: aCanvas >>>> Â aCanvas pathTransform â¦ >>>> >>>> drawOn: aCanvas >>>> Â Â aCanvas scaleBy: 0.5 @0.5 ; translateBy: 10@10 . >>>> Â Â â¦.. > > the canvas #pathTransform actually should answer a delegate, > which should allow you to manipulate coordinate system transformation. > There's no intent to expose the state directly. You can modify > transformation matrix > only via corresponding protocol, but don't manipulate its state directly. > > now about > canvas scaleBy: ... versus canvas pathTransform scaleBy:... > why i did it like that? because there are multiple transformation > matrices responsible > for different parts of computations. > for instance, in OpenVG model there are four: > Â - path > Â - image > Â - stroke > Â - (forgot) :) > > or take an openGL for example there are 3 (or 4) matrices again: > Â - model > Â - projection > Â - texture > Â - color space > > if you expose all of them via canvas, then you have to bloat canvas > protocol with duplicate messages like: > > canvas pathScale: > canvas pathRotate: > canvas imageScale: > canvas imageRotate: > ... etc > > that's why there are separate delegates, which represent concrete > matrix, and common protocol which > you can use for all of them: > > canvas pathTransform scaleBy: > canvas imageTransform scaleBy: > etc > > > -- > Best regards, > Igor Stasenko.

2 1

Re: [Pharo-project] Pharo VMs should be more Pharo-like
by Marcus Denker Nov. 29, 2011

Nov. 29, 2011

On Nov 29, 2011, at 1:46 PM, Esteban Lorenzano wrote: > Hi, > > Currently, we are linking official VMs for pharo taking directly from Jenkins a version and packaging for download (or for Pharo One-Click). > I think this is a temporal solution, we need something better: > > 1) Pharo VMs should have Pharo Icons. > 2) Pharo VMs should be named "pharo" or "pharovm" (better the fist), not "CogVM", which is an internal name. > 3) We should include a PLUGINS.txt file with information about present plugins (internal and external) > 4) We should include a LICENCE.txt file with all licence information. > > ... I think that's all :) > > I know... this is very dumb and clearly not mandatory, but it says a lot about the maturity of our Pharo :) > > All agree? Should I create a ticket? > yes. > > pd: I'm the only one who does not likes One-Click versions? I would prefer a different package for each platform (Is ugly to have a directory named Pharo.app in linux or windows. Also, no need to have all those duplicated-but-for-different-platform files) Yes, I was thinking about that, too... its nice for the very first step, but then it's more a problem. Maybe having 3 packages for the three architectures would be better? -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] 1.4 arch users of Smalltalk does not work anymore
by StÃ©phane Ducasse Nov. 29, 2011

Nov. 29, 2011

Hi ben I cannot work with 1.4 to look for users for example of Smalltalk. Can you have a look because it is dead slow. May be something with the Class comments. Stef

1 0

Re: [Pharo-project] Building 32-bit Cairo library on Macs
by Fernando Olivero Nov. 29, 2011

Nov. 29, 2011

Igor, i've downloaded the latest native boots vm, loaded the NB and NBCairo, only missing Cairo now. Could you provide the library you built for the Mac. Thanks, Fernando On Sun, Nov 27, 2011 at 10:12 PM, fernando.olivero(a)usi.ch <fernando.olivero(a)usi.ch> wrote: > nice! thanks a lot for dealing with the ugliness outside the smalltalk > world, so we mortals can deal with higher level languages. > > Looking forward to see an Athens binding to Cairo. > Fernando > > On Fri, Nov 25, 2011 at 7:33 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> cool >> We want more :) >> >> Stef >> >> On Nov 25, 2011, at 5:17 PM, Igor Stasenko wrote: >> >>> Just to let you know: >>> >>> it works on Mac! >>> I just loaded the code which Javier did for linux, changed path to >>> library and it worked out of the box. >>> all examples in [1] are working out of the box! >>> >>> So, now i can start wiring Cairo backend for Athens :) >>> >>> [1] http://squeaksource.com/NBCairo/ >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >> > >

3 2

[Pharo-project] RenameMethodRefactoring Comment
by Sean P. DeNigris Nov. 29, 2011

Nov. 29, 2011

Here's a free bonus class comment: I do just what my name says. Example Usage: refactoring := RenameMethodRefactoring renameMethod: oldSelector in: class to: newSelector permutation: (0 to: oldSelector numArgs). refactoring execute. A few things to keep in mind: - even though a class is specified, my action is system-wide. The only thing I do with the class is make sure it defines oldSelector - the permutation should be a collection that specifies what order the arguments from the oldSelector should appear in the newSelector. If the argument order doesn't change, you can just use the interval shortcut shown above in the example. Example when arguement order changes: oldSelector: arg1 with: arg2 with: arg3 newSelector: arg2 with: arg3 with: arg1 permutation := { 2. 3. 1 } -- View this message in context: http://forum.world.st/RenameMethodRefactoring-Comment-tp4117939p4117939.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 1

Re: [Pharo-project] Morphic replacement
by Fernando Olivero Nov. 28, 2011

Nov. 28, 2011

When the vm, starts announcing multitouch events, it's a matter of adding that particular peripheral device to the model. For now, the vm only announces mouse and keyboard events, therefore i only modeled those. Thanks for the question, maybe we should ask the vm guys to add this to their todo list. Fernando On Sat, Nov 26, 2011 at 8:15 PM, Douglas Brebner <squeaklists(a)fang.demon.co.uk> wrote: > On 25/11/2011 10:00, Fernando Olivero wrote: > > Sounds good except maybe >> The world has a mouse and a keyboard, which take care of events >> announced by the world. > > Does that mean you're not thinking of support for multitouch? > > >

2 1

Re: [Pharo-project] Athens work in progress: couple screenshots
by Fernando Olivero Nov. 28, 2011

Nov. 28, 2011

Don't know, but in case we cant modify Athens, we can always rename the project and start fresh, given that Igor rewrote most of it right?. Fernando On Fri, Nov 25, 2011 at 12:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Nov 25, 2011, at 10:35 AM, Fernando Olivero wrote: > >> Ok, i will try to do so from now on! >> >> Igor, thanks for detailed response, i see now there's no real need for >> caching the glyphs, even though i didn't consider rotation as an >> available affine transformation. >> >> Just a question on the protocol of the canvas, i found it better to >> use the following convenience methods, instead of exposing the >> transformation (or canvas state) directly to the sender: >> >> drawOn: aCanvas >> Â aCanvas pathTransform â¦ >> >> drawOn: aCanvas >> Â Â aCanvas scaleBy: 0.5 @0.5 ; translateBy: 10@10 . >> Â Â â¦.. > > thanks for the feedback > >> Regarding the cleaning, a good start would be the Tweak related >> package, i could do it. > > Can we throw it away? > Because we should get license problem? > > Stef >> >> Fernando >> >> On Thu, Nov 24, 2011 at 10:57 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> On Nov 24, 2011, at 12:33 AM, Fernando Olivero wrote: >>> >>>> Ah! So Athens is a facade, for a Canvas API, based on Paths, that >>>> could have a Cairo, OpenGl or BallonCanvas rendering engine as a >>>> backend. >>> >>> Yes!!! >>> Yo got it. >>> >>>> In the current case, using BallonCanvas (bit map based), i guess you >>>> are implementing the scalable fonts using the free type library? In >>>> Gaucho, i've done exactly that, i have a FontLibrary which acts as a >>>> cache for a particular font family, at a requested size. So when Â the >>>> canvas renders a string with a given font, it asks the library for the >>>> font at the current scale of the desired size. >>> >>> fernando >>> you should mention more often what you are doing. >>> Because like that we can maximize impact and interaction. >>> >>>> Although i prefer the abstractions that are present in Athens, and >>>> will try to use it instead eventually. >>>> >>>> Fernando >>>> pd: attached screen shot of Gaucho, using a scalable GCanvas (built on >>>> top of the free type lib and FormCanvas). >>>> >>>> >>>> On Wed, Nov 23, 2011 at 1:08 PM, Alexandre Bergel >>>> <alexandre.bergel(a)me.com> wrote: >>>>> +1 >>>>> >>>>> Something big is happening in the Pharo World. >>>>> >>>>> Alexandre >>>>> >>>>> >>>>> On 23 Nov 2011, at 08:44, StÃ©phane Ducasse wrote: >>>>> >>>>>> put it in the class comments somewhere. >>>>>> Do not expect that people will know what you know. >>>>>> Make the entry simple and immediate. >>>>>> >>>>>> Stef >>>>>> >>>>>>> On 23 November 2011 11:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>>>>> Igor >>>>>>>> >>>>>>>> prepare the following: >>>>>>>> Â Â Â - a class showing an example >>>>>>>> Â Â Â Â Â Â Â with the transformation stuff (because it is unclear) >>>>>>> >>>>>>> There is one: >>>>>>> AthensBalloonSurfaceExamples >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Â Â Â - a tester canvas so that people can to >>>>>>>> >>>>>>>> (CanvasTester testClass: CircleMorph) open. >>>>>>>> >>>>>>> err.. what is it? >>>>>>> >>>>>>> To test morphic display on Athens you can do following: >>>>>>> >>>>>>> | surf | >>>>>>> Â Â Â surf := AthensBalloonSurface new form: (Form extent: Display extent depth: 32). >>>>>>> >>>>>>> Â Â Â surf drawDuring: [ :canvas | >>>>>>> >>>>>>> Â Â Â Â Â Â Â canvas fullDrawMorph: yourMorph. >>>>>>> ]. >>>>>>> >>>>>>> Display getCanvas translucentImage: surf form at: 0@0 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> People could then extend the Athens package with the method in the morph. >>>>>>>> >>>>>>>>> It would be great to help adapting all morphs for Athens. >>>>>>>>> Morphs, that having own draw method(s), should also have own >>>>>>>>> #drawOnAthensCanvas: >>>>>>>>> >>>>>>>>> I didn't covered all of them yet, so a little help with it would be nice. >>>>>>>>> Also, it is good for checking the missing functionality in Athens API >>>>>>>>> as well as learning it. >>>>>>>>> >>>>>>>>> There's not much to learn yet :) >>>>>>>>> >>>>>>>>> basicly what you should know is that you have coordinate system: >>>>>>>>> >>>>>>>>> canvas pathTransform >>>>>>>>> Â (instance of AthensAffineTransform) >>>>>>>>> >>>>>>>>> which you can manipulate to achieve desirable results. >>>>>>>>> >>>>>>>>> And actual drawing: >>>>>>>>> >>>>>>>>> canvas setPaint: somePaintObject. ( color, gradient, or anything which >>>>>>>>> conforms to AthensPaint protocol ). >>>>>>>>> canvas drawShape: Â (rect or path or anything , which responds to: >>>>>>>>> 'paintFillsUsing: aPaint on: anAthensCanvas' ). >>>>>>>>> canvas draw: (anything , which responds to #drawOnAthensCanvas: ) >>>>>>>> >>>>>>>> think that we are dummies willing to help and do the two things I mention above. >>>>>>>> I'm then sure you will get contributions. >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Igor Stasenko. >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel Â http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> <scalableText-gCanvas.jpg> >>> >>> > >

3 2