Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Don't go there. As a long term Mac developer, I can assure you, no solution is really working well. I tried so many solutions, but they are all not too good. I think the problem is that Apple does not really document the meta data format for the necessary data.</p> <p>Here's how I'm doing it for a long time, very successfully:</p> <ol> <li><p>Create a new DMG, writeable(!), big enough to hold the expected binary and extra files like readme (sparse might work).</p></li> <li><p>Mount the DMG and give it a layout manually in Finder or with whatever tools suits you for doing that (see FileStorm link at the bottom for a good tool). The background image is usually an image we put into a hidden folder (".something") on the DMG. Put a copy of your app there (any version, even outdated one will do). Copy other files (aliases, readme, etc.) you want there, again, outdated versions will do just fine. Make sure icons have the right sizes and positions (IOW, layout the DMG the way you want it to be).</p></li> <li><p>Unmount the DMG again, all settings should be stored by now.</p></li> <li><p>Write a create DMG script, that works as follows: </p> <ul> <li>It copies the DMG, so the original one is never touched again.</li> <li>It mounts the copy.</li> <li>It replaces all files with the most up to date ones (e.g. latest app after build). You can simply use <em>mv</em> or <em>ditto</em> for that on command line. Note, when you replace a file like that, the icon will stay the same, the position will stay the same, everything but the file (or directory) content stays the same (at least with ditto, which we usually use for that task). You can of course also replace the background image with another one (just make sure it has the same dimensions).</li> <li>After replacing the files, make the script unmount the DMG copy again.</li> <li>Finally call hdiutil to convert the writable, to a compressed (and such not writable) DMG.</li> </ul></li> </ol> <p>This method may not sound optimal, but trust me, it works really well in practice. You can put the original DMG (DMG template) even under version control (e.g. SVN), so if you ever accidentally change/destroy it, you can just go back to a revision where it was still okay. You can add the DMG template to your Xcode project, together with all other files that belong onto the DMG (readme, URL file, background image), all under version control and then create a target (e.g. external target named "Create DMG") and there run the DMG script of above and add your old main target as dependent target. You can access files in the Xcode tree using ${SRCROOT} in the script (is always the source root of your product) and you can access build products by using ${BUILT_PRODUCTS_DIR} (is always the directory where Xcode creates the build results).</p> <p>Result: Actually Xcode can produce the DMG at the end of the build. A DMG that is ready to release. Not only you can create a relase DMG pretty easy that way, you can actually do so in an automated process (on a headless server if you like), using xcodebuild from command line (automated nightly builds for example).</p> <p>Regarding the initial layout of the template, <a href="http://www.mindvision.com/filestorm.asp" rel="noreferrer">FileStorm</a> is a good tool for doing it. It is commercial, but very powerful and easy to use. The normal version is less than $20, so it is really affordable. Maybe one can automate FileStorm to create a DMG (e.g. via AppleScript), never tried that, but once you have found the perfect template DMG, it's really easy to update it for every release.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I create a nice-looking DMG for Mac OS X using command-line tools?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMecki
    1. USMecki
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've already discarded the idea of doing it this way, for several reasons. Here are two of them: the contents of the installers will vary with product, and we want to rely only on software installed on the pack machines and scripts - a single, minimal, manual routine for adding new products.
      singulars
      1. PO
      1. USLudvig A. Norin
    2. COThis is the same scenario as we have. We have more than a dozen of products; each has an entirely different DMG. Creating one template DMG per product is one time only task and takes you a couple of minutes. And what do you mean by "installer"? PKG/MPKG install packages?
      singulars
      1. PO
      1. USMecki
    3. COIt's not the same scenario. We add products often, with short notice. The minimal manual routine means running a script giving the product a name and a few other attributes. There are reasons beyond this as well that made us make the decision not to use that kind of solution.
      singulars
      1. PO
      1. USLudvig A. Norin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload