Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41801B15.8050409@brondsema.net>
Date: Wed, 27 Oct 2004 18:03:01 -0400
From: Dave Brondsema <dave@brondsema.net>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: [RT] Including Plugin documentation in Forrest website
References: <417EE0E9.5050904@apache.org>
 <417FD9E0.4050303@brondsema.net>	 <417FE583.80804@apache.org>
 <1b0b455704102714596be21c6f@mail.gmail.com>
In-Reply-To: <1b0b455704102714596be21c6f@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigBB922585AA0224EA0B643AEC"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigBB922585AA0224EA0B643AEC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Diwaker Gupta wrote:
> On Wed, 27 Oct 2004 19:14:27 +0100, Ross Gardler <rgardler@apache.org> wrote:
> 
>>Am I still going in the wrong direction? I have no problem with it
>>staying in the IMSManifest plugin, just wanting to know if it has a
>>wider use.
> 
> 
> I think its a **great** thought, and will definitely go a long way in
> making Forrest a mature product. There are many many more use cases
> that can be thought of, but the ones you list make a representative
> list. But I'll add just another one:
> 
> Consider the computer science department of a University. The systems
> people maintain their own webpage, the theory guys maintain their own
> (do they??!), the vision people their own. The CS webadmins then
> simply can use Forrest to plug-in these separate websites to create an
> integrated website for the department.
> 
> I'm +1 on the 2) approach -- this should be core forrest
> functionality. Further, I have a feeling that (like IMSManifest) any
> plugin that does this would not be able to provide fine grained
> control over site.xml and tabs.xml (atleast not easily).
> 

Yeah I think it's a fine idea.  Is it really related to IMSManifests? 
Would it be better as it's own plugin?  Or would it even be better as 
part of core forrest.. I'm not sure how much change it would require.

But for our need of documenting plugins, lets go the simple route.  If 
we need to use this feature in the future, we can, but I don't see the 
need now.

-- 
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal

--------------enigBB922585AA0224EA0B643AEC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBgBsVVvBSb5uzznARAl/LAKCR52suvbDVVb+FSBm9fu4+XEIiKwCfTzhx
vGvyjZm0vSNJ11T10BCqtzM=
=CYxR
-----END PGP SIGNATURE-----

--------------enigBB922585AA0224EA0B643AEC--