Stephen W. Meeley
1-Jun-2005, 09:35 AM
Chris (and others),
Do you have a list of specific bugs that you feel fall into the category
of "bug issues that effect the end-user applications"? I understand that
there are lots of additions or changes that you (and others) will feel
have tremendous end-user impact, and I'm not trying to ignore those
types of things at all.
I just want to start a specific conversation focused on known bugs that
you feel would "get them (them being end-users) some benefit".
Once I get a good handle on which bugs can give the end-user impact you
are looking for (and we do want to provide), we can move on to other
areas.
I will add one thing: keep in mind that many of the changes we make that
may seem at first blush to be more development oriented are really there
in support of the changes we (and developers) make (or want to make)
that will have tremendous end-user impact. The underlying development
system needs to be solid and critical technologies need to be supported
in order to have the building blocks necessary to take advantage of
what's out there. FlexCOM and Web Services (and then the addition of
struct and array support in both those areas) are great examples of
this. They don't give you a specific new control to use, they open up
entire new worlds to you (and us too).
In any case, let's take this "how to get end-user impact" discussion
forward, starting with bugs.
Best regards,
-SWM-
-----Original Message-----
From: Chris Spencer [mailto:nomail@nomail.com]
Posted At: Tuesday, May 31, 2005 6:14 PM
Posted To: product-direction
Conversation: Download Update option
Subject: Re: Download Update option
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
>
>
>
Do you have a list of specific bugs that you feel fall into the category
of "bug issues that effect the end-user applications"? I understand that
there are lots of additions or changes that you (and others) will feel
have tremendous end-user impact, and I'm not trying to ignore those
types of things at all.
I just want to start a specific conversation focused on known bugs that
you feel would "get them (them being end-users) some benefit".
Once I get a good handle on which bugs can give the end-user impact you
are looking for (and we do want to provide), we can move on to other
areas.
I will add one thing: keep in mind that many of the changes we make that
may seem at first blush to be more development oriented are really there
in support of the changes we (and developers) make (or want to make)
that will have tremendous end-user impact. The underlying development
system needs to be solid and critical technologies need to be supported
in order to have the building blocks necessary to take advantage of
what's out there. FlexCOM and Web Services (and then the addition of
struct and array support in both those areas) are great examples of
this. They don't give you a specific new control to use, they open up
entire new worlds to you (and us too).
In any case, let's take this "how to get end-user impact" discussion
forward, starting with bugs.
Best regards,
-SWM-
-----Original Message-----
From: Chris Spencer [mailto:nomail@nomail.com]
Posted At: Tuesday, May 31, 2005 6:14 PM
Posted To: product-direction
Conversation: Download Update option
Subject: Re: Download Update option
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
>
>
>