FYI -
The Turbine Developers Kit (TDK) is underway!
Just want to let everyone know that the the TDK is finally
materializing. Still alot to do - but it's started.
The goal of the TDK is to provide a _single_ download, easy to
install kit, so users ( especially newbies ) can get started using
Turbine. It also should be ideal for laptop development and quick
demos.
Currently here's what I've got working on the TDK:
* Scaled down, customized version of Tomcat included.
* Preconfigures all property files ( WebMacro, TurbineResources) when
you create a new app. (preset to use WebMacroSite)
* Single turbine.jar that includes all the needed Jar
files for development and deployment. The only thing you need in your
existing classpath is Java
* Configured to use the TurbineNoDbUser ( no DB setup)
Here's how it works ( at least on my machine currently):
1. Download the TDK.zip
2. Unzip it into the directory of your choice.
3. Set the tdk.properties file to point to the directory where
you extracted the TDK.
4. CD into the TDK/bin directory
5. run ./newapp.sh "destination_path/myapp". This creates the
WEB-INF directories, and the properties files with all the preset path
info. needed. ( you can do this for as many apps as you'd like)
6. CD into "destination_path/myapp/bin" and type "sh tomcat.sh run"
7. Point your browser to http://127.0.0.1:9000/servlet/Turbine
You see the demo webmacro index.wm
Each application is unique and will run from where you create it.
This still is barebones, but it at least provides an easy start for new
Turbine users ( or experienced ones in a hurry ).
-------------------
Jon,
I'd like to keep this separate in CVS from the Turbine base. Is that
possible? And if so, where should i put it.
I'd also like to eventually set it up for nightly/stable builds.
This way TDK users could just download a pre packaged version off the
Turbine site with out messing with the Turbine src base. Is that
possible also?
--------------------
What's left to do ( Plenty ):
* Create .bat files for Windows users.
* Set up the build file for each application to compile your custom
code
* Preconfigure hSQL for DB use. ( any thoughts on this? )
* Trim more fat (example code etc...) out of the base Turbine.jar
* include javadoc, a getting started guide, and a Tutorial.
* integrate the Database generation stuff.
* TEST it !
Ideally I see us taking a periodic snapshots of the Turbine base to
include in it.
As soon as I document it and find where we want to put it
in CVS. I'll get it up on the site.
--
dave
[EMAIL PROTECTED]
----------------------
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
