forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: [RT] plugin infrastructure
Date Sun, 07 Nov 2004 22:24:38 GMT
Here's a little question...

On Nov 7, 2004, at 2:09 PM, Nicola Ken Barozzi wrote:
<snip>
>>>>> - sitemap.xmap - this provides the infrastructure matchers (i.e. 
>>>>> site.xml, faq.xml, issues.xml), as such it will be mounted before 
>>>>> *any* of the Forrest matches. This sitemap can override any 
>>>>> behaviour within Forrest)
>>>>>
>>>>> - source.xmap - this provides the source matchers (i.e. **.xml), 
>>>>> it is mounted in forrest.xmap before the default forrest **.xml 
>>>>> behaviour and therefore can override that default behaviour but it 
>>>>> will not interfere with any internal Forrest infrastructure 
>>>>> matches, or any other plugins infrastructure matches.
>>>>>
>>>>> - output.xmap - this provides (surprise!) the output matchers 
>>>>> (i.e. **.html, **.pdf, **.slides), it is mounted before any of the 
>>>>> default matchers for Forrest and so can override this default 
>>>>> behaviour

Does it make sense to call them:

- input.xmap (instead of source.xmap)
- output.xmap?

That way, it's immediately clear what's happening. Otherwise, a newbie 
may not 'get it'... (I hope this isn't like asking if they can make the 
Panama Canal a 'few feet wider'? ;-))

Web Maestro Clay
-- 
Clay Leeds - <cleeds@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>


Mime
View raw message