|
From: Colin B. <Col...@as...> - 2001-11-21 00:57:51
|
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 |
