July 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» 32,mac - Build # 194 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 8, 2012

Re: [Pharo-project] [ANN]: Vim Shortcuts for Nautilus (Proof-of-concept)

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > > If I were you, I would have put all the VIM shortcut in one class, instead > of putting them around but :) > I'll keep that in mind once I get it working ;-) Benjamin Van Ryseghem-2 wrote > > Like that, you could add yours in a specific context, and remove them. > Any luck finding those detach* methods? Googling/Nabbling "detachKeymapCategory" turned up nothing. Also, I think of my use case here for the "enter command mode" shortcut as "Change the default shortcuts for a Morph class". It seems that what's required for this type of use is a registration mechanism more like the world menu. For the world menu, I can insert an entry at any level, not just an existing one, without overriding anything. In KM currently, in order to do this, it seems we're forced to hitch a ride on an existing category. Maybe a special pragma indicating that certain categories should be attached for the class by default. In summary, I'm still unclear on the relationship between the class-side <keymap> defaults methods and changing shortcuts on the fly, but what seems to be missing are: * a way to register shortcuts/categories to be attached to a Morph class by default * a way to detach categories * a way to detach individual shortcuts Thanks, this is very exciting. We're *so* close to having this work... Sean -- View this message in context: http://forum.world.st/ANN-Vim-Shortcuts-for-Nautilus-Proof-of-concept-tp463… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 8, 2012

[Pharo-project] [update 2.0] #20195

by Marcus Denker

20195 ----- Issue 6259: DataStream is still there http://code.google.com/p/pharo/issues/detail?id=6259 Issue 4095: Suggestion: rename some methods for consistency (just example methods, no API changes) http://code.google.com/p/pharo/issues/detail?id=4095 -- Marcus Denker -- http://marcusdenker.de

July 8, 2012

Re: [Pharo-project] [ANN]: Vim Shortcuts for Nautilus (Proof-of-concept)

by Benjamin

If I were you, I would have put all the VIM shortcut in one class, instead of putting them around but :) For the attachment, the solution could be to attach simultaneously several shortcuts category. Like that, you could add yours in a specific context, and remove them. An ugly solution right now could be to duplicate all the NautilusSourceCodeShortcuts entries, and to switch between NautilusSourceCodeShortcuts and VIMShortcuts. A kind of hack could be: AbstractNautilusUI class>>buildInsertModeKeymappingsOn: aBuilder <keymap> (KMRepository default categoryForName: #NautilusSourceCodeShortcuts) keymaps do: [:km | (aBuilder shortcut: (km name, 'VIM') asSymbol) category: VimInsertModeShortcuts default: km shortcut do: km action ]. (aBuilder shortcut: #commandMode) category: #NautilusSourceCodeShortcuts "#VimInsertModeShortcuts" default: Character escape asShortcut do: [ :target | Editor dumbbellCursor: true. target sourceTextArea changed. target sourceTextArea attachKeymapCategory: #VimCommandModeShortcuts ]. It's kind of a hack, but like that you ensure to have the same shortcuts in the midtime Ben On Jul 8, 2012, at 3:13 AM, Sean P. DeNigris wrote: > > Sean P. DeNigris wrote >> >> - how do I remove an individual shortcut or shortcut category from a >> morph? (so I can toggle the command/insert mode shortcuts) >> > > I'm having trouble toggling insert mode... Right now I have > AbstractNautilusUI class>>buildInsertModeKeymappingsOn: aBuilder > <keymap> > > (aBuilder shortcut: #commandMode) > category: #NautilusSourceCodeShortcuts "#VimInsertModeShortcuts" > default: Character escape asShortcut > do: [ :target | > Editor dumbbellCursor: true. > target sourceTextArea changed. > target sourceTextArea attachKeymapCategory: #VimCommandModeShortcuts ]. > > The problem is that: > * I think I have to put these shortcuts into #NautilusSourceCodeShortcuts to > have them load without overriding anything > * If I don't put them in their own category (i.e. #VimInsertModeShortcuts), > I don't know how to remove them when entering command mode (I only see a way > to remove whole categories) > > Guille, Ben - are those assumptions correct and how should I proceed? > > Thanks, > Sean > > -- > View this message in context: http://forum.world.st/ANN-Vim-Shortcuts-for-Nautilus-Proof-of-concept-tp463… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 8, 2012

Re: [Pharo-project] StartupPreferences

by Mariano Martinez Peck

On Sun, Jul 8, 2012 at 10:16 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sun, Jul 8, 2012 at 6:17 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > >> Mariano, >> >> Can any of the script lookup logic from 2.0 be ported to 1.4? >> > > Migrate everything (the new logic and all the last improvements) is too > much. Mostly because I don't have time and because it is not a dead or > alive bug. In fact, it was never before and people never complained ;) > What you COULD do if you want is to just do this: > > > >> StartupPreferences doesn't seem very useful if only the image folder is >> checked, > > > Why it only searches in the image folder? > > buildActionList > > "First, we look at image folder, > then we look at preferences folder, > and finally at general preferences folder " > > ^ OrderedCollection new > add: [ self lookInImageDirectory ]; > add: [self lookInPreferencesFolder ]; > add: [self lookInGeneralPreferencesFolder ]; > yourself. > Ok, I was checking an old version of 1.4. Now I see: buildActionList "First, we look at image folder, then we look at preferences folder, and finally at general preferences folder " self flag: #todo. "I'm disabling this sequence because lookup of preferences folder is broken in windows." ^ OrderedCollection new add: [ self lookInImageDirectory ]; "add: [self lookInPreferencesFolder ]; add: [self lookInGeneralPreferencesFolder ];" yourself. so....migrate all the new version is costly. I don't have time to do it. If you want, you can just enable back for all but for windows: buildActionList "First, we look at image folder, then we look at preferences folder, and finally at general preferences folder " | directories | self flag: #todo. "I'm disabling this sequence because lookup of preferences folder is broken in windows. NOTE: this has been fixed in Pharo 2.0" directories := OrderedCollection new. directories add: [ self lookInImageDirectory ]. (OSPlatform current platformFamily = #Windows) ifFalse: [ directories add: [self lookInPreferencesFolder ]. directories add: [self lookInGeneralPreferencesFolder ]. ]. ^ directories > > > it should check there (the version that is in 1.4). The only reason this > version would stop searching in other places is if it did find something. > When it finds something, it stops searching (in 2.0 it contiues and > executes all the ones that are found). > > > given that the initial use case was for working in many fresh >> images. >> >> > +99 > > >> - S >> >> -- >> View this message in context: >> http://forum.world.st/StartupPreferences-tp4639058.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

July 8, 2012

Re: [Pharo-project] On the frontpage of news.ycombinator.com

by Peter Hugosson-Miller

I tried, but it wouldn't let me log in, and I couldn't see any way of fixing that. Maybe I'll have better luck from a real computer later. -- Cheers, Peter. On 8 jul 2012, at 12:12, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Super! > > I just voted it up. > > On 08 Jul 2012, at 08:23, Marcus Denker wrote: > >> http://news.ycombinator.com/ >> >> Sunday morning... but nevertheless :-) >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > >

July 8, 2012

Re: [Pharo-project] On the frontpage of news.ycombinator.com

by Sven Van Caekenberghe

Super! I just voted it up. On 08 Jul 2012, at 08:23, Marcus Denker wrote: > http://news.ycombinator.com/ > > Sunday morning... but nevertheless :-) > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >

July 8, 2012

[Pharo-project] [update 2.0] #20194

by Marcus Denker

20194 ----- Issue 6304: [BUG]: Completion DNU in Inspector/Object Explorer for 2.0 http://code.google.com/p/pharo/issues/detail?id=6304 Issue 6301: Halts in image http://code.google.com/p/pharo/issues/detail?id=6301 Issue 6274: another step to remove StringHolder hierarchy element http://code.google.com/p/pharo/issues/detail?id=6274 -- Marcus Denker -- http://marcusdenker.de

July 8, 2012

Re: [Pharo-project] StartupPreferences

by Mariano Martinez Peck

On Sun, Jul 8, 2012 at 6:17 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Mariano, > > Can any of the script lookup logic from 2.0 be ported to 1.4? > Migrate everything (the new logic and all the last improvements) is too much. Mostly because I don't have time and because it is not a dead or alive bug. In fact, it was never before and people never complained ;) What you COULD do if you want is to just do this: > StartupPreferences doesn't seem very useful if only the image folder is > checked, Why it only searches in the image folder? buildActionList "First, we look at image folder, then we look at preferences folder, and finally at general preferences folder " ^ OrderedCollection new add: [ self lookInImageDirectory ]; add: [self lookInPreferencesFolder ]; add: [self lookInGeneralPreferencesFolder ]; yourself. it should check there (the version that is in 1.4). The only reason this version would stop searching in other places is if it did find something. When it finds something, it stops searching (in 2.0 it contiues and executes all the ones that are found). given that the initial use case was for working in many fresh > images. > > +99 > - S > > -- > View this message in context: > http://forum.world.st/StartupPreferences-tp4639058.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

July 8, 2012

[Pharo-project] pharo-2.0-tests Â» 32,mac - Build # 193 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 8, 2012