Doug Cutting wrote:
>One idea we've had is to change the format of search.jsp so that it is
valid XML.  This
> should be fairly simple, as there are XML versions of all of the JSP tags.

Yes, that would be great. And good to hear, that it will be not much work to
change it.

Doug Cutting wrote:
> A related issue is the navigation menu on the left: I think search
> result pages should span the fill page width, and not be forced into a
> narrow column.  So, if they're to be generated by nutch-page.xsl, then
> that template needs to be able to generate pages which have no left menu
>   space.  This obviously has implications on the design.

I agree. But than the XML has to contain any information that it is
generated for searchpage to drop the navigation column there.
I have two ideas to do that without destroying all the tables:
1st: Depending on output-site I can make a parameter, that tells searchpage
navigation to have a witdth of 1pixel only and add the remaining space to
the middle.
or 2nd: I can make a big

if organisation
    template stuff 1
else
    template stuff 2

It will double the size of the XSLT, but it will have not much influence on
performance.
May be it is more easy to use seperate XSLTs for organization and search
site. But I have no idea, how much changings therefore are necessary.

Frank





----- Original Message -----
From: "Doug Cutting" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 05, 2004 7:10 PM
Subject: Re: [Nutch-dev] question about search (output)


> Frank Henze wrote:
> > can somebody commit an search-output XML to the list? I can only find
> > the searchform itself in the CVS. I will need it to continue with the
> > XSLT stuff.
>
> Search output is currently generated by search.jsp.  One idea we've had
> is to change the format of search.jsp so that it is valid XML.  This
> should be fairly simple, as there are XML versions of all of the JSP
> tags.  Then search.jsp could itself be generated with the XSLT template.
>   Until then, it just shares the header and footer with other pages, but
> is not generated by nutch-page.xsl.
>
> A related issue is the navigation menu on the left: I think search
> result pages should span the fill page width, and not be forced into a
> narrow column.  So, if they're to be generated by nutch-page.xsl, then
> that template needs to be able to generate pages which have no left menu
>   space.  This obviously has implications on the design.
>
> > And one more question: the search.jsp does include the same header as
> > the organization website. The links here are relative
> >
> > <item><a href="about.html">About</a></item>
>
> They're relative, but there is a base tag that is dynamically generated,
> making them, in effect, absolute.  The JSP pages examine the language
> preference header sent by the browser.  This is used to determine both
> the base URL and to internationalize the page content.  The static pages
> are required for offline use, as Nutch documentation.  But, once you're
> running JSP, the dynamic home page can detect your language preference
> and lead you into the correct static pages.
>
> Doug
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Nutch-developers mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nutch-developers
>
>




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers

Reply via email to