Michael, you have to read the instructions in the archive.

It says e.g. you need to replace this entry in TR.props with your class:
tool.request.page=....

Turbine has a lot of functionality, but occassionally it happens that
certain function don't work right away. In that case you have to explore the
Turbine-API yourself to find a solution that fits your needs.
Turbine is a great framework, but keep in mind it's Open Source Software!

Marc


> -----Urspr�ngliche Nachricht-----
> Von: Eigen Technology Pty Ltd [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 19. Dezember 2002 12:27
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Multiple addPathInfo
>
>
> I found the message in the Archive and I have also downloaded Soctt's
> .java file.  I put that file under:
>
> /WEB-INF/src/java/org/mycompany/eigen/modules/actions/TemplatePage
> AttributesEx.java
>
> Compiled it and restarted TDK.  My question is:
>
> Do I still have the same line in the .vm file?
>
> $page.setStyleSheet($content.getURI("resources/vpistyle.css")
>
> It did not work, an error was generated.
>
> cheers
> michael
>
>
>
>
>
>
> > From: "Marc Lustig" <[EMAIL PROTECTED]>
> > > When I don't use any of the methods of my
> TemplatePageExtendedAttributes
> > class in my Default.vm everything works fine. When I include one of the
> > methods like the setScript nothing appears except the error message.
> > When I comment the one statement in setScript it works fine as well, but
> > nothing is put into the head, of course.
> > It seems the problem is due to the RunData-field not being initialized
> > properly.
> > > Also, your patch appears incomplete since the RunData-field in
> > TemplatePageAttributes is declared private. You need to add the field to
> the
> > extended class in order to compile.
> > I have to dig further...
>
> I think I understand the problem now.  You have to remember that the patch
> was for TemplatePageAttributes itself.  If you are implementing a
> class that
> extends TemplatePageAttributes then there are a few extra things you need.
> To make this easy for you I have attached my
> TamplatePageAttributesEx class
> which I use with my turbine 2.1 based application.
>
> Cheers,
>
> Scott
> --
>
>
>
>
>
>
>
>
> > I would put the Stylesheet in resources/.
> > Then try
> > $page.setStyleSheet($content.getURI("resources/stylesheet.css")) But I
> > think class TemplatePageAttributes of 2.1 doesn't have a method
> > setStyleSheet().
> > You have to extend this class and add custom methods.
> > Read the archive for instructions. Try searching
> > "TemplatePageAttributesEx" and you will find Scott's solution.
> >
> > Good luck!
> > Marc
> >
> >> -----Urspr�ngliche Nachricht-----
> >> Von: Eigen Technology Pty Ltd [mailto:[EMAIL PROTECTED]]
> >> Gesendet: Donnerstag, 19. Dezember 2002 12:09
> >> An: [EMAIL PROTECTED]
> >> Betreff: Re: Multiple addPathInfo
> >>
> >>
> >> I am using tdk2.1.
> >>
> >> the .vm file is in app/screens, I tried to put the style.css in
> >> app/screens and app/layouts, and include this line in the .vm file:
> >>
> >> $page.setStyleSheet("./vpistyle.css")
> >>
> >> and then
> >>
> >> $page.setStyleSheet("/vpistyle.css")
> >>
> >> but it does not seem to have worked. Any idea?
> >>
> >> thanks
> >> michael
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> > On 19/12/2002 4:33 PM, "Eigen Technology Pty Ltd"
> >> > <[EMAIL PROTECTED]> wrote:
> >> >
> >> >> Thanks Scott, that worked...$page.setStyleSheet("./vpistyle.css")
> >> >>
> >> >> could you also tell me where to put my personal style sheet in the
> >> Turbine layout.
> >> >>
> >> >> cheers
> >> >> michael
> >> > Assuming you are using t2.2, I think you can go:
> >> >
> >> >     $page.setStyleSheet(url, media)
> >> >
> >> > Use $content.getURI("relative file path") to construct the url. Your
> >> media will most likely be "screen".
> >> >
> >> > HTH,
> >> >
> >> > Scott
> >> > --
> >> > Scott Eade
> >> > Backstage Technologies Pty. Ltd.
> >> > http://www.backstagetech.com.au
> >> > .Mac Chat/AIM: seade at mac dot com
> >> >
> >> >
> >> > --
> >> > To unsubscribe, e-mail:
> >> > <mailto:[EMAIL PROTECTED]> For additional
> >> commands, e-mail: <mailto:[EMAIL PROTECTED]>
> >>
> >>
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> >> <mailto:[EMAIL PROTECTED]>
> >> For additional commands, e-mail:
> >> <mailto:[EMAIL PROTECTED]>
> >>
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]> For additional
> > commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to