> Then I can run "plucker-build -s dilbert" to create a Plucker document > and on Sunday (when the comics strip is too large for the default > format) I run "plucker-build -s dilbert -s sunday" to get a Plucker > document with less bit depth but with a better scale factor for the > larger image. The sunday section can be used together with other > sections, too.
Aha I see, that was the critical bit--I never paid attention to the -s option in the plucker-build list of things. Nice. > At the moment, I only include sections with a home_url key in my list > of channels, e.g. in my pluckerrc file I use both "standalone" sections > and "support" sections and the latter doesn't make sense in a list of > channels. That makes good sense, and is a good strategy. > My view of the config file is to consider the DEFAULT section to > include "global" options and then all the real work is put into the > individual sections. Definately, I agree. 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). Also faster on the loading of rows into main dialog's list control and easier to execute with a button execute command. I was wondering about where to best save a channels's home.html, in a GUI context of having a HTML editable file of a list of links, but which you want to abstract this concept away from them? 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)? Best wishes, Robert
