PDA

View Full Version : Download Update option



David Martinko
31-May-2005, 08:36 AM
I'ld like to see an option in the studio to check for updates for installed
components and allow for optional download.

I think it should resemble the product registration program... and list all
updates available. A user should not be forced to upgrade to the latest
(especially since the latest may still be a beta). Updates are for the
current version of each product, so a registration for VDF 9 does not tell
you and update is available because VDF 10 is out there. It should only
notify if updates for VDF 9 are available.

All that should be needed is a webservice. I would open my IDE, goto the
Help menu and select Check for Updates. The IDE would generate an XML
document of all VDF registrations on my PC (same thing that appears in the
product registration). This is transmitted to DAC via a webservice. The
returned XML document is modified to list all product updates available for
download, including the path to each download. A list of these updates are
displayed to the user who can then decide to install all updates, a few, or
none.

If possible, the list might also display which updates are a part of the
developer's subscription model and which aren't (using the serial number, I
imagine).

Since this would be a program launched from the IDE, and not a part of the
IDE, it could be redistributable to end-users to make sure their RC is
up-to-date. If a client's machine wasn't working properly with the latest
install, I could have then run the Check for Updates program to make sure
they have the latest client runtime.

Any thoughts?

--
David Martinko
Redeemed Software
248-535-7495
RedeemedSoftware(SHIFT+2)Hotmail(PERIOD)com
www.redeemedsoftware.com

Anders Öhrt
31-May-2005, 10:16 AM
> I'ld like to see an option in the studio to check for updates for
> installed
> components and allow for optional download.
>
> I think it should resemble the product registration program... and list
> all updates available. A user should not be forced to upgrade to the
> latest (especially since the latest may still be a beta). Updates are for
> the current version of each product, so a registration for VDF 9 does not
> tell you and update is available because VDF 10 is out there. It should
> only notify if updates for VDF 9 are available.

But there are almost never any updates, atleast not yet. I remember VDF
having a service pack, and there is a WinPrint update to 10.1, but that
doesn't seem to be enough things to update to warrent a check for it.

// Anders

Chris Spencer
31-May-2005, 05:14 PM
David

I would not like to see DAWs resources funnelled of to do this.
Updates don't come from DAW at such a pace that it is difficult to keep up.
A simple note in the NG is all that is required.

However on the topic of updates I would prefer to see resources now spent on
runtime and bug issues that effect the end-user applications.
I am happy to work within the development environment as it is now.

DAW have in place a client subscription model and to make that attractive
(and saleable) to end-users the end-user needs to see that paying there $$$s
gets them some benefit. All the fixes and improvements in the development
environment amount to zero for the end-user. (There can be the argument that
better tools means better response to users but at the end of the day the
user does not see anything.)

Things that the client sees are like in the last release richEdit classes
etc. I would like to see the developmenyt in these areas. There are many
more data presentation tools and classes that could be provided to make the
end-users experience a good one

Chris Spencer
TUFware Systems

"David Martinko" <RedeemedSoftware@Hotmail.com> wrote in message
news:Xq8RSXeZFHA.1312@dacmail.dataaccess.com...
> I'ld like to see an option in the studio to check for updates for
> installed components and allow for optional download.
>
> I think it should resemble the product registration program... and list
> all updates available. A user should not be forced to upgrade to the
> latest (especially since the latest may still be a beta). Updates are for
> the current version of each product, so a registration for VDF 9 does not
> tell you and update is available because VDF 10 is out there. It should
> only notify if updates for VDF 9 are available.
>
> All that should be needed is a webservice. I would open my IDE, goto the
> Help menu and select Check for Updates. The IDE would generate an XML
> document of all VDF registrations on my PC (same thing that appears in the
> product registration). This is transmitted to DAC via a webservice. The
> returned XML document is modified to list all product updates available
> for download, including the path to each download. A list of these updates
> are displayed to the user who can then decide to install all updates, a
> few, or none.
>
> If possible, the list might also display which updates are a part of the
> developer's subscription model and which aren't (using the serial number,
> I imagine).
>
> Since this would be a program launched from the IDE, and not a part of the
> IDE, it could be redistributable to end-users to make sure their RC is
> up-to-date. If a client's machine wasn't working properly with the latest
> install, I could have then run the Check for Updates program to make sure
> they have the latest client runtime.
>
> Any thoughts?
>
> --
> David Martinko
> Redeemed Software
> 248-535-7495
> RedeemedSoftware(SHIFT+2)Hotmail(PERIOD)com
> www.redeemedsoftware.com
>
>
>

wila
1-Jun-2005, 02:45 AM
Hear hear!

I completely agree with Chris.

--
Wil

Chris Spencer wrote:
> David
>
> I would not like to see DAWs resources funnelled of to do this.
> Updates don't come from DAW at such a pace that it is difficult to keep up.
> A simple note in the NG is all that is required.
>
> However on the topic of updates I would prefer to see resources now spent on
> runtime and bug issues that effect the end-user applications.
> I am happy to work within the development environment as it is now.
>
> DAW have in place a client subscription model and to make that attractive
> (and saleable) to end-users the end-user needs to see that paying there $$$s
> gets them some benefit. All the fixes and improvements in the development
> environment amount to zero for the end-user. (There can be the argument that
> better tools means better response to users but at the end of the day the
> user does not see anything.)
>
> Things that the client sees are like in the last release richEdit classes
> etc. I would like to see the developmenyt in these areas. There are many
> more data presentation tools and classes that could be provided to make the
> end-users experience a good one
>
> Chris Spencer
> TUFware Systems
>
> "David Martinko" <RedeemedSoftware@Hotmail.com> wrote in message
> news:Xq8RSXeZFHA.1312@dacmail.dataaccess.com...
>
>>I'ld like to see an option in the studio to check for updates for
>>installed components and allow for optional download.
>>
>>I think it should resemble the product registration program... and list
>>all updates available. A user should not be forced to upgrade to the
>>latest (especially since the latest may still be a beta). Updates are for
>>the current version of each product, so a registration for VDF 9 does not
>>tell you and update is available because VDF 10 is out there. It should
>>only notify if updates for VDF 9 are available.
>>
>>All that should be needed is a webservice. I would open my IDE, goto the
>>Help menu and select Check for Updates. The IDE would generate an XML
>>document of all VDF registrations on my PC (same thing that appears in the
>>product registration). This is transmitted to DAC via a webservice. The
>>returned XML document is modified to list all product updates available
>>for download, including the path to each download. A list of these updates
>>are displayed to the user who can then decide to install all updates, a
>>few, or none.
>>
>>If possible, the list might also display which updates are a part of the
>>developer's subscription model and which aren't (using the serial number,
>>I imagine).
>>
>>Since this would be a program launched from the IDE, and not a part of the
>>IDE, it could be redistributable to end-users to make sure their RC is
>>up-to-date. If a client's machine wasn't working properly with the latest
>>install, I could have then run the Check for Updates program to make sure
>>they have the latest client runtime.
>>
>>Any thoughts?
>>
>>--
>>David Martinko
>>Redeemed Software
>>248-535-7495
>>RedeemedSoftware(SHIFT+2)Hotmail(PERIOD)com
>>www.redeemedsoftware.com
>>
>>
>>
>
>
>