On Sep 29, 2008, at 6:32 pm, Joe Strout wrote:
On Sep 29, 2008, at 3:58 PM, Dennis Birch wrote:
You could write a correct info.plist file and then add it to your
app's bundle with an IDE build script. I do that for setting Help
information in my applications. It's a little more work to keep the
file updated with version changes, but it's the only way I know of
handling that short of hand-editing the file each time you build your
application.
Hmm... it used to be you could create a 'plst' #0 resource in a
resource file, and drag this into your project, and it would get
used instead of the auto-generated plist (even for bundled apps
where the plist is a file rather than a resource). But of course
that probably only works on Macs, and it's been such a long time
since I tried it, I don't know whether it still works at all.
A sensible feature request would be for the IDE to check for a text
file in your project called exactly "info.plist", and if found, use
that instead of the auto-generated one.
I requested something like that a while ago, except what I was asking
for was an IDE editor for the Info.plist file. I was thinking of an
interface that would show what RB was intending to insert and then
having a way to add our own tags.
This problem of the DOCTYPE bothers me though. I wonder if there are
other side-effects that we don't know about yet.
Greg O'Lone
Stretched Out Software
--------------------------
Excellence Through Innovation
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|