-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 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.
It's on the list? What list? We've never actually condoned adding
internal clipboard support to Plucker, since most external "hacks" and
third-party tools can provide that.
> 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!
You just gave me an idea, and one I think we should add fairly
quickly... a "Copy URL of this page to Memo" option. Right now, we only have
the option of copying the URL when it exceeds home_maxdepth. There is
currently no way to copy the URL of a page you are _actively_ viewing in
Plucker itself. Shouldn't be too hard to add.
> 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...?
FlingIt does just that, and there are other third-party browser
plugin ideas. Probably not something the viewer should ship with, but if
anyone wants to write one, you could do it with ActiveX in IE and XUL in
Mozilla if you wanted. Something like a File->SendTo->Plucker option, or
SaveAs->Plucker or something. Not hard, but probably not something that the
Plucker team would be responsible for, unless someone had some spare time to
play around with it.
> 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.
Sitescooper has its place, as does Plucker. They complement each
other well, with certain content. Let's not try to merge them together
(although Sitescooper's maintainer is looking to pass on the project to
someone else).
> 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).
That's called "transcoding", and probably won't be added into
Plucker, since tools like Pyrite, Sitescooper, and others do a fine job of
it themselves. You could also just wget the content, and pre-process it
locally with a few perl/awk/sed statements to remove the bits you didn't
want to see.
> Thank you for reading this!
Sure, keep the ideas flowing.
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.92 (GNU/Linux)
iD8DBQE9pwR9kRQERnB1rkoRAurcAJ9b3iwL0zvZGj7qSgUSocEmuTKT0QCfZlWR
anpc0maTyubAad2DFuly7RU=
=xRpG
-----END PGP SIGNATURE-----
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
