[Pharo-project] OSProcess and CommandShell in Pharo 2.0
I think we have it now: - ConfigurationOfOSProcess and ConfigurationOfCommandShell have been updated to work in 1.4 and 2.0 - Each config has been copied to its project repo (e.g. sqs/CommandShell). I was starting to get confused with all the locations (sqs/MetacelloRepository, xyz/MetaRepoForAbc, etc). I think it's a more sane model to keep the configs with the project and then mirror them as necessary. Metacello was designed to manage dialect dependencies, so there should be no need to fork a ConfigurationOfXyz. The only issue we have is when we don't have access to the project's repo, for which it'd be great if we implement per-project inboxes ( maybe in StHub, hint, hint ;) ) Anyway, thanks to David and Steph for all the hard work getting this working. OSP and CommandShell are vitally important projects and it's great to know that they will continue working well in Pharo for the foreseeable future :) -- View this message in context: http://forum.world.st/OSProcess-and-CommandShell-in-Pharo-2-0-tp4669674.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Got the configuration to load in the latest 2.0. But when doing and edit test and doing a save, there is an error occuring. See screenshot. Hey, CommandShell is ubercool! Phil 2013/2/13 Sean P. DeNigris <sean@clipperadams.com>:
I think we have it now: - ConfigurationOfOSProcess and ConfigurationOfCommandShell have been updated to work in 1.4 and 2.0 - Each config has been copied to its project repo (e.g. sqs/CommandShell). I was starting to get confused with all the locations (sqs/MetacelloRepository, xyz/MetaRepoForAbc, etc). I think it's a more sane model to keep the configs with the project and then mirror them as necessary. Metacello was designed to manage dialect dependencies, so there should be no need to fork a ConfigurationOfXyz. The only issue we have is when we don't have access to the project's repo, for which it'd be great if we implement per-project inboxes ( maybe in StHub, hint, hint ;) )
Anyway, thanks to David and Steph for all the hard work getting this working. OSP and CommandShell are vitally important projects and it's great to know that they will continue working well in Pharo for the foreseeable future :)
-- View this message in context: http://forum.world.st/OSProcess-and-CommandShell-in-Pharo-2-0-tp4669674.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Thanks a lot Sean! Dave On Wed, Feb 13, 2013 at 07:16:25AM -0800, Sean P. DeNigris wrote:
I think we have it now: - ConfigurationOfOSProcess and ConfigurationOfCommandShell have been updated to work in 1.4 and 2.0 - Each config has been copied to its project repo (e.g. sqs/CommandShell). I was starting to get confused with all the locations (sqs/MetacelloRepository, xyz/MetaRepoForAbc, etc). I think it's a more sane model to keep the configs with the project and then mirror them as necessary. Metacello was designed to manage dialect dependencies, so there should be no need to fork a ConfigurationOfXyz. The only issue we have is when we don't have access to the project's repo, for which it'd be great if we implement per-project inboxes ( maybe in StHub, hint, hint ;) )
Anyway, thanks to David and Steph for all the hard work getting this working. OSP and CommandShell are vitally important projects and it's great to know that they will continue working well in Pharo for the foreseeable future :)
-- View this message in context: http://forum.world.st/OSProcess-and-CommandShell-in-Pharo-2-0-tp4669674.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
participants (3)
-
David T. Lewis -
phil＠highoctane.be -
Sean P. DeNigris