Best Update Standalone Scenario

[Sivakatirswami]

Aloha, Chipp and Mark:

Excellent, thanks... I have copied Chipps scenario to my own  
knowledge base.

Two questions:

1)  How do you handle the Splash Screen-Engine-Player after the  
MainStack is opened... set it to invisible? Just let it sit in the  
background behind everything? I would guess the former, which is more  
normal UI behavior (I mean there is no Splash screen present in the  
visible GUI once the user opens an MS word document, or any Adobe  
document either...)

2) Marie Signe recently said the special folder path to /Application  
Data/ on Windows was (26)... this email say (35) ....

Looking at the MSDN site we see:

CSIDL_APPDATA (0x001a)
     Version 4.71. The file system directory that serves as a common  
repository for application-specific data. A typical path is C: 
\Documents and Settings\username\Application Data. This CSIDL is  
supported by the redistributable Shfolder.dll for systems that do not  
have the Microsoft Internet Explorer 4.0 integrated Shell installed.

= specialFolderPath(26)

CSIDL_CDBURN_AREA (0x003b)
     Version 6.0. The file system directory acting as a staging area  
for files waiting to be written to CD. A typical path is C:\Documents  
and Settings\username\Local Settings\Application Data\Microsoft\CD  
Burning.

= specialFolderPath(59)

CSIDL_COMMON_APPDATA (0x0023)
     Version 5.0. The file system directory containing application  
data for all users. A typical path is C:\Documents and Settings\All  
Users\Application Data.

= specialFolderPath(35)

Aside query about Windows systems... why are two different ones for

C:\Documents and Settings\username\Application Data
and
C:\Documents and Settings\username\Local Settings\Application Data\)

??
What should we use and why?

Sivakatirswami






theOn Oct 22, 2005, at 7:32 AM, Mark Wieder wrote:

> Chipp-
>
> Friday, October 21, 2005, 10:56:24 PM, you wrote:
>
>
>> Check out
>> http://lists.runrev.com/pipermail/use-revolution/2003-August/ 
>> 021590.html
>>
>
> The only things I would add to Chipp's excellent writeup are:
>
> I have an aversion to apps that "phone home" on their own at startup,
> so I leave this as an option for the users to check for updated
> versions on their own. There are obviously cases, though, where you do
> want the automatic checks to occur at startup.
>
> And the "splash screen" approach to segmenting your program also has a
> couple of advantages that Chipp didn't metion: a) since the process of
> creating a standalone binds the engine to the mainstack, this then
> gets attached to the splash screen, making updates much smaller and
> faster downloads; and b) the user perception of the smaller download
> is that you're not really giving them a whole new application (you may
> be), but that it's a minor update, making them feel better about
> updating the app.
>
> -- 
> -Mark Wieder
>  mwieder at ahsoftware.net
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>