You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Jeff Turner <je...@apache.org> on 2003/07/15 14:31:08 UTC
Forrest planning (Re: Elements on the skinconf)
On Mon, Jul 14, 2003 at 07:54:28PM +0200, Juan Jose Pablos wrote:
> Jeff,
>
> >
> >It wouldn't be difficult, but it would break compatibility with existing
> >skins. skinconf.xml and forrest.properties should go away entirely in
> >0.6, so it's not worth breaking backwards-compatibility by fixing it.
>
> I have not been able to see the project plan, is there anywhere i can
> see that?, I only saw "Forrest 0.5 outstanding issues" but nothing to do
> of what is going to go away.
Yes, sorry about that, what plan there is is kinda spread over numerous
emails. After getting the docs updated for 0.5, I'm planning on sifting
through the old threads, and making serious use of our JIRA bugtracker
for recording it all. Then we can have a clear roadmap of what needs to
be done for 0.6, like this one:
http://jira.atlassian.com/secure/BrowseProject.jspa?id=10240&report=roadmap
The issue in question (the fate of skinconf.xml) is tied to various
discussions about having a common gump-like data model for Forrest sites.
The basic idea is to have all project metadata in a single XML file
(probably a straight Gump descriptor, but other formats allowable). This
would contain metadata currently stored in skinconf.xml and
forrest.properties (the 'project.*' properties):
http://marc.theaimsgroup.com/?t=104997203700003&r=1&w=2
--Jeff
> Cheers
>
> Cheche
>