forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Williams <william...@gmail.com>
Subject Re: Locationmap now works for repositories
Date Mon, 06 Jun 2005 19:01:33 GMT
I'm thinking my latest round of questions seem to have gotten lost... 
The ones with a single ">" in front.

--tim

...
> > > of course site.xml and tabs.xml which are handled differently than
> > > other content in xdocs.
> >
> > They are, but they need not be. This is something that needs to be
> > addressed. We should be able to get site.xml and tabs.xml from the
> > locationmap source too.
> 
> I've got both of these working with locationmap now, let me know if
> that's preferable. This makes me wonder how "default" locationmaps
> will be set up.  Is there a concept of fallback locationmaps sorta
> like sitemaps do (e.g., allow project overrides to forrest
> pre-defined)?  I guess the question is: have you a grander design yet
> for how these things will actually work when it comes to *all*
> resources?  It seems like this idea of overriding the forrest
> locationmap settings with the project locationmap settings seems
> necessary?



> > > Also, are you looking into expanding it for resource (graphics
> > > specifically) content too?
> >
> > Yes. My goal is to be able to use the locationmap for everything.
> > However, this is a pretty big job and could introduce many unexpected
> > bugs so would need lots of testing. As you get more comfortable with
> > sitemaps and the like, perhaps you can help (hint resources are handled
> > by the resources.xmap file).
> 
> Clearly there's a lot left to learn but I'm no longer as intimidated
> with the *xmaps -- frightening as it may be, they're actually
> beginning to make sense now.   Having looked at resources.xmap though,
> I agree, it is going to be a big job.  Before looking more at it
> though, I'd like to get your vision of how it should work.  Seems to
> me there needs to be some sort of forrest:locationmap and
> project:locationmap concepts in place first?  In other words as the
> locationmap concept is carried over to forrest assets as well as
> project assets, should each not have a overridable locationmap?

Mime
View raw message