February 2014 - Pharo-users

Fonts

by Bob Williams

I am using Pharo 3.0 and I want to experiment with Unicode Fonts; however, I am running into trouble getting a instance of the font for use with the selector /font/:. I can use the FreeTypeSelectionWindow to select the font I want, namely: FreeTypeFont('Cambria Math' 'Regular' 10). I do this by creating an instance of that Dialog and inspecting it. The inspector is of little use because the Dialog is no modal, i.e., it does not force a return. I can, however, perform the selection of the desired font which updates the inspector and then I can open an inspector on the realFont instance variable. While this tortured trail lead me to my answer the problem is still not solved. There are three solutions to my problem, namely: either the selection window can be made modal or there is a method that will take the parameters, FreeTypeFont, 'Cambria Math', 'Regular' and the pointSize 10, and will return a instance of the font, or the drawing method of the string accepts those parameters. Any help will be greatly appreciated, I hope to gain enough knowledge to document the proper use of Unicode. I need to understand it so I can create a math formula equation editor. Thanks to those that have answered my previous questions.

Feb. 4, 2014

Video "Pharo: Objects at your Fingertips" now on youtube

by Marcus Denker

Hi, The talk I gave at Universitat PolitÃ¨cnica de Catalunya on Oct 30 is now on youtube: Pharo: Objects at your Fingertips http://www.youtube.com/watch?v=xhPlUaXpCU4 This should be simpler than the mms: link or silverlight player version that there was before. Slides are here: http://www.slideshare.net/MarcusDenker/pharo-objects-at-your-fingertips http://marcusdenker.de/talks/13BarcelonaTalk/PharoObjectsAtYourFingertips.p… Marcus

Feb. 4, 2014

Re: [Pharo-users] Instance-specific behavior

by Alejandro Infante

Proxy maybe? I remember an example in Pharo by Example Book chapter 13 or 14. So the main idea would be: Create MyProxy, subclass of ProtoObject and with an instance variable. MyProxy>>initialize morph := self. Override doesNotUnderstand to dispatch the message to the other object. Also implement your custom behavior in the MyProxy. Then use #become: to install the proxy. (The one that swaps all the references) Cheers, Alejandro 2014-02-04 Sean P. DeNigris <sean(a)clipperadams.com>: > What would be the best way (as an experiment) to change the behavior of > just > one instance. For example, say: > SpecialMorph>>#color > ^ Color blue. > but (the effect of) > aSpecialMorph>>#color > ^ owner color. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Instance-specific-behavior-tp4741502.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 4, 2014

Instance-specific behavior

by Sean P. DeNigris

What would be the best way (as an experiment) to change the behavior of just one instance. For example, say: SpecialMorph>>#color ^ Color blue. but (the effect of) aSpecialMorph>>#color ^ owner color. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Instance-specific-behavior-tp4741502.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 4, 2014

Re: [Pharo-users] Roassal Sunburst examples not working

by Arturo Zambrano

Thanks for your help. I tried activating freetype in the Appearance window and also programmatically doing: FreeTypeFontProvider current updateFromSystem. I still have the same problem. SunburstExample new sunburstExample1 works SunburstExample new sunburstExample2 fail SunburstExample new sunburstExample3 fail On Tue, Feb 4, 2014 at 6:09 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Alejandro wrote > >World Menu > System > Settings > Appearance: > > - Activate Use Free type... (If is already activated, deactivate it and > activate it again). > > FreeTypeFontProvider current updateFromSystem. >

Feb. 4, 2014

Re: [Pharo-users] Xs&Os game

by Yuriy Tymchuk

On 04 Feb 2014, at 18:08, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 04 Feb 2014, at 18:04, ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½ <mrizun(a)gmail.com> wrote: > >> Really appreciate your comments, they are very useful for me. >> I will do my best to make commits as soon as possible to fix problems that you pointed out. >> Plus I've learned so much from only one message! thx:) >> >> 2014-02-04 Damien Cassou <damien.cassou(a)gmail.com>: >> >> Would you consider writing a tutorial on how to implement an Xs&Os game in Pharo? >> >> After finishing this game completely (it will take a while), I have in plans to implement another game. Then, if I have enoug experience in pharo, I want to write 2 tutorials for both games. > > Iâd suggest you to start writing a tutorial on X&O now, and then do something more. Itâs important to have a constant impact. Also if you have a short tutorial (e.g. on Athens) which can help sleepy developers on their deadline hight, I can include you as an author of http://sleepycoders.blogspot.com * deadline night > > Uko > > P.S. good job :) > >> >> Mark >

Feb. 4, 2014

Re: [Pharo-users] Xs&Os game

by Yuriy Tymchuk

On 04 Feb 2014, at 18:04, ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½ <mrizun(a)gmail.com> wrote: > Really appreciate your comments, they are very useful for me. > I will do my best to make commits as soon as possible to fix problems that you pointed out. > Plus I've learned so much from only one message! thx:) > > 2014-02-04 Damien Cassou <damien.cassou(a)gmail.com>: > > Would you consider writing a tutorial on how to implement an Xs&Os game in Pharo? > > After finishing this game completely (it will take a while), I have in plans to implement another game. Then, if I have enoug experience in pharo, I want to write 2 tutorials for both games. Iâd suggest you to start writing a tutorial on X&O now, and then do something more. Itâs important to have a constant impact. Also if you have a short tutorial (e.g. on Athens) which can help sleepy developers on their deadline hight, I can include you as an author of http://sleepycoders.blogspot.com Uko P.S. good job :) > > Mark

Feb. 4, 2014

Re: [Pharo-users] Xs&Os game

by ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½

Really appreciate your comments, they are very useful for me. I will do my best to make commits as soon as possible to fix problems that you pointed out. Plus I've learned so much from only one message! thx:) 2014-02-04 Damien Cassou <damien.cassou(a)gmail.com>: > > > Would you consider writing a tutorial on how to implement an Xs&Os game in > Pharo? > > After finishing this game completely (it will take a while), I have in plans to implement another game. Then, if I have enoug experience in pharo, I want to write 2 tutorials for both games. Mark

Feb. 4, 2014

Re: [Pharo-users] Xs&Os game

by Damien Cassou

On Mon, Feb 3, 2014 at 11:39 AM, ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½ <mrizun(a)gmail.com> wrote: > As a novice in pharo, waiting for comments and advice. > Ð¡ritique is welcome too ;) > random comments (tested on Pharo 3.0): - I played and things work perfectly as far as I saw :-) - your code is of very good quality! - 2 tests don't pass (EmptyCellTestCase, CellRendererTestCase) - usually we don't append 'Case' at the end of our test classes - the package name doesn't follow the convention ( https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Convent… ) - you may want to avoid the use of non-alphanumeric characters in the package name (e.g., avoid &) - please indent your code (use ALT+Shift+u on each method to get automatic indentation) - "self should: [ offset = (50 @ 50) ]" --> "self assert: offset equals: 50@50" - "self should: [ cell isOff ]." --> "self assert: cell isOff" - all subclasses of Cell override #initialize in exactly the same way. Consider moving that to the superclass - you should try to avoid as much as possible doing a super send in a different method. For example, EmptyCell>>initializeState does a super send on #initialize. - OCell and XCell are exactly the same, this should not be and is very suspicious. - CellRenderer has 2 methods with an uppercase letter. This is not conventional - you use a lot of variables you use only once. Consider inlining them. For example in CellRenderer>>offsetWithinGridForm, all variables seem useless : "^ CellRenderer cellExtent * ((self cellLocation x - 1) @ (self cellLocation y - 1))" - CellRenderer>>renderContents uses branching on the class of objects instead of polymorphism. That's bad design in my opinion. Consider delegating to OCell and XCell or using double-dispatch. - Same thing for CellRenderer class>>rendererFor: All in all, very good job. Would you consider writing a tutorial on how to implement an Xs&Os game in Pharo? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 4, 2014

Re: [Pharo-users] Google Summer of Code is here, your ideas please!

by Stephan Eggermont

Configuration sanity checker. Load all ConfigurationOfs and check if dependencies are missing or conflicting. By checking monticello files, the introduction moment and interface changes of classes are known, so a range of possible version combinations can be generated. See DeprecationFinder for some sample code. Distributed Issue Tracker, see LightHouse. New widget set, for use with Spec & Glamour. Needs a designer too. Stephan

Feb. 4, 2014