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

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

by Marcus Denker

http://news.ycombinator.com/ Sunday morning... but nevertheless :-) Marcus -- Marcus Denker -- http://marcusdenker.de

July 8, 2012

Re: [Pharo-project] ConfigurationOfPharoVM

by Dale Henrichs

Stef, Good question. An import of a baseline from a version is recommended. A baseline should have no imports. So chaining involves importing a baseline from another baseline or a version fron another version. I admit that I am guilty of chaining and there are probably examples of chaining in the early versions of Metacello, but I found over time that when I wanted to restructure a project that had been chained I spent a fair amount of time "collapsing the chain" ... it gets even more difficult when you try to "collapse the chain" in someone else's project:) Dale ----- Original Message ----- | From: "Sean P. DeNigris" <sean(a)clipperadams.com> | To: pharo-project(a)lists.gforge.inria.fr | Sent: Saturday, July 7, 2012 8:11:51 PM | Subject: Re: [Pharo-project] ConfigurationOfPharoVM | | | Dale Henrichs wrote | > | > So I recommend against chaining... | > | | Does chaining mean importing a version into another version, or the | x.x-x | thing? | | -- | View this message in context: | http://forum.world.st/ConfigurationOfPharoVM-tp4639007p4639052.html | Sent from the Pharo Smalltalk mailing list archive at Nabble.com. | |

July 8, 2012

[Pharo-project] StartupPreferences

by Sean P. DeNigris

Mariano, Can any of the script lookup logic from 2.0 be ported to 1.4? StartupPreferences doesn't seem very useful if only the image folder is checked, given that the initial use case was for working in many fresh images. - S -- View this message in context: http://forum.world.st/StartupPreferences-tp4639058.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 8, 2012

Re: [Pharo-project] Bug fix to review for Summer Release

by Sean P. DeNigris

Sean P. DeNigris wrote > > Please someone take <<5 min to review this fix > Here's another easy one: Issue 6305: StartupPreferences "run once" broken Status: FixReviewNeeded Type-Bug Milestone-1.4 Pharo1.4 Latest update: #14451 Fix in inbox: SLICE-Issue-6305-StartupPreferences-run-once-broken-SeanDeNigris.1 Port StartupAction>>execute from Pharo 2.0, which seems to be working. Manually tested in 1.4 with: | item1 item2 | item1 := StartupAction name: 'Open Help' code: 'Workspace openContents: ''Here is just an example of how to use the StartupLoader. I should only be displayed once. You can also see StartupLoader class>>#example'' label: ''Help''' runOnce: true. item2 := StartupAction name: 'Open Workspace' code: [ Workspace openContents: 'I should be displayed each time' ]. " StartupLoader default addAtStartup: {item1. item2}." FileLocator imageDirectory ensureDirectory / StartupLoader default startupScriptName fileStreamDo: [ :str | str nextPutAll: (StartupLoader default buildStreamFor: {item1. item2}) ]. StartupLoader default loadStartupScript. StartupLoader default loadStartupScript. -- View this message in context: http://forum.world.st/Bug-fix-to-review-for-Summer-Release-tp4639053p463905… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 8, 2012

[Pharo-project] Bug fix to review for Summer Release

by Sean P. DeNigris

Please someone take <<5 min to review this fix so we can avoid ugly DNUs in our release... Issue 6303: [BUG]: Completion DNU in Inspector/Object Explorer for 1.4 http://code.google.com/p/pharo/issues/detail?id=6303 Status: FixReviewNeeded To reproduce: 1. DoIt: "Morph new explore" 2. In the bottom pane of the explorer, type "bounds s" You will get a DNU #guessTypeForName: Fix in inbox: Name: SLICE-Issue-6303-BUG-Completion-DNU-in-InspectorObject-Explorer-for-14-SeanDeNigris.1 Implement very basic #guessTypeForName: in ObjectExplorer and Inspector to avoid DNUs during code completion -- View this message in context: http://forum.world.st/Bug-fix-to-review-for-Summer-Release-tp4639053.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 8, 2012

Re: [Pharo-project] ConfigurationOfPharoVM

by Sean P. DeNigris

Dale Henrichs wrote > > So I recommend against chaining... > Does chaining mean importing a version into another version, or the x.x-x thing? -- View this message in context: http://forum.world.st/ConfigurationOfPharoVM-tp4639007p4639052.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 8, 2012

Re: [Pharo-project] ConfigurationOfPharoVM

by Dale Henrichs

Keep in mind the fact that if you chain baselines or versions in this way, it is very difficult for humans to understand just what they are getting. It also makes it harder for tools to do the right thing as well ... So I recommend against chaining... Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <marianopeck(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Saturday, July 7, 2012 3:28:22 PM | Subject: Re: [Pharo-project] ConfigurationOfPharoVM | | | | | On Sat, Jul 7, 2012 at 9:03 PM, Sean P. DeNigris < | sean(a)clipperadams.com > wrote: | | | I noticed the versions vary between x.x.x and x.x-x and that some of | the | versions import baselines and others import other versions. I've | never seen | it done like that... what's the intention? | | | | Usually, a version imports a baseline. However, imagine that you have | several packages/projects and between version X and Y only changed a | few packages. | Instead of having to re-put all versions of all packages in Y, you | make Y import X and you just change the ones you want. | | | | e.g. | "Baseline with dot imported by version with dash" | version145: spec | <version: '1.4-5' imports: #('1.4.1-baseline')> | | "version importing another version" | version143: spec | <version: '1.4-3' imports: #('1.4-2')> | | Cheers, | Sean | | -- | View this message in context: | http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html | Sent from the Pharo Smalltalk mailing list archive at Nabble.com. | | | | | -- | Mariano | http://marianopeck.wordpress.com | |

July 8, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by Sean P. DeNigris

EstebanLM wrote > > mmm... probably, but PharoVM needs an update too Please check this carefully. The changes are simple, but I'm not sure I fully understand the standard procedure here. Issue 6302: Update OSProcess Plugin http://code.google.com/p/pharo/issues/detail?id=6302 Fix in inbox: SLICE-Issue-6302-Update-OSProcess-Plugin-SeanDeNigris.1 ConfigurationOfCog * v. 4.7 - bless as release * v. 4.8 - bless as release (will be used by updated ConfigurationOfPharoVM) - merge in changes from v. 4.9 - import v. 4.7 instead of baseline and remove duplication * v. 4.9 - remove ConfigurationOfPharoVM - change stable version for #'pharo1.4.x' to version: '2.0-2', which loads v. 4.8 of ConfigurationOfCog Sean p.s. I forgot to mention in the commit comment that 4.8 updates the OSProcess plugin to 4.4.11 -- View this message in context: http://forum.world.st/OSProcess-test-failures-in-Pharo-1-4-tp4638907p463904… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 8, 2012

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

by Sean P. DeNigris

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] [ANN]: Vim Shortcuts for Nautilus (Proof-of-concept)

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > > Those methods detach* has been moved from extension directly into KM. > They are still extension methods in 20193 (and seem to be broken) Issue 6300: Detach keymaping shortcuts http://code.google.com/p/pharo/issues/detail?id=6300 Nautilus has Morph>>detach*KeymapCategory* extension methods. These are generally useful and should be moved from Nautilus to KM Also, they are broken... Morph>>detachKeymapCategory: signals MessageNotUnderstood: KMDispatcher>>detachKeymapCategory: -- 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