1) as i'm still getting used to the file and directory structure
of a newly-seeded forrest project, it's sometimes difficult
to remember which file to look at to configure a particular
feature. there's the top-level forrest.properties and
statux.xml files i've checked out so far, and further down,
there's the directories content, resources and skins, and
under skins we have skinconf.xml and ... whew.
i realize i can, if i want, simplify things via forrest.properties,
but i'm loathe to do that until i understand the rationale
for the current layout. is there, somewhere, an explanation
for this layout? i suspect it's just because i don't know
enough about what i can do with forrest that i don't appreciate
the hierarchy. yet.
2) what's happens if you seed an already populated directory?
from a previous posting, there are some changes in the CVS
tree. so what if i download the CVS tree, then go to the
top of my current project, and type "forrest seed". the
idea would be to overwrite any older files with the newer
ones but, of course, i'd want to preserve any that i'd already
modified.
what's the advice on applying a newer CVS download to an
existing project? or does that question make any sense?
and am i just asking for trouble?
3) is there an aesthetic reason for the tabs to be, by default,
on the right hand side for the avalon-tigris skin? it seems a
bit odd, and inconsistent with the other default skins, but
that's just nitpicking.
more later.
rday
--
Robert P. J. Day
Eno River Technologies
Unix, Linux and Open Source training
Waterloo, Ontario
www.enoriver.com
|