July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] State of Sound in Morph

by Hilaire Fernandes

Thanks guys for your feedback, I will make the necessary changes in the package. I have also applied the changes to sound from the Squeak friends. By the way, I wonder if the sound package should not be cut in two package, one related to sound synthesis and the other to morph stuff. Hilaire >> clone was a shallow copy and we replaced it by shallowCopy, copy >> copy >> >> ^ self shallowCopy postCopy >> >> >> We removed clone from pharo because tired to have three times the same half way done. >> because only some parts of the system used clone and other shallow > > IE, the correct action would be to replace #clone calls with #shallowCopy (alternatively copy, if that makes more sense) calls in the PharoSound package?

July 23, 2010

Re: [Pharo-project] Another RB engine change

by Lukas Renggli

I fixed that and about 30 other occurrences of the same problem. Name: Refactoring-Core-lr.147 Author: lr Time: 23 July 2010, 8:14:01 am UUID: 8e608df4-579d-4a3d-a589-0eb90109275e Ancestors: Refactoring-Core-lr.146 - fixed numerous occurrences where the old 'Smalltalk' was used Thank you for pointing out. Lukas On 23 July 2010 00:01, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: > Hi Lukas, here is another change in the RB engine package. > > RBClass>>realName: aSymbol > Â Â Â Â self realClass: (Smalltalk at: aSymbol) > > Â Â Â Â => > Â Â Â Â Â Â Â Â self realClass: (Smalltalk globals at: aSymbol) > > Fernando > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 23, 2010

Re: [Pharo-project] About validating the result of RBParser >> parseMethod:

by Lukas Renggli

You can use #parseMethod:onError: to check for syntactical errors. Semantical errors are harder to detect, some of them (e.g. undeclared variables) you can find using AST-Semantics. Lukas On 23 July 2010 00:35, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: > I have a question about validating a methodNode, suppose we have the following: > > parsedNode := Â RBParser parseMethod: 'test ^ self add: anUnbindedVariable'. > > Is there a way of checking the health/validity of the parsedNode? > > I couldn't find any behavior in RBMethodNode or related classes. > > Lukas, do you have an idea is i could run any Lint rule? > > My idea is to provide a method editor morph, that prevents from accepting invalid sources, and informs the user any problems detected with the edited code. > > Thanks, > Fernando > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 23, 2010

Re: [Pharo-project] Invalid utf8 input detected: now what?

by Yanni Chiu

Schwab,Wilhelm K wrote: > > I got an error (on Ubuntu 9.10) trying open an old text file that I > created on Windows some time ago. The encoding (if gedit's save-as > dialog can be trusted??) is Western ISO-8859-15; resaving as utf8 > lets me read it. You could try viewing the original file in a web browser. Try different encodings until the stuff looks right. Then you might have a better idea of whether you really have a file in ISO-8859-15. You could also view your converted UTF-8 file in a web browser too, and compare the two renderings. If this checks out, then maybe it's a Pharo issue.

July 23, 2010

[Pharo-project] Invalid utf8 input detected: now what?

by Schwab,Wilhelm K

Hello all, I got an error (on Ubuntu 9.10) trying open an old text file that I created on Windows some time ago. The encoding (if gedit's save-as dialog can be trusted??) is Western ISO-8859-15; resaving as utf8 lets me read it. So, is Pharo working by design? Did I do the correct/only thing needed to read the file? What should I be asking? Is there anything I can do to turn this into a useful test/debugging example? Bill

July 23, 2010

Re: [Pharo-project] Literal array with evaluated value of stmts, vars etc..

by Eliot Miranda

2010/7/22 Henrik Johansen <henrik.s.johansen(a)veloxit.no> > > On Jul 22, 2010, at 7:39 43PM, Eliot Miranda wrote: > > > > 2010/7/22 Sudhakar Krishnamachari <skrishnamachari(a)gmail.com> > >> And of course the extensibility it gives: >> >> [ 1->'asd'. 2->'asd'. 3->'dsd' ] asDictionary >> > > I think Travis Griggs' once is much much nicer: > > [{ 1->'asd'. 2->'asd'. 3->'dsd' } asDictionary] once > > when once is sent to a BlockClosure it becomes itself into a > CachedBlockClosure that remembers and answers the evaluated value. > You could add selectors to this such as > onceEachSession - destroy the cached value on image startup > > It doesn't require any special compiler machinery (unlike ##(...)) and so > there are no problems with browsing references or senders within > compile-time evaluated forms. It is easily extensible to different > life-times. It is portable. > > my 2Â¢ > > Eliot > > > I like once as well, after using it in VisualWorks. > For my tastes, it's uses just the right amount of magickery to both be able > to easily understand how it works, and provide useful functionality. > > F.ex. I wrote a tool where I tagged (time-expensive) methods I suspected of > being invariants during a large analysis, the tool then ran those methods > wrapped in a once block, and told me which did not affect the end results. > Much faster than a manual verification of whether they were really > invariants, and provided an ok speedup for the amount of (brain) effort > required :D > > Only problem I've encountered in VW (7.7 at least), is the debugger raising > an mnu if you try to step into the once call of a CachedBlockClosure. > In Squeak 4.1 it seems fine :) I really like Assets. The whole framework is small, flexible, useful and easy to understand. best Eliot > > Cheers, > Henry > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 22, 2010

Re: [Pharo-project] State of Sound in Morph

by Henrik Johansen

On Jul 22, 2010, at 11:51 30PM, StÃ©phane Ducasse wrote: > > On Jul 22, 2010, at 10:14 PM, Hilaire Fernandes wrote: > >> Le 22/07/2010 21:11, Hilaire Fernandes a Ã©crit : >>> Le 22/07/2010 20:53, StÃ©phane Ducasse a Ã©crit : >>> >>>>> >>>>> Of course I took your latest commit. Do this latest commit include the >>>>> patches Stephane mentioned? >>>> >>>> no I guess not. >>>> Hilaire if you can have a look at the bugtracker and harvest the fixes into sound >>>> it would be great. >>> >>> Sure >> >> The proposed pathes are not related to the problem. >> I replace the clone by a copy, it helps but I don't know the eventual >> side effects. > > clone was a shallow copy and we replaced it by shallowCopy, copy > copy > > ^ self shallowCopy postCopy > > > We removed clone from pharo because tired to have three times the same half way done. > because only some parts of the system used clone and other shallow IE, the correct action would be to replace #clone calls with #shallowCopy (alternatively copy, if that makes more sense) calls in the PharoSound package? Cheers, Henry

July 22, 2010

Re: [Pharo-project] Literal array with evaluated value of stmts, vars etc..

by Henrik Johansen

On Jul 22, 2010, at 7:39 43PM, Eliot Miranda wrote: > > > 2010/7/22 Sudhakar Krishnamachari <skrishnamachari(a)gmail.com> > And of course the extensibility it gives: > > [ 1->'asd'. 2->'asd'. 3->'dsd' ] asDictionary > > I think Travis Griggs' once is much much nicer: > > [{ 1->'asd'. 2->'asd'. 3->'dsd' } asDictionary] once > > when once is sent to a BlockClosure it becomes itself into a CachedBlockClosure that remembers and answers the evaluated value. > You could add selectors to this such as > onceEachSession - destroy the cached value on image startup > > It doesn't require any special compiler machinery (unlike ##(...)) and so there are no problems with browsing references or senders within compile-time evaluated forms. It is easily extensible to different life-times. It is portable. > > my 2Â¢ > > Eliot I like once as well, after using it in VisualWorks. For my tastes, it's uses just the right amount of magickery to both be able to easily understand how it works, and provide useful functionality. F.ex. I wrote a tool where I tagged (time-expensive) methods I suspected of being invariants during a large analysis, the tool then ran those methods wrapped in a once block, and told me which did not affect the end results. Much faster than a manual verification of whether they were really invariants, and provided an ok speedup for the amount of (brain) effort required :D Only problem I've encountered in VW (7.7 at least), is the debugger raising an mnu if you try to step into the once call of a CachedBlockClosure. Cheers, Henry

July 22, 2010

[Pharo-project] About validating the result of RBParser >> parseMethod:

by Fernando olivero

I have a question about validating a methodNode, suppose we have the following: parsedNode := RBParser parseMethod: 'test ^ self add: anUnbindedVariable'. Is there a way of checking the health/validity of the parsedNode? I couldn't find any behavior in RBMethodNode or related classes. Lukas, do you have an idea is i could run any Lint rule? My idea is to provide a method editor morph, that prevents from accepting invalid sources, and informs the user any problems detected with the edited code. Thanks, Fernando

July 22, 2010

Re: [Pharo-project] Mac like editing?

by StÃ©phane Ducasse

yes one idea is to have a look at keybinding or keymapper pick up the ones that works and has tests and incrementally work there. Sean gave me squeak images with these package loaded but I got no time to have a look. > Right now they are hardcoded here > > TextEditor class, category: keyboard shortcut tables > > For example: > > TextEditor class>> initializeBasicCmdKeyShortcuts > > Wouldn't be hard to plug a customized mapping. And then do the same in > > TextEditor>>dispatchOn: aKeyboardEvent > > You could make this changes, and later test them easily using NewTextMorph. > > Fernando > > On Jul 22, 2010, at 8:59 PM, Max Leske wrote: > >> I checked Squeak 4.1 basic image (Damien's server didn't let me download the SqueakDev image). There are no preferences in the preferences browser for editing shortcuts. The only shortcut I could verify was cmd + -> and cmd + <- for skipping words (I have that in my list as alt + -> and alt + <-). There seem to be a couple of other nice shortcuts (e.g. advancing to the next argument when typing a multi argument message) but I's prefer the basic shortcuts would work... >> >> There is an Editor class with two sub classes that has replaced a former implementation (apparently TextMorphEditor). I couldn't figure out where the shortcuts are actually defined though. >> >> Max >> >> On 22.07.2010, at 20:14, StÃ©phane Ducasse wrote: >> >>> I guess that they did that in squeak can you check? >>> >>> On Jul 22, 2010, at 8:10 PM, Max Leske wrote: >>> >>>> No I haven't. I'll take a look at it later on. >>>> Are you planning to replace Paragraph with Editor? >>>> >>>> Max >>>> >>>> >>>> On 22.07.2010, at 20:05, StÃ©phane Ducasse wrote: >>>> >>>>> What I want is a real way to define, plug a shortcut table. >>>>> Max did you check the new Editor class. >>>>> >>>>> Stef >>>>> >>>>> >>>>>> Hi everyone. >>>>>> >>>>>> I have no idea what the status is on the editor in pharo and if there are any plans to do something to / with it. If there's some resource, could you point me to it? >>>>>> In the meantime I thought I'd share my impressions with you; doesn't hurt at least. >>>>>> >>>>>> Since I started developing in Pharo I've struggled with the editor, in particular with the fact that I need to use the mouse a lot to position the cursor which, as all of you know, makes development quite a bit slower. >>>>>> Before I came to Pharo I used to develop in Eclipse and Eclipse supports all shortcuts used inside OS X (and if not you can change the shortcut settings). My favorite shortcuts: >>>>>> â¢ cmd + -> : go to end of line >>>>>> â¢ cmd + <- : go to beginning of line >>>>>> â¢ alt + -> : go to end of the current word >>>>>> â¢ alt + -> : go to beginning of current word >>>>>> â¢ alt + arrow up : switch the line above with the current line (current line has line number -1, line above has line number +1) >>>>>> â¢ alt + arrow down : switch the line below with the current line >>>>>> â¢ cmd + l : delete line (I know this shortcut is used to cancel changes at the moment. Still, I haven't found a shortcut yet that deletes a single line) >>>>>> >>>>>> I'd LOVE to see this in Pharo, or at least be able to configure the shortcuts myself. I think, being able to change the shortcuts is important anyway because each developer has an own style. >>>>>> I'd try to come up with a solution myself but I just don't have the time at the moment. >>>>>> >>>>>> Thanks for listening to my yapping :) >>>>>> >>>>>> Max >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2010