Here are a few ideas for future enhancements to Plucker.

First is clipboarding. I know it's on the list, and I'm sure there are 
other, more pressing things to do, but it's something I miss sorely. Book 
titles from reviews, restaurant addresses, URLs given as text, tips and 
tricks, references, recipes, etc. -- these are all things I now write (via 
graffiti) or copy (via ClipStringHack), neither of which are ideal 
solutions. Please, please -- pretty please, beg, grovel -- consider moving 
this up in the list of priorities!

Second is a "wouldn't it be nice" idea. At this point, we can point Plucker 
to an .html file and have it plucked. What if we could do the same with a 
file displayed in the browser? Go to a site, right-click, select "Send to 
Plucker", and voil�, page is plucked. Perhaps even with a selected block 
only...?

Third and last is an idea borrowed from sitescooper. Sitescooper does an 
admirable job of scooping and paring down pages, but sometimes it feels 
like overkill. What if Plucker had two more options, something like 
pluckfrom="string" and pluckto="string"? Only what is between the two 
strings would be parsed (in the <body> section), with 'top' and 'bottom' as 
defaults if either one is missing (i.e., the full <body> section). If 
implemented so that only one such tuple is allowed, we could, for instance, 
get rid of mastheads, navigation bars and third-column ads while still 
allowing images to be plucked from the main part of the page (based on the 
existing options for images, that doesn't have to be changed). If multiple 
tuples are allowed, individual sections can be included or ignored as well. 
Just a thought.

Thank you for reading this!
Ariel

_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list

Reply via email to