var output = widget.system( "/path/to/command", null ).outputString;
On Aug 25, 2006, at 7:57 AM, Niels Meersschaert wrote:
Have you tried running the command outside of the Dashboard environment? Is the performance poor there too? Perhaps the command itself is the problem. Alternatively, you could call the command asynchronously from the widget, so that the command won't block further execution of the widget. You need to register a handler to be called on completion.
We are strongly recommending that ALL widget.system calls be asynchronous. Only use synchronous widget.system for development, if you must at all.
Christian.
