squirrel-sql-develop Mailing List for SQuirreL SQL Client (Page 49)

Hi Patrick,

I ran those two scripts last night and it fell over with a class not found
error on one of the ant classes. org.apache....Main. I checked the scripts,
found the jar ant.jar and tried to unzip it and got a corrupt zip error.

There is an issue with uploading binary files as text. Take a look at
http://www.cvshome.org/docs/manual/cvs_9.html#SEC80


This is the relevant portion of the doc:

===============

There are two issues with using CVS to store binary files. The first is that
CVS by default converts line endings between the canonical form in which
they are stored in the repository (linefeed only), and the form appropriate
to the operating system in use on the client (for example, carriage return
followed by line feed for Windows NT).

The second is that a binary file might happen to contain data which looks
like a keyword (see section 12. Keyword substitution), so keyword expansion
must be turned off.

The `-kb' option available with some CVS commands insures that neither line
ending conversion nor keyword expansion will be done.

Here is an example of how you can create a new file using the `-kb' flag:

 

$ echo '$Id$' > kotest
$ cvs add -kb -m"A test file" kotest
$ cvs ci -m"First checkin; contains a keyword" kotest

If a file accidentally gets added without `-kb', one can use the cvs admin
command to recover. For example:

 

$ echo '$Id$' > kotest
$ cvs add -m"A test file" kotest
$ cvs ci -m"First checkin; contains a keyword" kotest
$ cvs admin -kb kotest
$ cvs update -A kotest
# For non-unix systems:
# Copy in a good copy of the file from outside CVS
$ cvs commit -m "make it binary" kotest

When you check in the file `kotest' the file is not preserved as a binary
file, because you did not check it in as a binary file. The cvs admin -kb
command sets the default keyword substitution method for this file, but it
does not alter the working copy of the file that you have. If you need to
cope with line endings (that is, you are using CVS on a non-unix system),
then you need to check in a new copy of the file, as shown by the cvs commit
command above. On unix, the cvs update -A command suffices.

==================

Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Thursday, 22 November 2001 10:11
To: Colin Bell
Cc: Squirrel Developers List (E-mail)
Subject: Re: [Squirrel-sql-develop] CVS


Colin,

Hmm.. checked in as text shouldn't matter.  From your win32 box try the
following once you've done a fresh checkout of the module 'squirrel'

c:\cvs\squirrel>configure.bat

c:\cvs\squirrel>build.bat dist

Try those two commands which should configure your environment and build
a distribution.. (It works on my unix box and win32 box).  I personally
don't use the default cmd.exe shell provided with win32, I use cygwin
which emulates a unix shell on my win32 environment.  In any event,
that's whole nother can of worms..

Try that and tell me exactly what happens despite the CVS warnings that
you get..

-P


Colin Bell wrote:
> 
> Hi Patrick,
> 
> No I wasn't. I sent you an email from home last night but it hasn't got to
> the list yet - Bloody ISP! (or just possibly I forget to actually send
it).
> 
> I wasn't able to build as all the binary files seem to have gone up as
text
> (jars, gifs etc.) I'm new to CVS so bear with me while I ask some stupid
> questions. Is this anything to do with the way I checked the module out?
I'm
> using WinCVS and it did a good job of recognising the different file types
> when I did the original import and checking them back out just seemed to
> work but now that you've done an import from a different OS are we having
> some kind of file compatability problem?
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Thursday, 22 November 2001 9:47
> Cc: Squirrel Developers List (E-mail)
> Subject: Re: [Squirrel-sql-develop] CVS
> 
> Were you able to get the program to build?  the squirrel module builds
> properly.  I commented out the plugins from the installer since it was
> not properly working.  Other, than that it builds ok.  (see
> src/resources/izpack/izpack-complete-buildmagic.xml)
> 
> -P
> 
> Colin Bell wrote:
> >
> > Hi Patrick,
> >
> > Until we get the BuildMagic process sorted out I'll just keep using the
> > squirrel-sql module and I will manually synch them up later.
> >
> > If anybody else wants to use CVS you can put your plugin code up in
> > squirrel-sql/plugins/<plugin_internal_name> but just remember that
you'll
> > need to copy it over to the new module later.
> >
> > Col
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list

> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Colin,

Hmm.. checked in as text shouldn't matter.  From your win32 box try the
following once you've done a fresh checkout of the module 'squirrel'

c:\cvs\squirrel>configure.bat

c:\cvs\squirrel>build.bat dist

Try those two commands which should configure your environment and build
a distribution.. (It works on my unix box and win32 box).  I personally
don't use the default cmd.exe shell provided with win32, I use cygwin
which emulates a unix shell on my win32 environment.  In any event,
that's whole nother can of worms..

Try that and tell me exactly what happens despite the CVS warnings that
you get..

-P


Colin Bell wrote:
> 
> Hi Patrick,
> 
> No I wasn't. I sent you an email from home last night but it hasn't got to
> the list yet - Bloody ISP! (or just possibly I forget to actually send it).
> 
> I wasn't able to build as all the binary files seem to have gone up as text
> (jars, gifs etc.) I'm new to CVS so bear with me while I ask some stupid
> questions. Is this anything to do with the way I checked the module out? I'm
> using WinCVS and it did a good job of recognising the different file types
> when I did the original import and checking them back out just seemed to
> work but now that you've done an import from a different OS are we having
> some kind of file compatability problem?
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Thursday, 22 November 2001 9:47
> Cc: Squirrel Developers List (E-mail)
> Subject: Re: [Squirrel-sql-develop] CVS
> 
> Were you able to get the program to build?  the squirrel module builds
> properly.  I commented out the plugins from the installer since it was
> not properly working.  Other, than that it builds ok.  (see
> src/resources/izpack/izpack-complete-buildmagic.xml)
> 
> -P
> 
> Colin Bell wrote:
> >
> > Hi Patrick,
> >
> > Until we get the BuildMagic process sorted out I'll just keep using the
> > squirrel-sql module and I will manually synch them up later.
> >
> > If anybody else wants to use CVS you can put your plugin code up in
> > squirrel-sql/plugins/<plugin_internal_name> but just remember that you'll
> > need to copy it over to the new module later.
> >
> > Col
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list

> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Hi Patrick,

No I wasn't. I sent you an email from home last night but it hasn't got to
the list yet - Bloody ISP! (or just possibly I forget to actually send it).

I wasn't able to build as all the binary files seem to have gone up as text
(jars, gifs etc.) I'm new to CVS so bear with me while I ask some stupid
questions. Is this anything to do with the way I checked the module out? I'm
using WinCVS and it did a good job of recognising the different file types
when I did the original import and checking them back out just seemed to
work but now that you've done an import from a different OS are we having
some kind of file compatability problem?

Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Thursday, 22 November 2001 9:47
Cc: Squirrel Developers List (E-mail)
Subject: Re: [Squirrel-sql-develop] CVS


Were you able to get the program to build?  the squirrel module builds
properly.  I commented out the plugins from the installer since it was
not properly working.  Other, than that it builds ok.  (see
src/resources/izpack/izpack-complete-buildmagic.xml)

-P

Colin Bell wrote:
> 
> Hi Patrick,
> 
> Until we get the BuildMagic process sorted out I'll just keep using the
> squirrel-sql module and I will manually synch them up later.
> 
> If anybody else wants to use CVS you can put your plugin code up in
> squirrel-sql/plugins/<plugin_internal_name> but just remember that you'll
> need to copy it over to the new module later.
> 
> Col
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Were you able to get the program to build?  the squirrel module builds
properly.  I commented out the plugins from the installer since it was
not properly working.  Other, than that it builds ok.  (see
src/resources/izpack/izpack-complete-buildmagic.xml)

-P

Colin Bell wrote:
> 
> Hi Patrick,
> 
> Until we get the BuildMagic process sorted out I'll just keep using the
> squirrel-sql module and I will manually synch them up later.
> 
> If anybody else wants to use CVS you can put your plugin code up in
> squirrel-sql/plugins/<plugin_internal_name> but just remember that you'll
> need to copy it over to the new module later.
> 
> Col
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Hi Patrick,

Until we get the BuildMagic process sorted out I'll just keep using the
squirrel-sql module and I will manually synch them up later.

If anybody else wants to use CVS you can put your plugin code up in
squirrel-sql/plugins/<plugin_internal_name> but just remember that you'll
need to copy it over to the new module later.

Col

Hi Patrick,

The link http://sourceforge.net/docman/display_doc.php?docid=772&group_id=1
has some instructions on how to setup CVS on SourceForge to email a mailing
list whenever code gets checked into CVS. I took a look at the instructions
but when I hit the line saying "chmod +x" I knew I wouldn't be able to do it
under Windows. Would you be able to setup the Squirrel CVS to email to
squ...@li...?

Thanks
Col

I'm synching CVS now... Stay tuned for further developments.

-----Original Message-----
From: squ...@li...
[mailto:squ...@li...]On Behalf Of
Patrick Lacson
Sent: Wednesday, 21 November 2001 4:54 PM
To: Colin Bell
Cc: 'pa...@la...'; squirrel-dev
Subject: RE: [Squirrel-sql-develop] new module 'squirrel'


I tried and could not get plugins working.. I believe the structure is
correct.

Could you try running

./build dist

run

java -jar <version>-install.jar

and look at the produced plugins directory..

I believe I have it right.  I checked the squirrel-log file and nothing
out of the ordinary except for the exceptions of not being able to load
the default jdbc drivers from the CLASSPATH..

-P

On Wed, 21 Nov 2001, Colin Bell wrote:

> Take a look at /squirrel/doc/plugins.html for more info.
>
> If you think the have the directory structure correct (see below) but
you're
> not getting any plugins loaded make sure that the system property user.dir
> is pointed to the directory that contains the plugins directory. This
would
> normally be the case if your shell script is in <squirrel-app> and the
> plugins in <squirrel-app>/plugins.
>
> One screwup that can occur in Windows is in you create a shortcut to the
> batch file and change the working directory to the something other than
the
> default.
>
> If it still doesn't work look for any error msgs in
> <user-home>/.squirrel-sql/squirrel-sql.log
>
> You can get more info from the log by editing
> <user-home>/.squirrel-sql/prefs.xml and replacing
>         <debugMode>false</debugMode>
>
> with
>         <debugMode>true</debugMode>
>
> Squirrel should be shutdown while you edit prefs.xml or it will overwrite
> your changes.
>
> ----------------------
>
> The plugin jars should live in the <squirrel-app>/plugins directory. All
> other files should be kept within the plugins personal direcotry beneath
> plugins.
>
> E.G. The Look and Feel plugin has an internal name of laf so its jar
should
> be called laf.jar, it should be placed in /plugins and its own files
should
> eb placed in /plugins/laf
>
> C:\sql\plugins>dir /s
>  Volume in drive C has no label.
>  Volume Serial Number is 9802-DD37
>
>
>  Directory of C:\sql\plugins
>
> 21/11/01  11:48         <DIR>          .
> 21/11/01  11:48         <DIR>          ..
> 21/11/01  11:47         <DIR>          laf
> 20/11/01  09:34                 28,267 laf.jar
>                4 File(s)         28,267 bytes
>
>  Directory of C:\sql\plugins\laf
>
> 21/11/01  11:47         <DIR>          .
> 21/11/01  11:47         <DIR>          ..
> 20/11/01  09:34                 26,925 kunststoff_Licence.txt
> 21/11/01  11:47         <DIR>          lafs
> 20/11/01  09:34                364,713 skinlf.jar
> 20/11/01  09:34                  2,383 skin_look_and_feel_licence.txt
> 20/11/01  09:34                 34,072 src.jar
> 21/11/01  11:47         <DIR>          theme_packs
>                8 File(s)        428,093 bytes
>
>  Directory of C:\sql\plugins\laf\lafs
>
> 21/11/01  11:47         <DIR>          .
> 21/11/01  11:47         <DIR>          ..
> 20/11/01  09:34                 23,595 kunststoff.jar
> 20/11/01  09:34                    163 readme.txt
>                4 File(s)         23,758 bytes
>
>  Directory of C:\sql\plugins\laf\theme_packs
>
> 21/11/01  11:47         <DIR>          .
> 21/11/01  11:47         <DIR>          ..
> 24/07/01  16:52                108,854 aquathemepack.zip
> 24/07/01  16:52                 22,851 beosthemepack.zip
> 24/07/01  16:52                108,049 macosthemepack.zip
> 24/07/01  16:52                 45,799 modernthemepack.zip
> 20/11/01  09:34                    123 readme.txt
> 20/06/01  05:11                 27,898 themepack.zip
> 20/11/01  09:34                 25,550 whistlerthemepack.zip
>                9 File(s)        339,124 bytes
>
>
> Hope this helps.
> Col
>
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Wednesday, 21 November 2001 10:10
> To: squirrel-dev
> Subject: Re: [Squirrel-sql-develop] new module 'squirrel'
>
>
> The installation now works, however I think I really need help on the
> plugins section.  Should I just drop the say lafs.jar into the
> plugins/lafs.jar directory and everything will automagically happen?  I
> tried loading the plugin jar files into the plugins directory and from
> the UI I look at Plugins and it just shows 'Summary' with a big empty
> text box.
>
> Any ideas what I'm doing wrong?  Anyway I think the build-system is 95%
> ready with the plugins still preventing a golden build.
>
> -P
>
>
>
> Patrick Lacson wrote:
> >
> > All,
> >
> > I think with buildmagic, the one thing we have to get used to is a
> > CLASSPATH-less environment.  Also your environment must not have
> > ANT_HOME set or the incorrect version of ANT may be used.  The
> > build-system "magically" creates the CLASSPATH for us providing a very
> > tight and clean build room.  This prevents any possiblity of
> > contaminated libraries from being loaded which could potentially break
> > compilation.  So with that I give my status update..
> >
> > The squirrel module is now 90% complete.  I've checked in the izPack
> > libraries and 'skeleton' templates that are required to build.
> >
> > Right now an untested install.jar is created by typing:
> >
> > ./build izpack
> >
> > This will automatically compile all the sources and create the jars and
> > pack them into the install.jar located in the root directory as
> >
> > ./squirrel-0.1-alpha-install.jar (naming can easily be modified later)
> >
> > For developers who want to start the application directly from their
> > build environment they can by typing
> >
> > ./build start (this will launch the application in a separate JVM)
> >
> > Colin,
> >
> > I noticed that you have 2 version of the installation, basic and
> > complete.  I take it that basic is without the source code and plugins,
> > while complete is everytihng but the kitchen sink?  Also can somebody
> > explain the concept of plugins?  Are we using them as dynamically
> > loadable components?  Or are they just plugins that extend the
> > application?  For example if we wanted to add a query-wizard, that would
> > be added as a plugin right?  Is the plugin a open interface or is it
> > something that we wrote in-house?  Open-interface I mean something like
> > JMX which seems to be the hottest buzz word for "pluggable" components
> > in the J2EE space..
> >
> > Thanks,
> >
> > -P
> >
> > Patrick Lacson wrote:
> > >
> > > Guys,
> > >
> > > This was a lot quicker than I suspected.  The new module squirrel is
> > > ready to go.  The only important target left is "release".
> > >
> > > So far the new system can compile the sources and run the app from a
> > > target.
> > >
> > > Just read the README on how to compile and run.  The release target
will
> > > be a bit tricky since Colin has an elaborate scheme with the izPack
> > > stuff which I haven't looked at yet.. MOre fun tommorow!
> > >
> > > Just a reminder, checkins will now have to be carefully monitored
since
> > > we've created a whole new module.  I wish I could say that his is a
> > > branch but it is not, it is a whole new module due to the new tree
> > > structures.
> > >
> > > So pleasse let's all be careful before checking in any new code or
else
> > > we could easily muck up the two modules and get out of sync and create
> > > mass confusion!!  Colin, any ideas on how we can keep everybody from
> > > checking stuff in?  Or rather how can be best prevent an out-of-sync
> > > situation between the modules.  They are in sync as of 11/19/2001
7:00pm
> > > Pacific Standard Time
> > >
> > > -P
> > >
> > > _______________________________________________
> > > Squirrel-sql-develop mailing list
> > > Squ...@li...
> > > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

--
</Patrick>
pa...@bo...
Ext: 3694


_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

I tried and could not get plugins working.. I believe the structure is
correct.

Could you try running

./build dist

run

java -jar <version>-install.jar

and look at the produced plugins directory..

I believe I have it right.  I checked the squirrel-log file and nothing
out of the ordinary except for the exceptions of not being able to load
the default jdbc drivers from the CLASSPATH..

-P

On Wed, 21 Nov 2001, Colin Bell wrote:

> Take a look at /squirrel/doc/plugins.html for more info.
>
> If you think the have the directory structure correct (see below) but you're
> not getting any plugins loaded make sure that the system property user.dir
> is pointed to the directory that contains the plugins directory. This would
> normally be the case if your shell script is in <squirrel-app> and the
> plugins in <squirrel-app>/plugins.
>
> One screwup that can occur in Windows is in you create a shortcut to the
> batch file and change the working directory to the something other than the
> default.
>
> If it still doesn't work look for any error msgs in
> <user-home>/.squirrel-sql/squirrel-sql.log
>
> You can get more info from the log by editing
> <user-home>/.squirrel-sql/prefs.xml and replacing
>         <debugMode>false</debugMode>
>
> with
>         <debugMode>true</debugMode>
>
> Squirrel should be shutdown while you edit prefs.xml or it will overwrite
> your changes.
>
> ----------------------
>
> The plugin jars should live in the <squirrel-app>/plugins directory. All
> other files should be kept within the plugins personal direcotry beneath
> plugins.
>
> E.G. The Look and Feel plugin has an internal name of laf so its jar should
> be called laf.jar, it should be placed in /plugins and its own files should
> eb placed in /plugins/laf
>
> C:\sql\plugins>dir /s
>  Volume in drive C has no label.
>  Volume Serial Number is 9802-DD37
>
>
>  Directory of C:\sql\plugins
>
> 21/11/01  11:48         <DIR>          .
> 21/11/01  11:48         <DIR>          ..
> 21/11/01  11:47         <DIR>          laf
> 20/11/01  09:34                 28,267 laf.jar
>                4 File(s)         28,267 bytes
>
>  Directory of C:\sql\plugins\laf
>
> 21/11/01  11:47         <DIR>          .
> 21/11/01  11:47         <DIR>          ..
> 20/11/01  09:34                 26,925 kunststoff_Licence.txt
> 21/11/01  11:47         <DIR>          lafs
> 20/11/01  09:34                364,713 skinlf.jar
> 20/11/01  09:34                  2,383 skin_look_and_feel_licence.txt
> 20/11/01  09:34                 34,072 src.jar
> 21/11/01  11:47         <DIR>          theme_packs
>                8 File(s)        428,093 bytes
>
>  Directory of C:\sql\plugins\laf\lafs
>
> 21/11/01  11:47         <DIR>          .
> 21/11/01  11:47         <DIR>          ..
> 20/11/01  09:34                 23,595 kunststoff.jar
> 20/11/01  09:34                    163 readme.txt
>                4 File(s)         23,758 bytes
>
>  Directory of C:\sql\plugins\laf\theme_packs
>
> 21/11/01  11:47         <DIR>          .
> 21/11/01  11:47         <DIR>          ..
> 24/07/01  16:52                108,854 aquathemepack.zip
> 24/07/01  16:52                 22,851 beosthemepack.zip
> 24/07/01  16:52                108,049 macosthemepack.zip
> 24/07/01  16:52                 45,799 modernthemepack.zip
> 20/11/01  09:34                    123 readme.txt
> 20/06/01  05:11                 27,898 themepack.zip
> 20/11/01  09:34                 25,550 whistlerthemepack.zip
>                9 File(s)        339,124 bytes
>
>
> Hope this helps.
> Col
>
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Wednesday, 21 November 2001 10:10
> To: squirrel-dev
> Subject: Re: [Squirrel-sql-develop] new module 'squirrel'
>
>
> The installation now works, however I think I really need help on the
> plugins section.  Should I just drop the say lafs.jar into the
> plugins/lafs.jar directory and everything will automagically happen?  I
> tried loading the plugin jar files into the plugins directory and from
> the UI I look at Plugins and it just shows 'Summary' with a big empty
> text box.
>
> Any ideas what I'm doing wrong?  Anyway I think the build-system is 95%
> ready with the plugins still preventing a golden build.
>
> -P
>
>
>
> Patrick Lacson wrote:
> >
> > All,
> >
> > I think with buildmagic, the one thing we have to get used to is a
> > CLASSPATH-less environment.  Also your environment must not have
> > ANT_HOME set or the incorrect version of ANT may be used.  The
> > build-system "magically" creates the CLASSPATH for us providing a very
> > tight and clean build room.  This prevents any possiblity of
> > contaminated libraries from being loaded which could potentially break
> > compilation.  So with that I give my status update..
> >
> > The squirrel module is now 90% complete.  I've checked in the izPack
> > libraries and 'skeleton' templates that are required to build.
> >
> > Right now an untested install.jar is created by typing:
> >
> > ./build izpack
> >
> > This will automatically compile all the sources and create the jars and
> > pack them into the install.jar located in the root directory as
> >
> > ./squirrel-0.1-alpha-install.jar (naming can easily be modified later)
> >
> > For developers who want to start the application directly from their
> > build environment they can by typing
> >
> > ./build start (this will launch the application in a separate JVM)
> >
> > Colin,
> >
> > I noticed that you have 2 version of the installation, basic and
> > complete.  I take it that basic is without the source code and plugins,
> > while complete is everytihng but the kitchen sink?  Also can somebody
> > explain the concept of plugins?  Are we using them as dynamically
> > loadable components?  Or are they just plugins that extend the
> > application?  For example if we wanted to add a query-wizard, that would
> > be added as a plugin right?  Is the plugin a open interface or is it
> > something that we wrote in-house?  Open-interface I mean something like
> > JMX which seems to be the hottest buzz word for "pluggable" components
> > in the J2EE space..
> >
> > Thanks,
> >
> > -P
> >
> > Patrick Lacson wrote:
> > >
> > > Guys,
> > >
> > > This was a lot quicker than I suspected.  The new module squirrel is
> > > ready to go.  The only important target left is "release".
> > >
> > > So far the new system can compile the sources and run the app from a
> > > target.
> > >
> > > Just read the README on how to compile and run.  The release target will
> > > be a bit tricky since Colin has an elaborate scheme with the izPack
> > > stuff which I haven't looked at yet.. MOre fun tommorow!
> > >
> > > Just a reminder, checkins will now have to be carefully monitored since
> > > we've created a whole new module.  I wish I could say that his is a
> > > branch but it is not, it is a whole new module due to the new tree
> > > structures.
> > >
> > > So pleasse let's all be careful before checking in any new code or else
> > > we could easily muck up the two modules and get out of sync and create
> > > mass confusion!!  Colin, any ideas on how we can keep everybody from
> > > checking stuff in?  Or rather how can be best prevent an out-of-sync
> > > situation between the modules.  They are in sync as of 11/19/2001 7:00pm
> > > Pacific Standard Time
> > >
> > > -P
> > >
> > > _______________________________________________
> > > Squirrel-sql-develop mailing list
> > > Squ...@li...
> > > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

-- 
</Patrick>
pa...@bo...
Ext: 3694

Don't worry about it - found your code in my Yahoo account. <Duh/>



-----Original Message-----
From: Colin Bell 
Sent: Wednesday, 21 November 2001 12:01
To: 'Guido Cervone'; 'squ...@li...'
Subject: RE: [Squirrel-sql-develop] Re: Inductive Databases and squirrel


Hi Guido,

Could you please repost your code to the list. I've just lost the harddrive
on my laptop and that contained the only copy of it.

Thanks
Col

-----Original Message-----
From: Guido Cervone [mailto:gce...@gm...]
Sent: Tuesday, 20 November 2001 18:12
To: squ...@li...
Subject: [Squirrel-sql-develop] Re: Inductive Databases and squirrel


Guido Cervone wrote:
> 
> Hello everyone,
> 
> sorry for entering the circuite late. Last week was though and I did not
> have time to write anything.   Colin, I am going to write here my
> project description that I think I sent you already.
> 
> A little of introduction:
> 
> I work in the Machine Learning and Inference Laboratory at the George
> Mason University in Fairfax, VA, USA.  We are developing what we call an
> 'inductive database', which in brief is a system that allows creating
> knowlege using simple SQL-like commands. The knowledge can be expressed
> as attributional rules that describe specific patterns, as a conceptual
> association graph, as a tree, etc.
> 
> The idea is to extend the SQL language with few new commands that will
> invoke specific knowlege generation operators. We tentatively called
> this extension of the SQL language KQL, which stands for Knowledge Query
> Language.  However this is not finalized, and we would like some
> suggestions.   For example, the command to extract rules looks like the
> following:
> 
> create rules from <Event_Table> for <Decision_Attribute> using
> <Parameters_Table>
> 
> Inductive databses will allow people with little or no experience in
> Machine Learning, Statistics, etc to run sophisticated algorithms and
> possibly discover new knowledge.
> 
> To implement these ideas we considered writing our own SQL client, and
> we realizes this is a too big effort.  We started looking at several
> alternatives for an open-source SQL client we could extend, and we
> finally landed in the Squirrel world! I think it would be nice if such
> capabilities could be built into Squirrel, maybe using a plugin, that
> Colin likes so much! :)
> 
> I have modified the source code for 1.0 to accomodate some of our
> needs.  The first feature that I believe is very interesting is allowing
> Squirrel to import a comma separated file.  This very useful to enter
> data that is stored locally.
> Next I have added an extra parser for KQL commands.  It checks the sql
> statement, and if it finds something like create rules, then it invokes
> the correct knowledge generation operator.
> 
> 
> Thanks
> 
> Guido

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Hi Guido,

Could you please repost your code to the list. I've just lost the harddrive
on my laptop and that contained the only copy of it.

Thanks
Col

-----Original Message-----
From: Guido Cervone [mailto:gce...@gm...]
Sent: Tuesday, 20 November 2001 18:12
To: squ...@li...
Subject: [Squirrel-sql-develop] Re: Inductive Databases and squirrel


Guido Cervone wrote:
> 
> Hello everyone,
> 
> sorry for entering the circuite late. Last week was though and I did not
> have time to write anything.   Colin, I am going to write here my
> project description that I think I sent you already.
> 
> A little of introduction:
> 
> I work in the Machine Learning and Inference Laboratory at the George
> Mason University in Fairfax, VA, USA.  We are developing what we call an
> 'inductive database', which in brief is a system that allows creating
> knowlege using simple SQL-like commands. The knowledge can be expressed
> as attributional rules that describe specific patterns, as a conceptual
> association graph, as a tree, etc.
> 
> The idea is to extend the SQL language with few new commands that will
> invoke specific knowlege generation operators. We tentatively called
> this extension of the SQL language KQL, which stands for Knowledge Query
> Language.  However this is not finalized, and we would like some
> suggestions.   For example, the command to extract rules looks like the
> following:
> 
> create rules from <Event_Table> for <Decision_Attribute> using
> <Parameters_Table>
> 
> Inductive databses will allow people with little or no experience in
> Machine Learning, Statistics, etc to run sophisticated algorithms and
> possibly discover new knowledge.
> 
> To implement these ideas we considered writing our own SQL client, and
> we realizes this is a too big effort.  We started looking at several
> alternatives for an open-source SQL client we could extend, and we
> finally landed in the Squirrel world! I think it would be nice if such
> capabilities could be built into Squirrel, maybe using a plugin, that
> Colin likes so much! :)
> 
> I have modified the source code for 1.0 to accomodate some of our
> needs.  The first feature that I believe is very interesting is allowing
> Squirrel to import a comma separated file.  This very useful to enter
> data that is stored locally.
> Next I have added an extra parser for KQL commands.  It checks the sql
> statement, and if it finds something like create rules, then it invokes
> the correct knowledge generation operator.
> 
> 
> Thanks
> 
> Guido

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Patrick,

My laptop just died so I haven't had a look at your work.

<snip>
I noticed that you have 2 version of the installation, basic and
complete.  I take it that basic is without the source code and plugins,
while complete is everytihng but the kitchen sink?
</snip>

Basic is probably the distribution that we'd actualy use and then each user
of Squirrel can decide which plugins they want and download just those.
Complete (the squirrel app, source, all plugins etc.) we may also put up so
that those who want to take a look at everything can do so without having to
do multiple downloads and installs. No decision has been made yet.

<snip>
Also can somebody
explain the concept of plugins?  Are we using them as dynamically
loadable components?  Or are they just plugins that extend the
application?  For example if we wanted to add a query-wizard, that would
be added as a plugin right?  Is the plugin a open interface or is it
something that we wrote in-house?  Open-interface I mean something like
JMX which seems to be the hottest buzz word for "pluggable" components
in the J2EE space..
</snip>

A plugin is a piece of code that is loaded into Squirrel at runtime. This
code can then modify the Squirrel environment and add functionality to it.
E.G. The Look and Feel plugin adds a tab to the application settings
allowing people to select a different look and feel; at startup it sets the
look and feel to what was previously selected.

The plugin API is just somethibng I started hacking together, its certainly
not based on anything like JMX.

Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Wednesday, 21 November 2001 7:25
To: squirrel-dev
Subject: Re: [Squirrel-sql-develop] new module 'squirrel'


All,

I think with buildmagic, the one thing we have to get used to is a
CLASSPATH-less environment.  Also your environment must not have
ANT_HOME set or the incorrect version of ANT may be used.  The
build-system "magically" creates the CLASSPATH for us providing a very
tight and clean build room.  This prevents any possiblity of
contaminated libraries from being loaded which could potentially break
compilation.  So with that I give my status update..

The squirrel module is now 90% complete.  I've checked in the izPack
libraries and 'skeleton' templates that are required to build.

Right now an untested install.jar is created by typing:

./build izpack

This will automatically compile all the sources and create the jars and
pack them into the install.jar located in the root directory as

./squirrel-0.1-alpha-install.jar (naming can easily be modified later)

For developers who want to start the application directly from their
build environment they can by typing

./build start (this will launch the application in a separate JVM)

Colin,

I noticed that you have 2 version of the installation, basic and
complete.  I take it that basic is without the source code and plugins,
while complete is everytihng but the kitchen sink?  Also can somebody
explain the concept of plugins?  Are we using them as dynamically
loadable components?  Or are they just plugins that extend the
application?  For example if we wanted to add a query-wizard, that would
be added as a plugin right?  Is the plugin a open interface or is it
something that we wrote in-house?  Open-interface I mean something like
JMX which seems to be the hottest buzz word for "pluggable" components
in the J2EE space..

Thanks,

-P





Patrick Lacson wrote:
> 
> Guys,
> 
> This was a lot quicker than I suspected.  The new module squirrel is
> ready to go.  The only important target left is "release".
> 
> So far the new system can compile the sources and run the app from a
> target.
> 
> Just read the README on how to compile and run.  The release target will
> be a bit tricky since Colin has an elaborate scheme with the izPack
> stuff which I haven't looked at yet.. MOre fun tommorow!
> 
> Just a reminder, checkins will now have to be carefully monitored since
> we've created a whole new module.  I wish I could say that his is a
> branch but it is not, it is a whole new module due to the new tree
> structures.
> 
> So pleasse let's all be careful before checking in any new code or else
> we could easily muck up the two modules and get out of sync and create
> mass confusion!!  Colin, any ideas on how we can keep everybody from
> checking stuff in?  Or rather how can be best prevent an out-of-sync
> situation between the modules.  They are in sync as of 11/19/2001 7:00pm
> Pacific Standard Time
> 
> -P
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Take a look at /squirrel/doc/plugins.html for more info.

If you think the have the directory structure correct (see below) but you're
not getting any plugins loaded make sure that the system property user.dir
is pointed to the directory that contains the plugins directory. This would
normally be the case if your shell script is in <squirrel-app> and the
plugins in <squirrel-app>/plugins.

One screwup that can occur in Windows is in you create a shortcut to the
batch file and change the working directory to the something other than the
default.

If it still doesn't work look for any error msgs in
<user-home>/.squirrel-sql/squirrel-sql.log

You can get more info from the log by editing
<user-home>/.squirrel-sql/prefs.xml and replacing 
        <debugMode>false</debugMode>

with
        <debugMode>true</debugMode>

Squirrel should be shutdown while you edit prefs.xml or it will overwrite
your changes.

----------------------

The plugin jars should live in the <squirrel-app>/plugins directory. All
other files should be kept within the plugins personal direcotry beneath
plugins.

E.G. The Look and Feel plugin has an internal name of laf so its jar should
be called laf.jar, it should be placed in /plugins and its own files should
eb placed in /plugins/laf

C:\sql\plugins>dir /s
 Volume in drive C has no label.
 Volume Serial Number is 9802-DD37


 Directory of C:\sql\plugins

21/11/01  11:48         <DIR>          .
21/11/01  11:48         <DIR>          ..
21/11/01  11:47         <DIR>          laf
20/11/01  09:34                 28,267 laf.jar
               4 File(s)         28,267 bytes

 Directory of C:\sql\plugins\laf

21/11/01  11:47         <DIR>          .
21/11/01  11:47         <DIR>          ..
20/11/01  09:34                 26,925 kunststoff_Licence.txt
21/11/01  11:47         <DIR>          lafs
20/11/01  09:34                364,713 skinlf.jar
20/11/01  09:34                  2,383 skin_look_and_feel_licence.txt
20/11/01  09:34                 34,072 src.jar
21/11/01  11:47         <DIR>          theme_packs
               8 File(s)        428,093 bytes

 Directory of C:\sql\plugins\laf\lafs

21/11/01  11:47         <DIR>          .
21/11/01  11:47         <DIR>          ..
20/11/01  09:34                 23,595 kunststoff.jar
20/11/01  09:34                    163 readme.txt
               4 File(s)         23,758 bytes

 Directory of C:\sql\plugins\laf\theme_packs

21/11/01  11:47         <DIR>          .
21/11/01  11:47         <DIR>          ..
24/07/01  16:52                108,854 aquathemepack.zip
24/07/01  16:52                 22,851 beosthemepack.zip
24/07/01  16:52                108,049 macosthemepack.zip
24/07/01  16:52                 45,799 modernthemepack.zip
20/11/01  09:34                    123 readme.txt
20/06/01  05:11                 27,898 themepack.zip
20/11/01  09:34                 25,550 whistlerthemepack.zip
               9 File(s)        339,124 bytes


Hope this helps.
Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Wednesday, 21 November 2001 10:10
To: squirrel-dev
Subject: Re: [Squirrel-sql-develop] new module 'squirrel'


The installation now works, however I think I really need help on the
plugins section.  Should I just drop the say lafs.jar into the
plugins/lafs.jar directory and everything will automagically happen?  I
tried loading the plugin jar files into the plugins directory and from
the UI I look at Plugins and it just shows 'Summary' with a big empty
text box.

Any ideas what I'm doing wrong?  Anyway I think the build-system is 95%
ready with the plugins still preventing a golden build.

-P



Patrick Lacson wrote:
> 
> All,
> 
> I think with buildmagic, the one thing we have to get used to is a
> CLASSPATH-less environment.  Also your environment must not have
> ANT_HOME set or the incorrect version of ANT may be used.  The
> build-system "magically" creates the CLASSPATH for us providing a very
> tight and clean build room.  This prevents any possiblity of
> contaminated libraries from being loaded which could potentially break
> compilation.  So with that I give my status update..
> 
> The squirrel module is now 90% complete.  I've checked in the izPack
> libraries and 'skeleton' templates that are required to build.
> 
> Right now an untested install.jar is created by typing:
> 
> ./build izpack
> 
> This will automatically compile all the sources and create the jars and
> pack them into the install.jar located in the root directory as
> 
> ./squirrel-0.1-alpha-install.jar (naming can easily be modified later)
> 
> For developers who want to start the application directly from their
> build environment they can by typing
> 
> ./build start (this will launch the application in a separate JVM)
> 
> Colin,
> 
> I noticed that you have 2 version of the installation, basic and
> complete.  I take it that basic is without the source code and plugins,
> while complete is everytihng but the kitchen sink?  Also can somebody
> explain the concept of plugins?  Are we using them as dynamically
> loadable components?  Or are they just plugins that extend the
> application?  For example if we wanted to add a query-wizard, that would
> be added as a plugin right?  Is the plugin a open interface or is it
> something that we wrote in-house?  Open-interface I mean something like
> JMX which seems to be the hottest buzz word for "pluggable" components
> in the J2EE space..
> 
> Thanks,
> 
> -P
> 
> Patrick Lacson wrote:
> >
> > Guys,
> >
> > This was a lot quicker than I suspected.  The new module squirrel is
> > ready to go.  The only important target left is "release".
> >
> > So far the new system can compile the sources and run the app from a
> > target.
> >
> > Just read the README on how to compile and run.  The release target will
> > be a bit tricky since Colin has an elaborate scheme with the izPack
> > stuff which I haven't looked at yet.. MOre fun tommorow!
> >
> > Just a reminder, checkins will now have to be carefully monitored since
> > we've created a whole new module.  I wish I could say that his is a
> > branch but it is not, it is a whole new module due to the new tree
> > structures.
> >
> > So pleasse let's all be careful before checking in any new code or else
> > we could easily muck up the two modules and get out of sync and create
> > mass confusion!!  Colin, any ideas on how we can keep everybody from
> > checking stuff in?  Or rather how can be best prevent an out-of-sync
> > situation between the modules.  They are in sync as of 11/19/2001 7:00pm
> > Pacific Standard Time
> >
> > -P
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

The installation now works, however I think I really need help on the
plugins section.  Should I just drop the say lafs.jar into the
plugins/lafs.jar directory and everything will automagically happen?  I
tried loading the plugin jar files into the plugins directory and from
the UI I look at Plugins and it just shows 'Summary' with a big empty
text box.

Any ideas what I'm doing wrong?  Anyway I think the build-system is 95%
ready with the plugins still preventing a golden build.

-P



Patrick Lacson wrote:
> 
> All,
> 
> I think with buildmagic, the one thing we have to get used to is a
> CLASSPATH-less environment.  Also your environment must not have
> ANT_HOME set or the incorrect version of ANT may be used.  The
> build-system "magically" creates the CLASSPATH for us providing a very
> tight and clean build room.  This prevents any possiblity of
> contaminated libraries from being loaded which could potentially break
> compilation.  So with that I give my status update..
> 
> The squirrel module is now 90% complete.  I've checked in the izPack
> libraries and 'skeleton' templates that are required to build.
> 
> Right now an untested install.jar is created by typing:
> 
> ./build izpack
> 
> This will automatically compile all the sources and create the jars and
> pack them into the install.jar located in the root directory as
> 
> ./squirrel-0.1-alpha-install.jar (naming can easily be modified later)
> 
> For developers who want to start the application directly from their
> build environment they can by typing
> 
> ./build start (this will launch the application in a separate JVM)
> 
> Colin,
> 
> I noticed that you have 2 version of the installation, basic and
> complete.  I take it that basic is without the source code and plugins,
> while complete is everytihng but the kitchen sink?  Also can somebody
> explain the concept of plugins?  Are we using them as dynamically
> loadable components?  Or are they just plugins that extend the
> application?  For example if we wanted to add a query-wizard, that would
> be added as a plugin right?  Is the plugin a open interface or is it
> something that we wrote in-house?  Open-interface I mean something like
> JMX which seems to be the hottest buzz word for "pluggable" components
> in the J2EE space..
> 
> Thanks,
> 
> -P
> 
> Patrick Lacson wrote:
> >
> > Guys,
> >
> > This was a lot quicker than I suspected.  The new module squirrel is
> > ready to go.  The only important target left is "release".
> >
> > So far the new system can compile the sources and run the app from a
> > target.
> >
> > Just read the README on how to compile and run.  The release target will
> > be a bit tricky since Colin has an elaborate scheme with the izPack
> > stuff which I haven't looked at yet.. MOre fun tommorow!
> >
> > Just a reminder, checkins will now have to be carefully monitored since
> > we've created a whole new module.  I wish I could say that his is a
> > branch but it is not, it is a whole new module due to the new tree
> > structures.
> >
> > So pleasse let's all be careful before checking in any new code or else
> > we could easily muck up the two modules and get out of sync and create
> > mass confusion!!  Colin, any ideas on how we can keep everybody from
> > checking stuff in?  Or rather how can be best prevent an out-of-sync
> > situation between the modules.  They are in sync as of 11/19/2001 7:00pm
> > Pacific Standard Time
> >
> > -P
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

All,

I think with buildmagic, the one thing we have to get used to is a
CLASSPATH-less environment.  Also your environment must not have
ANT_HOME set or the incorrect version of ANT may be used.  The
build-system "magically" creates the CLASSPATH for us providing a very
tight and clean build room.  This prevents any possiblity of
contaminated libraries from being loaded which could potentially break
compilation.  So with that I give my status update..

The squirrel module is now 90% complete.  I've checked in the izPack
libraries and 'skeleton' templates that are required to build.

Right now an untested install.jar is created by typing:

./build izpack

This will automatically compile all the sources and create the jars and
pack them into the install.jar located in the root directory as

./squirrel-0.1-alpha-install.jar (naming can easily be modified later)

For developers who want to start the application directly from their
build environment they can by typing

./build start (this will launch the application in a separate JVM)

Colin,

I noticed that you have 2 version of the installation, basic and
complete.  I take it that basic is without the source code and plugins,
while complete is everytihng but the kitchen sink?  Also can somebody
explain the concept of plugins?  Are we using them as dynamically
loadable components?  Or are they just plugins that extend the
application?  For example if we wanted to add a query-wizard, that would
be added as a plugin right?  Is the plugin a open interface or is it
something that we wrote in-house?  Open-interface I mean something like
JMX which seems to be the hottest buzz word for "pluggable" components
in the J2EE space..

Thanks,

-P





Patrick Lacson wrote:
> 
> Guys,
> 
> This was a lot quicker than I suspected.  The new module squirrel is
> ready to go.  The only important target left is "release".
> 
> So far the new system can compile the sources and run the app from a
> target.
> 
> Just read the README on how to compile and run.  The release target will
> be a bit tricky since Colin has an elaborate scheme with the izPack
> stuff which I haven't looked at yet.. MOre fun tommorow!
> 
> Just a reminder, checkins will now have to be carefully monitored since
> we've created a whole new module.  I wish I could say that his is a
> branch but it is not, it is a whole new module due to the new tree
> structures.
> 
> So pleasse let's all be careful before checking in any new code or else
> we could easily muck up the two modules and get out of sync and create
> mass confusion!!  Colin, any ideas on how we can keep everybody from
> checking stuff in?  Or rather how can be best prevent an out-of-sync
> situation between the modules.  They are in sync as of 11/19/2001 7:00pm
> Pacific Standard Time
> 
> -P
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Guido Cervone wrote:
> 
> Hello everyone,
> 
> sorry for entering the circuite late. Last week was though and I did not
> have time to write anything.   Colin, I am going to write here my
> project description that I think I sent you already.
> 
> A little of introduction:
> 
> I work in the Machine Learning and Inference Laboratory at the George
> Mason University in Fairfax, VA, USA.  We are developing what we call an
> 'inductive database', which in brief is a system that allows creating
> knowlege using simple SQL-like commands. The knowledge can be expressed
> as attributional rules that describe specific patterns, as a conceptual
> association graph, as a tree, etc.
> 
> The idea is to extend the SQL language with few new commands that will
> invoke specific knowlege generation operators. We tentatively called
> this extension of the SQL language KQL, which stands for Knowledge Query
> Language.  However this is not finalized, and we would like some
> suggestions.   For example, the command to extract rules looks like the
> following:
> 
> create rules from <Event_Table> for <Decision_Attribute> using
> <Parameters_Table>
> 
> Inductive databses will allow people with little or no experience in
> Machine Learning, Statistics, etc to run sophisticated algorithms and
> possibly discover new knowledge.
> 
> To implement these ideas we considered writing our own SQL client, and
> we realizes this is a too big effort.  We started looking at several
> alternatives for an open-source SQL client we could extend, and we
> finally landed in the Squirrel world! I think it would be nice if such
> capabilities could be built into Squirrel, maybe using a plugin, that
> Colin likes so much! :)
> 
> I have modified the source code for 1.0 to accomodate some of our
> needs.  The first feature that I believe is very interesting is allowing
> Squirrel to import a comma separated file.  This very useful to enter
> data that is stored locally.
> Next I have added an extra parser for KQL commands.  It checks the sql
> statement, and if it finds something like create rules, then it invokes
> the correct knowledge generation operator.
> 
> 
> Thanks
> 
> Guido

Each day SourceForge generates a tarball of the CVS repository for projects.
Those of you who still haven't got CVS working can get the tarball for
Squirrel from
http://cvs.sourceforge.net/cvstarballs/squirrel-sql-cvsroot.tar.gz

The current one obviously won't have Patricks work in in yet.

Guys,

This was a lot quicker than I suspected.  The new module squirrel is
ready to go.  The only important target left is "release".

So far the new system can compile the sources and run the app from a
target.

Just read the README on how to compile and run.  The release target will
be a bit tricky since Colin has an elaborate scheme with the izPack
stuff which I haven't looked at yet.. MOre fun tommorow!

Just a reminder, checkins will now have to be carefully monitored since
we've created a whole new module.  I wish I could say that his is a
branch but it is not, it is a whole new module due to the new tree
structures. 

So pleasse let's all be careful before checking in any new code or else
we could easily muck up the two modules and get out of sync and create
mass confusion!!  Colin, any ideas on how we can keep everybody from
checking stuff in?  Or rather how can be best prevent an out-of-sync
situation between the modules.  They are in sync as of 11/19/2001 7:00pm
Pacific Standard Time

-P

Now that Patrick is starting to look at the build process we all need to
think about how we want to deploy plugins.

One of the important things about plugins is that they can be downloaded
separately from the main Squirrel distribution and then installed. The
question is how should that installation process occur?.

One method would be to simply unzip/untar the deployment file into the
<squirrel_app>/plugins folder hoping that they remember to use the "use
folder names" option. This has the advantage of simplicity from our point of
view but isn't real friendly. It also doesn't give us the option of running
any code at installation time although its debatable whether or not we
should, rather any first-time code should be run on the first execution of a
plugin.

Another possibility would be creating a IzPack installer for each plugin.
When the installer is run it would default to the install directory for
Squirrel (we would need to modify IzPack for this) unpack the plugin into
the appropriate directory structure etc.

As well we need to think about how we want the plugins to appear on the
SourceForge downloads page. I don't like the idea of each plugin having its
own package. Once you have a few plugins each with a few releases it would
get quite messy. I quite like the Jext method
http://sourceforge.net/project/showfiles.php?group_id=1494

Here there is a single package for all the plugins, each plugin has its own
release. This has the advantage of keeping everything simple. Possibly the
only change I would make would be putting the plugin release number as part
of the release name. This would make it easier for people to see whether a
new release has occurred.

Any ideas, comments?

Thanks Patrick.

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Tuesday, 20 November 2001 12:48
To: Colin Bell
Cc: 'col...@bi...'; squirrel-dev
Subject: Re: source


Colin,

I've checked in this minor change since you've added me as a developer. 
The Unix shell script is very simple for now and can be later modified
to check for JAVA_HOME but right now I think we can live with what we
have unless we have users complaining the script doesn't work.

-P

Colin Bell wrote:
> 
> Hi Patrick,
> 
> Thanks, good idea.
> 
> I don't use unix myself (although thats changing next month when I get my
> new PC), do you have any other suggestions for the script or for unix
> support in general within Squirrel?
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Tuesday, 20 November 2001 17:34
> To: Colin Bell
> Subject: Re: source
> 
> Colin,
> 
> I run cygwin from home and I suspect most other unix/win32 developers do
as
> well.  I'd like to recommend a minor hack in the squirrel-sql.sh script:
> 
> #! /bin/sh
> 
> if [ `uname -s` = "CYGWIN_NT-5.0" ]; then
> 
>
NT_CLASSPATH=squirrel-sql.jar:lib/jdom-b4.jar:lib/xerces.jar:lib/skinlf.jar.
> jar:$CLASSPATH
> 
>   #modify the CLASSPATH to speak cygtalk
>   NT_CLASSPATH=`cygpath -w -p $NT_CLASSPATH`
>   $JAVA_HOME/bin/java -cp $NT_CLASSPATH com.bigfoot.colbell.squirrel.Main
> else
>
UNIX_CP=squirrel-sql.jar:lib/jdom-b4.jar:lib/xerces.jar:lib/skinlf.jar.jar
>   UNIX_CP=$UNIX_CP:$CLASSPATH
>   $JAVA_HOME/bin/java -cp $UNIX_CP com.bigfoot.colbell.squirrel.Main
> fi
> 
> -Patrick
> 
> ----- Original Message -----
> From: "Colin Bell" <Col...@as...>
> To: <pa...@la...>
> Sent: Sunday, November 18, 2001 6:56 PM
> Subject: RE: source
> 
> > Hi Patrick,
> >
> > Squirrel is now up in CVS at SourceForge. Just send me your SF user name
> > (I've managed to lose it and theres a couple of Patrick Lacsons at SF)
and
> > I'll add you to the project.
> >
> > The current build stuff (such as it is) is in the module
> squirrel-sql/build.
> > If you could have a look at it I'd be muchly appreciative. I'm using Ant
> > (obviously) for the build process and the IzPack installer from
> > www.izforge.com to create the installer. One thing that would be nice
> would
> > be an Ant task for IzPack, its been discussed on the IzPack mailing list
> but
> > nothing seems to be happening and I can't see anyway I'm going to have
> time
> > to look at it.
> >
> > Thanks
> > Col
> >
> > -----Original Message-----
> > From: Patrick Lacson [mailto:pa...@la...]
> > Sent: Wednesday, 7 November 2001 11:07
> > To: co...@us...
> > Subject: Re: source
> >
> >
> > Yes!  I sit across the guy who wrote it.  He's now part of the JBoss
> > project and apparently they too started using BuildMagic.  Hopefully,
> > this will make your life easier.  Tell you what if you add me as a
> > developer for this project I can add the buildmagic project-template and
> > have your builds up and running in under a day.
> >
> > -P
> >
> > Colin Bell wrote:
> > >
> > > I'm interested in anything that makes my life easier
> > > <grin/>. Are you talking about the BuildMagic that is
> > > part of the Bliss project at SourceForge
> > > http://sourceforge.net/projects/bliss/?
> > >
> > > Col
> > >
> > >  --- Patrick Lacson <pa...@la...> wrote: >
> > > Colin,
> > > >
> > > > Would you be interested in an easier build sytem
> > > > that is based on Ant?
> > > > We currently use BuildMagic for our builds here at
> > > > work.  BuildMagic is
> > > > basically an extension of Ant allowing better
> > > > organizational semantics
> > > > and cleaner task extensions to Ant.
> > > >
> > > > -P
> > > >
> > > > Colin Bell wrote:
> > > > >
> > > > > Hi Pat,
> > > > >
> > > > > You can get the source from the latest release
> > > > >
> > > >
> > >
> >
>
http://sourceforge.net/project/showfiles.php?group_id=28383&release_id=59420

Gregs working on a plugin that will visually show the tables in a database
and the relationships. Eventually it should do a lot more than that. Heres a
screen capture of an example.

Col
 <<teaser1.gif>> 

Colin,

I've checked in this minor change since you've added me as a developer. 
The Unix shell script is very simple for now and can be later modified
to check for JAVA_HOME but right now I think we can live with what we
have unless we have users complaining the script doesn't work.

-P

Colin Bell wrote:
> 
> Hi Patrick,
> 
> Thanks, good idea.
> 
> I don't use unix myself (although thats changing next month when I get my
> new PC), do you have any other suggestions for the script or for unix
> support in general within Squirrel?
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Tuesday, 20 November 2001 17:34
> To: Colin Bell
> Subject: Re: source
> 
> Colin,
> 
> I run cygwin from home and I suspect most other unix/win32 developers do as
> well.  I'd like to recommend a minor hack in the squirrel-sql.sh script:
> 
> #! /bin/sh
> 
> if [ `uname -s` = "CYGWIN_NT-5.0" ]; then
> 
> NT_CLASSPATH=squirrel-sql.jar:lib/jdom-b4.jar:lib/xerces.jar:lib/skinlf.jar.
> jar:$CLASSPATH
> 
>   #modify the CLASSPATH to speak cygtalk
>   NT_CLASSPATH=`cygpath -w -p $NT_CLASSPATH`
>   $JAVA_HOME/bin/java -cp $NT_CLASSPATH com.bigfoot.colbell.squirrel.Main
> else
>   UNIX_CP=squirrel-sql.jar:lib/jdom-b4.jar:lib/xerces.jar:lib/skinlf.jar.jar
>   UNIX_CP=$UNIX_CP:$CLASSPATH
>   $JAVA_HOME/bin/java -cp $UNIX_CP com.bigfoot.colbell.squirrel.Main
> fi
> 
> -Patrick
> 
> ----- Original Message -----
> From: "Colin Bell" <Col...@as...>
> To: <pa...@la...>
> Sent: Sunday, November 18, 2001 6:56 PM
> Subject: RE: source
> 
> > Hi Patrick,
> >
> > Squirrel is now up in CVS at SourceForge. Just send me your SF user name
> > (I've managed to lose it and theres a couple of Patrick Lacsons at SF) and
> > I'll add you to the project.
> >
> > The current build stuff (such as it is) is in the module
> squirrel-sql/build.
> > If you could have a look at it I'd be muchly appreciative. I'm using Ant
> > (obviously) for the build process and the IzPack installer from
> > www.izforge.com to create the installer. One thing that would be nice
> would
> > be an Ant task for IzPack, its been discussed on the IzPack mailing list
> but
> > nothing seems to be happening and I can't see anyway I'm going to have
> time
> > to look at it.
> >
> > Thanks
> > Col
> >
> > -----Original Message-----
> > From: Patrick Lacson [mailto:pa...@la...]
> > Sent: Wednesday, 7 November 2001 11:07
> > To: co...@us...
> > Subject: Re: source
> >
> >
> > Yes!  I sit across the guy who wrote it.  He's now part of the JBoss
> > project and apparently they too started using BuildMagic.  Hopefully,
> > this will make your life easier.  Tell you what if you add me as a
> > developer for this project I can add the buildmagic project-template and
> > have your builds up and running in under a day.
> >
> > -P
> >
> > Colin Bell wrote:
> > >
> > > I'm interested in anything that makes my life easier
> > > <grin/>. Are you talking about the BuildMagic that is
> > > part of the Bliss project at SourceForge
> > > http://sourceforge.net/projects/bliss/?
> > >
> > > Col
> > >
> > >  --- Patrick Lacson <pa...@la...> wrote: >
> > > Colin,
> > > >
> > > > Would you be interested in an easier build sytem
> > > > that is based on Ant?
> > > > We currently use BuildMagic for our builds here at
> > > > work.  BuildMagic is
> > > > basically an extension of Ant allowing better
> > > > organizational semantics
> > > > and cleaner task extensions to Ant.
> > > >
> > > > -P
> > > >
> > > > Colin Bell wrote:
> > > > >
> > > > > Hi Pat,
> > > > >
> > > > > You can get the source from the latest release
> > > > >
> > > >
> > >
> >
> http://sourceforge.net/project/showfiles.php?group_id=28383&release_id=59420

After looking briefly at the plugins, they look like they would fit as
part of the main directory since they are actually compiled so it would
look something like:


./src
./src/main
./src/main/net/sourceforge/squirrel-sql/plugins/**
./src/main/net/sourceforge/squirrel-sql/client/**
./src/main/com/ice/util/**

./src/bin/*.bat and .sh scripts

./src/website/** contains all .html, .js, .css, .png, files related to
the website

./thirdparty/
./thirdparty/n3/lib/nanoxml.jar
./thirdparty/apache/lib/*xmlparsers and such
./thirdparty/whatever-else

when a distribution or 'release' in buld-magic terms, a directory called

./output/release/<version>-squirrel-sql/classes
./output/release/<version>-squirrel-sql/lib/squirrel-sql.jar
./output/release/<version>-squirrel-sql/doc/README and javadoc


So that's the jist of the new structure.  Anything compiled should be in
the ./src/main/** directory, while static libraries should remain in the
thirdparty/<vendor>/lib directory.

Colin,  I'll start on this and have the new workspace ready by either
wednesday night or thursday morning.

-P


Colin Bell wrote:
> 
> Welcome aboard Patrick.
> 
> How would you see the plugins fitting into this? Being as they would need a
> separate build process as well as being part of the main build.
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Tuesday, 20 November 2001 5:41
> To: squirrel-dev
> Subject: [Squirrel-sql-develop] Build re-org
> 
> Colin,
> 
> Hello everyone!  Colin, thanks for getting me onboard and I look forward
> to contributing to this cool project!  FYI, Colin and I have been
> discussing a build structure and possibly using the BuildMagic system
> that the JBOSS group uses, for simplification and ease of use.
> 
> Colin, as it turns out from our last discussion, a lot of the work
> you've done in the CVS checkin of squirrel-sql can be easily ported to
> the buildmagic semantic.
> 
> The BuildMagic tree structure adheres to the following semantic:
> 
> modified files for project
> --------------------------
> ./build.xml (obvious)
> ./project.xml (this is where all your project specific information is
> stored)
> 
> buildmagic system files
> -----------------------
> ./build.sh (script that uses the bundled ant lib instead of local ant)
> ./etc/buildmagic/common.xml (system tree structure defaults)
> ./etc/buildmagic/init.xml (system init defaults)
> 
> source code info
> ----------------
> ./src (source tree)
> ./src/main (main src tree)
> ./src/bin (executable scripts, batch files, etc)
> ./src/etc (config files required for compilation or release)
> 
> external tools and lib
> ----------------------
> ./thirdparty (thirdparty applications/libraries like ice, izPack,
> jdbc-drivers, etc.)
> ./tools (tools used for development testing such as junit, etc.)
> 
> compile info
> ------------
> ./output/build/classes (all files that are compiled from ./src/main
> ./output/build/lib (contains the jar file when ./build jar is used)
> 
> release info
> ------------
> ./output/build/release/<version>-squirrel-sql/ (common doc and info)
> ./output/build/release/<version>-squirrel-sql/bin (contains and
> executables)
> ./output/build/release/<version>-squirrel-sql/classes (compiled
> byte-code)
> ./output/build/release/<version>-squirrel-sql/api (java-doc files)
> ./output/build/release/<version>-squirrel-sql/lib (bundled squirrel.jar)
> 
> Basically this will keep things in a logical and intuitive structure.
> When we do a release a structure similar to 'release info' will be
> provided, granted that ./output/build/release/<version>-squirrel-sql is
> the root of tree.  This is the structure that BuildMagic uses which we
> use here at work.  Does anybody have any questions or comments?
> 
> --
> </Patrick>
> pa...@la...
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Welcome aboard Patrick.

How would you see the plugins fitting into this? Being as they would need a
separate build process as well as being part of the main build.

Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Tuesday, 20 November 2001 5:41
To: squirrel-dev
Subject: [Squirrel-sql-develop] Build re-org


Colin,

Hello everyone!  Colin, thanks for getting me onboard and I look forward
to contributing to this cool project!  FYI, Colin and I have been
discussing a build structure and possibly using the BuildMagic system
that the JBOSS group uses, for simplification and ease of use.  

Colin, as it turns out from our last discussion, a lot of the work
you've done in the CVS checkin of squirrel-sql can be easily ported to
the buildmagic semantic.

The BuildMagic tree structure adheres to the following semantic:

modified files for project
--------------------------
./build.xml (obvious)
./project.xml (this is where all your project specific information is
stored)

buildmagic system files
-----------------------
./build.sh (script that uses the bundled ant lib instead of local ant)
./etc/buildmagic/common.xml (system tree structure defaults)
./etc/buildmagic/init.xml (system init defaults)

source code info
----------------
./src (source tree)
./src/main (main src tree)
./src/bin (executable scripts, batch files, etc)
./src/etc (config files required for compilation or release)

external tools and lib
----------------------
./thirdparty (thirdparty applications/libraries like ice, izPack,
jdbc-drivers, etc.)
./tools (tools used for development testing such as junit, etc.)

compile info
------------
./output/build/classes (all files that are compiled from ./src/main
./output/build/lib (contains the jar file when ./build jar is used)

release info
------------
./output/build/release/<version>-squirrel-sql/ (common doc and info)
./output/build/release/<version>-squirrel-sql/bin (contains and
executables)
./output/build/release/<version>-squirrel-sql/classes (compiled
byte-code)
./output/build/release/<version>-squirrel-sql/api (java-doc files)
./output/build/release/<version>-squirrel-sql/lib (bundled squirrel.jar)

Basically this will keep things in a logical and intuitive structure. 
When we do a release a structure similar to 'release info' will be
provided, granted that ./output/build/release/<version>-squirrel-sql is
the root of tree.  This is the structure that BuildMagic uses which we
use here at work.  Does anybody have any questions or comments?



--
</Patrick>
pa...@la...

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Go for it.

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Tuesday, 20 November 2001 11:52
To: BradLyon
Cc: squirrel-dev
Subject: Re: [Squirrel-sql-develop] Build re-org


Guys,

Would anybody object if I create a new module in CVS called "squirrel"
that will apply the new BuildMagic system?  Colin, your call..

-P


BradLyon wrote:
> 
> Great to have you involved, Patrick.  I am not familiar with either
> BuildMagic or JBOSS, but I am interested.
> 
> At 10:41 AM 11/19/01 -0800, Patrick Lacson wrote:
> >Colin,
> >
> >Hello everyone!  Colin, thanks for getting me onboard and I look forward
> >to contributing to this cool project!  FYI, Colin and I have been
> >discussing a build structure and possibly using the BuildMagic system
> >that the JBOSS group uses, for simplification and ease of use.
> >
> >Colin, as it turns out from our last discussion, a lot of the work
> >you've done in the CVS checkin of squirrel-sql can be easily ported to
> >the buildmagic semantic.
> >
> >The BuildMagic tree structure adheres to the following semantic:
> >
> >modified files for project
> >--------------------------
> >./build.xml (obvious)
> >./project.xml (this is where all your project specific information is
> >stored)
> >
> >buildmagic system files
> >-----------------------
> >./build.sh (script that uses the bundled ant lib instead of local ant)
> >./etc/buildmagic/common.xml (system tree structure defaults)
> >./etc/buildmagic/init.xml (system init defaults)
> >
> >source code info
> >----------------
> >./src (source tree)
> >./src/main (main src tree)
> >./src/bin (executable scripts, batch files, etc)
> >./src/etc (config files required for compilation or release)
> >
> >external tools and lib
> >----------------------
> >./thirdparty (thirdparty applications/libraries like ice, izPack,
> >jdbc-drivers, etc.)
> >./tools (tools used for development testing such as junit, etc.)
> >
> >compile info
> >------------
> >./output/build/classes (all files that are compiled from ./src/main
> >./output/build/lib (contains the jar file when ./build jar is used)
> >
> >release info
> >------------
> >./output/build/release/<version>-squirrel-sql/ (common doc and info)
> >./output/build/release/<version>-squirrel-sql/bin (contains and
> >executables)
> >./output/build/release/<version>-squirrel-sql/classes (compiled
> >byte-code)
> >./output/build/release/<version>-squirrel-sql/api (java-doc files)
> >./output/build/release/<version>-squirrel-sql/lib (bundled squirrel.jar)
> >
> >Basically this will keep things in a logical and intuitive structure.
> >When we do a release a structure similar to 'release info' will be
> >provided, granted that ./output/build/release/<version>-squirrel-sql is
> >the root of tree.  This is the structure that BuildMagic uses which we
> >use here at work.  Does anybody have any questions or comments?
> >
> >
> >
> >--
> ></Patrick>
> >pa...@la...
> >
> >_______________________________________________
> >Squirrel-sql-develop mailing list
> >Squ...@li...
> >https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Guys,

Would anybody object if I create a new module in CVS called "squirrel"
that will apply the new BuildMagic system?  Colin, your call..

-P


BradLyon wrote:
> 
> Great to have you involved, Patrick.  I am not familiar with either
> BuildMagic or JBOSS, but I am interested.
> 
> At 10:41 AM 11/19/01 -0800, Patrick Lacson wrote:
> >Colin,
> >
> >Hello everyone!  Colin, thanks for getting me onboard and I look forward
> >to contributing to this cool project!  FYI, Colin and I have been
> >discussing a build structure and possibly using the BuildMagic system
> >that the JBOSS group uses, for simplification and ease of use.
> >
> >Colin, as it turns out from our last discussion, a lot of the work
> >you've done in the CVS checkin of squirrel-sql can be easily ported to
> >the buildmagic semantic.
> >
> >The BuildMagic tree structure adheres to the following semantic:
> >
> >modified files for project
> >--------------------------
> >./build.xml (obvious)
> >./project.xml (this is where all your project specific information is
> >stored)
> >
> >buildmagic system files
> >-----------------------
> >./build.sh (script that uses the bundled ant lib instead of local ant)
> >./etc/buildmagic/common.xml (system tree structure defaults)
> >./etc/buildmagic/init.xml (system init defaults)
> >
> >source code info
> >----------------
> >./src (source tree)
> >./src/main (main src tree)
> >./src/bin (executable scripts, batch files, etc)
> >./src/etc (config files required for compilation or release)
> >
> >external tools and lib
> >----------------------
> >./thirdparty (thirdparty applications/libraries like ice, izPack,
> >jdbc-drivers, etc.)
> >./tools (tools used for development testing such as junit, etc.)
> >
> >compile info
> >------------
> >./output/build/classes (all files that are compiled from ./src/main
> >./output/build/lib (contains the jar file when ./build jar is used)
> >
> >release info
> >------------
> >./output/build/release/<version>-squirrel-sql/ (common doc and info)
> >./output/build/release/<version>-squirrel-sql/bin (contains and
> >executables)
> >./output/build/release/<version>-squirrel-sql/classes (compiled
> >byte-code)
> >./output/build/release/<version>-squirrel-sql/api (java-doc files)
> >./output/build/release/<version>-squirrel-sql/lib (bundled squirrel.jar)
> >
> >Basically this will keep things in a logical and intuitive structure.
> >When we do a release a structure similar to 'release info' will be
> >provided, granted that ./output/build/release/<version>-squirrel-sql is
> >the root of tree.  This is the structure that BuildMagic uses which we
> >use here at work.  Does anybody have any questions or comments?
> >
> >
> >
> >--
> ></Patrick>
> >pa...@la...
> >
> >_______________________________________________
> >Squirrel-sql-develop mailing list
> >Squ...@li...
> >https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop