Page 1 of 1
Importing SysStats stuff to AveScripter
#1
Posted 19 November 2005 - 08:26 AM
#2
Posted 19 November 2005 - 11:43 AM
Thanks to the ObjectModel property of the Desklet object, you can tap into the SysStats object model from any COM enabled desklet or effectlet.
However, AveScripter does not seem to export this at the moment.
As a rule of thumb, I'd recommend to keep it going as is. AveScripter may have a great potential but its too early to port such a huge thing from scratch. Your 'tenfold' may look a bit smaller from the distance...
For the config import, I doubt there is an easy solution. If you find out the whereabouts you even may re-use the non-UI meters and stuff from SysStats within AveScripter so that you can move away painlessly, if you really must.
However, AveScripter does not seem to export this at the moment.
As a rule of thumb, I'd recommend to keep it going as is. AveScripter may have a great potential but its too early to port such a huge thing from scratch. Your 'tenfold' may look a bit smaller from the distance...
For the config import, I doubt there is an easy solution. If you find out the whereabouts you even may re-use the non-UI meters and stuff from SysStats within AveScripter so that you can move away painlessly, if you really must.
#4
Posted 19 November 2005 - 02:56 PM
herd said:
Thanks to the ObjectModel property of the Desklet object, you can tap into the SysStats object model from any COM enabled desklet or effectlet.
However, AveScripter does not seem to export this at the moment.
As a rule of thumb, I'd recommend to keep it going as is. AveScripter may have a great potential but its too early to port such a huge thing from scratch. Your 'tenfold' may look a bit smaller from the distance...
For the config import, I doubt there is an easy solution. If you find out the whereabouts you even may re-use the non-UI meters and stuff from SysStats within AveScripter so that you can move away painlessly, if you really must.
However, AveScripter does not seem to export this at the moment.
As a rule of thumb, I'd recommend to keep it going as is. AveScripter may have a great potential but its too early to port such a huge thing from scratch. Your 'tenfold' may look a bit smaller from the distance...
For the config import, I doubt there is an easy solution. If you find out the whereabouts you even may re-use the non-UI meters and stuff from SysStats within AveScripter so that you can move away painlessly, if you really must.
SOB.... hmmm missed that API when I did the SDK. I've just added it in so the Interface the scripter will be accessed by ObjectModel property. There was no reason to hide it. It was just a lost API when I did the SDK for Delphi.
BTW Herd, I Forgot to say hi on MSN yesterday, was in a meeting all day.
#5
Posted 19 November 2005 - 03:24 PM
Given all the above you should be able to manipulate a SysStats desklet from an AveScripter desklet any way you'd like. Everything that SysStats can do is exposed via COM and documented in the script documentation.
Of course the reverse is also true. Now that PCM has made his Object Model available to AveDesk you should be able to manipulate an AveScripter desklet anyway you like from within a SysStats script.
Of course the reverse is also true. Now that PCM has made his Object Model available to AveDesk you should be able to manipulate an AveScripter desklet anyway you like from within a SysStats script.
Page 1 of 1








Sign In »
Register Now!
Help

MultiQuote