Colm McCartan wrote:
>
> Jason -
>
> Thanks for the response...
>
> 06/06/2001 16:49:43, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >Layout templates are searched for because every screen template has
> >a corresponding layout template. Read the FSD:
> >
> >http://jakarta.apache.org/turbine/fsd.html
>
> That would be my fifth time...
>
> >If you want to learn about the relationship between layouts and screens.
> >And read the Velocity site howto to find out how templates are searched
> >for. There is a search order for templates so you may see some failed
> >attempts in your logs for various layout templates.
> >
> >http://jakarta.apache.org/turbine/howto/velocity-site-howto.html
>
> I've carried dog-eared versions of *all* the howtos around in my bag for the
> last week or two reading them in different orders, reading more about servlets,
> then going back to them etc...
>
> >> I suspect I have a faulty understanding of the interaction between layouts
> and
> >> screens - I'm using data.setScreenLayout to set the destination screens...
> >
> >You are setting the layout here which is not what you want. Were
> >you trying to set the layout or the screen? Did you look at
> >the TDK sample app?
>
> I've been over it several times...
>
> >You no longer need to use any manual setting of layouts. Just use
> >
> >data.setScreenTemplate(template)
> >
> >and the corresponding layout template will be found for you.
>
> Jason, don't get me wrong, I think theres a tremendous amount of good work gone
> into this but (I'm gonna get flamed to death) these docs are not terribly well-
> written or easy to understand. They are also - by admission of several members
> of this group - out of date in places.
The docs are admittedly lacking. I was planning to take the summer to
rewrite as this coincides with a book I'm doing but it's a big job.
>
> I suspect I'm speaking for a few lurkers to say that the whole Turbine/velocity
> framework is mildly confusing
I think it's more than mildly confusing :-) There is a lot of code in
Turbine
and it takes a while to digest.
> at first and the docs are actually counter-
> productive in parts since they are so obviously written by someone who *already
> understands* the system...
This is generally the problem, people work through there problems and
rarely
document things as they go and then don't have time afterward.
> They are still of a much higher quality than are
> found in most OSS projects and I'm not knocking them. However, always pointing
> people to the same docs when they are beginners and confused doesn't help much.
Sorry, not much else I can do. We have what we have, and the TDK will
eventually
be a lot more comprehensive.
> I believe the vast majority of people do look at these docs before posting and
> post because they require clarification.
I agree. They need to be completely overhauled.
> Perhaps I could suggest that 'senior' members of the list simply don't answer if
> they don't want to/feel its too simple a question/the person needs an RTFM. This
> might encourage people at a lower level to trade experiences... Anyone agree?
People are always encouraged to trade experiences. Even if some of the
answers
the 'senior' members give are a little terse they are probably still
helpful.
> Like I said, I appreciate the response and this email isn't meant to sound as
> ungrateful as it seems looking back over it...
>
> For the record, I am using setScreenTemplate but read the thread from a few
> weeks back (http://www.mail-archive.com/turbine-user%
> 40jakarta.apache.org/msg00635.html) about using setScreen from action classes
> and setScreenTemplate inside screen classes... this got me a ClassNotFound so
> its back to the docs...
>
> colm
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://jakarta.apache.org/commons
http://tambora.zenplex.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
