- Pharo-dev - lists.pharo.org

Re: [Pharo-project] color when editing code

by Alain Plantec

Le 15/04/2011 20:17, Dale Henrichs a Ã©crit : > On 04/15/2011 09:55 AM, Alexandre Bergel wrote: >> Hi! >> >> Just a comment, I obtain the following when opening a debugger: > > I have the same problem and have wasted a fair bit of time misreading > the actual location of the cursor:) > > I like the idea of the highlighting, but the colors used shouln't be > so close together... yes, you can change it from the setting browser. Cheers Alain > > Dale > >

April 15, 2011

[Pharo-project] [update 1.3] #13158

by laurent laffont

13158 ----- COTDC Integration: 40 - PasswordDialogWindow - L.Laffont 41 - NonReentrantWeakMessageSend + ExclusiveWeakMessageSend - H.Johansen 42 - ExpanderMorphContracted - G.Chambers 43 - FreeTypeFontSelectorDialogWindow - L.Laffont 44 - ColorChanged - L.Laffont 45 - TestCoverage - L.Laffont 46 - SUnitUnloader - S.V.Caekenberghe 47 - TAssertable - M.M.Peck 48 - ClassFactoryForTestCase - A.Bergel Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

April 15, 2011

Re: [Pharo-project] color when editing code

by Dale Henrichs

On 04/15/2011 09:55 AM, Alexandre Bergel wrote: > Hi! > > Just a comment, I obtain the following when opening a debugger: I have the same problem and have wasted a fair bit of time misreading the actual location of the cursor:) I like the idea of the highlighting, but the colors used shouln't be so close together... Dale

April 15, 2011

Re: [Pharo-project] [COTDC] 48 - ClassFactoryForTestCase

by laurent laffont

Thank you Alexandre. Laurent On Thu, Apr 14, 2011 at 11:39 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > -=-=-=-=-=-=-=-=-= > The class ClassFactoryForTestCase is useful when classes needs to be > created during the execution of the test. This avoid polluting your unit > tests with dummy and mock classes. > A typical usage of it is: > > TestCase subclass: #YourTest > instanceVariableNames: 'classFactory' > > YourTest>>setUp > classFactory := ClassFactoryForTestCase new > > YourTest>>tearDown > classFactory deleteClasses. > > YourTest>>testIsBehavior > | cls | > cls := classFactory newClass. > self assert: cls isBehavior > -=-=-=-=-=-=-=-=-= > > Cheers, > Alexandre > > On 14 Apr 2011, at 16:07, laurent laffont wrote: > > > Today: ClassFactoryForTestCase > > > > Come on guys ! Go Go Go !! > > > > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

April 15, 2011

[Pharo-project] Finder: case-insensitive search

by DougEdmunds

I did a search for 'message names' in Source using Finder. I get one set of results. I get different results if I search for 'Message names'. I get yet different results if I search for 'Message Names'. I want to search without having to guess every possible case-sensitive combination. How can I search Source for case-insensitive results? By comparison, searching in Selectors is not case sensitive. A search for 'message' will find 'message' or 'Message'. Entering 'message' and checking the regex box limits it to case-sensitive results (only finding message but not Message). But it doesn't work this way for Source. Why the inconsistency? -- View this message in context: http://forum.world.st/Finder-case-insensitive-search-tp3452633p3452633.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 15, 2011

Re: [Pharo-project] color when editing code

by Alain Plantec

no Alexandre, you're not alone :) I see two solutions: - change the selection color - disable globally the secondary selection color. but I think it's an issue. there should be a way to disable the secondary selection locally (here in the debugger). Cheers Alain Le 15/04/2011 18:55, Alexandre Bergel a Ã©crit : > Hi! > > Just a comment, I obtain the following when opening a debugger: > > > > > I always have to fiddle a bit to guess where the cursor caret is located. > Am I the only one to experience this? > > Cheers, > Alexandre

April 15, 2011

[Pharo-project] color when editing code

by Alexandre Bergel

Hi! Just a comment, I obtain the following when opening a debugger: I always have to fiddle a bit to guess where the cursor caret is located. Am I the only one to experience this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 15, 2011

[Pharo-project] Please update Help> Announcements tutorial

by DougEdmunds

1. Not understanding how announcements work, I tried the tutorial information found under World menu > Help> Help Browser > Announcements framework 2. Under Tutorial - Step 3, there is this line: "Transcript open." That crashes, because apparently Transcript no longer understands 'open'. How do you open a Transcript from a workspace under 1.3? 3. I created a category 'Sandbox', and a class 'MyStuff'. I put the code from Tutorial -Step 3 into a method called anno1 Object subclass: #MyStuff instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Sandbox'! !MyStuff methodsFor: 'as yet unclassified' stamp: 'DougEdmunds 4/14/2011 16:27'! anno1 | announcer | World announcer on: WindowOpened send: #value to: [ Transcript show: 'A new window was opened';cr].! ! I ran "MyStuff new anno1." in a workspace. Now every time I open a window, the Transcript shows. "A new window was opened." 4. I removed the MyStuff class. But every time I open a window, the Transcript still shows "A new window was opened." I return to the Announcements Tutorial, and there is NO EXPLANATION how to get rid of this 'announcement' or whatever I should call the line that appears in the Transcript. 6. So, please whoever wrote the Tutorial, update it. 7. And the more immediate question: how do I stop automatically printing 'A new window was opened' in the Transcript every time I open a window? -- View this message in context: http://forum.world.st/Please-update-Help-Announcements-tutorial-tp3452524p3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 15, 2011

[Pharo-project] Last chance to Nile

by Mariano Martinez Peck

Every single release we do, I've to spend a lot of time making Nile tests green. We have not never even received a mail in the mailing list about Nile. So..or nobody care about its tests, or nobody use it. So...if tests are not green when Pharo 1.3 release arrives, we will remove it from the dev image. It's a pity because I like the project and I like to see Traits. Regards, -- Mariano http://marianopeck.wordpress.com

April 15, 2011

Re: [Pharo-project] Issue 4030 in pharo: defaultBackgroundColor should not use self theme

by pharo＠googlecode.com

Updates: Status: FixToInclude Labels: Milestone-1.3 Comment #1 on issue 4030 by marianopeck: defaultBackgroundColor should not use self theme http://code.google.com/p/pharo/issues/detail?id=4030 Name: SLICE-Issue-4030-defaultBackgroundColor-should-not-use-self-theme-MarianoMartinezPeck.1 Author: MarianoMartinezPeck Time: 15 April 2011, 5:13:24 pm UUID: dc3d1b20-ff43-422c-96fd-7fd265e93ec3 Ancestors: Dependencies: Tools-MarianoMartinezPeck.581 Fix to 4030

April 15, 2011