Thread: Re: [Squirrel-sql-develop] Mac OS X install package
A Java SQL client for any JDBC compliant database
Brought to you by:
colbell,
gerdwagner
From: Colin B. <co...@ba...> - 2006-10-28 23:36:59
|
Hi Petr, I've cced the SQuirreL developers list so that the appropriate person will see this mail. On Sat, Oct 28, 2006 at 09:30:21AM -0700, Petr Srajer wrote: > > Message body follows: > > Hello Colin. > > I have created Squirrel 2.3 simple installation package for OS X. It contains: > -A little bit better icon > -Starting scripts > -ReadMe.rtf and License.rtf > -Description how to make OS X install package > -Squirrel-2.3.dmg file is big - cca 15MB. > > I found "mac" directory in src, but the content is old. My questions are: > > 1) It is possible to put this install package to download section? If yes then > who can put it there? > 2) How can I put content of installation files (icons, scripts,...) into CVS ? > > Bye > Petr. > > -- > This message has been sent to you, a registered SourceForge.net user, > by another site user, through the SourceForge.net site. This message > has been delivered to your SourceForge.net mail alias. You may reply > to this message using the "Reply" feature of your email client, or > using the messaging facility of SourceForge.net at: > https://sourceforge.net/sendmessage.php?touser=651297 > -- Colin Bell http://www.baibell.org |
From: Robert M. <rob...@gm...> - 2006-10-29 01:36:28
|
Hello Petr, I am responsible for producing the release builds and have to confess guilt for neglect in the MacOS X offering. I don't have access to a machine with this platform, so I've been relying on contributions from others who are willing to start with the distributions we create, and put them into a format that MacOS X users find more convenient. I can place the distribution you've created up on SF for you. I'd also like to take a look at whatever scripts you used, so I might be able to incorporate it into the release builds. I'll be careful to attribute anything you send me to you so that your contribution is recorded for future use. Rob On 10/28/06, Colin Bell <co...@ba...> wrote: > Hi Petr, > > I've cced the SQuirreL developers list so that the appropriate person > will see this mail. > > > On Sat, Oct 28, 2006 at 09:30:21AM -0700, Petr Srajer wrote: > > > > Message body follows: > > > > Hello Colin. > > > > I have created Squirrel 2.3 simple installation package for OS X. It contains: > > -A little bit better icon > > -Starting scripts > > -ReadMe.rtf and License.rtf > > -Description how to make OS X install package > > -Squirrel-2.3.dmg file is big - cca 15MB. > > > > I found "mac" directory in src, but the content is old. My questions are: > > > > 1) It is possible to put this install package to download section? If yes then > > who can put it there? > > 2) How can I put content of installation files (icons, scripts,...) into CVS ? > > > > Bye > > Petr. > > > > -- > > This message has been sent to you, a registered SourceForge.net user, > > by another site user, through the SourceForge.net site. This message > > has been delivered to your SourceForge.net mail alias. You may reply > > to this message using the "Reply" feature of your email client, or > > using the messaging facility of SourceForge.net at: > > https://sourceforge.net/sendmessage.php?touser=651297 > > > > -- > Colin Bell > http://www.baibell.org > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
From: Charles A. <cha...@po...> - 2006-10-29 09:15:47
|
And I'd be happy (I'm sure Petr would as well) to offer any suggestions as to incorporating a solid OS X [app bundle] target into the IzPack installer process (the OS X ant task doesn't include any additional plugins). For me, the main catch so far is that I haven't had the time to figure out how the IzPack stuff is configured, launched and built. Nor, regretably, have I even asked here for assistance in replicating the build process. Perhaps those of us with an interest in improving the OS X product could collaborate on some goals for the next release. -Charles cha...@po... At 9:36 PM -0400 10/28/06, Robert Manning wrote: >Hello Petr, > >I am responsible for producing the release builds and have to confess guilt >for neglect in the MacOS X offering. I don't have access to a machine with >this platform, so I've been relying on contributions from others who are >willing to start with the distributions we create, and put them into a format >that MacOS X users find more convenient. I can place the distribution >you've created up on SF for you. I'd also like to take a look at whatever >scripts you used, so I might be able to incorporate it into the release >builds. I'll be careful to attribute anything you send me to you so that your >contribution is recorded for future use. > >Rob > >On 10/28/06, Colin Bell <co...@ba...> wrote: >> Hi Petr, >> >> I've cced the SQuirreL developers list so that the appropriate person >> will see this mail. >> >> >> On Sat, Oct 28, 2006 at 09:30:21AM -0700, Petr Srajer wrote: >> > >> > Message body follows: >> > >> > Hello Colin. >> > >> > I have created Squirrel 2.3 simple installation package for OS X. It contains: >> > -A little bit better icon >> > -Starting scripts >> > -ReadMe.rtf and License.rtf >> > -Description how to make OS X install package >> > -Squirrel-2.3.dmg file is big - cca 15MB. >> > >> > I found "mac" directory in src, but the content is old. My questions are: >> > >> > 1) It is possible to put this install package to download section? If yes then >> > who can put it there? >> > 2) How can I put content of installation files (icons, scripts,...) into CVS ? >> > >> > Bye > > > Petr. |
From: Rowe, N. <Nev...@dk...> - 2006-10-29 07:46:30
|
It's been me who has previously done mac customisations, but I'm a bit busy at the moment at work. If you look in sql12/build/build.xml there is a mac_dist target which produces a .app package for the mac with appropriate plugins (in particular the macos plugin) and documentation in the right place, and then wraps that as a compressed file for distribution. Someone (Gerd ?) fixed (or intended to fix) the macos package so it should build on any platform (using reflection to determine if and use the mac-specific libraries where available) so actually mac the mac distribution should be buildable on any platform - I don't think that has been tested though. I didn't know how to produce a .dmg and decided not to as I think that would restrict the build process to running on a mac only. Anyway with v2.3 I've build a local copy on my mac and it all worked fine but I'm not going to get a chance to do anything about uploading any time soon so if someone (Petr) has the time then thank-you... Neville -----Original Message----- From: squ...@li... [mailto:squ...@li...] On Behalf Of Robert Manning Sent: 29 October 2006 01:36 To: Petr Srajer Cc: squ...@li... Subject: Re: [Squirrel-sql-develop] Mac OS X install package Hello Petr, I am responsible for producing the release builds and have to confess guilt for neglect in the MacOS X offering. I don't have access to a machine with this platform, so I've been relying on contributions from others who are willing to start with the distributions we create, and put them into a format that MacOS X users find more convenient. I can place the distribution you've created up on SF for you. I'd also like to take a look at whatever scripts you used, so I might be able to incorporate it into the release builds. I'll be careful to attribute anything you send me to you so that your contribution is recorded for future use. Rob On 10/28/06, Colin Bell <co...@ba...> wrote: > Hi Petr, > > I've cced the SQuirreL developers list so that the appropriate person=20 > will see this mail. > > > On Sat, Oct 28, 2006 at 09:30:21AM -0700, Petr Srajer wrote: > > > > Message body follows: > > > > Hello Colin. > > > > I have created Squirrel 2.3 simple installation package for OS X. It contains: > > -A little bit better icon > > -Starting scripts > > -ReadMe.rtf and License.rtf > > -Description how to make OS X install package -Squirrel-2.3.dmg file > > is big - cca 15MB. > > > > I found "mac" directory in src, but the content is old. My questions are: > > > > 1) It is possible to put this install package to download section?=20 > > If yes then who can put it there? > > 2) How can I put content of installation files (icons, scripts,...) into CVS ? > > > > Bye > > Petr. > > > > -- > > This message has been sent to you, a registered SourceForge.net=20 > > user, by another site user, through the SourceForge.net site. This=20 > > message has been delivered to your SourceForge.net mail alias. You=20 > > may reply to this message using the "Reply" feature of your email=20 > > client, or using the messaging facility of SourceForge.net at: > > https://sourceforge.net/sendmessage.php?touser=3D651297 > > > > -- > Colin Bell > http://www.baibell.org > > ---------------------------------------------------------------------- > --- Using Tomcat but need to do more? Need to support web services,=20 > security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on=20 > Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D1216 > 42 _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > ------------------------------------------------------------------------ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1= 21642 _______________________________________________ Squirrel-sql-develop mailing list Squ...@li... https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop ---------------------------------------------------------------------------= ----- The information contained herein is confidential and is intended solely for= the addressee. Access by any other party is unauthorised without the express=20 written permission of the sender. If you are not the intended recipient, pl= ease=20 contact the sender either via the company switchboard on +44 (0)20 7623 800= 0, or via e-mail return. If you have received this e-mail in error or wish to rea= d our e-mail disclaimer statement and monitoring policy, please refer to=20 http://www.dresdnerkleinwort.com/disc/email/ or contact the sender.=20 ---------------------------------------------------------------------------= ----- |
From: Charles A. <cha...@po...> - 2006-10-29 23:23:32
|
Rob built the current OS X build for 2.3 (SquirrelsQLMac-2.3final.tgz) using little more than the "mac_dist" ant task and a couple of sed scripts to fix the version information in the Info.plist. And, notably, not on a mac. [Note, the weird capitalization in the name "SquirrelsQLMac-2.3final.tgz" was sloppy typing on my part when I sent him a script to make a distributable build. I probably should have gone with "squirrel-sql2.3final-macosx.tar.gz" or "squirrel-sql2.3final-macosx-base.tar.gz" so it looked like the rest of the release, and notably, like 2.0rc1. C'est la vie.] Granted, we don't have the latest JavaApplicationStub in CVS (as Petr noted earlier) and I suppose that could lead to issues. One of the things I've been wondering is whether we can leverage OS X-style "Contents/Plugins" and "Contents/Plugins (Disabled)" directories inside the app bundle (and get the classpaths to interpret correctly) so as to allow turning the plugins on and off via the Finder's Get Info window. But that might involve modifying the plugin loader mechanism. Especially if OS X expects ".plugin" bundles. Questions, questions, questions, and little time to dig in and find the answers - even if they are relatively straightforward. >sigh< -Charles cha...@po... At 7:46 AM +0000 10/29/06, Rowe, Neville wrote: >It's been me who has previously done mac customisations, but I'm a bit >busy at the moment at work. If you look in sql12/build/build.xml there >is a mac_dist target which produces a .app package for the mac with >appropriate plugins (in particular the macos plugin) and documentation >in the right place, and then wraps that as a compressed file for >distribution. Someone (Gerd ?) fixed (or intended to fix) the macos >package so it should build on any platform (using reflection to >determine if and use the mac-specific libraries where available) so >actually mac the mac distribution should be buildable on any platform - >I don't think that has been tested though. I didn't know how to produce >a .dmg and decided not to as I think that would restrict the build >process to running on a mac only. > >Anyway with v2.3 I've build a local copy on my mac and it all worked >fine but I'm not going to get a chance to do anything about uploading >any time soon so if someone (Petr) has the time then thank-you... > >Neville > >-----Original Message----- >From: squ...@li... >[mailto:squ...@li...] On Behalf Of >Robert Manning >Sent: 29 October 2006 01:36 >To: Petr Srajer >Cc: squ...@li... >Subject: Re: [Squirrel-sql-develop] Mac OS X install package > >Hello Petr, > >I am responsible for producing the release builds and have to confess >guilt for neglect in the MacOS X offering. I don't have access to a >machine with this platform, so I've been relying on contributions from >others who are willing to start with the distributions we create, and >put them into a format that MacOS X users find more convenient. I can >place the distribution you've created up on SF for you. I'd also like >to take a look at whatever scripts you used, so I might be able to >incorporate it into the release builds. I'll be careful to attribute >anything you send me to you so that your contribution is recorded for >future use. > >Rob > >On 10/28/06, Colin Bell <co...@ba...> wrote: >> Hi Petr, >> >> I've cced the SQuirreL developers list so that the appropriate person >> will see this mail. >> >> >> On Sat, Oct 28, 2006 at 09:30:21AM -0700, Petr Srajer wrote: >> > >> > Message body follows: >> > >> > Hello Colin. >> > >> > I have created Squirrel 2.3 simple installation package for OS >X. It contains: >> > -A little bit better icon >> > -Starting scripts >> > -ReadMe.rtf and License.rtf >> > -Description how to make OS X install package -Squirrel-2.3.dmg file > >> > is big - cca 15MB. > > > >> > I found "mac" directory in src, but the content is old. My >questions are: >> > >> > 1) It is possible to put this install package to download section? >> > If yes then who can put it there? >> > 2) How can I put content of installation files (icons, scripts,...) >into CVS ? >> > >> > Bye >> > Petr. >> > >> > -- >> > This message has been sent to you, a registered SourceForge.net >> > user, by another site user, through the SourceForge.net site. This >> > message has been delivered to your SourceForge.net mail alias. You >> > may reply to this message using the "Reply" feature of your email >> > client, or using the messaging facility of SourceForge.net at: >> > https://sourceforge.net/sendmessage.php?touser=651297 >> > >> >> -- >> Colin Bell >> http://www.baibell.org >> >> ---------------------------------------------------------------------- >> --- Using Tomcat but need to do more? Need to support web services, >> security? >> Get stuff done quickly with pre-integrated technology to make your job > >> easier Download IBM WebSphere Application Server v.1.0.1 based on >> Apache Geronimo >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=1216 >> 42 _______________________________________________ >> Squirrel-sql-develop mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > >------------------------------------------------------------------------ >- >Using Tomcat but need to do more? Need to support web services, >security? >Get stuff done quickly with pre-integrated technology to make your job >easier Download IBM WebSphere Application Server v.1.0.1 based on Apache >Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Squirrel-sql-develop mailing list >Squ...@li... >https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > > >-------------------------------------------------------------------------------- >The information contained herein is confidential and is intended solely for the >addressee. Access by any other party is unauthorised without the express >written permission of the sender. If you are not the intended recipient, please >contact the sender either via the company switchboard on +44 (0)20 7623 8000, or >via e-mail return. If you have received this e-mail in error or wish to read our >e-mail disclaimer statement and monitoring policy, please refer to >http://www.dresdnerkleinwort.com/disc/email/ or contact the sender. >-------------------------------------------------------------------------------- > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Squirrel-sql-develop mailing list >Squ...@li... >https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop |
From: Robert M. <rob...@gm...> - 2006-10-29 12:04:42
|
On 10/29/06, Charles Albrecht <cha...@po...> wrote: > And I'd be happy (I'm sure Petr would as well) to offer any suggestions as to incorporating a solid OS X [app bundle] target into the IzPack installer process (the OS X ant task doesn't include any additional plugins). For me, the main catch so far is that I haven't had the time to figure out how the IzPack stuff is configured, launched and built. Nor, regretably, have I even asked here for assistance in replicating the build process. > IzPack uses an XML file (izpack-super.xml for current installer) to build an install jar. This file tells it exactly what files get installed and where (and which ones are mandatory - in our case "base") . We include all of the plugins in the install jar and group them into "standard" which is our way of saying universal not dependant on your database and "optional" which includes everything else. Although this makes the installer big (~15M), it eases the burden of downloading plugins and dealing with version compatibility. We have release build scripts that take the installer and build the various platform-specific plain zip archives. IzPack can take an "auto-install" XML file and feed that to the installer to eliminate the need to use a GUI. This way, the plain zips are created with a script. We currently produce 6 of them - 3 for Win32 and 3 for UNIX. The three are Base, Standard and Optional plain zips provide only what there name indicates, with Optional being the whole enchilada. For Win32 and UNIX, the file structure of SQuirreL once installed is pretty much the same - just different launch scripts. I don't know if the same can be said for MacOS X. If it's just moving a few files around, we could probably have a new script to produce plain zips for MacOS X. That's not very flexible for the user - they must then choose either base, standard or *all* optional plugins. If we want to have the installer be able to recognize MacOS X and lay the files down differently that will take a bit of work - I believe - in the izpack-super.xml file. Maybe even some post-installation work. Not having a Mac I'm a little out of my element here, so those are just guesses. I guess I really need to know what the key parts of a MacOS X app directory structure are. I'll do some research and see what I find. Rob |
From: Charles A. <cha...@po...> - 2006-10-29 23:23:51
|
At 8:04 AM -0400 10/29/06, Robert Manning wrote: > >On 10/29/06, Charles Albrecht <cha...@po...> wrote: >> >>And I'd be happy (I'm sure Petr would as well) to offer any >>suggestions as to incorporating a solid OS X [app bundle] target >>into the IzPack installer process (the OS X ant task doesn't include >>any additional plugins). > >IzPack uses an XML file (izpack-super.xml for current installer) to >build an install jar. That's built from build/snapshot/izpack-super.xml.template, right? It looks like build/izpack-super.xml has been deleted. >then choose either base, standard or *all* optional plugins. If we >want to have the installer be able to recognize MacOS X and lay the >files down differently that will take a bit of work - I believe - >in the izpack-super.xml file. Maybe even some post-installation >work. Not having a Mac I'm a little out of my element here, so >those are just guesses. I guess I really need to know what the key >parts of a MacOS X app directory structure are. I'll do some >research and see what I find. An OS X app build is essentially the mac/Contents directory inside of a directory with a ".app" suffix with the normal distribution files placed in a directory called Java inside Contents/Resources. Contents/MacOS/JavaApplicationStub needs to be executable. Beyond that, it should be fairly straightforward. Contents/Info.plist has two fields which should reflect the current version number. And the process that pulls that into the IzPack jar could update those before pulling it in. It seems that it already does this for Version.java. I'll try to take some time this week to play around with the izpack-super template and see whether I can generate some functional OS X installers with it. -Charles cha...@po... |
From: Robert M. <rob...@gm...> - 2006-11-04 15:02:01
|
On 10/29/06, Charles Albrecht <cha...@po...> wrote: > >IzPack uses an XML file (izpack-super.xml for current installer) to > >build an install jar. > > That's built from build/snapshot/izpack-super.xml.template, right? It looks like build/izpack-super.xml has been deleted. It's now a template file that ant reads in and replaces some strings that are determined during the build initialization. The template file is located in the snapshots directory. The build-weekly.xml in the snapshots directory reads build-weekly.properties and is used for all current releases of SQuirreL. We did this because it does many things that a developer probably doesn't want to do, but are essential for release builds (fresh checkout, build, build install jar, auto-install to temp dir, launch for build verification, export source code and archive it, generate the release notes - someday it may even upload the resultant install jar and source archive to SF). My original goal was to play with it in the "snapshot" sandbox then eventually move it to the build/build.xml file - but I'm somewhat happy with it where it is. It's more complex to understand how the release builds are done and that complexity is hidden in the snapshots directory. Probably the most confusion is caused by my ill-chosen name for the directory - snapshot - as it is probably more correctly referred to as "release". > An OS X app build is essentially the mac/Contents directory inside of a directory with a ".app" suffix with the normal distribution files placed in a directory called Java inside Contents/Resources. Contents/MacOS/JavaApplicationStub needs to be executable. Beyond that, it should be fairly straightforward. Contents/Info.plist has two fields which should reflect the current version number. And the process that pulls that into the IzPack jar could update those before pulling it in. It seems that it already does this for Version.java. > Thanks for the info. I just ordered an iMac 500Mhz (384MB ram) with Mac OS X (10.4.7) pre-loaded last night. My only purpose for it at this point is to be able to test the changes that you all are proposing for the installer and to help incorporate them into the build scripts. I was trying to get something that was reasonably priced (yet capable of performing) for the task at hand. I think I found a bargain for an iMac 500 under $100. We'll see when it gets here next week ;) > I'll try to take some time this week to play around with the izpack-super template and see whether I can generate some functional OS X installers with it. If you have any questions, just ask. Rob |
From: Robert M. <rob...@gm...> - 2006-11-08 05:36:56
|
All, My iMac arrived today. In true Apple form I plugged it in, turned it on and started playing. Being that this is my first Mac ( I've used them occasionally at work ) I was pleasantly surprised that I was able to find things - I used to own a NeXT workstation so some things are coming back to me when I look at what's available on the filesystem through terminal. A few observations: 1. The macosx plugin can be built on WinXP and deployed on the Mac - the reflection logic is there to keep it from failing to compile on non-mac platforms. The plugin is indeed responsible for putting the custom menu with the 'About' menu item in the taskbar at the top 2. I had SQuirreL installed in a couple of minutes using the 2.3 final install jar (double-click the jar .. piece of cake). However, it took me 20 minutes of searching to be able to launch SQuirreL (I finally resorted to using terminal and ran squirrel-sql.sh from the command-line). I see now why this is such a stumbling block for mac users - no casual mac user is going to put up with that. I had no idea how bad it was :( 3. It's inconsistent to have the About menu appear in the main menu bar, while the other SQuirreL menus (File, Drivers, Aliases, etc.) continue to reside in the app window. So, the macosx plugin needs to have a significant effort to see about migrating all of these menus using the apple-specific/proxy class mechanism that Neville and Gerd have already put together for the About menu. 4. As far as producing dmg files, we currently perform all release builds in linux. IzPack has some issues regarding eol chars if you create installers with it under windows. So, unless dmg format is some proprietary format that only apple tools (closed source) can generate, I would imagine this format could be produced under linux. If not, the build guy (me) now has an apple mac build platform - slow as it is :) 5. If we need to, we could produce an install jar specifically for MacOS X that places files in the right location. Just need to write a new IzPack template. Need to include the macosx.jar plugin regardless of whether or not we generate a different installer. It doesn't hurt to have it, but does hurt to exclude it. Well that's it for now. Let me know if anyone has any additional insight on my observations. As far as I can tell, there are a number of things we could do to make installing and using SQuirreL easier for mac users. Rob On 11/5/06, Charles Albrecht <cha...@po...> wrote: > At 8:24 AM +0100 10/30/06, Petr Srajer wrote: > > Hello Charles. > > > > In the attachement is "my" content of /CVS/mac directory. I did not use JavaApplicationStub because a had a trouble with Aqua L&F. When I used JavaApplicationStub a cannot get Mac kind of menubar. I copied bash start script from NetBeans and it works. You can use anything from attachement if you want (Especially icon :) ). > > I can help you if you write me how. (writing code, testing, ...) > > > > Petr. > > > >PS: I can imagine following customization for mac: > >-Installation package > >-Menu bar change (About move to Application menu, Preferences move to application menu, Remove Quit menu from file menu) > >-Use OSX keychains for passwords. > > > >Who can tell me if I can working on it? > > The menu bar is already as you suggest when building with the ant task. This is probably a consequence of using the macosx plugin. > > cd sql12/build > ant mac_dist > open ../../squirrel-sql-dist/squirrel-sql/mac/SquirrelSQL/SquirrelSQL.app > > Download "SquirrelsQLMac-2.3final.tgz" from http://sourceforge.net/project/showfiles.php?group_id=28383&package_id=29193&release_id=453704 and see. > > Notably, it includes the macosx plugin and does not leverage the laf plugin. > > -C > |
From: Rowe, N. <Nev...@dk...> - 2006-11-08 07:30:42
|
Um9iLA0KDQpJIGd1ZXNzIHRoaXMgaWxsdXN0cmF0ZXMgdGhlIHByb2JsZW1zIG9mIG5vdCBiZWlu ZyBpbiB0aGUgbWFpbiBpbnN0YWxsIHByb2Nlc3MuDQoNCklmIGluc3RlYWQgb2YgZG93bmxvYWRp bmcgMi4zIEZpbmFsLCB5b3UgYnVpbGQgZnJvbSBzb3VyY2UgYW5kIHVzZSB0aGUgbWFjX2Rpc3Qg dGFyZ2V0IHRoYXQgcHJvZHVjZXMgYSAudGFyLmd6IGZpbGUuIEluIHRoZXJlIGlzIGEgU3F1aXJy ZWxTUUwuYXBwIHdoaWNoIGhhbmRsZXMgYWxsIHRoZSBpc3N1ZXMgeW91J3ZlIG1lbnRpb25lZCBi ZWxvdy4gVGhhdCBpcyB3aGF0IHdlIHNob3VsZCBiZSB0ZWxsaW5nIG1hYyB1c2VycyB0byBkb3du bG9hZCwgcmF0aGVyIHRoZW4gdGhlIGdlbmVyaWMgbm90LXdpbmRvd3MgdmVyc2lvbi4NCg0KTi4N Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IHNxdWlycmVsLXNxbC1kZXZlbG9w LWJvdW5jZXNAbGlzdHMuc291cmNlZm9yZ2UubmV0IDxzcXVpcnJlbC1zcWwtZGV2ZWxvcC1ib3Vu Y2VzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldD4NClRvOiBDaGFybGVzIEFsYnJlY2h0IDxjaGFybGVz YUBwb2JveC5jb20+DQpDQzogUGV0ciBTcmFqZXIgPFBldHIuU3JhamVyQGFpcy5jej47IHNxdWly cmVsLXNxbC1kZXZlbG9wQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCA8c3F1aXJyZWwtc3FsLWRldmVs b3BAbGlzdHMuc291cmNlZm9yZ2UubmV0Pg0KU2VudDogV2VkIE5vdiAwOCAwNTozNTo1MCAyMDA2 DQpTdWJqZWN0OiBSZTogW1NxdWlycmVsLXNxbC1kZXZlbG9wXSBNYWMgT1MgWCBpbnN0YWxsIHBh Y2thZ2UNCg0KQWxsLA0KDQpNeSBpTWFjIGFycml2ZWQgdG9kYXkuICBJbiB0cnVlIEFwcGxlIGZv cm0gSSBwbHVnZ2VkIGl0IGluLCB0dXJuZWQgaXQNCm9uIGFuZCBzdGFydGVkIHBsYXlpbmcuDQpC ZWluZyB0aGF0IHRoaXMgaXMgbXkgZmlyc3QgTWFjICggSSd2ZSB1c2VkIHRoZW0gb2NjYXNpb25h bGx5IGF0IHdvcmsNCikgSSB3YXMgcGxlYXNhbnRseSBzdXJwcmlzZWQgdGhhdCBJIHdhcyBhYmxl IHRvIGZpbmQgdGhpbmdzIC0gSSB1c2VkDQp0byBvd24gYSBOZVhUIHdvcmtzdGF0aW9uIHNvIHNv bWUgdGhpbmdzIGFyZSBjb21pbmcgYmFjayB0byBtZSB3aGVuIEkNCmxvb2sgYXQgd2hhdCdzIGF2 YWlsYWJsZSBvbiB0aGUgZmlsZXN5c3RlbSB0aHJvdWdoIHRlcm1pbmFsLiAgQSBmZXcNCm9ic2Vy dmF0aW9uczoNCg0KMS4gVGhlIG1hY29zeCBwbHVnaW4gY2FuIGJlIGJ1aWx0IG9uIFdpblhQIGFu ZCBkZXBsb3llZCBvbiB0aGUgTWFjIC0NCnRoZSByZWZsZWN0aW9uIGxvZ2ljIGlzIHRoZXJlIHRv IGtlZXAgaXQgZnJvbSBmYWlsaW5nIHRvIGNvbXBpbGUgb24NCm5vbi1tYWMgcGxhdGZvcm1zLiAg VGhlIHBsdWdpbiBpcyBpbmRlZWQgcmVzcG9uc2libGUgZm9yIHB1dHRpbmcgdGhlDQpjdXN0b20g bWVudSB3aXRoIHRoZSAnQWJvdXQnIG1lbnUgaXRlbSBpbiB0aGUgdGFza2JhciBhdCB0aGUgdG9w DQoNCjIuIEkgaGFkIFNRdWlycmVMIGluc3RhbGxlZCBpbiBhIGNvdXBsZSBvZiBtaW51dGVzIHVz aW5nIHRoZSAyLjMgZmluYWwNCmluc3RhbGwgamFyIChkb3VibGUtY2xpY2sgdGhlIGphciAuLiBw aWVjZSBvZiBjYWtlKS4gIEhvd2V2ZXIsIGl0IHRvb2sNCm1lIDIwIG1pbnV0ZXMgb2Ygc2VhcmNo aW5nIHRvIGJlIGFibGUgdG8gbGF1bmNoIFNRdWlycmVMIChJIGZpbmFsbHkNCnJlc29ydGVkIHRv IHVzaW5nIHRlcm1pbmFsIGFuZCByYW4gc3F1aXJyZWwtc3FsLnNoIGZyb20gdGhlDQpjb21tYW5k LWxpbmUpLiAgSSBzZWUgbm93IHdoeSB0aGlzIGlzIHN1Y2ggYSBzdHVtYmxpbmcgYmxvY2sgZm9y IG1hYw0KdXNlcnMgLSBubyBjYXN1YWwgbWFjIHVzZXIgaXMgZ29pbmcgdG8gcHV0IHVwIHdpdGgg dGhhdC4gIEkgaGFkIG5vDQppZGVhIGhvdyBiYWQgaXQgd2FzIDooDQoNCjMuIEl0J3MgaW5jb25z aXN0ZW50IHRvIGhhdmUgdGhlIEFib3V0IG1lbnUgYXBwZWFyIGluIHRoZSBtYWluIG1lbnUNCmJh ciwgd2hpbGUgdGhlIG90aGVyIFNRdWlycmVMIG1lbnVzIChGaWxlLCBEcml2ZXJzLCBBbGlhc2Vz LCBldGMuKQ0KY29udGludWUgdG8gcmVzaWRlIGluIHRoZSBhcHAgd2luZG93LiAgU28sIHRoZSBt YWNvc3ggcGx1Z2luIG5lZWRzIHRvDQpoYXZlIGEgc2lnbmlmaWNhbnQgZWZmb3J0IHRvIHNlZSBh Ym91dCBtaWdyYXRpbmcgYWxsIG9mIHRoZXNlIG1lbnVzDQp1c2luZyB0aGUgYXBwbGUtc3BlY2lm aWMvcHJveHkgY2xhc3MgbWVjaGFuaXNtIHRoYXQgTmV2aWxsZSBhbmQgR2VyZA0KaGF2ZSBhbHJl YWR5IHB1dCB0b2dldGhlciBmb3IgdGhlIEFib3V0IG1lbnUuDQoNCjQuIEFzIGZhciBhcyBwcm9k dWNpbmcgZG1nIGZpbGVzLCB3ZSBjdXJyZW50bHkgcGVyZm9ybSBhbGwgcmVsZWFzZQ0KYnVpbGRz IGluIGxpbnV4LiAgSXpQYWNrDQpoYXMgc29tZSBpc3N1ZXMgcmVnYXJkaW5nIGVvbCBjaGFycyBp ZiB5b3UgY3JlYXRlIGluc3RhbGxlcnMgd2l0aCBpdA0KdW5kZXIgd2luZG93cy4gIFNvLCB1bmxl c3MgZG1nIGZvcm1hdCBpcyBzb21lIHByb3ByaWV0YXJ5IGZvcm1hdCB0aGF0DQpvbmx5IGFwcGxl IHRvb2xzIChjbG9zZWQgc291cmNlKSBjYW4gZ2VuZXJhdGUsIEkgd291bGQgaW1hZ2luZSB0aGlz DQpmb3JtYXQgY291bGQgYmUgcHJvZHVjZWQgdW5kZXIgbGludXguICBJZiBub3QsIHRoZSBidWls ZA0KZ3V5IChtZSkgbm93IGhhcyBhbiBhcHBsZSBtYWMgYnVpbGQgcGxhdGZvcm0gLSBzbG93IGFz IGl0IGlzIDopDQoNCjUuIElmIHdlIG5lZWQgdG8sIHdlIGNvdWxkIHByb2R1Y2UgYW4gaW5zdGFs bCBqYXIgc3BlY2lmaWNhbGx5IGZvcg0KTWFjT1MgWCB0aGF0IHBsYWNlcyBmaWxlcyBpbiB0aGUg cmlnaHQgbG9jYXRpb24uICBKdXN0IG5lZWQgdG8gd3JpdGUgYQ0KbmV3IEl6UGFjayB0ZW1wbGF0 ZS4gIE5lZWQgdG8gaW5jbHVkZSB0aGUgbWFjb3N4LmphciBwbHVnaW4gcmVnYXJkbGVzcw0Kb2Yg d2hldGhlciBvciBub3Qgd2UgZ2VuZXJhdGUgYSBkaWZmZXJlbnQgaW5zdGFsbGVyLiAgSXQgZG9l c24ndCBodXJ0DQp0byBoYXZlIGl0LCBidXQgZG9lcyBodXJ0IHRvIGV4Y2x1ZGUgaXQuDQoNCldl bGwgdGhhdCdzIGl0IGZvciBub3cuICBMZXQgbWUga25vdyBpZiBhbnlvbmUgaGFzIGFueSBhZGRp dGlvbmFsDQppbnNpZ2h0IG9uIG15IG9ic2VydmF0aW9ucy4gIEFzIGZhciBhcyBJIGNhbiB0ZWxs LCB0aGVyZSBhcmUgYSBudW1iZXINCm9mIHRoaW5ncyB3ZSBjb3VsZCBkbyB0byBtYWtlIGluc3Rh bGxpbmcgYW5kIHVzaW5nIFNRdWlycmVMIGVhc2llciBmb3INCm1hYyB1c2Vycy4NCg0KUm9iDQoN Cg0KT24gMTEvNS8wNiwgQ2hhcmxlcyBBbGJyZWNodCA8Y2hhcmxlc2FAcG9ib3guY29tPiB3cm90 ZToNCj4gQXQgODoyNCBBTSArMDEwMCAxMC8zMC8wNiwgUGV0ciBTcmFqZXIgd3JvdGU6DQo+ID4g ICAgICAgSGVsbG8gQ2hhcmxlcy4NCj4gPg0KPiA+ICAgSW4gdGhlIGF0dGFjaGVtZW50IGlzICJt eSIgY29udGVudCBvZiAvQ1ZTL21hYyBkaXJlY3RvcnkuIEkgZGlkIG5vdCB1c2UgSmF2YUFwcGxp Y2F0aW9uU3R1YiBiZWNhdXNlIGEgaGFkIGEgdHJvdWJsZSB3aXRoIEFxdWEgTCZGLiBXaGVuIEkg dXNlZCBKYXZhQXBwbGljYXRpb25TdHViIGEgY2Fubm90IGdldCBNYWMga2luZCBvZiBtZW51YmFy LiBJIGNvcGllZCBiYXNoIHN0YXJ0IHNjcmlwdCBmcm9tIE5ldEJlYW5zIGFuZCBpdCB3b3Jrcy4g WW91IGNhbiB1c2UgYW55dGhpbmcgZnJvbSBhdHRhY2hlbWVudCBpZiB5b3Ugd2FudCAoRXNwZWNp YWxseSBpY29uIDopICkuDQo+ID4gICBJIGNhbiBoZWxwIHlvdSBpZiB5b3Ugd3JpdGUgbWUgaG93 LiAod3JpdGluZyBjb2RlLCB0ZXN0aW5nLCAuLi4pDQo+ID4NCj4gPiAgIFBldHIuDQo+ID4NCj4g PlBTOiBJIGNhbiBpbWFnaW5lIGZvbGxvd2luZyBjdXN0b21pemF0aW9uIGZvciBtYWM6DQo+ID4t SW5zdGFsbGF0aW9uIHBhY2thZ2UNCj4gPi1NZW51IGJhciBjaGFuZ2UgKEFib3V0IG1vdmUgdG8g QXBwbGljYXRpb24gbWVudSwgUHJlZmVyZW5jZXMgbW92ZSB0byBhcHBsaWNhdGlvbiBtZW51LCBS ZW1vdmUgUXVpdCBtZW51IGZyb20gZmlsZSBtZW51KQ0KPiA+LVVzZSBPU1gga2V5Y2hhaW5zIGZv ciBwYXNzd29yZHMuDQo+ID4NCj4gPldobyBjYW4gdGVsbCBtZSBpZiBJIGNhbiB3b3JraW5nIG9u IGl0Pw0KPg0KPiBUaGUgbWVudSBiYXIgaXMgYWxyZWFkeSBhcyB5b3Ugc3VnZ2VzdCB3aGVuIGJ1 aWxkaW5nIHdpdGggdGhlIGFudCB0YXNrLiBUaGlzIGlzIHByb2JhYmx5IGEgY29uc2VxdWVuY2Ug b2YgdXNpbmcgdGhlIG1hY29zeCBwbHVnaW4uDQo+DQo+IGNkIHNxbDEyL2J1aWxkDQo+IGFudCBt YWNfZGlzdA0KPiBvcGVuIC4uLy4uL3NxdWlycmVsLXNxbC1kaXN0L3NxdWlycmVsLXNxbC9tYWMv U3F1aXJyZWxTUUwvU3F1aXJyZWxTUUwuYXBwDQo+DQo+IERvd25sb2FkICJTcXVpcnJlbHNRTE1h Yy0yLjNmaW5hbC50Z3oiIGZyb20gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC9wcm9qZWN0L3Nob3dm aWxlcy5waHA/Z3JvdXBfaWQ9MjgzODMmcGFja2FnZV9pZD0yOTE5MyZyZWxlYXNlX2lkPTQ1Mzcw NCBhbmQgc2VlLg0KPg0KPiBOb3RhYmx5LCBpdCBpbmNsdWRlcyB0aGUgbWFjb3N4IHBsdWdpbiBh bmQgZG9lcyBub3QgbGV2ZXJhZ2UgdGhlIGxhZiBwbHVnaW4uDQo+DQo+IC1DDQo+DQoNCi0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0NClVzaW5nIFRvbWNhdCBidXQgbmVlZCB0byBkbyBtb3JlPyBOZWVkIHRvIHN1 cHBvcnQgd2ViIHNlcnZpY2VzLCBzZWN1cml0eT8NCkdldCBzdHVmZiBkb25lIHF1aWNrbHkgd2l0 aCBwcmUtaW50ZWdyYXRlZCB0ZWNobm9sb2d5IHRvIG1ha2UgeW91ciBqb2IgZWFzaWVyDQpEb3du bG9hZCBJQk0gV2ViU3BoZXJlIEFwcGxpY2F0aW9uIFNlcnZlciB2LjEuMC4xIGJhc2VkIG9uIEFw YWNoZSBHZXJvbmltbw0KaHR0cDovL3NlbC5hcy11cy5mYWxrYWcubmV0L3NlbD9jbWQ9bG5rJmtp ZD0xMjA3MDkmYmlkPTI2MzA1NyZkYXQ9MTIxNjQyDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXw0KU3F1aXJyZWwtc3FsLWRldmVsb3AgbWFpbGluZyBsaXN0 DQpTcXVpcnJlbC1zcWwtZGV2ZWxvcEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCmh0dHBzOi8vbGlz dHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL3NxdWlycmVsLXNxbC1kZXZlbG9wDQoN Cg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaGVy ZWluIGlzIGNvbmZpZGVudGlhbCBhbmQgaXMgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUNCmFkZHJl c3NlZS4gQWNjZXNzIGJ5IGFueSBvdGhlciBwYXJ0eSBpcyB1bmF1dGhvcmlzZWQgd2l0aG91dCB0 aGUgZXhwcmVzcyANCndyaXR0ZW4gcGVybWlzc2lvbiBvZiB0aGUgc2VuZGVyLiBJZiB5b3UgYXJl IG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2UgDQpjb250YWN0IHRoZSBzZW5kZXIg ZWl0aGVyIHZpYSB0aGUgY29tcGFueSBzd2l0Y2hib2FyZCBvbiArNDQgKDApMjAgNzYyMyA4MDAw LCBvcg0KdmlhIGUtbWFpbCByZXR1cm4uIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZS1tYWls IGluIGVycm9yIG9yIHdpc2ggdG8gcmVhZCBvdXINCmUtbWFpbCBkaXNjbGFpbWVyIHN0YXRlbWVu dCBhbmQgbW9uaXRvcmluZyBwb2xpY3ksIHBsZWFzZSByZWZlciB0byANCmh0dHA6Ly93d3cuZHJl c2RuZXJrbGVpbndvcnQuY29tL2Rpc2MvZW1haWwvIG9yIGNvbnRhY3QgdGhlIHNlbmRlci4gDQot LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQo= |
From: Robert M. <rob...@gm...> - 2006-11-08 10:33:47
|
On 11/8/06, Rowe, Neville <Nev...@dk...> wrote: > I guess this illustrates the problems of not being in the main install > process. > > If instead of downloading 2.3 Final, you build from source and use the > mac_dist target that produces a .tar.gz file. In there is a SquirrelSQL.app > which handles all the issues you've mentioned below. That is what we should > be telling mac users to download, rather then the generic not-windows > version. If we do _just_ that we exclude them from the benefits of the plugins (base, standard and optional). They get the SQuirreL jars and macosx.jar from looking at the mac_dist target. It seems like we should at least give them an installer that outputs the format of the mac_dist target and gives them "base" plugins, while allowing them to choose "standard" and "optional" plugins - like the current installer. Maybe we should also provide base.dmg, standard.dmg and optional.dmg as well. Any thoughts? Rob |
From: Rowe, N. <Nev...@dr...> - 2006-11-08 12:42:53
|
Sorry, I didn=B9t mean to suggest we only did that =AD simply that the star= ting point should be the results of the mac_dist build rather than the generic build. The mac_dist build includes the macos plugin which solves most of the problems you raised and builds SquirrelSQL.app which is the application package which macs understand =AD clickable, etc. I guess the best solution might be for the installer to effectively do what 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 select additional standard or optional plugins at install time. Neville On 8/11/06 10:33, "Robert Manning" <rob...@gm...> wrote: > On 11/8/06, Rowe, Neville <Nev...@dk...> wrote: >> > I guess this illustrates the problems of not being in the main install >> > process. >> > >> > If instead of downloading 2.3 Final, you build from source and use the >> > mac_dist target that produces a .tar.gz file. In there is a SquirrelSQ= L.app >> > which handles all the issues you've mentioned below. That is what we s= hould >> > be telling mac users to download, rather then the generic not-windows >> > version. >=20 > If we do _just_ that we exclude them from the benefits of the plugins > (base, standard and optional). They get the SQuirreL jars and > macosx.jar from looking at the mac_dist target. It seems like we > should at least give them an installer that outputs the format of the > mac_dist target and gives them "base" plugins, while allowing them to > choose "standard" and "optional" plugins - like the current installer. > Maybe we should also provide base.dmg, standard.dmg and optional.dmg > as well. >=20 > Any thoughts? >=20 > Rob >=20 ---------------------------------------------------------------------------= ----- The information contained herein is confidential and is intended solely for= the addressee. Access by any other party is unauthorised without the express=20 written permission of the sender. If you are not the intended recipient, pl= ease=20 contact the sender either via the company switchboard on +44 (0)20 7623 800= 0, or via e-mail return. If you have received this e-mail in error or wish to rea= d our e-mail disclaimer statement and monitoring policy, please refer to=20 http://www.dresdnerkleinwort.com/disc/email/ or contact the sender.=20 ---------------------------------------------------------------------------= ----- |
From: Charles A. <cha...@po...> - 2006-11-08 21:02:52
|
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 |
From: Robert M. <rob...@gm...> - 2006-11-08 22:00:10
|
On 11/8/06, Charles Albrecht <cha...@po...> wrote: > On 11/08/2006 4:42 AM, "Rowe, Neville" <Nev...@dr...= m> > wrote: > > > > I guess the best solution might be for the installer to effectively do = what > > mac_dist does and build up SquirrelSQL.app dynamically =AD always inclu= ding the > > macos plugin & other base plugins, but giving the user the chance to se= lect > > 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 su= re > IzPack sets JavaApplicationStub executable.) > Agreement here as well. I'll work on an IzPack template for the mac installer which will produce the structure currently done by the mac_dist target, and read up on JavaApplicationStub. > And the optional plugins, as a consequence, wouldn't be loaded by > squirrel-sql. (For the ideal Mac-like user experience, the plugins and th= eir > associated directories would be bundled together in a single place. Eithe= r > inside a bundling jar or inside a directory with an extension like .plugi= n. > 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".) The plugin manager today loads plugins that it finds in jars just as you say. It sucks all of the classes in each jar file it finds into a classloader, then finds classes assignable from IPlugin interface, using the classloader. It's not terribly efficient when you have big jar files to load in (like netbeans editor jars) - but it makes up for that with elegance in that no classpath editing is necessary. All plugins are stored in the "plugins" directory. There is some experimental support in SQuirreL for disabling plugins, but it's currently commented out because it breaks the dynamic loading - once you disable a plugin, it is no longer loaded, and so it can't be re-enabled. Someone needs to think through that mechanism a little more - it's definitely a feature I would love to have working. Developing a plugin would be faster if you could disable all the ones you weren't interested in loading, temporarily. Perhaps caching the result of the first startup into an xml file describing what plugins are available would be the right answer - kind of like the schema caching that we do now, only using an xml file. And the installer could update the xml file if new plugins get installed later. Hmmm, not a bad idea. Rob |
From: Robert M. <rob...@gm...> - 2006-11-11 18:09:07
|
On 11/11/06, Petr =8Arajer <Pet...@ai...> wrote: > I have 2 more questions: > 1) How can I change JVM max memory? > 2) What about other plugins? It is possible to bundle all plugins in mac > install package? Petr, I've just completed the first cut of the SQuirreL MacOS X IzPack installer for 2.3.1. You can download it here: http://sourceforge.net/project/showfiles.php?group_id=3D28383&package_id=3D= 29193&release_id=3D462367 Download squirrel-sql-2.3.1-MacOSX-install.jar and double-click it to install. It will let you choose any optional plugins as well. The one notable exception is LAF plugin. It interfered with specifying the native LAF (which is Aqua on my iMac). Let me know what you think and if I've missed anything. Rob |
From: Rowe, N. <Nev...@dk...> - 2006-11-13 13:41:26
|
I just gave this a go and it seemed to be excellent to me. Two minor problems. Firstly I think the Apple standard for developer tools is they are installe= d in /Developer/Applications so I would have expected that to be the defaul= t rather than /Applications. Secondly naturally I log into my machine as a normal user, but the applicat= ion dir is writable by an adminstrator only. Most installers flash up somet= hing saying - please authenticate. IzPack just says the dir is not writable= , I don't know if anything could be done about that ? Neville=20 -----Original Message----- From: squ...@li... [mailto:squirrel-s= ql-...@li...] On Behalf Of Robert Manning Sent: 11 November 2006 18:09 To: Petr =A9rajer Cc: Charles Albrecht; squ...@li... Subject: Re: [Squirrel-sql-develop] Mac OS X install package On 11/11/06, Petr =A9rajer <Pet...@ai...> wrote: > I have 2 more questions: > 1) How can I change JVM max memory? > 2) What about other plugins? It is possible to bundle all plugins in=20 > mac install package? Petr, I've just completed the first cut of the SQuirreL MacOS X IzPack installer = for 2.3.1. You can download it here: http://sourceforge.net/project/showfiles.php?group_id=3D28383&package_id=3D= 29193&release_id=3D462367 Download squirrel-sql-2.3.1-MacOSX-install.jar and double-click it to insta= ll. It will let you choose any optional plugins as well. The one notable e= xception is LAF plugin. It interfered with specifying the native LAF (whic= h is Aqua on my iMac). Let me know what you think and if I've missed anything. Rob ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easi= er Download IBM WebSphere Application Server v.1.0.1 based on Apache Geroni= mo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1= 21642 _______________________________________________ Squirrel-sql-develop mailing list Squ...@li... https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop ---------------------------------------------------------------------------= ----- The information contained herein is confidential and is intended solely for= the addressee. Access by any other party is unauthorised without the express=20 written permission of the sender. If you are not the intended recipient, pl= ease=20 contact the sender either via the company switchboard on +44 (0)20 7623 800= 0, or via e-mail return. If you have received this e-mail in error or wish to rea= d our e-mail disclaimer statement and monitoring policy, please refer to=20 http://www.dresdnerkleinwort.com/disc/email/ or contact the sender.=20 ---------------------------------------------------------------------------= ----- |
From: Charles A. <cha...@po...> - 2006-11-13 21:42:35
|
On 11/13/2006 5:41 AM, "Rowe, Neville" <Nev...@dk...> wrote: > > Firstly I think the Apple standard for developer tools is they are installed > in /Developer/Applications so I would have expected that to be the default > rather than /Applications. Sqirrel-sql doesn't fall into the "part of Xcode" that would make /Developer/Applications a standard place for the install. It is very likely that /Developer doesn't even exist on a user's machine. It won't be until the user has installed Xcode. Personally, I install my general development tools in /Applications/dev - a directory I've created to draw my development tools together. This (or /Applications/Productivity) is where I am most likely to install squirrel. I'd say that /Applications is a reasonable default. > Secondly naturally I log into my machine as a normal user, but the application > dir is writable by an adminstrator only. Most installers flash up something > saying - please authenticate. IzPack just says the dir is not writable, I > don't know if anything could be done about that ? Perhaps a preflight shell script call to something like: osascript -e 'do shell script "mkdir -m 777 /Applications/SquirrelSQL.app" \ with administrator privileges ' ...followed after the install with: osascript -e 'do shell script "chmod 755 /Applications/SquirrelSQL.app" \ with administrator privileges ' But that still feels pretty clunky, doesn't work well if SquirrelSQL.app already exists, etc. The one thing we didn't get with the current installer, was an update for the Version String in the Info.plist file. We have: <key>CFBundleShortVersionString</key> <string>1.2</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>@SquirrelVersion@</string> I would recommend: <key>CFBundleShortVersionString</key> <string>2.3.1</string> <key>CFBundleSignature</key> <string>SQrL</string> <key>CFBundleVersion</key> <string>SQuirreL SQL Client 2.3.1</string> Or something along those lines (I don't know whether the signature "SQrL" has already been spoken for), having the population of that file handled when populating the version string in the installer itself. -Charles cha...@po... |
From: Robert M. <rob...@gm...> - 2006-11-13 22:23:21
|
On 11/13/06, Rowe, Neville <Nev...@dk...> wrote: > I just gave this a go and it seemed to be excellent to me. > > Two minor problems. > > Firstly I think the Apple standard for developer tools is they are installed in /Developer/Applications so I would have expected that to be the default rather than /Applications. Ok, that's easy to fix. I didn't realize that their was a separate applications directory. Incidentally, I don't seem to have an 'Applications' directory under /Developer. So I guess we just create it if it isn't there, or is that wrong? > > Secondly naturally I log into my machine as a normal user, but the application dir is writable by an adminstrator only. Most installers flash up something saying - please authenticate. IzPack just says the dir is not writable, I don't know if anything could be done about that ? > Oh yes, I see. If you are a "normal" user, then you do not have permission to write to the "Applications" directory. Same holds true for the Developer directory. In Windows you typically have write access to the "Program Files" directory. And if you install anything that writes to "Administrator-only" places (like the registry) you typically get the same response (Cannot be installed because you don't have permission). Does this same paradigm exist in Mac-land? I mean, do people routinely logout and back in to a privileged account and install software, then back out and in as the unprivileged account. If not, there must be some way to say 'launch this arbitrary executable with "Administrator" privileges and ask me to authenticate', right? If not, I don't know of a mechanism in Java that integrates that closely with the desktop such that a java process can "inherit" the privileges of a new user at any moment at the request of the OS- unless Apple has extended Java with their jvm in some clever way. Hopefully you know the answer - if not I'll be spending some time on the Apple developer site. Rob |
From: Robert M. <rob...@gm...> - 2006-11-13 22:51:06
|
> On 11/13/06, Rowe, Neville <Nev...@dk...> wrote: > > Secondly naturally I log into my machine as a normal user, but the application dir is writable by an adminstrator only. Most installers flash up something saying - please authenticate. IzPack just says the dir is not writable, I don't know if anything could be done about that ? Ok - it's still UNIX right? So: 1. Open a terminal 2. su - <administrator> 3. At the prompt type the password 4. At the prompt type 'java -jar ' 5. Drag the install jar from desktop to the Public/Drop Box 6. Drag the install jar from Drop Box to the terminal window 7. Hit <enter> in the terminal window. Installer is running as <administrator> and has the ability to install anywhere. 8. Installed app can be launched and run as the normal user, since preferences are stored in <user.home>/.squirrel-sql/*.xml Yes, that's cheating, but still better than logging out. Incidentally, I don't see a "Run as ..." in any of the menus for jar files. How would one accomplish this? Rob |
From: Brian M. <bri...@gm...> - 2006-11-14 20:53:16
|
I apologize in advance for possibly messing up the mailing list, as this is my first post. I've been reading for a few months. I'm happy to report that I'm running SQuirreL on my Mac right now. I have to run it from Terminal at present because I'm a little too lazy to create the AppleScript wrapper. Anyway, Robert Manning suggested: 1. Open a terminal 2. su - <administrator> 3. At the prompt type the password 4. At the prompt type 'java -jar ' 5. Drag the install jar from desktop to the Public/Drop Box 6. Drag the install jar from Drop Box to the terminal window 7. Hit <enter> in the terminal window. Installer is running as <administrator> and has the ability to install anywhere. 8. Installed app can be launched and run as the normal user, since preferences are stored in <user.home>/.squirrel-sql/*.xml Do everything as Robert suggested, except on #2 do "sudo java -jar install.jar". By default you'll run as root if you're in the admin group on the Mac. In Macspeak, that means you're an Administrator. Then the SQuirreL install should go normally. This is what I did to get it to install a few days ago. Thanks, -Brian PS: I love SQuirreL. If you guys need a tester, please let me know. I have a Panther Mac (10.3) at home and a Tiger Mac at work. Panther only has Java 1.4. |
From: Robert M. <rob...@gm...> - 2006-11-14 23:00:57
|
On 11/14/06, Brian Mauter <bri...@gm...> wrote: > I apologize in advance for possibly messing up the mailing list, as this is > my first post. I've been reading for a few months. Welcome aboard! > > I'm happy to report that I'm running SQuirreL on my Mac right now. I have > to run it from Terminal at present because I'm a little too lazy to create > the AppleScript wrapper. > > Anyway, Robert Manning suggested: > 1. Open a terminal > 2. su - <administrator> > 3. At the prompt type the password > 4. At the prompt type 'java -jar ' > 5. Drag the install jar from desktop to the Public/Drop Box > 6. Drag the install jar from Drop Box to the terminal window > 7. Hit <enter> in the terminal window. Installer is running as > <administrator> and has the ability to install anywhere. > 8. Installed app can be launched and run as the normal user, since > preferences are stored in <user.home>/.squirrel-sql/*.xml > > Do everything as Robert suggested, except on #2 do "sudo java -jar > install.jar". By default you'll run as root if you're in the admin group on > the Mac. In Macspeak, that means you're an Administrator. Then the > SQuirreL install should go normally. > Glad to hear it's working for you. I spent a little time last last week to improve the install build script so that we now have a Mac OS X installer! > PS: I love SQuirreL. If you guys need a tester, please let me know. I > have a Panther Mac (10.3) at home and a Tiger Mac at work. Panther only has > Java 1.4. We enjoy hearing praise! We certainly would appreciate any help in testing our releases. SQuirreL should work fine with 1.4 (and if you see it misbehaving, let us know). I would encourage you to look at our bug database as your testing if you come across an issue. If it's not in the bug database, chances are we don't know about it (or it's an old bug that has resurfaced). In either case we would greatly appreciate a description of the steps you took, what you expected, what actually happened and perhaps a log. Take care! Rob |