The GWToolkit CheckForUpdate object has ScriptVersion and UpdateURL
properties. You copy that object and set those in your script's local
copy to the current version and location of the script info XML. I don't
know about the update check in the add/remove dialog though, it works
with apps disabled so I'm presuming it doesn't use the toolkit.
On 5/8/2011 12:15 PM, Jacob Schmude wrote:
Hi Chip
No, but the user-defined check routines do one important thing, and
that is tell the update code the URL. However, the way most scripts
are written, this isn't done *until* the ini is checked and, since
there's no way for the GW Toolkit to automatically grab the update
URL, there is something in the middle that I'm not understanding, and
I need to. Clearly it does not use the ini check, yet how is it able
to get the appropriate script update URL in such scripts that do not
expose it unless the ini conditions are met? Do you see what I'm
trying to understand?
On 5/8/2011 07:55, Chip Orange wrote:
Jacob,
well, I'm pretty sure it's skipping the .ini file check, and in VBS
code you'll see that's not built into the check for update
functionality of the GW toolkit object, but left up to the .vbs file
to do for itself. There's no need for the "Add or Remove apps" to
check in the .ini file to see about automatic updates as the user
just instructed it to go check. the only other time it checks is
when the app itself does the checking, and that's when the .ini comes
into play.
As for where to get the update from ... that indeed would have to be
using app central as you too guessed ... there just isn't any other
information it would have access to. If you don't want to use app
central then the app of course could handle things itself, but it's a
shame you can't get WE to handle it here or at least disable it
altogether so it wouldn't incorrectly tell the user there's no
update. but we'd need a change in the package manager and the .wepm
format for it to be able to do anything like that ... or maybe some
redirection type of functionality on the part of app central so it
could be told to go get the xml for the update from some other
address if you didn't want to store the updates there on app
central. I guess that's what this is about, not storing them on app
central?
Chip
------------------------------------------------------------------------
*From:* Jacob Schmude [mailto:[email protected]]
*Sent:* Saturday, May 07, 2011 9:56 PM
*To:* [email protected]
*Subject:* Re: Package manager update question
Hi Chip
It's what I'm supposing as well, but I need to know for sure. The
trouble with that line of reasoning is that, when most CheckForUpdate
functions are written, they read the ini file of the script in
question to determine whether updates should be checked on script's
start or not. Yet, the add/remove update function runs through
scripts and successfully checks for updates even when there is no ini
file for the script in question and works even while the script is
already running. That suggests to me that it might be calling the
check for update code, but is somehow either using its own method or
else is faking the ini file event for that update check. If it's
using its own method, I need to understand how it gets the script's
URL (since that's exposed in the function written within the script).
I may need to do some internal script hosting, so I need to
understand exactly how this works so that all update functions will
point to the server they'll have to use. Hopefully it's not
hard-wired to check app central somehow.
Thanks
On 5/7/2011 16:08, Chip Orange wrote:
Hi Jacob,
I don't think it's documented anywhere; but I'd be surprised if it
didn't just run through the list of your installed apps, and do the
equivalent of check for update from the GW toolkit on each of them,
accumulating a single list however to present to you at the end,
rather than a series of update announcements.
Is this what you were looking for?
Chip
------------------------------------------------------------------------
*From:* Jacob Schmude [mailto:[email protected]]
*Sent:* Friday, May 06, 2011 11:21 PM
*To:* [email protected]
*Subject:* Package manager update question
Hi, all
I'm new to Window-Eyes app development, but not new to programming
in general. I have a quick question about the package manager. How
does the package manager check for updates? I've read the docs for
GW Toolkit, and I understand how the CheckForUpdates object works.
What I don't understand is how the package manager itself checks for
updates. Does it fire off a CheckForUpdates sequence on each app, or
does it work via some other method and where do I find docs for it
if it doesn't use the GW Toolkit?
Thanks
