Deployment to Mac (Hows? and Whys?)

Deploying to Mac OS? Ask Mac OS specific questions here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
Traxgeek
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 281
Joined: Wed Jan 09, 2013 10:11 am

Deployment to Mac (Hows? and Whys?)

Post by Traxgeek » Sun Dec 01, 2013 3:27 pm

Hi,

I've been using LC for a while and have deployed to my own Mac and my own Windows devices but now I want to take the plunge and (at least try to) deploy for the marketplace - both platforms if poss.

Question : is there a good tutorial that explains exactly what all the settings do in the 'Standalone Application Settings' pane - save me bombarding this forum with (inane) questions and you the trouble of reading them :)
Example of questions I currently have :
(1) What is the 'ideal' size of the application icon one uses for Mac (and then also Windows) deployment ?
(2) What is the Document Icon used for ? I see, further down the said pane, one may enter the Document Type and Document Extension BUT : Is this a help file and the like ? Where would I put the 'Document' and how would I reference / name / identify it ?
(3) What's the difference between the 'Short Version' and 'Long Version' numbers
(4) What is a 'Bundle Identifier'

Some of the above Q's are answered in this very useful / informative article - just took ages to wade through all the dross to find it : http://newsletters.livecode.com/june/is ... etter4.php

More general questions :
My app uses an sqlite database. How do I prevent my 'test' DB being automatically included in my deployed app ?
Where can I see all the files that will be included (and then maybe remove one or more of them) ?
Why would I just not simply create ALL my Builds for Mac OS X (Universal) ? Why / what are the advantages of creating individual builds -OR- what are the disadvantages of creating the generic (Universal) build... ?

Sooooo many questions...

I've read the manual - there seem various options the manual covers that don't exist in my 6.5 (commercial) version and vice-versa... just confused (again)... I'll continue looking but in the meantime, if anyone has some pointers I'd be very grateful.

Regards.
I'm 'getting there'... just far too slowly !
Mac (Siera) and PC (Win7)
LiveCode 8.1.2 / 7.1.1

seaniepie
Posts: 154
Joined: Wed Sep 07, 2011 10:56 am

Re: Deployment to Mac (Hows? and Whys?)

Post by seaniepie » Sun Jan 05, 2014 1:11 am

Hi There,

Looks like you didn't get a reply to these questions and that sucks so let me try.
(1) What is the 'ideal' size of the application icon one uses for Mac (and then also Windows) deployment ?
The starting point is 1024x1024. Use an app like 'Applicons' available on the Mac AppStore to create an icns file and various other sizes you will need.
(2) What is the Document Icon used for ? I see, further down the said pane, one may enter the Document Type and Document Extension BUT : Is this a help file and the like ? Where would I put the 'Document' and how would I reference / name / identify it ?
The document icon is for any saved files from your app that are associated to your app. The type and extension at one time used to have to be registered. Now you might only need to define your UTI (Uniform Type Identifier - fancy term for file type id) More info here: https://developer.apple.com/library/mac ... intro.html
(3) What's the difference between the 'Short Version' and 'Long Version' numbers
It's how they are displayed in various places like info panels. It's nothing to be too concerned about. LC sets you up with a basic set. For the AppStore you are best setting it to a three point system, so v1.0.0 rather than 1.0.0.0. This is not to be confused as the long and short versions. A short version contains only the actual number (1.0.0) where the long version might also contain the app name (My App 1.0.0)
(4) What is a 'Bundle Identifier'
When you want to have an app sold through the AppStore you will need one of these. You will have to go to your developer account on the iTunesConnect site then in the Manage Apps area you will Add a New App. In there you will be asked to create a bundle identifier. Usually you will have the reverse of your DNS, which in my case is uk.co.pidigital, followed by the app name. This ensures it is unique. So I could end up with something like com.pidigital.myapp which wouldn't be duplicated by anyone else. Once it has been created it exists for all time and cannot be destroyed. It can be used for multiple apps while in development but only one app can use it at a time on the store. It also does not have to be anything near the same as your actual app name. In fact, your app name as displayed in the store can change at will.
My app uses an sqlite database. How do I prevent my 'test' DB being automatically included in my deployed app ?
This is very simple as the only items that get included in your app are any embedded media (using the import as control dialogue) and those listed in the Standalone Settings 'Copy Files' area. So just make sure it isn't in either of those.
Where can I see all the files that will be included (and then maybe remove one or more of them) ?
Once your app for Mac has been built you will be able to right or ctrl click your app file and choose 'Show Package Contents'. In there within the 'Contents' area you will find another folder for resources. They will be in there somewhere.
Why would I just not simply create ALL my Builds for Mac OS X (Universal) ?
If you are going to submit to the AppStore then you will not be able to use Universal anymore. It MUST be Intel Only! Universal and PowerPC are no longer supported and this is actually an advantage to all of us. So only Intel CPU Macs will be able to run our apps.
I've read the manual - there seem various options the manual covers that don't exist in my 6.5 (commercial) version and vice-versa
This is something the RR team are very well aware of but have a huge job of catchup to do. I'm in the process of putting stuff together as a temporary solution and you will hear more about that in due time.

As an aside, when you do get around to the need to supply your app to the AppStore you will also need to code sign and package your app into an installer. To take away a lot of the pain in accomplishing this I have created a little app that got me out of trouble during the holidays and have now supplied it free to the entire community. You can download it from here:
http://pidigital.co.uk/OSXPackageMaker.zip

Hope all this helps you out in some way. If this is already too late for you hopefully it will help someone else out.

All the best
Sean

Traxgeek
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 281
Joined: Wed Jan 09, 2013 10:11 am

Re: Deployment to Mac (Hows? and Whys?)

Post by Traxgeek » Tue Jan 07, 2014 4:27 pm

Been a way for a long while there ! Back now - for a while...

Thanks a million Sean - simply fantastic - very informative and helpful. I'll no doubt be 'crowing' when I finally manage to get my app approved and on the app stores - you'll be hearing more form me then...

Once again, a million 'thank you's !
I'm 'getting there'... just far too slowly !
Mac (Siera) and PC (Win7)
LiveCode 8.1.2 / 7.1.1

Post Reply