On Sun, Nov 11, 2001, Robert O'Connor wrote: > Sections would definately be an easier way to deal with configurations (for > not the least of which, it would absolve of having to keep switching and > creating/destroying config objects).
I can send you a diff with the changes I had to do to make it work with sections instead of different config files. Not that many changes. Maybe you can find something useful in it. > I was wondering about where to best save a channels's home.html, Many "channels" will not have a home.html file, i.e. they will just include a URL to the contents. Others will have a local html file, but not necessarily a home.html file that is part of Plucker. > Also, farther down the road, a channels cache directory will probably > raise in importance as the stuff in it will likely be examined and > reused. Still worthwhile to have channel directories to hold these > two items (but not the channel's config file)? In Linux I don't see any use of a channels directory that can't be handled by the current PLUCKERDIR directory (default: ~/.plucker). That is, if the user wants to create a local file with links using the desktop tool's HTML editor then it could be stored in ~/.plucker (or a subdir) given a unique name instead of having a lot of home.html files in different directories. /Mike
