April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 3.0] #30023

by stephane ducasse

April 7, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Esteban Lorenzano

yep, because NOController is a derivative. anyway... NOController needs improvement in his finding algorithm, I'm think :S Esteban On Apr 7, 2013, at 6:20 AM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Sven Van Caekenberghe-2 wrote >> What is the difference between NECController and NOCController ? >> In my image the latter seems to be the default, Sean is using the former. >> Why ? > > I'm using NOCController. The class I referenced is NECPreferences, which > seems to control the settings no matter which controller you use. > > p.s. http://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf describes the > difference in controllers and is a fun read > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

April 7, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by MartinW

Igor Stasenko wrote > i prepared a small tutorial for Athens, which i did today at PharoConf. > But the code i did can be reused by non-participants of conference :) > > Any feedback & help & contributions & improvements is welcome. Very Cool, thank you! -- View this message in context: http://forum.world.st/FYI-Athens-tutorial-tp4679512p4680053.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 7, 2013

Re: [Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by Marten Feldtmann

Alexandre, I had the same feeling, when I had to use it starting around 1997 in our company :-) We are now C#'pers, but it is interesting to see, that one item is remembered by all persons in our team from the Smalltalk-epoche in our company in a friendly way: ENVY. This was the item, which seem to impressed most of the people - especially *after* switching to VS. Marten On 07.04.2013 04:48, Alexandre Bergel wrote: > Hi Marten, > > Frankly speaking, I find Envy way too complicated. I am using it these days and I am really not happy with. If I have to read a book to understand how it works, than there is no way I can teach students on how to use it in a reasonable amount of time. > Configuration Map, Application, edition, scratch version and many more are way too many concepts, in my opinion. > >

April 7, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by Fernando Olivero

NICE ! Excellent tutorial Igor. But i was expecting the tiger at the endâ¦with the song and everything. Fernando On Sun, Apr 7, 2013 at 9:07 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Alex you can use it for real in roassal > For the bootstrap > - connection with TextMorph > - reimplement all the drawOn: method > > stef > > > On Apr 7, 2013, at 5:37 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Really cool! >> Works well! >> >> How far are we from bootstrapping? >> >> Alexandre >> >> >> On Apr 3, 2013, at 8:07 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> Hello, there >>> >>> i prepared a small tutorial for Athens, which i did today at PharoConf. >>> But the code i did can be reused by non-participants of conference :) >>> >>> Here the instructions. >>> >>> Download Pharo 2.0 >>> >>> wget -O - get.pharo.org | bash >>> >>> Run Pharo 2.0 >>> >>> ./pharo-ui Pharo.image >>> >>> In a workspace, evaluate (line after line) >>> >>> Gofer it smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; load. >>> >>> ConfigurationOfAthens loadVersion: '2.0'. >>> >>> Gofer it smalltalkhubUser: 'Pharo' project: 'Athens'; >>> package:'Athens-Tutorial'; load. >>> >>> AthensTutorial new openWithSpec. >>> >>> >>> Took from here >>> https://gist.github.com/SergeStinckwich/44ca34b54cde83b687a3 >>> (just removed duplicates ;) >>> >>> Thanks, Serge for compiling it down ;) >>> >>> Once you load the code and have window open, skip step one (you already did it), >>> and then just follow the steps by pressing doit button changing the >>> code , pressing doit again , going forwards etc .. and playing with >>> it. >>> I put some comments there to serve as a small description/detail. >>> >>> Any feedback & help & contributions & improvements is welcome. >>> >>> P.S. if you get a DNU at step 30, enable Freetype in settings and try again. >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > >

April 7, 2013

[Pharo-project] [update 3.0] #30023

by Marcus Denker

April 7, 2013

Re: [Pharo-project] [Preview] Branch test coverage analysis tool for Pharo 3.0 :)

by ClÃ©ment Bera

I don't know. The main problem is that the AST-interpreter is not fast enough. The best solution for speed would be to improve it as they do in this paper : http://dl.acm.org/citation.cfm?id=2384587 (their ast-interpreter is faster than a byte code interpreter). Another solution would be to execute some method with the vm and other one with the ast-interpreter, but it is quite some work. 2013/4/7 Alexandre Bergel <alexandre.bergel(a)me.com> > Would it be possible to annotate the method with some checkpoints within > the method? This should be fast enough I guess. > > Alexandre > > > On Apr 6, 2013, at 10:35 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > This is exactly that. The tree coverage tool is a subclass of > AST-interpreter, which adding to the interpretation marks the nodes. And > then I use this marking to color the source code. And I use as you said RB > ast. > > > > This is why I implemented it in a few hours, I had already an > AST-interpreter, so I've just created a quick subclass and a spec UI. > > > > > > 2013/4/6 Frank Shearar <frank.shearar(a)gmail.com> > > So if you don't mind me being very loose with terminology, you > > interpret (RB) ASTs, and the act of interpreting marks the nodes in > > these ASTs, which you can then use to colour source? > > > > frank > > > > On 6 April 2013 11:00, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > Actually, it is quite different than Jejak. > > > > > > Implementation wise, Jejak used Opal so I guess it relies on bytecode > > > modification to do its analysis where my tool relies on ast > annotations. > > > > > > This implies some difference in features. It seems that Jejak record > all > > > calls, all values and all assignments in a method (which is byte code > level > > > feature), whereas I record for each ast node if it was interpreted or > not > > > (which is ast level feature). I guess there would be a little > difference in > > > the use cases. > > > > > > > > > 2013/4/6 Frank Shearar <frank.shearar(a)gmail.com> > > >> > > >> On 6 April 2013 07:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > >>> > > >>> Clement built in a couple of hours the following nice branch > > >>> analysecoverage tools :) > > >>> It is dead slow but cool. > > >> > > >> > > >> By "branch coverage tool" do you mean Jejak? > > >> > > >> frank > > >> > > >> > > > > > > > > > > > > -- > > > ClÃ©ment BÃ©ra > > > Mate Virtual Machine Engineer > > > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > > > > > > > > > -- > > ClÃ©ment BÃ©ra > > Mate Virtual Machine Engineer > > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

April 7, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by stephane ducasse

Alex you can use it for real in roassal For the bootstrap - connection with TextMorph - reimplement all the drawOn: method stef On Apr 7, 2013, at 5:37 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Really cool! > Works well! > > How far are we from bootstrapping? > > Alexandre > > > On Apr 3, 2013, at 8:07 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> Hello, there >> >> i prepared a small tutorial for Athens, which i did today at PharoConf. >> But the code i did can be reused by non-participants of conference :) >> >> Here the instructions. >> >> Download Pharo 2.0 >> >> wget -O - get.pharo.org | bash >> >> Run Pharo 2.0 >> >> ./pharo-ui Pharo.image >> >> In a workspace, evaluate (line after line) >> >> Gofer it smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; load. >> >> ConfigurationOfAthens loadVersion: '2.0'. >> >> Gofer it smalltalkhubUser: 'Pharo' project: 'Athens'; >> package:'Athens-Tutorial'; load. >> >> AthensTutorial new openWithSpec. >> >> >> Took from here >> https://gist.github.com/SergeStinckwich/44ca34b54cde83b687a3 >> (just removed duplicates ;) >> >> Thanks, Serge for compiling it down ;) >> >> Once you load the code and have window open, skip step one (you already did it), >> and then just follow the steps by pressing doit button changing the >> code , pressing doit again , going forwards etc .. and playing with >> it. >> I put some comments there to serve as a small description/detail. >> >> Any feedback & help & contributions & improvements is welcome. >> >> P.S. if you get a DNU at step 30, enable Freetype in settings and try again. >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 7, 2013

[Pharo-project] Debugger use case - variable reference from Glamour Inspector

by Ben Coman

Not sure what is possible with the work on the new debugger, but here is an idea / use case of mine... In Pharo 1.4, from the debugger I Explore (ie using Glamourous Inspector) a temporary variable (debugvar1) that is collection. After drilling in a little bit to a particular model object, I want to call a method (#someCalcWith:) on that object that requires a second temporary variable (debugvar2) from the debugger. At the moment from the debugger I resort to (Smalltalk at: #mydebug put: debugvar2) and then in GI going (self someCalcWith: (Smalltalk at: #mydebug)). It would be nice if an Explore from a debugger took with it the current context so that those variables could be referred to by name from the GI. As a stretch, perhaps even if the debugger moves its position on the stack, then the context available to the GI would change to match. cheers -ben

April 7, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > What is the difference between NECController and NOCController ? > In my image the latter seems to be the default, Sean is using the former. > Why ? I'm using NOCController. The class I referenced is NECPreferences, which seems to control the settings no matter which controller you use. p.s. http://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf describes the difference in controllers and is a fun read ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 7, 2013