Watcher This takes a URL that it will check in timed intervals, parsing it for new URLs that it then queues up to be downloaded. For our purposes here, the URL Downloader is a subset of the Gallery Downloader. URL Downloader This does just the Gallery Downloader's back-end-instead of taking a string query, it takes the gallery or post URLs directly from the user, whether that is one from a drag-and-drop event or hundreds pasted from clipboard. In hydrus, a downloader is one of: Gallery Downloader This takes a string like 'blue_eyes' to produce a series of thumbnail gallery page URLs that can be parsed for image page URLs which can ultimately be parsed for file URLs and metadata like tags. Your feedback on the system would be appreciated, and if something is confusing or you discover something in here that is out of date, please let me know. These help pages describe the different compontents with the intention of making an HTML- or JSON- fluent user able to create and share a full new downloader on their own.Īs always, this is all under active development. It is designed to be very simple to the front-end user-they will typically handle a couple of png files and then select a new downloader from a list-but very flexible (and hence potentially complicated) on the back-end. After the maintenance burden of the entire messy system proved too large for me to keep up with and a semi-editable booru system proved successful, I decided to overhaul the entire thing to allow user creation and sharing of every component. The first versions of hydrus's downloaders were all hardcoded and static-I wrote everything into the program itself and nothing was user-creatable or -fixable. Beware! If you are simply looking for how to add new downloaders, please head over here. Creating custom downloaders is only for advanced users who understand HTML or JSON.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |