Runtime as Mac OS X App Bundle?

[rrr]

Anyone have any tips or methods in regards to packing an FMP runtime solution into a single Mac OS X app bundle (for the purposes of easy launching, distribution, etc?)

ie: packing the .usr solution file, the runtime application the Extensions folder, and even the FMP Acknowledgements pdf, I guess, into a single double-clickable bundle?

Is this possible? Unadvisable? Any insight?

Thanks,

rrr

[bruceR]

Yes, it's possible, I've done it myself. Even created a runtime as a background process! Busy, can't supply more details at the moment.

Bruce

[rrr]

Yeah, ideally, I would be able to embed the .usr file(s) and the Extensions folder right inside of the existing runtime app bundle, but I don't know how to get the runtime app bundle to look for those resources inside of itself, instead of its parent directory. It may not be possible to go that route, but surely there is a decent way to bundle all of those resources together into a single double-clickable entity.

Rusty

[fmbiz.net]

Hi Rusty,

This is actually much easier to do on a Mac than on Windows. I currently use Iceberg with XCode Developer tools. You can download XCode from Apple's Developer tools website and you can get Iceberg from this link, http://www.versiontracker.com/dyn/moreinfo/macosx/22849.

Once you get comfortable with the options available it is a straight forward process of configuring your Install, everything from Install Scripts to the individual files you need to package. All completely free!

Best Regards,

FMBiz.net

[rrr]

Thanks, although I believe Iceberg is used to create an installer package, and this is not really what I am trying to do.

Rather, I am simply trying to wrap the solution file (.usr) and Extensions folder into the runtime's application bundle, so that the whole shebang can be treated by the user as a single, double-clickable entity.

[MickMc]

It's not elegant, but I created an second application bundle using applescript editor that can open an application placed inside of it.

Below is the code for the applescript. Just change the one line in the script, then save it as an application, and lastly open the new application bundle and drag your runtime solution folder in to the top level of the new bundle. I can't take credit for this--I found the script here

http://macosx.com/forums/mac-os-x-system-mac-software/303487-using-applescript-open-file.html

NOTE: Make sure to separate the folder and file name of your runtime solution with a colon and not a slash.

--Applescript

-- Mac path to a hidden script file in the bundle. CHANGE THE NEXT LINE TO MATCH YOUR RUNTIME FOLDER AND APP NAME

set hiddenscriptpath to (((path to me) as text) & "Folder Name:filemaker runtime app name.app")

-- Converting the Mac path to a Posix path

set hiddenscriptpath to POSIX path of hiddenscriptpath

-- Quoting the Posix path

set qtdhiddenscriptpath to quoted form of hiddenscriptpath

-- executing the script file

try

set command to "open " & qtdhiddenscriptpath

display dialog qtdhiddenscriptpath

do shell script command

end try

[rrr]

Thanks so much, MickMc. This is exactly what I was looking for. I was beginning to consider approaching this problem with AppleScript, and your contribution does exactly what I need. Very helpful.

[bruceR]

Alternately, you can create the simple applescript app bundle as previously mentioned, but view package contents and set it up like this. Double click the info.plist file and set the application executable reference as shown. In my case:

ToDo.app/Contents/MacOS/Runtime

[Ocean West]

I haven't tried it with a runtime, but this may work? http://fmforums.com/forum/showtopic.php?tid/213830/

[hugh71158]

It's not elegant, but I created an second application bundle using applescript editor that can open an application placed inside of it.

Below is the code for the applescript. Just change the one line in the script, then save it as an application, and lastly open the new application bundle and drag your runtime solution folder in to the top level of the new bundle. I can't take credit for this--I found the script here

http://macosx.com/forums/mac-os-x-system-mac-software/303487-using-applescript-open-file.html

NOTE: Make sure to separate the folder and file name of your runtime solution with a colon and not a slash.

--Applescript

-- Mac path to a hidden script file in the bundle. CHANGE THE NEXT LINE TO MATCH YOUR RUNTIME FOLDER AND APP NAME

set hiddenscriptpath to (((path to me) as text) & "Folder Name:filemaker runtime app name.app")

-- Converting the Mac path to a Posix path

set hiddenscriptpath to POSIX path of hiddenscriptpath

-- Quoting the Posix path

set qtdhiddenscriptpath to quoted form of hiddenscriptpath

-- executing the script file

try

set command to "open " & qtdhiddenscriptpath

display dialog qtdhiddenscriptpath

do shell script command

end try

I was hoping that you can answer a question.

I used your script and it works perfectly - but I am having one small issue. When trying to open, I always get a dialog box (see below) and when I click OK everything works. I just don't know

what is causing this dialog to appear, and how to stop it.

I am having errors in trying to create a package (with Packages) and I am guessing that the dialog is causing the issue.

Thanks a bunch!!

Hugh

[Vaughan]

THat looks like a FileMaker custom dialog: IOW, something the developer has put there for debugging, probably in the startup script.

[hugh71158]

THat looks like a FileMaker custom dialog: IOW, something the developer has put there for debugging, probably in the startup script.

Ah, that's interesting - more so since I am the developer. This is a database that I built for my business, but now people are asking me for it.

Anyway, I completely disabled the start up script, and still the dialog appears. It just seems to be verifying it's location. It's driving me crazy. Any other thoughts?

Thanks.

Hugh

[comment]

still the dialog appears. It just seems to be verifying it's location. It's driving me crazy. Any other thoughts?

I am not sue what exactly you did, but perhaps this has something to do with it:

display dialog qtdhiddenscriptpath

[hugh71158]

I am not sue what exactly you did, but perhaps this has something to do with it:

Well, this is my absolute first look at Applescript, and I am not proficient in ANY scripting environment, but a closer look probably would have thrown up that "display dialog" box. Worked perfectly when I removed that line.

I want to thank you very much, you have saved my sanity and I will sleep better tonight! Thank you!!! Vaughan, thank you too.

Hugh

[comment]

Long live voodoo programming...

This thread being over a year old, perhaps it's time to point to the official version:

http://developer.apple.com/library/mac/#documentation/CoreFoundation/Conceptual/CFBundles/Introduction/Introduction.html

[Otis]

Forget it then.

[bruceR]

If you are having difficulty doing this why are you trying to do it?

[Otis]

If you are having difficulty doing this why are you trying to do it?

What kind of question is that?

You've never heard of someone needing help?