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

Re: [Pharo-project] New widget

by Mariano Martinez Peck

Hi Ben, sounds good. However, I tried but I have the attached error. Cheers Mariano On Wed, Mar 9, 2011 at 6:09 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Hello everyone, > > I've done a new Morphic widget, that allow to easily switch from a > categorized view to a "all elements" view (quite hard to explain, let me > give you an example ^^) > > > > Gofer new > squeaksource: 'SwitchableTreeWidget'; > package: 'SwitchableTreeWidget'; > load. > > SwitchableCategoriesTreeExample new openInWorld. > > If you click on the button or just double click on the tree, you will > switch the view :) > > I wrote that widget to integrate it in a new browser (and if I succeed, to > create a new Glamour widget) > > > > Thanks in for your feedback :) > > > Ben >

March 9, 2011

Re: [Pharo-project] [COTDC] 27 - DropEvent

by laurent laffont

Added. Thanks Ricardo. Laurent. On Wed, Mar 9, 2011 at 7:50 PM, Ricardo Moran <richi.moran(a)gmail.com> wrote: > I would add the following: > > ========================== > > To handle this event a morph should override one of these methods: > > #acceptDroppingMorph:event: > #justDroppedInto:event: > > Additionaly, a morph can specify if it wants to accept a dropped morph by > overriding #wantsDroppedMorph:event:. Symmetrically, the morph being dropped > can specify if it wants to be dropped in another morph by > overriding #wantsToBeDroppedInto:. > Note that for a successful drop operation both parties need to agree. > > > On Mon, Mar 7, 2011 at 2:38 PM, laurent laffont <laurent.laffont(a)gmail.com > > wrote: > >> Today: DropEvent >> >> >> 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 >> >> Laurent >> > >

March 9, 2011

Re: [Pharo-project] [COTDC] 27 - DropEvent

by Ricardo Moran

I would add the following: ========================== To handle this event a morph should override one of these methods: #acceptDroppingMorph:event: #justDroppedInto:event: Additionaly, a morph can specify if it wants to accept a dropped morph by overriding #wantsDroppedMorph:event:. Symmetrically, the morph being dropped can specify if it wants to be dropped in another morph by overriding #wantsToBeDroppedInto:. Note that for a successful drop operation both parties need to agree. On Mon, Mar 7, 2011 at 2:38 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: DropEvent > > > 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 > > Laurent >

March 9, 2011

Re: [Pharo-project] InterpreterSimulator reloaded

by Pavel Krivanek

On Wed, Mar 9, 2011 at 3:20 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Mar 9, 2011, at 10:48 AM, Pavel Krivanek wrote: > >> Hi Stef, >> >> yes. I would chnage the packages on SqueakSource directly but in case >> of VMMaker we must pay attention to compatibility of forks etc. > Yes I imagine > >> If I look at ConfigurationOfVMMaker hacks, it is not the right way how >> the interfork project should be done. > > I do not know ConfigurationOfVMMaker > What is the problem? It does contain several methods like: fixVMMakerForPharo (Smalltalk at:#SmartSyntaxPluginCodeGenerator) compile: ' 'ccgValBlock: valString ... Cheers, -- Pavel > > Stef > >> >> -- Pavel >> >> On Wed, Mar 9, 2011 at 10:04 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> Thanks pavel >>> These are the changes you changed to david? so normally we do have to take actions? >>> >>> Stef >>> >>> On Mar 8, 2011, at 11:25 PM, Pavel Krivanek wrote: >>> >>>> I collected the changes from the image. See the attachment. >>>> >>>> To load the simulator in Pharo 1.3 do: >>>> >>>> Gofer new >>>> Â Â squeaksource: 'MetacelloRepository'; >>>> Â Â package: 'ConfigurationOfVMMaker'; >>>> Â Â load. >>>> >>>> (ConfigurationOfVMMaker project version: '1.5') load. >>>> >>>> proceed all deprecation warnings... >>>> load the attached fix. >>>> run the simulator: >>>> >>>> (InterpreterSimulator new openOn: 'cuis.image') test >>>> >>>> A good option is the Juan's small Cuis image (1.9MB with some next >>>> shrinking). The classical mini.image doesn't work on this version of >>>> the interpreter. >>>> >>>> Cheers, >>>> -- Pavel >>>> >>>> >>>> >>>> On Tue, Mar 8, 2011 at 10:47 PM, Pavel Krivanek >>>> <pavel.krivanek(a)gmail.com> wrote: >>>>> Hi, >>>>> >>>>> I tried to make the IneterpreterSimulator working on and with latest >>>>> images. The result is a Pharo image that you can download here: >>>>> >>>>> https://gforge.inria.fr/frs/shownotes.php?release_id=5897 >>>>> >>>>> It is still far from perfect however it can be used for simulations of >>>>> small headless images etc. It would be great if some VM guy will help >>>>> with integration of the changes. >>>>> >>>>> Cheers, >>>>> -- Pavel >>>>> >>>> <InterpreterSimulatorFix.1.cs> >>> >>> >>> >> > > >

March 9, 2011

[Pharo-project] [COTDC] 28 - ImmAbstractPlatform

by laurent laffont

Today: ImmAbstractPlatform 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 Laurent

March 9, 2011

[Pharo-project] New widget

by Benjamin

Hello everyone, I've done a new Morphic widget, that allow to easily switch from a categorized view to a "all elements" view (quite hard to explain, let me give you an example ^^) Gofer new squeaksource: 'SwitchableTreeWidget'; package: 'SwitchableTreeWidget'; load. SwitchableCategoriesTreeExample new openInWorld. If you click on the button or just double click on the tree, you will switch the view :) I wrote that widget to integrate it in a new browser (and if I succeed, to create a new Glamour widget) Thanks in for your feedback :) Ben

March 9, 2011

Re: [Pharo-project] NaturalLanguageTranslator seems useless

by laurent laffont

Maybe it can help: in http://code.google.com/p/pharo/wiki/CommentOfTheDayContest 19 - NaturalLanguageFormTranslator - G.Chambers Provides support for looking up Forms by name for presentation in the UI. Different forms can be registered for a name for different locales allowing images presented in the UI to be localised. Typically used where images contain language dependent text. E.g. buttonForm := (NaturalLanguageFormTranslator localeID: Locale current localeID) translate: 'submit button' Form translations are added like so: (NaturalLanguageFormTranslator isoLanguage: 'en' isoCountry: 'gb') name: 'submit button' form: aForm Laurent. On Wed, Mar 9, 2011 at 4:44 PM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> wrote: > Check out the Gettext package in the PharoNonCorePackages repository. > > Cheers, > Henry > > On Mar 9, 2011, at 2:42 42PM, Adrien BARREAU wrote: > > Hi, > > I'm reading some code and I saw that: > ^'File' translated. > > It calls NaturalLanguageTranslator translate: aString, which makes ... ^ > aString. > > It seems pretty useless ... > Is there any translation project? > > Adrien. > > >

March 9, 2011

Re: [Pharo-project] [Pharo-users] Problem with Sounds

by Mariano Martinez Peck

On Mon, Mar 7, 2011 at 12:42 AM, Matthew Fotzler <incongruous(a)gmail.com>wrote: > Hello, > > I'm trying to do some development with sound in Pharo. The problem > I'm having is as follows: > > 1) I load up Pharo-1.1.1-dev10.09.1.image and save it as test.image. > 2) I open test.image. > 3) I do "PluckedSound default play". The sound plays. > 4) I "Save and Quit" > 5) I reopen test.image and do "PluckedSound default play" again, but > no sound will play. > > I've only been using Pharo and smalltalk for a few weeks, so I'm still > very new. Is there something I'm doing wrong here? > > Thanks, > Matthew Fotzler > >

March 9, 2011

Re: [Pharo-project] Issue 3800 in pharo: StaticForm can be removed

by pharo＠googlecode.com

Comment #1 on issue 3800 by marianopeck: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 and what are you gonna do with the users of StaticForm ? replace it by Form?

March 9, 2011

[Pharo-project] Issue 3800 in pharo: StaticForm can be removed

by pharo＠googlecode.com

Status: Fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3800 by stephane...(a)gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 An optimization for Nebraska - a StaticForm does not change once created so it may be cached on the remote end. one method. isStatic ^true and not invoked

March 9, 2011