Re: [Squirrel-sql-develop] Mac OS X install package

[Charles A. <cha...@po...>]

On 11/08/2006 4:42 AM, "Rowe, Neville" <Nev...@dr...>
wrote:
>=20
> I guess the best solution might be for the installer to effectively do wh=
at
> mac_dist does and build up SquirrelSQL.app dynamically =AD always including=
 the
> macos plugin & other base plugins, but giving the user the chance to sele=
ct
> additional standard or optional plugins at install time.

I would agree with Neville here. The installer should be able to do this
just as easily as mac_dist does. (The only tricky part might be making sure
IzPack sets JavaApplicationStub executable.)

As far as disk images go, it may be worth experimenting with how garden-
variety iso images are handled by OS X's Finder. (I've looked around for th=
e
hdiutil(1) source, but haven't seen it yet. It's probably inside one of the
other packages on www.opensource.apple.com)


When I get some free cycles, I want to take a look at how tricky it would b=
e
to have squirrel-sql treat Contents/Plugins as an alternate plugins
directory to Contents/Resources/Java/plugins inside the app bundle. (The
Contents/Plugins directory can be managed from Finder "Get Info" windows.)
With this approach, the standard OS X install would include:

macosx   : Contents/Resources/Java/plugins
standard : Contents/Plugins
optional : Contents/Plugins Disabled

And the optional plugins, as a consequence, wouldn't be loaded by
squirrel-sql. (For the ideal Mac-like user experience, the plugins and thei=
r
associated directories would be bundled together in a single place. Either
inside a bundling jar or inside a directory with an extension like .plugin.
Of course, that would make the "include these classpaths" code for the
plugin loader more like a "walk this hierarchy and include any jars you
find".)

-C