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

Re: [Pharo-project] pharo and stand along GUI projects

by sergio_101

> People go to great lengths to worry about executables. Â As long as we have good lock-down tools, it is largely a non-issue. Â My one stand-alone GUI built in Pharo has an icon sitting on my Gnome menu bar; it points to a shell script that launches the vm with the correct image - done. Â Most problems I have with my Windows-based my biggest concern about executables is making sure that my users can install and run the program with absolutely no issues.. -- ---- peace, sergio photographer, journalist, visionary http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

June 7, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by Simon Denier

OK two other things 1) (minor) I find myself repeatdly trying to extend a Shape size to display more instance variables and methods by looking for the resize handle in the bottom right corner 2) when I want to edit a method, the shape takes the full screen and I can't see any other data. Why can't I edit the method in-place Also, I find it quickly annoying when I have to place manually each shape created. It would be better if shapes tend to stick to their parent shape when created, and I can move them freely after (I think that one point where codebubbles is good). I actually have more ideas about that, but it's tedious to explain by plain mail. On 7 juin 2010, at 14:44, Fernando olivero wrote: > 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 -- Simon

June 7, 2010

Re: [Pharo-project] Loading a cs by drag and drop does not work anymore

by Adrian Lienhard

Thanks for checking. I created issue http://code.google.com/p/pharo/issues/detail?id=2518 I think this should be fixed for a 1.1 release. Adrian On Jun 7, 2010, at 14:43 , Mariano Martinez Peck wrote: > Yes, I could reproduce the problem. No time to debug it :( > > 2010/6/7 Adrian Lienhard <adi(a)netstyle.ch> > >> When I drag a changeset (example attached) into a recent PharoCore 1.1 >> image and then choose to install it, I get a strange error (also attached). >> >> >> >> >> Has anybody else noted this problem? Do we have a ticket for it? >> >> Adrian >> >> >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> >> _______________________________________________ >> 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] pharo and stand along GUI projects

by sergio_101

> http://wiki.squeak.org/squeak/1794 (Some screenshots of different > applications developed with Squeak) > http://www.weather-dimensions.com/ (The well know Dan Ingalls application) > > And looking the new Preferences on Pharo 1.1 I really think that any > sort of application may be developed with Pharo with > a good look and feel. this all looks very promising.. my only concern is that i can deliver something cross platform that is VERY simply to install.. the core of the users will absolutely be non technical.. and i don't want them to have to struggle.. -- ---- peace, sergio photographer, journalist, visionary http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

June 7, 2010

Re: [Pharo-project] About TDD and Pharo

by Mariano Abel Coca

True, that happened to me too... Until I wanted to cancel the creation, and then I realized... It's a really bad name. Cheers, Mariano. On Mon, Jun 7, 2010 at 11:54 AM, Niko Schwarz <niko.schwarz(a)googlemail.com>wrote: > Right, only that I'm unhappy with the naming. I'd never have guessed > that "cancel" does what I want. So far, I've always chosen a random > junk category and fixed it up later. A button "Cancel" I'd expect to > cancel the creation altogether. > > Niko > > 2010/6/7 Hernan Wilkinson <hernan.wilkinson(a)gmail.com>: > > it is true, I almost all the time cancel that dialog to put the method as > > not yet categorized... but sometimes I select the category... I think > that > > pressing ESC or cancel is not that bad in this case and I would keep this > > dialog. > > > > On Mon, Jun 7, 2010 at 5:45 AM, Niko Schwarz < > niko.schwarz(a)googlemail.com> > > wrote: > >> > >> I think the rationale must be: during TDD it's ok to ask the developer > >> questions that he can answer right away. Thus, it's ok that the create > >> button asks for the class: you know instantly what to answer. But > >> asking for the method category is a major pain. I don't know about > >> y'all, but I never quite know upfront how I'll structure my > >> categories. That emerges much later in the process. > >> > >> In short: remove the asking for the method category. Just put it in > >> 'not yet categorized', and have me figure it out later. > >> > >> Cheers, > >> > >> Niko > >> > >> 2010/6/2 GermÃ¡n Leiva <leivagerman(a)gmail.com>: > >> > I'm thinking out load here ... > >> > In the debugger when a DNU is raised, for speeding up the programming > in > >> > "TDD mode": > >> > > >> > The create button must add the method in the class of the receiver, > the > >> > possibility to choose a superclass of the receiver must be optional (I > >> > don't > >> > like the recurrent asking...) in other button for example or having > >> > different shortcuts from the keyboard > >> > If I send a message that I already know that will be a getter, some > >> > option > >> > like "Create getter" could automagically create the method and the > >> > instance > >> > variable. > >> > When we a accept a method for the first time the pop-ups saying > "Unkown > >> > selector please confirm, select or cancel" are really annoying and > >> > decrease > >> > coding speed > >> > Same for the category pop-ups > >> > In the creation of a new class through "define new class" it will be > >> > helpful > >> > to remember the last class category used > >> > > >> > Some ToDo list supported from the environment and some facility for > the > >> > creation of test. > >> > All of the above maybe just make sense in TDD mode or not =P > >> > Cheers > >> > 2010/6/2 Alexandre Bergel <alexandre.bergel(a)inria.fr> > >> >> > >> >> The problems that I would like to see Pharo address are: > >> >> - redundancies in unit tests > >> >> - coverage of tests > >> >> - classification of low and high levels of tests (implementation > tests > >> >> vs > >> >> user stories) > >> >> > >> >> What are the tools to identify and solve this issues ? Research is > >> >> needed > >> >> :-) > >> >> > >> >> Alexandre > >> >> > >> >> > >> >> > >> >> On 2 Jun 2010, at 15:30, StÃ©phane Ducasse wrote: > >> >> > >> >> > Hi all > >> >> > > >> >> > Imagine that we would like to sell pharo (+ seaside) as THE agile > >> >> > platform for doing TDD. > >> >> > What would be the changes that we could do support it. > >> >> > I know that hernan did a package for that but not I would like to > >> >> > have a > >> >> > new list of items > >> >> > to support it. > >> >> > > >> >> > Stef > >> >> > _______________________________________________ > >> >> > 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 > >> > > >> > > >> > > >> > -- > >> > GermÃ¡n Leiva > >> > LeivaGerman(a)gmail.com > >> > > >> > _______________________________________________ > >> > 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 > >> > >> _______________________________________________ > >> 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 > > > > > > -- > http://scg.unibe.ch/staff/Schwarz > twitter.com/nes1983 > Tel: +41 076 235 8683 > > _______________________________________________ > 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

[Pharo-project] Support various focus holders for HandMorph [Was: Issue 2451: Make Algernon work in Pharo 1.1]

by Guillermo Polito

Can some Morphic gurÃº check this? Thanks! Guille http://code.google.com/p/pharo/issues/detail?id=2517&q=support&colspec=ID%2… On Mon, Jun 7, 2010 at 4:34 AM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Sorry I forget to send the thread: > > > http://forum.world.st/Putting-Algernon-and-WorkingSet-in-a-Dev-image-td1295… > > Cheers > > Mariano > > ** > On Mon, Jun 7, 2010 at 9:33 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Hi Guille. Yes, some months ago I discovered that changeset. I separated >> it, saved into a .ch, loaded it into a PharoCore clean image and I tried to >> understood it. >> My knoweldege about Morhpic is very limited, but the changed looked of for >> me. >> >> What would be cool is to commit to inbox such changes. Create an issue >> like "*support various focus holders for **HandMorph *" >> Then, send a separated mail about this changes and get feedback. If agree, >> we can integrate it in the core. With this, at least Algernon doesn't have >> to do such hack. >> >> I also asked this to Romian as he was developing WorkingSet and the >> problem was that you couldn't have both at the same time because of the >> shortcuts. These changes may solve that. Although he didn't have time to >> look at it. >> >> Cheers >> >> Mariano >> >> >> On Mon, Jun 7, 2010 at 5:54 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Hi, i was looking at this issue and I have some questions :): >>> >>> - There are some changes to HandMorph in a changeset hardcoded in the >>> ConfigurationOfAlgernon. As Mariano said here ( >>> http://forum.world.st/Putting-Algernon-and-WorkingSet-in-a-Dev-image-td1295…) >>> "The main change does the simples modifications to HandMorph for it to >>> support various focus holders". Is it safe to integrate it in Pharo? If >>> so, should it be integrated in the core Morph package? The changeset is >>> the following: >>> >>> * '''From Squeak3.7gamma of ''''17 July 2004'''' [latest update: #5985] >>> on 9 August 2004 at 7:56:10 pm''! >>> "Change Set: MultipleFocusHolder-hpt >>> Date: 9 August 2004 >>> Author: Hernan Tylim >>> >>> This changesets does the simplest modifications to HandMorph for it to >>> support various focus holders. >>> >>> The important changes are: >>> >>> * addiionalKeyboardFocuses instance variable was added with its getter >>> and setter methods. >>> >>> * HandMorph>>sendKeyboardEvent: was changed to traverse the list of >>> keyboard focus holders and call HandMorph>>sendEvent:focus:clear: to each >>> one of them. >>> >>> * HandMorph>>sendEvent:focus:clear: was changed to preserve the >>> ''wasHandled'' status of the event, before that info were lost because the >>> Event instance were copied before passed to the Morph. >>> "! >>> >>> Morph subclass: #HandMorph >>> instanceVariableNames: ''mouseFocus keyboardFocus eventListeners >>> mouseListeners keyboardListeners mouseClickState mouseOverHandler >>> lastMouseEvent targetOffset damageRecorder cacheCanvas cachedCanvasHasHoles >>> temporaryCursor temporaryCursorOffset hasChanged savedPatch userInitials >>> lastEventBuffer genieGestureProcessor additionalKeyboardFocuses '' >>> classVariableNames: ''DoubleClickTime EventStats NewEventRules >>> NormalCursor PasteBuffer ShowEvents '' >>> poolDictionaries: ''EventSensorConstants'' >>> category: ''Morphic-Kernel''! >>> >>> !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/8/2004 01:52''! >>> addAdditionalKeyboardFocus: aMorph >>> (self additionalKeyboardFocuses includes: aMorph) >>> ifFalse: [self additionalKeyboardFocuses addFirst: aMorph]! ! >>> >>> !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:47''! >>> additionalKeyboardFocuses >>> ^additionalKeyboardFocuses ifNil: [additionalKeyboardFocuses _ >>> OrderedCollection new].! ! >>> >>> !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/8/2004 00:12''! >>> clearFocusHolder: aMorph >>> self keyboardFocus == aMorph >>> ifTrue: [^self keyboardFocus: nil]. >>> (self additionalKeyboardFocuses includes: aMorph) >>> ifTrue: [self removeAdditionalKeyboardFocus: aMorph].! ! >>> >>> !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:48''! >>> fullKeyboardFocuses >>> ^self additionalKeyboardFocuses copyWith: self keyboardFocus.! ! >>> >>> !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:43''! >>> keyboardFocuses >>> keyboardFocuses ifNil: [keyboardFocuses := OrderedCollection new]. >>> ^keyboardFocuses! ! >>> >>> !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:49''! >>> removeAdditionalKeyboardFocus: aMorph >>> self additionalKeyboardFocuses remove: aMorph! ! >>> >>> !HandMorph methodsFor: ''private events'' stamp: ''hpt 8/8/2004 01:18''! >>> sendFocusEvent: anEvent to: focusHolder clear: aBlock >>> "Send the event to the morph currently holding the focus" >>> | result w e | >>> w _ focusHolder world ifNil:[^ aBlock value]. >>> w becomeActiveDuring:[ >>> ActiveHand _ self. >>> ActiveEvent _ anEvent. >>> e _ (anEvent transformedBy: (focusHolder transformedFrom: self)). >>> result _ focusHolder handleFocusEvent: e . >>> anEvent wasHandled: e wasHandled. >>> ]. >>> ^result! ! >>> >>> !HandMorph methodsFor: ''private events'' stamp: ''hpt 8/8/2004 01:09''! >>> sendKeyboardEvent: anEvent >>> "Send the event to the morph currently holding the focus, or if none >>> to the owner of the hand." >>> >>> self fullKeyboardFocuses do: [:focusHolder | >>> "(anEvent keyCharacter = $\) ifTrue: [self halt]." >>> anEvent wasHandled >>> ifFalse: [self sendEvent: anEvent focus: focusHolder >>> clear:[self clearFocusHolder: focusHolder]]].! ! >>> >>> Morph subclass: #HandMorph >>> instanceVariableNames: ''mouseFocus keyboardFocus eventListeners >>> mouseListeners keyboardListeners mouseClickState mouseOverHandler >>> lastMouseEvent targetOffset damageRecorder cacheCanvas cachedCanvasHasHoles >>> temporaryCursor temporaryCursorOffset hasChanged savedPatch userInitials >>> lastEventBuffer genieGestureProcessor additionalKeyboardFocuses'' >>> classVariableNames: ''DoubleClickTime EventStats NewEventRules >>> NormalCursor PasteBuffer ShowEvents'' >>> poolDictionaries: ''EventSensorConstants'' >>> category: ''Morphic-Kernel''! >>> *' >>> >>> It should be nice someone who knows well morphic checks it. >>> >>> Cheers, >>> Guille >>> >> >> >

June 7, 2010

Re: [Pharo-project] About TDD and Pharo

by Niko Schwarz

Right, only that I'm unhappy with the naming. I'd never have guessed that "cancel" does what I want. So far, I've always chosen a random junk category and fixed it up later. A button "Cancel" I'd expect to cancel the creation altogether. Niko 2010/6/7 Hernan Wilkinson <hernan.wilkinson(a)gmail.com>: > it is true, I almost all the time cancel that dialog to put the method as > not yet categorized... but sometimes I select the category... I think that > pressing ESC or cancel is not that bad in this case and I would keep this > dialog. > > On Mon, Jun 7, 2010 at 5:45 AM, Niko Schwarz <niko.schwarz(a)googlemail.com> > wrote: >> >> I think the rationale must be: during TDD it's ok to ask the developer >> questions that he can answer right away. Thus, it's ok that the create >> button asks for the class: you know instantly what to answer. But >> asking for the method category is a major pain. I don't know about >> y'all, but I never quite know upfront how I'll structure my >> categories. That emerges much later in the process. >> >> In short: remove the asking for the method category. Just put it in >> 'not yet categorized', and have me figure it out later. >> >> Cheers, >> >> Niko >> >> 2010/6/2 GermÃ¡n Leiva <leivagerman(a)gmail.com>: >> > I'm thinking out load here ... >> > In the debugger when a DNU is raised, for speeding up the programming in >> > "TDD mode": >> > >> > The create button must add the method in the class of the receiver, the >> > possibility to choose a superclass of the receiver must be optional (I >> > don't >> > like the recurrent asking...) in other button for example or having >> > different shortcuts from the keyboard >> > If I send a message that I already know that will be a getter, some >> > option >> > like "Create getter"Â couldÂ automagicallyÂ create the method and the >> > instance >> > variable. >> > When we a accept a method for the first time the pop-ups saying "Unkown >> > selector please confirm, select or cancel" are really annoying and >> > decrease >> > coding speed >> > Same for the category pop-ups >> > In the creation of a new class through "define new class" it will be >> > helpful >> > to remember the last class category used >> > >> > Some ToDo list supported from the environment and some facility for the >> > creation of test. >> > All of the above maybe just make sense in TDD mode or not =P >> > Cheers >> > 2010/6/2 Alexandre Bergel <alexandre.bergel(a)inria.fr> >> >> >> >> The problems that I would like to see Pharo address are: >> >> Â - redundancies in unit tests >> >> Â - coverage of tests >> >> Â - classification of low and high levels of tests (implementation tests >> >> vs >> >> user stories) >> >> >> >> What are the tools to identify and solve this issues ? Research is >> >> needed >> >> :-) >> >> >> >> Alexandre >> >> >> >> >> >> >> >> On 2 Jun 2010, at 15:30, StÃ©phane Ducasse wrote: >> >> >> >> > Hi all >> >> > >> >> > Imagine that we would like to sell pharo (+ seaside) as THE agile >> >> > platform for doing TDD. >> >> > What would be the changes that we could do support it. >> >> > I know that hernan did a package for that but not I would like to >> >> > have a >> >> > new list of items >> >> > to support it. >> >> > >> >> > Stef >> >> > _______________________________________________ >> >> > 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 >> > >> > >> > >> > -- >> > GermÃ¡n Leiva >> > LeivaGerman(a)gmail.com >> > >> > _______________________________________________ >> > 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 >> >> _______________________________________________ >> 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 > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

June 7, 2010

Re: [Pharo-project] About TDD and Pharo

by Mariano Abel Coca

Yes but the list should be shorter. Maybe only showing the class categories and what I've previously entered since I opened the image. And not all the hierarchy categories. Cheers, Mariano. 2010/6/7 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > it is true, I almost all the time cancel that dialog to put the method as > not yet categorized... but sometimes I select the category... I think that > pressing ESC or cancel is not that bad in this case and I would keep this > dialog. > > > On Mon, Jun 7, 2010 at 5:45 AM, Niko Schwarz <niko.schwarz(a)googlemail.com>wrote: > >> I think the rationale must be: during TDD it's ok to ask the developer >> questions that he can answer right away. Thus, it's ok that the create >> button asks for the class: you know instantly what to answer. But >> asking for the method category is a major pain. I don't know about >> y'all, but I never quite know upfront how I'll structure my >> categories. That emerges much later in the process. >> >> In short: remove the asking for the method category. Just put it in >> 'not yet categorized', and have me figure it out later. >> >> Cheers, >> >> Niko >> >> 2010/6/2 GermÃ¡n Leiva <leivagerman(a)gmail.com>: >> > I'm thinking out load here ... >> > In the debugger when a DNU is raised, for speeding up the programming in >> > "TDD mode": >> > >> > The create button must add the method in the class of the receiver, the >> > possibility to choose a superclass of the receiver must be optional (I >> don't >> > like the recurrent asking...) in other button for example or having >> > different shortcuts from the keyboard >> > If I send a message that I already know that will be a getter, some >> option >> > like "Create getter" could automagically create the method and the >> instance >> > variable. >> > When we a accept a method for the first time the pop-ups saying "Unkown >> > selector please confirm, select or cancel" are really annoying and >> decrease >> > coding speed >> > Same for the category pop-ups >> > In the creation of a new class through "define new class" it will be >> helpful >> > to remember the last class category used >> > >> > Some ToDo list supported from the environment and some facility for the >> > creation of test. >> > All of the above maybe just make sense in TDD mode or not =P >> > Cheers >> > 2010/6/2 Alexandre Bergel <alexandre.bergel(a)inria.fr> >> >> >> >> The problems that I would like to see Pharo address are: >> >> - redundancies in unit tests >> >> - coverage of tests >> >> - classification of low and high levels of tests (implementation tests >> vs >> >> user stories) >> >> >> >> What are the tools to identify and solve this issues ? Research is >> needed >> >> :-) >> >> >> >> Alexandre >> >> >> >> >> >> >> >> On 2 Jun 2010, at 15:30, StÃ©phane Ducasse wrote: >> >> >> >> > Hi all >> >> > >> >> > Imagine that we would like to sell pharo (+ seaside) as THE agile >> >> > platform for doing TDD. >> >> > What would be the changes that we could do support it. >> >> > I know that hernan did a package for that but not I would like to >> have a >> >> > new list of items >> >> > to support it. >> >> > >> >> > Stef >> >> > _______________________________________________ >> >> > 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 >> > >> > >> > >> > -- >> > GermÃ¡n Leiva >> > LeivaGerman(a)gmail.com >> > >> > _______________________________________________ >> > 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 >> >> _______________________________________________ >> 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 Marcus Denker

On Jun 7, 2010, at 3:54 PM, Niko Schwarz wrote: > Is there a website with this text that I can link to? > http://rmod.lille.inria.fr/web/pier/blog/2010-06-07 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 7, 2010

Re: [Pharo-project] Minimal release images (currently 6.2MB)

by Alain Plantec

Le 07/06/2010 14:17, Adrian Lienhard a Ã©crit : > > BTW, if you have more cleanup code or ideas where we could spare some bytes, let me know :) > the settings related packages should be removable: System-Settings and all Settings-* packages. Alain > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > 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