-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversion support #103
Conversion support #103
Conversation
bring up to date
The setting values can be found at GET The available formats can be acquired by fetching GET The conversion proposal can be fetched from GET [
{
'before': '/folder/file.zip'
'after': '/folder/file.cbz'
},
{
'before': '/folder/file_2.zip'
'after': '/folder/file_2.cbz'
}
] Applying the conversion can be done via POST As far as I know, this is all you need to build the frontend, but let me know if you're missing something or have a question :) |
All the backend is written now. Only thing left is the frontend and adding more conversion classes. The only conversion available currently is ZIP to CBZ (because it's purely renaming the extension, so easy to add and test with). But now we can start adding conversions like RAR to CBR, RAR to CBZ, RAR to ZIP, etc. Maybe we should also add conversion methods for turning an archive file (CBZ, ZIP, RAR, CBR, EPUB, etc.) in to raw files on the disk? Something like: extract files in to sub-folder -> filter extracted files for relevance -> delete irrelevant files -> move and rename relevant files. That is exactly what the unzipping feature is doing currently. Then we can merge unzipping with converting, because then unzipping is just the same as converting a ZIP to files. I think that, whatever way we do it, we should combine unzipping and conversion into one feature. |
Added UI for conversion, so only the only thing left is the conversion settings in the UI and merging unzipping with converting. |
No description provided.