Hi Igor, I think it is good to make OSPP (and AioPlugin and XDisplayControlPlugin where appropriate) available in all distributed VMs, but in some applications they provide too much access to the operating system, so it is good to have them as external modules so that people who do not want them on the system can delete the modules. So I think it is best to treat it like FFI, it is there if you want it but can be removed if you are doing some sort of application where the user should not have easy access to the OS functions. Dave On Sat, Mar 12, 2011 at 11:54:16PM +0100, Igor Stasenko wrote:
David, i don't remember the outcome of last discussion about it, but i heard some people proposed to add the OSProcess plugin to be built as internal one. Or at least ship it with every VMs, same as FFI plugin.
On 12 March 2011 20:53, David T. Lewis <lewis@mail.msen.com> wrote:
On Sat, Mar 12, 2011 at 11:34:11AM -0800, nullPointer wrote:
Please, I need know the actual status of OSProcess; what I can wit it and cannot:
-Works in main platforms? Mac, Windows Linux? works of same way on all places?
OSProcess works on unix platforms, including Mac and Linux. Windows support is incomplete.
-I could execute external executable files? -I could execute commandline tools?
Yes. You should also load CommandShell in addition to OSProcess.
-Which will be the next steps of development?
Well I probably should get Windows support working one of these days ;)
-OsProcess will be integrated in Core?
No, OSProcess and CommandShell are external packages.
-Exists some place with deep doc?
See class CommandShell, method category "documentation" on the class side, as well as class and method comments throughout. Many classes provide examples, and the unit tests may be helpful for understanding usage.
Additional information is at:
http://wiki.squeak.org/squeak/708 http://wiki.squeak.org/squeak/1914 http://wiki.squeak.org/squeak/2153 http://wiki.squeak.org/squeak/6023
Dave
-- Best regards, Igor Stasenko AKA sig.