windows
zip: https://github.com/hydrusnetwork/hydrus/releases/download/v230/Hydrus.Network.230.-.Windows.-.Extract.only.zip
exe: https://github.com/hydrusnetwork/hydrus/releases/download/v230/Hydrus.Network.230.-.Windows.-.Installer.exe
os x
app: https://github.com/hydrusnetwork/hydrus/releases/download/v230/Hydrus.Network.230.-.OS.X.-.App.dmg
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v230/Hydrus.Network.230.-.OS.X.-.Extract.only.tar.gz
linux
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v230/Hydrus.Network.230.-.Linux.-.Executable.tar.gz
source
tar.gz: https://github.com/hydrusnetwork/hydrus/archive/v230.tar.gz
I had a great week. The first version of my parser is done and I have moved the menu id bug fix forward.
menu id
I further developed last week's new menu id system and moved the 'pending' menu over to it. Everything seems to clean up after itself as expected, and I believe this should fix the menu id bug for most users.
If you have had this bug, please try this version and let me know if you still get it.
parser v1.0
services->manage parsing scripts is no longer under construction. I believe I've created all the ui and hooked all the buttons together properly, and I've added some mini-help 'info' panels to the big dialogs as well. Created scripts will now save to the database on dialog ok and can be freely created and shared between users.
I've created a functional 'gelbooru md5' script as well–if you are interested in making some scripts, please check out how it works. Try putting 'c4d072a43f4db650c2d78840a5e8ff60' or any other gelbooru file's md5 into the test panel–you'll get some live gelbooru tags back. Putting an md5 that gelbooru doesn't have will also correctly return nothing. I didn't have time to add an iqdb script (which will show off how the 'link' child node works), but I'll make sure to do it for next week.
I would also like to finally make a 'suggested tags' control that pulls these 'file lookup' scripts for next week.
There is a lot more to do on all this, including more help, script types, content types, json parsing formulae, and a unified bit of gui to control a script in action and to describe how it is working or failing. I expect to make most of these changes as needed, so let me know what you think.
Eventually, all program parsing (including all the gallery downloaders) will be managed (and hence user-editable/fixable) through the same system.
full list
- all multiline text ctrls now support ctrl+a for select all, wew
- added dynamic menu_item tracking to new menu id system
- added submenu tracking to new menu id system
- added comprehensive menu, submenu, and menu item destruction to new menu id system.
- 'pending' menu now works on the new menu id system–is likely a major cause of the menu id bugs
- added 'info' tabs to the script/nodes/formula parsing gui panels
- added a 'veto' content type for discovering undesired redirects
- added special veto support to parsing engine
- expanded the content node panel to handle and display multiple content types
- added 'link' parsing node panel
- expanded 'link' panel test page and tied in secondary layer example url and data forwarding to children
- fixed the parsing node children control not forwarding example data up to nodes on edit
- file lookup url is now explicitly stored in the file lookup script object
- file lookup url is now passed to child parsing dialogs for test example data purposes
- expanded internal 'requests' interface a little–it now also always includes the 'user-agent' request header as the typical 'hydrus/version_number'
- wrote script GET/POST engine gubbins and tied it into the respective test page
- wrote link GET engine gubbins and tied it into the respective test page
- 'person' namespace added to default namespace colours–it is RGB ( 0, 128, 0 ), a darker version of 'character' green
next week
I'll add the 'suggested tags from file lookup' control, and I'd like to add more layout options for all the suggested tags stuff. With any luck, that should be all I need to do for it, and I can move on to the next big thing in my list: a faster dupe search algorithm.