At 02:01 AM 11/20/2002 +0000, Robert O'Connor wrote:
Looking through, I think it is very nicely done. Great work!
Thanks.
For exclusion lists, this has come up before with regards to how to package these withThis raises an issue of interfaces. Certainly we could move exclusions to Plucker.INI, but for much of my parser testing (like when I was adding --stayondomain) I ran Plucker from the command line without a corresponding INI channel. Doing that, I can load exclusion lists from the command-line. So I certainly wouldn't want to completely deprecate exclusion files.
descriptions of sites, since that is arguably the most important part, as it is the part that
most people don't know how to set up on their own.
Exclusion lists are about one of the few areas of the config that would benefit from an XML
format. However, XML configs isn't doable now. Also, it would be beneficial to allow the
exclusions to be commandline accessbile for future tools that wanted to call the parser with
specific exclusions. Therefore, it was put forward, to include exclusions as numbered keys,
using the existing method of an exclusion list entry. For example:
exclusion_item1=0:-:.*\.mp3$
exclusion_item2=0:-:http://.*www.x10.com/.*
The parser would then loop through a section, looking to see if there was the next incremented
number of key, and if so, add that exclusion to the active exclusions.
On the other hand, I also agree that all channel-specific configuration data should go in a single place, and the INI file is a good contender for that.
But either way, that's not in the Parser nor would Desktop see them or save exclusions there itself, so there's not much point in doing it in PlkrData right now. The exclusion list has GOT to wind up in a file on the other side. So packaging it as an encoded blob is probably faster than enumerating through a series of keys.
Okay, I've got two minds about this. If you would like to coordinate work on this with me, I can handle the parser and PlkrData side with you handling the Desktop side of putting these changes into a synchronized release. I'm thinking that compatibility with the installed base would be a "good thing" though.
-Tony McNamara-
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
