March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 1064 in pharo: There are still problem with keyboard shortcuts in Windows
by pharo＠googlecode.com April 15, 2011

April 15, 2011

Updates: Status: FixProposed Comment #11 on issue 1064 by marianopeck: There are still problem with keyboard shortcuts in Windows http://code.google.com/p/pharo/issues/detail?id=1064 from tn.. KeyboardEvent keyValue for 'ctrl + i' is evaluated to 9 as ASCII control code, and the value conflicts to Character tab value. I tried to correct source code for this problem. Below is the workaround for Pharo-1.1.1-OneClickCogVM on Windows XP. -------------------- InputEventSensor>>processEvent: processEvent: evt ... "Finally keyboard" type = EventTypeKeyboard ifTrue: [ (evt at: 4)=0 ifTrue: [ "-- add --" "Sswap ctrl/alt keys if neeeded" KeyDecodeTable at: {evt at: 3. evt at: 5} ifPresent: [:a | evt at: 3 put: a first; at: 6 put: a first; "-- add --" at: 5 put: a second]. ]. "-- add --" "Update state for polling calls" modifiers := evt at: 5. ^evt]. ... In order to work this code, Preference Control and Alt keys must be set to "Full matching". Because ASCII control characters (e.g. ^i) is mapped to character code with KeyDecodeTable, only at the time. About key event, see InputEventFetcher class comment. And it is interesting that to contrast implementations between Pharo and Squeak4.2. Each implementation is below. Pharo: InputEventSensor>>processEvent: Squeak4.2: EventSensor>>processEvent: Thanks,

3 11

Re: [Pharo-project] Issue 3148 in pharo: Proposal: adding 261 named colors
by pharo＠googlecode.com April 14, 2011

April 14, 2011

Updates: Status: FixProposed Comment #2 on issue 3148 by marcus.d...(a)gmail.com: Proposal: adding 261 named colors http://code.google.com/p/pharo/issues/detail?id=3148 (No comment was entered for this change.)

1 1

[Pharo-project] Issue 3818 in pharo: CommandLine Manager
by pharo＠googlecode.com April 13, 2011

April 13, 2011

Status: FixProposed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3818 by stephane...(a)gmail.com: CommandLine Manager http://code.google.com/p/pharo/issues/detail?id=3818 The proposal of adrien is in PharoTaskForces/SLICE-Issue-00000-replaceAbstractProjectAndLinkedElement

1 8

Re: [Pharo-project] Issue 3262 in pharo: Debugger enhancement to open in a background process when the UI process is busy
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Updates: Summary: Debugger enhancement to open in a background process when the UI process is busy Comment #2 on issue 3262 by stephane.ducasse: Debugger enhancement to open in a background process when the UI process is busy http://code.google.com/p/pharo/issues/detail?id=3262 Tried to rescue some of Eliot Miranda improvement for the debugger. Strangely enough the functions introduced by eliot got removed and not invoked in latter versions. Now invoking the debugger crash the system probably because there is an problem with the semaphore or other. I just save this to avoid to redo everything. Attachments: Debugger.1.cs 4.4 KB

1 4

[Pharo-project] Issue 3393 in pharo: Better support of configuration dependencies in Monticello Browser
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Accepted Owner: alexandre.bergel CC: da...(a)teleport.com, stephane.ducasse Labels: Difficulty-Easy New issue 3393 by alexandre.bergel: Better support of configuration dependencies in Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3393 Configurations are better handled now. If the configuration you're editing depends on another configuration, then it is correctly defined in the baseline. MonticelloGUI-AlexandreBergel.83 in the inbox

1 2

[Pharo-project] Issue 3568 in pharo: Remove SelectorBrowser
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Accepted Owner: stephane...(a)gmail.com CC: Benjamin...(a)gmail.com Labels: Milestone-1.3 New issue 3568 by stephane...(a)gmail.com: Remove SelectorBrowser http://code.google.com/p/pharo/issues/detail?id=3568 Now we can remove SelectorBrowser. Before we should check that '*b' . 'ab' . true shows match in Finder.

1 5

[Pharo-project] Issue 3800 in pharo: StaticForm can be removed
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3800 by stephane...(a)gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 An optimization for Nebraska - a StaticForm does not change once created so it may be cached on the remote end. one method. isStatic ^true and not invoked

1 5

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed
by pharo＠googlecode.com April 11, 2011

April 11, 2011

Comment #6 on issue 3088 by vonbecm...(a)gmail.com: MNU Text>>withBlanksTrimmed http://code.google.com/p/pharo/issues/detail?id=3088 it doesn't work in Pharo image: Pharo1.2#12341 Virtual machine used: Squeak4.1 of 17 April 2010 [latest update: #9957] Platform Name: unix Class browser used (if applicable): Browser Same steps to reproduce. Attachments: PharoDebug.log 80.6 KB

1 9

Re: [Pharo-project] Issue 2703 in pharo: Unicode experiments of nicolas cellier on squeak
by pharo＠googlecode.com April 11, 2011

April 11, 2011

Updates: Status: FixProposed Comment #5 on issue 2703 by nicolas....(a)gmail.com: Unicode experiments of nicolas cellier on squeak http://code.google.com/p/pharo/issues/detail?id=2703 Name: SLICE-Issue-2703-Unicode-caseConversions-nice.1 Dependencies: Multilingual-Encodings-nice.10, Multilingual-Display-nice.11, Collections-Strings-nice.173 Install WideString uppercasing/lowercasing unicode utilities. Warning: the Unicode data will be initialized when loading the SLICE, and access to the internet is required in this phase (see #initializeCaseMappings). Todo: maybe have a look at classification tables and methods #isLowercase: #isUppercase:

1 2

Re: [Pharo-project] Issue 2986 in pharo: DemoMode should not change Fonts only sizes
by pharo＠googlecode.com April 11, 2011

April 11, 2011

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #4 on issue 2986 by marcus.d...(a)gmail.com: DemoMode should not change Fonts only sizes http://code.google.com/p/pharo/issues/detail?id=2986 let's do this as one of the first things in 1.3

1 4