Addendum...
Maybe storing option values is not the best way to do this. Using
specific tags for the task, like includeRSS and excludeRSS seems a
more natural choice, whereas any tags tagging to either of these will
be considered as the tags for inclusion or exclusion...
So, in the examples given above, the tag RSS would now tag to
includeRSS and the tags excludeSearch and systemConfig would tag to
excludeRSS.
Instead of reading from option values, the code would then look like
this...
// The body
var tids = store.getTiddlers("modified","excludeLists");
var n = config.numRssItems;
var i = store.getTaggedTiddlers('includeRSS').map(function(t){return
t.title;});
var e = store.getTaggedTiddlers('excludeRSS').map(function(t){return
t.title;});
for(var t=tids.length-1;t>=0;t--) {
if((!e[0]||!tids[t].tags.containsAny(e))&&
(!i[0]||tids[t].tags.containsAny(i))){
s.push("<item>\n" + tiddlerToRssItem(tids[t],u) +
"\n</item>");
n--;
}
if(n==0)break;
}
I think this is a much cleaner version than dealing with hidden
options or temporary cookies.
Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywikidev?hl=en.
