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

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by Juan Vuletich

Igor Stasenko wrote: > IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go. > (i mean get rid that 'color' thing in base class) :) > > Yep. I fully agree. Cheers, Juan Vuletich

Nov. 25, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by Juan Vuletich

StÃ©phane Ducasse wrote: > Indeed. I mean > I can't help, but feel free to go ahead > > Stef > > Great! Thanks for the clarification. Cheers, Juan Vuletich

Nov. 25, 2010

[Pharo-project] Issue 3292 in pharo: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97'

by pharo＠googlecode.com

Status: Accepted Owner: da...(a)teleport.com Labels: Type-ReportDefect Milestone-1.2 New issue 3292 by da...(a)teleport.com: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97' http://code.google.com/p/pharo/issues/detail?id=3292 I ran into the error running OBMercuryPanelTest>>testSenders. The following expression will trigger the problem: SourcedMethodReference class: Dictionary selector: #keyAtValue:ifAbsent: when executed in a Pharo1.2a-12251 image. It looks like the timestamp parser isn't written to accomodate older timestamp forms

Nov. 25, 2010

Re: [Pharo-project] [Pharo-coral] Update for Coral

by Mariano Martinez Peck

On Wed, Nov 24, 2010 at 8:50 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Hello Olivier, > > Very nice! I installed it according to the instructions ( > http://www.auverlot.fr/pharo/coralinstall/) and it works. > > I guess the next step is to have a class for the scripts? So that one can > define methods and have pre-defined > methods to ease script-writing... > > What about using Helvetia in a future? I guess that at the end will you will have a several of those methods, and those methods may become some kind of DSL/Language... i don't know, just an idea > Small edit for the readme: > > -> "3) make them executable: chmod +x coral.sh coraldb.sh" > ==> is now called coralDebug.sh > > > On Nov 24, 2010, at 2:53 PM, Olivier Auverlot wrote: > > > New methods for displaying in a UNIX console : > > > > * Console>>displayAttributes: > > * Console>>eraseScreen > > * Console>>esc: > > * Console>>locate: > > * Console>>plot: > > * Console>>resetAllAttributes > > > > Two examples: > > > > * scriptCarpet.cst > > * scriptHappyFace.cst > > > > Best regards > > Olivier > > > > www.auverlot.fr > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-coral mailing list > Pharo-coral(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-coral >

Nov. 24, 2010

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion

by Lukas Renggli

Why two lists when one list is enough? http://www.lukas-renggli.ch/blog/ob-completion-dialog Lukas On 24 November 2010 19:08, Alain Plantec <alain.plantec(a)free.fr> wrote: > Dear list, > I'm not should it's enough clear so > a screenshot is attached. > Cheers > Alain > -- Lukas Renggli www.lukas-renggli.ch

Nov. 24, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by Igor Stasenko

IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go. (i mean get rid that 'color' thing in base class) :) On 24 November 2010 16:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Indeed. I mean > Â Â Â Â I can't help, but feel free to go ahead > > Stef > >>>>> >> "I do not think that we can build something on simpleMorphic, what we can do is look at the kernel and see how the changes can be applied to Morphic", >> >> it really means that it should better not be done. It means "I think it can't be done, don't waste your time". >> >> If, instead of that, you say "I can't help, but feel free to go ahead", the reaction of the community will be completely different. >> >> Cheers, >> Juan Vuletich >> > > > -- Best regards, Igor Stasenko AKA sig.

Nov. 24, 2010

Re: [Pharo-project] Fwd: [Pharo-users] TestMock: a full featured mock testing framework now available in SqueakSource

by Luc Fabresse

Hi Laurent, > why Mocks are less necessary in Smalltalk than in other > (Ruby/Python/whatever...) languages ? Do you have some examples / link ? > Hey, I didn't write that ;-) I wrote that mocks are not always used in unit tests. I can write a lot of unit tests without mocks by using the tested objects directly. Sometimes I think a mocking library should be in PharoCore so I don't need > to write my own mocks..... > I agree, when mocks are needed, I library could help. #Luc

Nov. 24, 2010

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion

by Alain Plantec

Dear list, I'm not should it's enough clear so a screenshot is attached. Cheers Alain

Nov. 24, 2010

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion

by pharo＠googlecode.com

Comment #1 on issue 3291 by aplantec: Missing text field with completion http://code.google.com/p/pharo/issues/detail?id=3291 In PharoTaskForces: SLICE-Issue-3291-Missing-text-field-with-completion For testing. Not documented. Test it with the findClass dialog which now makes use of a completion list for class name input field.

Nov. 24, 2010

[Pharo-project] Issue 3291 in pharo: Missing text field with completion

by pharo＠googlecode.com

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3291 by aplantec: Missing text field with completion http://code.google.com/p/pharo/issues/detail?id=3291 Could be added as an instrumentation of PluggableTextFieldMorph.

Nov. 24, 2010