"Quinton McCombs" wrote: >I would rather see one or two sample apps that are ready to be built >with Maven replace the TDK. One should use JSP. The other should use >Velocity. I think this would be much more helpful to new users.
I agree 100% with this, it doesn't make sense to me to have to download a whole server to get started with Turbine. It is a jar library right?, so if I pack my web application with turbine in a WAR file, it should run on every tomcat server. I know that probably this is kind of ideallistic, but that is what I was expecting when I started with Turbine. So I think that we should have a set of WARs showing different turbine applications. Starting with Turbine was not too difficult, but I think it could be much more simpler. Understanding about how to use Actions, Screens, Navigations, etc, is difficult enough and it is something we can not avoid, however, the newapp example was not helpful, it forced me to use a lot of things (e.g.: Torque) that I didn't want. I think it would be better to have simple examples, that can be extended by the user, than to have a complex, monolithic application and find out that it is full of stuff that I don't need. Otto. ----- Original Message ----- From: "Quinton McCombs" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, March 13, 2003 10:55 AM Subject: RE: [RFC] We need a new TDK > -----Original Message----- > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 9:36 AM > To: [EMAIL PROTECTED] > Subject: Re: [RFC] We need a new TDK > > > "Quinton McCombs" <[EMAIL PROTECTED]> writes: > > >Granted, I was using the TDK in 2.1. When I moved to 2.2, I stopped > >using the TDK. That could have had a great deal to do with > my problems > >concerning the TDK. > > I think, most of us did this. The 2.1 TDK simply didn't work with T2.2 > > I've never looked into the current TDK. I consider it a huge > achievement that Martin was able to get a 2.2 TDK running. > > >I would rather see one or two sample apps that are ready to be built > >with Maven replace the TDK. One should use JSP. The other > should use > >Velocity. I think this would be much more helpful to new users. > > Please read what I proposed. Basically a new TDK would be > > - preconfigured servlet container > - (maybe) preconfigured, simple database e.g. hsqldb > - preconfigured build tools (maven, maybe ant) > - some ant/maven tasks to copy an application into the servlet > container for testing (tdk:install, tdk:clean, tdk:deploy) > > - a small skeleton to set up a build environment outside > the webapps directory (!). Small means, my current skeleton > has 25 kBytes and consists mainly of TR.props, Log4j.props > and a little ant script to create the directory structure. > > - demo apps > - documentation I guess I did a poor job or reading then.... I do like this idea. I simply detest the directory structure of the TDK. I do think that it is important that we have more than one sample application. I really would like to see at least two each with a different view. We say that Turbine supports JSP. However, my application was written in JSP before I moved to Turbine 2.1. I converted to Velocity not because I really wanted to but because all of the examples were in Velocity. I think the Velocoty is better but clearly demonstrating to new users (and potential ones) that there choise is there is important. By the same token, we could have one using mysql and one using hsqldb. The docs should show how easy it easy to switch databases. I see your point that we should provide support for building these apps with Ant. I cringe at the thought of this though.... Memories of tracking down required jar files, figuring out where to put them, headaches, etc.... However, I qalso realize there are any tasks now that can download dependecies just like Maven. I do want to see the application setup in a Maven directory structure though. I think that it makes complete sense. Maven also does a nice job of building a site that can be published to the user's intranet quite easily. Granted, there are other tools that can do this as well but most of the people who help support Turbine also use Maven. > Well, you might not need it and I might not need it, but > getting all the parts together for testing and debugging a > turbine app can be quite cumbersome and most of us learned > how to do this by using the TDK. I agree. Once you understand how everything is working, there is no need for the TDK. For people trying to understand how to use Turbine, it will be invaluable. I also think that it will be come a valuable resource for the developer as well. We don't really do any testing against a generic application. This is another reason why I want to see JSP used..... > BTW: Internally I use "META" for this "new tdk": > "Maven Environment for Turbine Applications" :-) > > Regards > Henning Let's start talking about more of the details over on the dev list when you have time. I am very willing to help out with this. I develop on Windows and Linux.... > -- > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > Java, perl, Solaris, Linux, xSP Consulting, Web Services > freelance consultant -- Jakarta Turbine Development -- hero for hire > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
