These changes have been checked in to the latest Sitescooper bleeding edge. Here's the mail from the Sitescooper mailing list. This looks like good stuff and worth the iinvestigating. Thanks Chris!
Quote:
[scoop] Checked in improved support for isiloXC
Chris Werner chriswerner at mail.telepac.pt
Mon Mar 22 16:36:34 GMT 2004 Improved support for isiloXC:
Thanks Jason for extending developer privileges so that I was able to check
this in.
Short explanation:
==================
If you read your scoops with isilo and you use the -misilox or -isilox
argument, but you don't like the default settings that sitescooper passes to
isiloxc - perhaps you want more colours, or a different category - then this
fix will help you.
To take advantage of it, simply:
i) run the isiloX gui tool
ii) in a new file, add a single document (there can be only one!)
iii) setup the options you want for bit depth, table handling, etc
iv) forget about the source, destination, and link options, these are
overridden by sitescooper
v) save as default_isilox.ixl in your sitescooper main directory
vi) edit sitescooper.cf and uncomment the last line
(For site-specific settings read the details below and the site_params.html
doc)
Detailed explanation:
=====================
1. Added a new param to sitescooper.cf "ISiloDefaultIxlFile" that points to
an .ixl file in the file system.
This means that users can change the iSiloX options by using the iSiloX GUI
tool to create a new document, change all the options, then save as a .ixl
file. The <Source> and <Destination> tags of the document are stripped and
replaced by sitescooper but the rest is used for generating the isilox pdb.
More details are given in the comments in sitescooper.cf.
The most common likely use for this is to allow the users of -isilox to
specify global settings for things like image depth, color, inclusion,
dithering etc, and perhaps for category too.
2. Added a new site param called "ExtraISiloIxlTags", to allow ixl settings
specific to a site. Updated doc/site_params.html, so see this for more
details.
This is a little different in that the user has to specify a set of
top-level tags for the .ixl file. These get appended to the generated file
thus overriding the defaults (or overriding the global options if the new
config param is used). This takes advantage of the fact that isilox
tolerates the tags appearing more than once by simply taking the last tag
and ignoring earlier copies (or at least its xml parser does).
So you can set general options in your .ixl file and override specific
options in the .site files.
The fact that you have to override the whole tag such as <ImageOptions>
means that you can't override, say bitdepth separately from dithering, but
its still pretty powerful. And simpler and more durable (ie resitant to
changes in isilox) than adding a bunch of new site params.
cheers
Chris
PS: changed the following files:
CVS: Modified Files:
CVS: sitescooper/sitescooper.cf sitescooper/doc/site_params.html
CVS: sitescooper/lib/Sitescooper/Main.pm
CVS: sitescooper/lib/Sitescooper/SCF.pm
CVS: Added Files:
CVS: sitescooper/default_isilox.ixl
|