forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Koberg" <>
Subject RE: Link-Addressing, and breaking up the sitemap
Date Thu, 05 Sep 2002 13:27:11 GMT

> -----Original Message-----
> From: Marc Portier []
> Sent: Thursday, September 05, 2002 3:39 AM
> Hi Robert,
> Robert Koberg wrote:
> > Hi,
> >
> >
> >>-----Original Message-----
> >>From: Marc Portier []
> >
> >
> >>Still: configuring the load of what forrest should know about
> >>your project all in *one* file seems logic to me.  (as long as it
> >>is all inside the one concern which I would largely define as
> >>"organize the project site" This would be involving: choosing
> >>some skin, and maybe setting some skin-specific customizations,
> >>decide on which parts get hooked up in which tabs, setup the
> >>libre auto-indexing rules, ...
> >>
> >>Even if the concerns would grow out of one role (person) this
> >>could still be the entry config-file that maybe lists where other
> >>files are.
> >
> >
> > I have found that two main config files are a good thing. One that
> describes the
> > site and one that describes the resources. The resources are
> referenced in the
> > site config for easy reuse.
> >
> can't say I fully grasp yet what is in there, just some random
> thoughts:
> - they look machine generated rather then hand-made

Users will usually use a browser gui to edit them (they usually don't know they
exist). I tend to do the bulk of the my stuff in XMLSpy and some Ant tasks. I
find it easier and extremely clear what is going on

> - seem to be relating to one document repository that manages all
> 'article-ids' (while here we try to get some mechanism to cross
> ref between parts coming from different locations we still want
> to publish all together)

Yes it is a simple site example. Resources can come from anywhere.

I am noticing most hits to the docs site listed below are going to empty (not
404) pages. What you are seeing is a storyboard that is definitely a work in
progress. First thing I do with a site is storyboard out a wireframe, add
content and play with the site till it is workable.

If you go to:
there is a pager that will take you through the site config. Each element and
it's attributes are described.

I have also described the XSLT here:

I separate them into 3 categories (links to further description are on the page
and in the nav):
1. Primary - these are the main XSLTs that setup a page structure and include
the other types
2. Common - these are generic templates to handle common web needs
3. Utility - eeeekkk! business logic :)

> > I have some incomplete documentation with Relax NG Schemas (I think
> I generated
> > DTDs and W3 Schema) up at:
> >
> >
> >
> >
> > </snip>
> >
> >>whadayathink?
> >>using the CLI is about "staticalizing" your content.  The webapp
> >>does not have this concern, so only the CLI needs to be taking up
> >>this concern to 'relativise' all the /-leading references in the
> >>produced static content.
> >>(At first I mentioned some transformer for this, but 'in office'
> >>Steven correctly pointed out that this has only got to do with
> >>the use of the crawler.)
> >>
> >
> >
> > What happens when your static output is PDF or some other binary
> staticalized :)
> > output?
> >
> honestly: I have *no* idea.
> For static HTML it seems natural to have relative links between
> all that sit in one dir with subdirs so they can be moved around
> in the vritual root of any webserver at will...
> For static pdf it seems natural to have only full fledged http://
> links... given the fact that you would maybe download, print,
> mail those around? (even harder to realize)
> It would not make a lot of sense to me to start browsing around
> from pdf to pdf... but who am I?

You are the savior of the forrest :)

Yes, I suppose it does not make much sense unless the PDF comes with other
things that it needs to link to when downloaded to a filesystem.

Another thing might be Flash movies that have relative resources.

I am trying to say that it does not seem to be a universal answer to the
relative links problem


> > -Rob
> >
> >
> -marc=
> --
> Marc Portier                  
> Outerthought - Open Source, Java & XML Competence Support Center

View raw message