- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo 1.4

by Schwab,Wilhelm K

Exactly. I am the first to disable both, but there is nothing personal in it. Well, it *IS* personal, but simply my personal preference to type vs. having lists block my view of the code. I think it is great that the tools exist and provide good service to those who want them. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Francisco Ortiz PeÃ±aloza [patchinko(a)gmail.com] Sent: Sunday, August 28, 2011 10:57 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pharo 1.4 In fact Pharo 1.3 uses OCompletion built on top of ECompletion[1] and RoelTyper. I just looked at 1.4 and it looks simpler but OCompletion works great for me! I think is a great tool but it's not well integrated (cause there's been a lot of changes, new editors and yada yada yada) IMHO it does't hurt to have them (you can disable it and use ECompletion instead or you can even disable both tools) and makes Pharo more friendly to newcomers from others IDEs. Cheers, Francisco [1] http://uncomplex.net/ecompletion/ On Sun, Aug 28, 2011 at 7:04 PM, Frank Shearar <frank.shearar(a)gmail.com<mailto:frank.shearar@gmail.com>> wrote: On 28 August 2011 21:18, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > Damien Cassou wrote: >> >> > > Cool! That would make a big difference. Where are they/what are they called? I know of Roel Wuyts' RoelTyper (http://decomp.ulb.ac.be/roelwuyts/smalltalk/roeltyper/) and Lex Spoon's Chuck (http://www.lexspoon.org/ti/) Matt Might has also written about k-CFA (Control Flow Analysis) for inferring types in a dynamic language (Scheme, in particular) - http://matt.might.net/articles/implementation-of-kcfa-and-0cfa/ - which we might be able to apply to Smalltalk. frank > Sean > > -- > View this message in context: http://forum.world.st/Pharo-1-4-tp3759684p3774973.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Aug. 29, 2011

Re: [Pharo-project] Pharo 1.4

by Francisco Ortiz PeÃ±aloza

In fact Pharo 1.3 uses OCompletion built on top of ECompletion[1] and RoelTyper. I just looked at 1.4 and it looks simpler but OCompletion works great for me! I think is a great tool but it's not well integrated (cause there's been a lot of changes, new editors and yada yada yada) IMHO it does't hurt to have them (you can disable it and use ECompletion instead or you can even disable both tools) and makes Pharo more friendly to newcomers from others IDEs. Cheers, Francisco [1] http://uncomplex.net/ecompletion/ On Sun, Aug 28, 2011 at 7:04 PM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 28 August 2011 21:18, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > > Damien Cassou wrote: > >> > >> > > > > Cool! That would make a big difference. Where are they/what are they > called? > > I know of Roel Wuyts' RoelTyper > (http://decomp.ulb.ac.be/roelwuyts/smalltalk/roeltyper/) and Lex > Spoon's Chuck (http://www.lexspoon.org/ti/) Matt Might has also > written about k-CFA (Control Flow Analysis) for inferring types in a > dynamic language (Scheme, in particular) - > http://matt.might.net/articles/implementation-of-kcfa-and-0cfa/ - > which we might be able to apply to Smalltalk. > > frank > > > Sean > > > > -- > > View this message in context: > http://forum.world.st/Pharo-1-4-tp3759684p3774973.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > >

Aug. 29, 2011

Re: [Pharo-project] [ANN] glamorous inspector

by Tudor Girba

Hi, There are a couple of improvements related to the GT Inspector: - A morph has a dedicated submorphs tab with which we can inspect the tree of morphs (see attached picture) - A parse tree has a dedicated view that provides a tree of RB nodes and previews the information as a selection on the method source code (see the attached picture) - On the top right there is a refresh button to update the inspector (it does not happen automatically) - Damien Cassou fixed the "do it" support in the evaluator so now you can use the default keys as in the workspace - Some more relevant menu items for manipulation Cheers, Doru On 24 Aug 2011, at 11:12, Tudor Girba wrote: > The GT Inspector is now available by default in the Moose image (CMD+Shift+i). > > It seems to work quite well. > > Cheers, > Doru > > > On 22 Aug 2011, at 22:59, StÃ©phane Ducasse wrote: > >> Thanks doru :) >> >> Stef >> >> On Aug 22, 2011, at 7:59 PM, Tudor Girba wrote: >> >>> Hi, >>> >>> I am happy to announce the first release of the Glamorous Inspector, a new browser for inspecting objects based on Glamour. >>> >>> More information, including a demo and screenshots, can be found here: >>> http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk >>> >>> To download it follow the instructions from: >>> http://www.moosetechnology.org/tools/glamoroustoolkit >>> >>> You can use it by: >>> 1. "GTInspector openOn: someObject", or >>> 2. "GTInspector registerToolsOn: Smalltalk tools" and then use CMD+I (explore) >>> >>> Please let your opinion be heard :) >>> >>> Cheers, >>> Doru >>> >>> p.s. Have fun at ESUG :) >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every successful trip needs a suitable vehicle." >>> >>> >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > -- www.tudorgirba.com "Some battles are better lost than fought."

Aug. 28, 2011

Re: [Pharo-project] Pharo 1.4

by Frank Shearar

On 28 August 2011 21:18, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Damien Cassou wrote: >> >> > > Cool! That would make a big difference. Where are they/what are they called? I know of Roel Wuyts' RoelTyper (http://decomp.ulb.ac.be/roelwuyts/smalltalk/roeltyper/) and Lex Spoon's Chuck (http://www.lexspoon.org/ti/) Matt Might has also written about k-CFA (Control Flow Analysis) for inferring types in a dynamic language (Scheme, in particular) - http://matt.might.net/articles/implementation-of-kcfa-and-0cfa/ - which we might be able to apply to Smalltalk. frank > Sean > > -- > View this message in context: http://forum.world.st/Pharo-1-4-tp3759684p3774973.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Aug. 28, 2011

Re: [Pharo-project] Pharo 1.4

by Sean P. DeNigris

Damien Cassou wrote: > > Cool! That would make a big difference. Where are they/what are they called? Sean -- View this message in context: http://forum.world.st/Pharo-1-4-tp3759684p3774973.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 28, 2011

Re: [Pharo-project] Pharo 1.4

by Damien Cassou

On Sun, Aug 28, 2011 at 9:41 PM, nullPointer <epicfan(a)gmail.com> wrote: > I donÂ´t understand the behavior of any completion mechanism than works on > Pharo/Squeak. When I type a literal, for example "1000" and later type "fac" > appears always a great number of messages from system than nothing have > relation with the object where we doing message call. IÂ´ll wait for example > #factorial message and other fews. I suppose that donÂ´t easy solve in a > language with donÂ´t strong type, but another Smalltalks like Dolphin seems > work very good in that. > > Thanks for read my poor english :) There are existing tools to infer types but they need to be integrated. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 28, 2011

Re: [Pharo-project] Pharo 1.4

by nullPointer

I donÂ´t understand the behavior of any completion mechanism than works on Pharo/Squeak. When I type a literal, for example "1000" and later type "fac" appears always a great number of messages from system than nothing have relation with the object where we doing message call. IÂ´ll wait for example #factorial message and other fews. I suppose that donÂ´t easy solve in a language with donÂ´t strong type, but another Smalltalks like Dolphin seems work very good in that. Thanks for read my poor english :) -- View this message in context: http://forum.world.st/Pharo-1-4-tp3759684p3774928.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 28, 2011

Re: [Pharo-project] Omnibrowser in 1.4

by Jan van de Sandt

I think Lukas means Nautilus. [1] http://www.squeaksource.com/Nautilus.html On Sun, Aug 28, 2011 at 8:46 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > 2011/8/28 Lukas Renggli <renggli(a)gmail.com>: > > There are currently no plans to make OB work in upcoming Pharo > > versions; Pharo 1.4 is supposed to have its own much better browser > > framework. > > > > Which framework? > >

Aug. 28, 2011

Re: [Pharo-project] Omnibrowser in 1.4

by HernÃ¡n Morales Durand

2011/8/28 Lukas Renggli <renggli(a)gmail.com>: > There are currently no plans to make OB work in upcoming Pharo > versions; Pharo 1.4 is supposed to have its own much better browser > framework. > Which framework?

Aug. 28, 2011

Re: [Pharo-project] Halt

by Marcus Denker

On Aug 28, 2011, at 8:10 PM, Lukas Renggli wrote: > We have a class Halt and the class-side is empty. This seems to be the > right place to hold all the code in the protocols #debugging and > #debuggin-haltonce of Object. With a few renames we could get a really > nice DSL: > > Halt now. > Halt if: a = 2. > Halt once. > Nice! I want that. This would even allow for making the #haltIf: less overloaded and provide a explicit control flow based halt with something like this: Halt selector: #DoIt. or maybe better: Halt ifCalledFrom: #testMyWonderfulBuggyTest Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 28, 2011