- Pharo-dev - lists.pharo.org

Re: [Pharo-project] the glamorous toolkit project

by Tudor Girba

Hi Mariano, Thanks for the suggestions. As I said, you are welcome to participate. It does not have to be much. You can just spend a bit of time to learn Glamour and then play 15 minutes per day :). Cheers, Doru On 14 Mar 2011, at 19:34, Mariano Martinez Peck wrote: > Hi Tudor? do you want to succeed? Do a kind of OB but with multiple selection :) > I would like to remove, for example, several methods together... > > cheers > > mariano > > On Sun, Mar 13, 2011 at 10:45 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Thanks, Esteban. > > Jorge did a nice job at improving it to handle special objects. There are still a couple of situations left, but it is already reliable. > > Cheers, > Doru > > > On 13 Mar 2011, at 19:33, Esteban Lorenzano wrote: > > > wow.... GTInspector is really great :) > > gamorous tools are becoming very interesting... keep going that way! > > > > I do believe in the near future GT can replace OB as our default IDE, if we continue improving like this :) > > > > cheers, > > Esteban > > > > El 13/03/2011, a las 10:34a.m., Marcus Denker escribiÃ³: > > > >> > >> On Mar 13, 2011, at 2:05 PM, Tudor Girba wrote: > >> > >>> I think that this is a good idea. Having the Core tools better is definitely a good thing. > >>> > >> > >> One thing to keep in mind is that we need (ass soon as possible) to have *one* set > >> of tools... with OB we have seen that we have just not the manpower to in parallel > >> maintain two sets of tools (Core vs. Dev). > >> > >> The notion of "Core Tools" is broken. Whichever tools we do in the future need > >> to *replace* the old tools. > >> > >> Marcus > >> > >> > >> -- > >> Marcus Denker -- http://www.marcusdenker.de > >> INRIA Lille -- Nord Europe. Team RMoD. > >> > >> > > > > > > -- > www.tudorgirba.com > > "Not knowing how to do something is not an argument for how it cannot be done." > > > -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

March 14, 2011

Re: [Pharo-project] PBenchmark as a general framework for benchmarking in Smalltalk (commit access)

by Alexandre Bergel

You can check the class MondrianHealth2 that belongs to the package Mondrian-Tests of http://www.squeaksource.com/Mondrian.html The class contains many methods having a name that begins with 'metric'. Some students worked on a kind of Hudson that exploit these information. You can have a look at it: http://kimen.dcc.uchile.cl:8008/VerMon01/faces/project_details.xhtml?id=1 It would be cool to have a standard for this. As we have for SUnit. I think that what I did goes in the right direction, but the code is not as clean as it should. It would be cool to have a report generation, which could be .pdf, sending emails, ... Cheers, Alexandre On 14 Mar 2011, at 16:23, Stefan Marr wrote: > Hi Alexandre: > > > On 14 Mar 2011, at 18:10, Alexandre Bergel wrote: > >>> Since the general idea is to write benchmarks like unit tests, how about 'SMark'/'SBench' instead of 'SUnit'? >> >> >> I like the idea. Actually, this is what I have done with HealthReportProducer. A benchmark is created by subclassing it and defining #metric* methods. > Ehm, could you elaborate? Do you want me to have a look at something and steal some code/ideas? If so, I would need a more elaborate hint than just a name. > I googled for it, and there seems to be some reference in a metachello project, and interestingly google indexed already this email... > > Thanks > Stefan > > > > >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 14, 2011

Re: [Pharo-project] PBenchmark as a general framework for benchmarking in Smalltalk (commit access)

by Stefan Marr

Hi Alexandre: On 14 Mar 2011, at 18:10, Alexandre Bergel wrote: >> Since the general idea is to write benchmarks like unit tests, how about 'SMark'/'SBench' instead of 'SUnit'? > > > I like the idea. Actually, this is what I have done with HealthReportProducer. A benchmark is created by subclassing it and defining #metric* methods. Ehm, could you elaborate? Do you want me to have a look at something and steal some code/ideas? If so, I would need a more elaborate hint than just a name. I googled for it, and there seems to be some reference in a metachello project, and interestingly google indexed already this email... Thanks Stefan > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

March 14, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Comment #12 on issue 3581 by snoob...(a)yahoo.ie: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 Ok I see now. Then is it safe to just do ObjectAsMethodWrapper>>flushCache self selector flushCache.

March 14, 2011

[Pharo-project] There is life in Mars. A post explaining current status

by Esteban Lorenzano

Hi all, Several months passed without Mars news, and I'm trying to correct that (it is "some kind" a compromise to publish some news at least once a month, starting from now... so people can see our advances). I prepared a very long post explaining last months and next steps we want to make (to long to add it as a simple mail to the list). If you are interested, you can read it here: http://smallworks.com.ar/blogs/The+Martian+Chronicles/2011-03-14-The-fly-to… Cheers, Esteban

March 14, 2011

Re: [Pharo-project] Issue 3815 in pharo: Filing in Class comments raises an error

by pharo＠googlecode.com

Comment #14 on issue 3815 by ryd...(a)gmail.com: Filing in Class comments raises an error http://code.google.com/p/pharo/issues/detail?id=3815 So, it's ok to leave stuff we broke between versions broken if we intend to replace it with something better in some future version? I don't see the logic in that.

March 14, 2011

Re: [Pharo-project] Issue 3214 in pharo: better Stack implementation

by pharo＠googlecode.com

Comment #3 on issue 3214 by renggli: better Stack implementation http://code.google.com/p/pharo/issues/detail?id=3214 In 99% of the cases OrderedCollection is probably the best choice.

March 14, 2011

[Pharo-project] Jtalk, a Smalltalk for web developers

by Nicolas Petton

Hi, I would like to share a project I'm working on on my spare time: Jtalk Smalltalk. http://nicolaspetton.github.com/jtalk https://github.com/NicolasPetton/jtalk Jtalk is an implementation of the Smalltalk language that compiles into JavaScript. Some features: - it is written in itself (including the parser/compiler) - it is self-contained - it compiles into efficient JS code - it uses the Squeak chunk format - Pharo is considered as the reference implementation I think Jtalk can be compared to CoffeeScript[1], Objective-J[2] or Clamato[3], from which it reuses some ideas and code. Jtalk includes an IDE with a class browser, transcript and workspace, an HTML canvas similar to Seaside and a jQuery binding. It is still a young piece of code, and some important features are still missing/incomplete. Cheers, Nicolas Petton [1] http://jashkenas.github.com/coffee-script/ [2] http://cappuccino.org/ [3] http://clamato.net

March 14, 2011

Re: [Pharo-project] the glamorous toolkit project

by Mariano Martinez Peck

Hi Tudor? do you want to succeed? Do a kind of OB but with multiple selection :) I would like to remove, for example, several methods together... cheers mariano On Sun, Mar 13, 2011 at 10:45 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Thanks, Esteban. > > Jorge did a nice job at improving it to handle special objects. There are > still a couple of situations left, but it is already reliable. > > Cheers, > Doru > > > On 13 Mar 2011, at 19:33, Esteban Lorenzano wrote: > > > wow.... GTInspector is really great :) > > gamorous tools are becoming very interesting... keep going that way! > > > > I do believe in the near future GT can replace OB as our default IDE, if > we continue improving like this :) > > > > cheers, > > Esteban > > > > El 13/03/2011, a las 10:34a.m., Marcus Denker escribiÃ³: > > > >> > >> On Mar 13, 2011, at 2:05 PM, Tudor Girba wrote: > >> > >>> I think that this is a good idea. Having the Core tools better is > definitely a good thing. > >>> > >> > >> One thing to keep in mind is that we need (ass soon as possible) to have > *one* set > >> of tools... with OB we have seen that we have just not the manpower to > in parallel > >> maintain two sets of tools (Core vs. Dev). > >> > >> The notion of "Core Tools" is broken. Whichever tools we do in the > future need > >> to *replace* the old tools. > >> > >> Marcus > >> > >> > >> -- > >> Marcus Denker -- http://www.marcusdenker.de > >> INRIA Lille -- Nord Europe. Team RMoD. > >> > >> > > > > > > -- > www.tudorgirba.com > > "Not knowing how to do something is not an argument for how it cannot be > done." > > >

March 14, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Comment #11 on issue 3581 by marianopeck: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 The problem is that if you use addSelector:withMethod then you will need to implement a lot of messages, like #methodClass: , #selector: , #pragmas, etc. In summary, a lot of methods from CompiledMethod. Notice that ObjectAsMethodWrapper is subclass of Object, not CompiledMethod. Cheers Mariano

March 14, 2011