You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Cyriaque Dupoirieux <Cy...@pcotech.fr> on 2005/07/26 10:06:26 UTC
[Views] Export-links
Hi,
The export link templates do not use the skinconf file - that is if
you disable the pdf link, it is always generated...
Is it the way you want to use views or do we still allow the user to
configure his site with the skinconf file ?
IMO it is easy for the user to set these export links via the
skinconf file and to add at the beginning of each templates :
<xsl:if test="not($config/disable-pdf-link) or $disable-pdf-link
= 'false'">
<!-- xhtml generation... -->
</a>
So, the default.fv will always call the export-link.vt.xml, which
will generate what is needed.
--
Cordialement,
Cyriaque,
Re: [Views] Export-links
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
Ross Gardler a écrit :
> Cyriaque Dupoirieux wrote:
>
>> Cyriaque Dupoirieux a écrit :
>
>
> ...
>
>>> In fact :
>>>
>>> * the tags <disable-???-link/> can be considered as deprecated with
>>> views,
>>> * attributes @location or @location-box also...
>>>
>>> I like it.
>>> But then, because nothing is simple, we should not test the
>>> motd-page/@location nor the minitoc/@location in the following :
>>>
>>> * content-minitoc.ft,
>>> * content-motd-page.ft
>>>
>>> Regards,
>>
>>
>>
>> Forget it, the problem is different with toc and motd location...
>> It is important to decide where you want to display a toc ...
>
>
> No you were right fist time. The location should be set in the
> Template (was View), not in the contract. COnsider, for example, that
> the MOTD normally appears in both the nav menu and the body, for the
> photogallery plugin this does not work since the MOTD overlays the
> photo's displayed.
>
> Ross
Yes, I realised I was wrong just when I sent the mail.
In the pelt skin, MOTD can be in the menus or at the top of the content
(close to the minitoc.) and I recently changed the content-motd-page.ft
which was testing the location and prevent me to use the same contract
to display it in both locations.
Cyriaque,
>
> Ross
>
>
Re: [Views] Export-links
Posted by Thorsten Scherler <th...@apache.org>.
On Tue, 2005-07-26 at 11:10 +0100, Ross Gardler wrote:
> Cyriaque Dupoirieux wrote:
> > Cyriaque Dupoirieux a écrit :
>
> ...
>
> >> In fact :
> >>
> >> * the tags <disable-???-link/> can be considered as deprecated with
> >> views,
> >> * attributes @location or @location-box also...
> >>
> >> I like it.
> >> But then, because nothing is simple, we should not test the
> >> motd-page/@location nor the minitoc/@location in the following :
> >>
> >> * content-minitoc.ft,
> >> * content-motd-page.ft
> >>
> >> Regards,
> >
> >
> > Forget it, the problem is different with toc and motd location...
> > It is important to decide where you want to display a toc ...
>
> No you were right fist time. The location should be set in the Template
> (was View),
Please do *not* make more confusion and call views templates. Until we
decide officially we will rename them they are *views*.
I am preparing a proposal and then we can discuss the renaming.
@Cyriaque you are right we need to clean out the contracts from
skinconf. skinconf is deprecated in views and hereby should not be used
within the contracts.
salu2
> not in the contract. COnsider, for example, that the MOTD
> normally appears in both the nav menu and the body, for the photogallery
> plugin this does not work since the MOTD overlays the photo's displayed.
>
> Ross
>
> Ross
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [Views] Export-links
Posted by Ross Gardler <rg...@apache.org>.
Cyriaque Dupoirieux wrote:
> Cyriaque Dupoirieux a écrit :
...
>> In fact :
>>
>> * the tags <disable-???-link/> can be considered as deprecated with
>> views,
>> * attributes @location or @location-box also...
>>
>> I like it.
>> But then, because nothing is simple, we should not test the
>> motd-page/@location nor the minitoc/@location in the following :
>>
>> * content-minitoc.ft,
>> * content-motd-page.ft
>>
>> Regards,
>
>
> Forget it, the problem is different with toc and motd location...
> It is important to decide where you want to display a toc ...
No you were right fist time. The location should be set in the Template
(was View), not in the contract. COnsider, for example, that the MOTD
normally appears in both the nav menu and the body, for the photogallery
plugin this does not work since the MOTD overlays the photo's displayed.
Ross
Ross
Re: [Views] Export-links
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
Cyriaque Dupoirieux a écrit :
> Ross Gardler a écrit :
>
>> Cyriaque Dupoirieux wrote:
>>
>>> Hi,
>>>
>>> The export link templates do not use the skinconf file - that is
>>> if you disable the pdf link, it is always generated...
>>> Is it the way you want to use views or do we still allow the user
>>> to configure his site with the skinconf file ?
>>>
>>> IMO it is easy for the user to set these export links via the
>>> skinconf file and to add at the beginning of each templates :
>>> <xsl:if test="not($config/disable-pdf-link) or
>>> $disable-pdf-link = 'false'">
>>> <!-- xhtml generation... -->
>>> </a>
>>> So, the default.fv will always call the export-link.vt.xml, which
>>> will generate what is needed.
>>>
>>
>> Skinconfig should is not used in Templates (Views) + Themes. More
>> info by searching the archives for "per plugin config" and other such
>> threads. Basically we want to be able to configure page display on a
>> per page or per directory basis. Hence the ability to override the
>> *.fv files.
>>
>> In other words, the PDF page should only be generated when there is a
>> link to it in the site itself.
>>
>> So if we have a default Template (was View) that turns on the PDF
>> link but we have a special page called "noPDF.html" which overrides
>> the default and turns off the PDF link then PDF should be generated
>> for all pages *except* the "noPDF" page.
>
>
> Ok, so you will think the same for the several alternate locations
> that we can find in the pelt skin : for instance, the search box can
> be at the tabs level or in the menus. For you, only the Template
> (View) will decide if you want to display the Search box and where you
> want to display it.
>
> In fact :
>
> * the tags <disable-???-link/> can be considered as deprecated with
> views,
> * attributes @location or @location-box also...
>
> I like it.
> But then, because nothing is simple, we should not test the
> motd-page/@location nor the minitoc/@location in the following :
>
> * content-minitoc.ft,
> * content-motd-page.ft
>
> Regards,
Forget it, the problem is different with toc and motd location...
It is important to decide where you want to display a toc ...
Cyriaque,
>
>>
>> Ross
>>
>>
>
>
Re: [Views] Export-links
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
Ross Gardler a écrit :
> Cyriaque Dupoirieux wrote:
>
>> Hi,
>>
>> The export link templates do not use the skinconf file - that is
>> if you disable the pdf link, it is always generated...
>> Is it the way you want to use views or do we still allow the user
>> to configure his site with the skinconf file ?
>>
>> IMO it is easy for the user to set these export links via the
>> skinconf file and to add at the beginning of each templates :
>> <xsl:if test="not($config/disable-pdf-link) or
>> $disable-pdf-link = 'false'">
>> <!-- xhtml generation... -->
>> </a>
>> So, the default.fv will always call the export-link.vt.xml, which
>> will generate what is needed.
>>
>
> Skinconfig should is not used in Templates (Views) + Themes. More info
> by searching the archives for "per plugin config" and other such
> threads. Basically we want to be able to configure page display on a
> per page or per directory basis. Hence the ability to override the
> *.fv files.
>
> In other words, the PDF page should only be generated when there is a
> link to it in the site itself.
>
> So if we have a default Template (was View) that turns on the PDF link
> but we have a special page called "noPDF.html" which overrides the
> default and turns off the PDF link then PDF should be generated for
> all pages *except* the "noPDF" page.
Ok, so you will think the same for the several alternate locations that
we can find in the pelt skin : for instance, the search box can be at
the tabs level or in the menus. For you, only the Template (View) will
decide if you want to display the Search box and where you want to
display it.
In fact :
* the tags <disable-???-link/> can be considered as deprecated with
views,
* attributes @location or @location-box also...
I like it.
But then, because nothing is simple, we should not test the
motd-page/@location nor the minitoc/@location in the following :
* content-minitoc.ft,
* content-motd-page.ft
Regards,
>
> Ross
>
>
Re: [Views] Export-links
Posted by Ross Gardler <rg...@apache.org>.
Cyriaque Dupoirieux wrote:
> Hi,
>
> The export link templates do not use the skinconf file - that is if
> you disable the pdf link, it is always generated...
> Is it the way you want to use views or do we still allow the user to
> configure his site with the skinconf file ?
>
> IMO it is easy for the user to set these export links via the
> skinconf file and to add at the beginning of each templates :
> <xsl:if test="not($config/disable-pdf-link) or $disable-pdf-link
> = 'false'">
> <!-- xhtml generation... -->
> </a>
> So, the default.fv will always call the export-link.vt.xml, which
> will generate what is needed.
>
Skinconfig should is not used in Templates (Views) + Themes. More info
by searching the archives for "per plugin config" and other such
threads. Basically we want to be able to configure page display on a per
page or per directory basis. Hence the ability to override the *.fv files.
In other words, the PDF page should only be generated when there is a
link to it in the site itself.
So if we have a default Template (was View) that turns on the PDF link
but we have a special page called "noPDF.html" which overrides the
default and turns off the PDF link then PDF should be generated for all
pages *except* the "noPDF" page.
Ross