[futurebasic] Re: [FB] Observed Version Tracker Problem

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : August 2004 : Group Archive : Group : All Groups

From: tedd <tedd@...>
Date: Sun, 22 Aug 2004 18:59:14 -0400
Scott:

-snip- FB version/name problem.

>Clear as mud?  I vote for the return to the good old days when 
>version numbers where not mixed up in the name...

Okay, your addressing one of the problems I see. It would be my guess 
that version numbers and application names should not be mixed -- 
even in the "new way" of doing things (excluding the "old style").

As I see it, in the property list (plist) there are key tags for both 
CFBundleName (which should be the name of the application) and 
CFBundleShortVersionString (which should be the version number) -- 
wouldn't that be a correct assessment?

However, if one takes the application "FutureBASIC [Carbon]" and 
tries to inspect the "contents" (Show Package Contents) you'll find 
none -- is that they way it's supposed to be? Or was this application 
not supposed to have a "contents" folder like other applications?

It's confusing -- but, the plist may provide relief, if understood 
and applied correctly.

In the plist, there are a large assortment of key tags -- most I've 
seen start with a CF prefix (i.e., CFBundleDevelopmentRegion = 
"English" and so on). I think we need to address each tag to find out 
what it means and when to use it. While it may be easy to understand 
that CFBundlePackageType = "APPL" and CFBundleSignature = <creator 
code>, I am clueless as to what CFBundleInfoDictionaryVersion, or 
CFBundleTypeMIMETypes, mean as well as many other key-tag names.

Also, I have observed that there are still other key tags that appear 
to be custom (i.e., BuildVersion, SourceVerson, ProjectName and so 
on). Likewise, I think we need (or at least I do) need to address 
these and know what they mean.

Furthermore, which of these tags are actually needed in an 
application, and why. If you look at Safari, you'll find very few 
tags in its version plst, but many tags in its info.plst , which 
answer my previous question to Ken as to if an application can have 
more than one plist -- clearly it can have more than one.

The plist appears to have many avenues for investigation -- perhaps 
too many, and thus adding even more to my confusion.

Thanks for taking a shot at it.

tedd
-- 
--------------------------------------------------------------------------------
http://sperling.com/