> Jason, > I think that idea of writing user manual is excellent...I know a lot of people > how use Turbine are ninja-java-masters who can figure it out by reading the > source code...
I still have problems reading the source code :-) I know that turbine is very difficult to get up and running with. It can be daunting. > but for the rest of us humans it's all a bit much at first and a really well > written manual would certainly help. In fact I think it's an absolute must if > Turbine wants to enjoy large scale adoption by web-developers at large. That's always been the plan. A book will come one fine day, but probably not anytime soon unfortunately. > Speaking from my own experience, I'd love to see a good overview/introduction > document as I spent about 6 weeks just getting to grips with the whole >framework and figuring out where to start before I could really even begin to >produce anything usefull. Other things that I think would be an excellent help >is a "cookbook" type of document (similar to the O'Reilly cookbooks), and maybe >a document that focuses on how best to go about designing your applications so >that they work well with the Turbine framework. All good ideas, just a matter of time. > Anway, that's my opinion...for what's worth =:o) Thanks! -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
