forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gav..." <>
Subject Re: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Date Thu, 06 Apr 2006 04:48:55 GMT

> Gav.... wrote:
>> Hi All,
>> There is progress on this. We have two directions to go in here.
>> As stated by David :
>> <quote>
>> One really good idea was to create the new Glossary plugin
>> and use that.
>> Failing that, i reckon just use an ordinary document
>> with concise definitions that link to examples in
>> the other documents.
>> However it gets done is good.
>> </quote>
>> So we have:
>> 1. Deploy Glossary Plugin to main Forrest Site so we can create a
>> Glossary
>> File to put the terminology. However this is in Whiteboard and now
>> involves
>> :-
>> <quote=Ross>
>> Yes, it should be in whiteboard until:
>> a) it works fully
>> b) it is documented
>> c) it has community support
>> </quote>
> I reckon that it is okay to use plugins that are
> in the whiteboard. In fact we need to do that so
> that we can find any shortcomings, finalise them,
> and get them out of the whiteboard.
> We would need to deploy the plugin to the download site.
> We already have others, e.g. f.a.o.plugin.input.Daisy
> I am going to go ahead and do that, and will be happy
> to revert it if people disagree.

Ok, good.

>> 2. Write terminology to a howto-dispatcher-terminology.xml file.
>> I have started work on both types of file, just need to now input the
>> actual
>> terminology descriptions.
> Why do we need a Howto? My suggestion was intended
> to just create a plain document with a <ul> list
> or simple table until we got the "glossary" plugin
> working then transfer the content.

Sorry, my bad, I realise you meant a plain doc, but I
thought it should be grouped in with the rest of the
dispatcher/structurer 'howto' docs, so called it that.

>> So, what is needed now to get Option 1 under way ?
>> I'll send a patch for Option 2 when done.
> Still send it if you think that both are needed.
> -David

I dont now think we need two, was just as you say doing the
normal doc until the Glossary Plugin was available for use
on the main site. As it is going to happen quicker than I
thought, I will just concentrate on the Glossary Version.




View raw message