Stack version?

[Joe Lewis Wilkins]

> Bill, in my HC days, I made it a point to have a copyright field/ 
> announcement on the first card of every stack that I released to  
> others; that, when clicked on, provided an answer dialog with all  
> of my version info. Of course I wasn't distributing my stacks over  
> a very broad user base, and every time I made a modification to a  
> stack I updated the version number by merely command/shift/option/ 
> clicking on the copyright field. If the date was different than the  
> one stored in the field, the version number was incremented and the  
> date changed; otherwise it did nothing. If I wanted a major version  
> change I did that one by hand. Not very sophisticated, but it  
> worked well for me. Plus it was quite visible. If there were  
> multiple stacks involved, the change was scripted and posted to  
> them as well, though sometimes not visibly. This enabled me to do  
> lots of things, even checking on authorized (not licensed) users in  
> some cases.

Joe Wilkins

> On May 26, 2007, at 9:42 PM, Bill Vlahos wrote:
>
>> I was wondering how others deal with versionioning their stacks. I  
>> don't mean the standalones which already have version information  
>> but regular stacks.
>>
>> I have a stack that is opened by a standalone stub. The standalone  
>> won't change much but the program stack that is opened will. I  
>> want to be able to do updates from the Internet that essentially  
>> replaces the stack.
>>
>> To do this I need to standardize on a way to code a version number  
>> in the stack and then compare the version the user has with that  
>> on the web server. If the web server version is newer I want to  
>> give the user the ability to download the new version which would  
>> replace the old version.
>>
>> I can come up with a way to do this but I'm pretty sure there are  
>> more experienced Revolutionaries on this list have have thought  
>> this over already.
>>
>> Bill Vlahos
>> _______________________________________________