----- Original Message ----- From: "Joe Terry" <[EMAIL PROTECTED]>
Turbine does have a fairly steep learning curve, the trick is to concentrate on one area at a time. Spend the time to figure out how the particular area works and then move on to the next. > A) Expanding the "Turbine_User" table and creating another table with a > foreign key so that my users will have a set of persistent properties. (I > tried the "Extend User Howto" and it was very confused and confusing, I'll > try again, but we need more coherent documentation) It is a shame you found the Extend User Howto difficult to understand. I guess the problem is that it was written by someone that had been using turbine and torque for a few months and perhaps the author (yours truly, enhancing work of others before me) skipped over some of the subtleties that seemed to be obvious. If you have any specific questions, please post them to the list and we will attempt to answer them. > B) Managing database access to several tables and preparing associated > screens. You need to separate this into two different problems. For database access turbine provides torque - read the docs, define your schema and away you go. For the screens you need do define your template structure and the screen classes or pull tools that will go with them. Newapp should be fine for the figuring out the general approach, but it does not currently use an application pull tool (implementation of a pull tool is well worth the up front effort). > C) Getting logging to work so that activities on the site can be monitored > and quantified. You can use TurbineResources.properties to switch over to Log4J which provides all sorts of great logging features, examples of many of these can be found in TR.props. I would imagine you ought to get well into problems A and B above before this is really an issue. > Anyone have a more developed application than "newapp" that comes with the > TDK that I can look at? Apart from an application pull tool and intake (used for server side validation of forms) newapp provides a good example of many of the features of turbine. It's simplicity is very helpful when you are new to turbine. I think you are more likely to get helpful answers to specific questions that indicate what you have tried so far and what is going wrong, or the particular aspect of turbine you are finding confusing than by asking the more general questions such as those you have asked in this message. HTH, Scott -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
