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

Re: [Pharo-project] Autotest / TDD + screencast

by laurent laffont

On Mon, Jun 7, 2010 at 3:28 PM, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > Hi Laurent, > > Cool! I like the idea. > > Now, what happens if there are too many tests? > One solution would be to ask the user if (s)he wants to run all tests if > there are more than say 300, though I feel that this will quickly become > painful. > For fun, try to change a method named size :).... and yes, we should limit the number of tests run. I want to add heuristics to run only tests of the same package, disable long tests, .... The repository is read / write, feel free to play and commit. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > Noury > > On 4 juin 2010, at 23:12, laurent laffont wrote: > > > Hi, > > > > Here's a first usable version of Autotest (automatic test runner, > inspired by Ruby's ZentTest autotest). > > > > The goal is to have instant feedback on the code you > > > > The screencast to see it in action: > http://lolgzs.free.fr/pharo/autotest_1.mpeg > > > > To load it: > > > > Gofer new > > squeaksource: 'Autotest'; > > package: 'Autotest'; > > load > > > > Comments are welcome as I have to rewrite it better :) Repository is read > / write for those who wants to contribute. > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > _______________________________________________ > > 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 >

June 7, 2010

Re: [Pharo-project] [JOB] We are Looking for a Pharo Engineer

by Niko Schwarz

Is there a website with this text that I can link to? Niko On Mon, Jun 7, 2010 at 3:48 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > INRIA RMOD is looking for a full-time engineer for helping with Pharo development. As researchers, we need a really great > system to explore new ideas with. The job of the engineer is to help us by improving the infrastructure we use for our work. > > What this of course means is that it's kind of a cool job: work in a research lab, but no paper writing, no teaching, > no administration. In addition: > > Â Â - live in France (one hour from Paris, 1h20 from London, 35 min from Brussels) > Â Â - try a lot of good beers (our office is just 10km from the border to Belgium) > Â Â - french food > Â Â - code all the day in Smalltalk and a bit of C > > Apparently from what the DHR services told us, the salary will depend on years of expertise and diplomas. > We can think that 2700 Euros (before final taxes) should be a good working number for a candidate of the experience > we are looking for. In France the employer pays already social security and pension. > So the salary already includes lots (and lots) of deductions compared to e.g. a german brutto salary. > > Lille is an active city but not expensive (lot of students...), centrally located with good connections > by train to everywhere (including CDG and Brussels airports). > > The job will to continue making Pharo better > Â Â Â - better tools > Â Â Â - better network support > Â Â Â - better compiler infrastructure > Â Â Â - improve the VM > Â Â Â - help with day-to-day bug fixing and constant improvement > > Therefore we are looking for a candidate with some years of Smalltalk (possible Pharo/Squeak) background. > > Duration: 30 months > Starting date: October 2010 > Location: Lille (no remote job possible) > Official Job Description and Application via: Â http://bit.ly/dyhdba > Deadline: 15 July 2010 > > More about > Â Â Â Â INRIA Lille: http://www.inria.fr/lille/ > Â Â Â Â INRIA in General: http://www.inria.fr > Â Â Â Â Engineers at INRIA: http://www.inria.fr/travailler/metiers/accompagnement/dev_applications.en.h… > Â Â Â Â Lille: http://en.wikipedia.org/wiki/Lille > Â Â Â Â Â Â Â Â Â http://www.mairie-lille.fr/en > Â Â Â Â Â Â Â Â Â http://wikitravel.org/en/Lille > > Do not hesitate to contact us for more information. > > Stef/Marcus > > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

June 7, 2010

[Pharo-project] [JOB] We are Looking for a Pharo Engineer

by Marcus Denker

Hello, INRIA RMOD is looking for a full-time engineer for helping with Pharo development. As researchers, we need a really great system to explore new ideas with. The job of the engineer is to help us by improving the infrastructure we use for our work. What this of course means is that it's kind of a cool job: work in a research lab, but no paper writing, no teaching, no administration. In addition: - live in France (one hour from Paris, 1h20 from London, 35 min from Brussels) - try a lot of good beers (our office is just 10km from the border to Belgium) - french food - code all the day in Smalltalk and a bit of C Apparently from what the DHR services told us, the salary will depend on years of expertise and diplomas. We can think that 2700 Euros (before final taxes) should be a good working number for a candidate of the experience we are looking for. In France the employer pays already social security and pension. So the salary already includes lots (and lots) of deductions compared to e.g. a german brutto salary. Lille is an active city but not expensive (lot of students...), centrally located with good connections by train to everywhere (including CDG and Brussels airports). The job will to continue making Pharo better - better tools - better network support - better compiler infrastructure - improve the VM - help with day-to-day bug fixing and constant improvement Therefore we are looking for a candidate with some years of Smalltalk (possible Pharo/Squeak) background. Duration: 30 months Starting date: October 2010 Location: Lille (no remote job possible) Official Job Description and Application via: http://bit.ly/dyhdba Deadline: 15 July 2010 More about INRIA Lille: http://www.inria.fr/lille/ INRIA in General: http://www.inria.fr Engineers at INRIA: http://www.inria.fr/travailler/metiers/accompagnement/dev_applications.en.h… Lille: http://en.wikipedia.org/wiki/Lille http://www.mairie-lille.fr/en http://wikitravel.org/en/Lille Do not hesitate to contact us for more information. Stef/Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 7, 2010

Re: [Pharo-project] A more concise array access (using negative indices)

by Damien Pollet

On Mon, Jun 7, 2010 at 15:23, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Â Â Â Â copyFrom: 1 to: does not convey that you should pass the second argument starting reverse. Of course, since it's the sign that does thatâ¦ > Â Â Â Â copyFrom: 3 toFromEnd: -2 then, why -2 if it's explicitly from the end ??? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

June 7, 2010

Re: [Pharo-project] A more concise array access (using negative indices)

by Niko Schwarz

On Mon, Jun 7, 2010 at 3:23 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > yes this one looks good. > but > > Â Â Â Â copyFrom: 1 to: does not convey that you should pass the second argument starting reverse. Well, in ruby it's a general convention that negative indices start counting from the right. A reasonable implementation would change all sequenceable collections such that they accept negative indices. In Phexample syntax: ((1 to: 5) at: -2) should = 4. The alternative is to always have two accessors, then of course non-negative: (1 to: 5) atFromEnd: 2) should = 4. and: ('hello' from: 2 toFromEnd: 2) should = 'ell' I clearly prefer the negative indices. Things you do all the time can be much shorter than things you don't do so often. Huffman-encode your programming :) Cheers, Niko -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

June 7, 2010

Re: [Pharo-project] ISSUE 2514

by Henrik Johansen

On Jun 7, 2010, at 3:03 33PM, Fernando olivero wrote: > Hi Adrian, i've added this test in the SLICE. > It wasn't there before. > > The problem is that in PharoCore-1.1-11383-Beta the new editors aren't initialized, and the test fails, > > TextEditor initialize. > SmalltalkEditor initialize. > SimpleEditor initialize. > > I could either add this statements as a test preconditions, or we could execute them and have already initialized in the image itself. So we have a valid state of the editors in the image. > > What is your opinion? > > Fernando Should do some refactoring too, right now actions are stored in a shared variable for SimpleEditor, and a class inst var for TextEditor. (capitalized differently) And most of them are initialized, it's just SmalltalkEditor which is not. Since it doesn't implement initialize directly, it is never executed when loaded from Monticello (or filed in, for that matter). With the initialize factored into different methods like that, the initialize method itself is seldomly updated, it's hard to ensure you've initialized correctly when using Monticello. In this case, a postload script for System-Text doing Editor allSubclassesDo: [:each | each initialize] might have been the simplest solution, but those don't exist anymore in Pharo. Cheers, Henry

June 7, 2010

Re: [Pharo-project] ISSUE 2514

by StÃ©phane Ducasse

Since the initialize methods are there the next time we will load it we will not have the problem so we can just do that in the next integration pass. Setf > Hi Adrian, i've added this test in the SLICE. > It wasn't there before. > > The problem is that in PharoCore-1.1-11383-Beta the new editors aren't initialized, and the test fails, > > TextEditor initialize. > SmalltalkEditor initialize. > SimpleEditor initialize. > > I could either add this statements as a test preconditions, or we could execute them and have already initialized in the image itself. So we have a valid state of the editors in the image. > > What is your opinion? > > Fernando > > > On Jun 7, 2010, at 8:45 AM, Adrian Lienhard wrote: > >> Hi Fernando, >> >> Thanks for the fix. Now there is a new failing test: #testAcceptConcents (at least I don't remember that we saw this failing before). Can you check? >> >> Cheers, >> Adrian >> >> On Jun 6, 2010, at 20:04 , StÃ©phane Ducasse wrote: >> >>> THANKS!!! >>> >>> Stef >>> >>> On Jun 6, 2010, at 7:16 PM, Jorge Ressia wrote: >>> >>>> Hi, >>>> >>>> Thanks Fernando! >>>> >>>> Adrian, Stef this is the fix required for fixing one of the remanning >>>> failing tests in Pharo 1.1 >>>> >>>> Cheers, >>>> >>>> Jorge >>>> >>>> On Sun, Jun 6, 2010 at 4:28 PM, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: >>>>> SLICE-NewTextMorph-acceptContents-FernandoOlivero.1 >>>>> >>>>> >>>>> >>>>> ISSUE 2514 >>>>> NewTextMorph does not accept on cmd-s. >>>>> NewTextMorph>>example1 is not working. >>>>> >>>>> Fixed this issue, made a test and aslo fixed #testFittingParagraph >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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

June 7, 2010

Re: [Pharo-project] Autotest / TDD + screencast

by Noury Bouraqadi

Hi Laurent, Cool! I like the idea. Now, what happens if there are too many tests? One solution would be to ask the user if (s)he wants to run all tests if there are more than say 300, though I feel that this will quickly become painful. Noury On 4 juin 2010, at 23:12, laurent laffont wrote: > Hi, > > Here's a first usable version of Autotest (automatic test runner, inspired by Ruby's ZentTest autotest). > > The goal is to have instant feedback on the code you > > The screencast to see it in action: http://lolgzs.free.fr/pharo/autotest_1.mpeg > > To load it: > > Gofer new > squeaksource: 'Autotest'; > package: 'Autotest'; > load > > Comments are welcome as I have to rewrite it better :) Repository is read / write for those who wants to contribute. > > Cheers, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 7, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by Gabriel Brunstein

good work!! it looks interesting. have you looked at codebubbles for some ideas? http://www.cs.brown.edu/people/acb/codebubbles_site.htm I have a question about this: "They visually represent system components such as packages, classes, methods, developers, and workspaces." can you visually represent instances too? 2010/6/7 Fernando olivero <oliverof(a)lu.unisi.ch> > Hi simon, thanks for the comments! > > On Jun 7, 2010, at 1:41 PM, Simon Denier wrote: > > Hi Fernando > > Already lots of good stuff in your app. It looks *very* good and it feels > quite good. I especially like the toolbar and the icons, as well as the > shape toolbar which appears when overing over a shape (the "appear" effect > is too long though). > > Oh, i'll change this! > > For this first release i've introduced a long delay in the fadein > animation, because for novice users the menu-toolbar will be used, but once > you learn the keyboard shortcuts to most common operations you don't need it > anymore. Also the menu-toolbar intention is to present what operations are > available on the focused shape. > > In the next version a Control panel will be available to modify the > behavior of widgets, icons, toolbars and the sytem. > > > > Is it possible to import/develop existing packages/classes into Gaucho? > That would be a cool way to go beyond BankAccount for people who want to try > it on larger scale :) > > > Yes! using the search widget you can import packages, classes and methods > present in the image. > For external you need to still use Gofer or Monticello outside Gaucho. > > This is how i actually code Gaucho within Gaucho. > > > For the usage of the search widget Look at the screencast named Searching > and workspaces ( http://gaucho.inf.usi.ch ). > > Sequence of actions: > > cmd-t: for opening the toolbar > navigate to the search button > press enter. > type the name of the package, class or method. > For importing a package "family", ( for example Gaucho-Core, > Gaucho-Morphic, etc...) type Gacho*. > the widget auto completes entries, and is smart enough to filter > accordingly. (it is still a litte slow, so dont type fast please). > press enter when the desired match is found. > the imported shape is highlighted in the pampas. > > > Thanks for the feedback, > Fernando > > > > On 7 juin 2010, at 00:22, Fernando olivero wrote: > > Hi Pharo programmers! > > We are happy to announce that Gaucho 1.0 is released. > > Gaucho is a direct manipulation environment for software. > > If you want to try it out go to http://gaucho.inf.usi.ch/ . > > Gaucho1.0 works in Pharo1.0. > > In the releases section you'll find the installation script , and a > description of all the features of Gaucho1.0. > > Any feedback you are willing to provide is welcomed! > In the website you will find a bug issue tracker and the mailing list > description. > Or you can also send us an email for any other purpose, such as > demo-request or inquiries about the Gaucho project. > > > Hope you enjoy using it as much as we do! > > Fernando Olivero > University Of Lugano > > > pd: Be ready for the next version, with many improvements and added > features! Soon to come. > > pd2: (Extract from the web page) > > -------------------------------------------------- > *Version: 1.0* > * > * > *Features included in this version:* > > - *Direct manipulation of Classes, methods and packages* > - *Easily perform rename refactorings of classes and methods* > - *Draggable arrows for manipulating the inheritance relationships > between classes* > - *Creating and runing tests for all the classes in the system* > - *Creating workspaces for taking snapshots of the current pampas* > - *Smart searching for any object in the system* > - *Keyboard shortcuts associated to the most important operations* > - *Logging all the changes to the system* > - *Saving/Loading developers and workspaces to the default local > directory* > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > -- > Simon > > > > <ATT00001..txt> > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 7, 2010

Re: [Pharo-project] [update 1.1] #11389

by StÃ©phane Ducasse

thanks adrian Stef On Jun 7, 2010, at 2:05 PM, Adrian Lienhard wrote: > 11389 > ----- > > - Split space using binary resources like images and fonts into separate package so it can be unloaded to produce a small image > - Improved cleanUpForProduction (resulting image < 6.5MB) > - Author>>reset fix > - Issue 2515: Changesets keeps dirty after cleanUpForRelease > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 7, 2010