Elliott Wolin wrote:
I'm about ready to give up on turbine due to lack of basic
documentation. Quite a few others I know have already given up, not a
good sign for a project that seeks wide acceptance. I have spent more
time trying to figure out the tdk than I've spent on any other similar
software product, and am close to giving up and writing the servlet myself.
I know what you mean, the learning curve seems to be a bit steep. I've heard it said on this list that you can expect to spend 6 to 8 months learning Turbine before you can make full use of it, though I'm a bit sceptical of that myself!
I see no documentation on how to start from scratch. I would like to
Well, that's what the TDK getting started guide is for...
create a simple web app. I create a directory "myapp" in tdk_root/webapps. At this point I have no clue what I must do at a minimum, what dirs must exist, what property and xml files I must supply, where I must run ant, etc (emphasis on the must). The example "newapp" contains hundreds of files and directories...I hope I don't need that many, and I don't want to figure all that out. A simple app should require a few to a dozen files and dirs, and a small number of steps to get it running...what are these files, dirs, and steps?
Looking at what's generated, at least half to two thirds of it is the source and class files for the Torque object model used by the Turbine security service. If you want to use that service, you'll want those files. Almost all the rest is the required libs and the sample screens, actions, etc. So it's not that excessive.
P.S. A reference to the example "skeleton" app helped, but it assumes one knows more about turbine and ant than I do. I want to learn the absolute minimum necessary about turbine and ant to get my app running, then work my way up from there.
So start with the TDK and the generated app, and as you get to know what's what you can start throwing out the bits you don't need. That's how I started out. I spent an evening or so palying with the generated app to understand how it fit together, then just junked the Torque stuff, flux and other bits I didn't need. It may look intimidating but once you get a little bit of a feel for what's what it's easy to trim according to requirements.
L.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
