From: stardiviner <firstname.lastname@example.org> To: Ihor Radchenko <email@example.com> Cc: Matthew Lundin <firstname.lastname@example.org>, Org Mode <email@example.com> Subject: Re: [Feature] add a new org-attach dispatcher command to offline save web page Date: Fri, 29 May 2020 10:06:24 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <875zcgugq2.fsf@localhost> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Thanks, Ihor, your explanation is helpful a lot!!! Ihor Radchenko <email@example.com> writes: >> My uneasiness has more to do with the specificity of the dependence on >> monolith and the way that is hard-coded into the patch. When it comes to >> patches, I think priority should go to those that are configurable, >> accessible, and useful for everyone as opposed to those that have >> hard-coded work-flows or highly-specific user configurations. > > Agree. Though I can see a use of having monolith as one of the options > to help people discover what kind of tools they can use. I personally > had a hard time finding command-line cli like monolith. Actually, it is > the first time I heard about some offline tool handling js without a > need to write python or ruby code. > >> The question is: which functionality? A simple downloading tool or a >> full archival tool? Achieving similar functionality to org-board or >> monolith would a big task, since they aim to download an archival >> version of a webpage (including all resources). > > My view on this is bare-bones download, in a spirit of org-attach > itself. There is already 'url method in org-attach-attach, but it is > hard-coded to url-retrieve-synchronously. It would be handy if user > could configure alternative retrievers (like monolith, wget, curl, or > some user-defined function). > > Note that monolith does not crawl the website. It only collects > everything needed to show the page as you see it in browser into single > html file. This behaviour is what one expects to obtain when saving a > full web-page from browser. > >> In addition, with >> archiving you also quickly run into the complexity of versioning based >> on time archived. > > I guess that org-attach-git can be used for versioning, but I don't > think that versioning is within scope of this patch. Monolith does not > even support versioning. > >> There's also the challenge of mapping the downloaded >> files to metadata (specifically the original url). Org-board currently >> handles both of these very well. > > org-board is a great package, but it is not built-in. I do not think > that all the org-board functionality needs to be included into > org-attach. At least not within scope of this patch as I understand it. > > Best, > Ihor > > Matthew Lundin <firstname.lastname@example.org> writes: > >> Ihor Radchenko <email@example.com> writes: >> >>> It does not mean that attaching URL directly is not worth including >>> into org. This sounds pretty common use case, especially considering >>> the number of packages providing similar feature. You mentioned >>> org-board, but there is also org-download and org-web-tools. >> >> My uneasiness has more to do with the specificity of the dependence on >> monolith and the way that is hard-coded into the patch. When it comes to >> patches, I think priority should go to those that are configurable, >> accessible, and useful for everyone as opposed to those that have >> hard-coded work-flows or highly-specific user configurations. >> >>> I agree that monolith is completely uncommon tool and I would not expect >>> the majority of users to have it installed, but the same functionality >>> utilising built-in url.el (as a default) should be acceptable. >> >> The question is: which functionality? A simple downloading tool or a >> full archival tool? Achieving similar functionality to org-board or >> monolith would a big task, since they aim to download an archival >> version of a webpage (including all resources). In addition, with >> archiving you also quickly run into the complexity of versioning based >> on time archived. There's also the challenge of mapping the downloaded >> files to metadata (specifically the original url). Org-board currently >> handles both of these very well. >> >> I suppose there would be a few options depending on what the aims are: >> >> 1. At the simple end, include little more than than a quick and dirty >> way of downloading a single resource (html, pdf, jpeg) using url.el >> or wget (or optionally, monolith) and putting that in the attachment >> folder. Those who want full archiving of all resources could use >> other tools like org-board or org-web-tools. >> >> 2. At the (much) more complex end, it would be to code out a robust >> archiving solution on top of url.el or wget. >> >> 3. Another, possibly simpler option... Add a command to the dispatcher >> that allows the user to invoke a custom function that is called with >> the attachment directory as the default-directory. This would enable >> more end-user flexibility, such as the ability to use >> wkhtmtoimage/wkhtmltopdf, monolith, phantom.js, archive.is, etc. >> >> Best, >> >> Matt - -- [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 -----BEGIN PGP SIGNATURE----- iQFIBAEBCAAyFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAl7QbiAUHG51bWJjaGls ZEBnbWFpbC5jb20ACgkQG13xyVromsP+zQf/fR+EfMEqnXjb7GHaQFy6c7oKwYV6 ha8Wn4surO/drg5jgGXAyCpU72ru9Q1hKlxxlUYI/ZVexiCZU8U4masVHxOIbMWG 2PrtBAJgVcC87jrYufTF+bnWfDBmNMgMtpCALa4NQ2tH83vMKSkpBK42vRSIWK61 YUbGUD0aPdUCjVz5Cwa5xfZe2i9phPPg6ipjBCm+sIdzOeFL8Dj/34dtPW1G/sOE LTFyntcWn44xpb9mjSgN6EWC1Y9LJYSPTyP0PWVu5JXBoQfA+4vf5i7UakLurI46 +fBPPWNkb48yRc5i5OTxnI3Nxxk5YlQQbXZStMmKuqpIKmsNJsVjqfGa+g== =8LEN -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2020-05-29 2:07 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-27 9:55 stardiviner 2020-05-28 2:55 ` Matthew Lundin 2020-05-28 5:49 ` Ihor Radchenko 2020-05-28 6:39 ` stardiviner 2020-05-28 14:03 ` Ihor Radchenko 2020-05-28 16:00 ` stardiviner 2020-05-28 18:16 ` Ihor Radchenko 2020-05-28 16:19 ` Matthew Lundin 2020-05-28 17:11 ` Ihor Radchenko 2020-05-28 22:15 ` Matthew Lundin 2020-05-29 2:15 ` stardiviner 2020-05-29 2:06 ` stardiviner [this message] 2020-05-29 2:03 ` stardiviner 2020-05-29 2:17 ` Ihor Radchenko 2020-05-29 6:16 ` stardiviner 2020-05-29 15:33 ` Matthew Lundin 2020-05-29 16:32 ` stardiviner 2020-05-30 6:09 ` Ihor Radchenko 2020-05-28 6:37 ` stardiviner 2020-05-28 6:40 ` stardiviner 2020-05-28 22:24 ` Samuel Wales 2020-05-29 2:23 ` [PATCH updated] " stardiviner 2020-05-29 2:27 ` stardiviner 2020-06-02 12:20 ` Bastien 2020-06-02 14:06 ` stardiviner 2020-06-02 14:26 ` Bastien 2020-06-02 14:40 ` stardiviner 2020-06-03 15:10 ` Bastien 2020-06-03 23:34 ` stardiviner
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [Feature] add a new org-attach dispatcher command to offline save web page' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).