On Apr 4, 10:05 am, p.le...@ctncorp.com wrote:
> On Apr 4, 10:34 am, "Bondo" <ostes...@hotmail.com> wrote:
>
> > Everything must take place on the client. The user opens
> > the data.xml file and, after the XSLT processing, sees
> > the XHTML.
>
> Poor choice. XHTML is not supported by MSIE. Transforming
> on the client side should be avoided unless you know very
> well what you're doing.
>
> > Since the full data set in data.xml can be quite large,
> > I'd like to offer a familiar Prev|1|2|3|...|Next type of
> > page navigation. How can this be done?
>
> If you want to transfer the entire data.xml to client and
> transform it client-side, the question has nothing to do
> with XML, since it boils down to implementing some
> JavaScript-driven UI gimmick that would hide portions of
> the resulting document. comp.lang.javascript is ===> that
> way.
>
> > I've searched on the Internet, but found it remarkably
> > quiet on the subject. Maybe I'm looking the wrong places.
> > And perhaps it's not even an XSLT issue?
>
> Consider doing it the right way. Transform server-side,
> serve HTML 4.01 Strict.
>
> --
> Pavel Lepin

Thanks for your prompt reply, Pavel. I understand your points -- I
failed to provide adequate details about the situation:

I have a native GUI application (.NET on the PC, Cocoa on the Mac)
that manipulate some data (photos and their meta data). As a function
in the application, the user must be able to locally generate web
pages of the data for later upload to a webserver (a web photo
gallery). The data set is exported to the XML file and then opened in
an embedded web view in the application. The user can also choose a
theme (a CSS file) that is referred to from within the XHTML output.
The user is ultimately looking at CSS-styled XHTML page which is what
I want.

This already works as a proof of concept, but I need to provide some
sort of navigation as mentioned in the original post.

Since this is a photo gallery, I suspect the amount of XML data will
perhaps be of the size of one full-size preview image, so bandwidth-
wise I don't have a problem transferring the whole XML file. But
perhaps there are other reasons not to.

So my dream scenario was simply to generate the XML file, containing
meta data and image paths, process that with an XSLT stylesheet and
have the resulting XHTML nicely presented with the mentioned page
navigation (index view: next page, previous page, jump to page, and
for detail view: next photo, previous photo, index).

As an alternative, I could generate a number of XHTML files, each
containing the relevant photo and data presentation, (still using
XSLT?), and upload these to the server.

Suggestions are highly appreciated.

Thanks in advance,
Joachim