brailleapps / dotify-cli Goto Github PK

Add automatic uploading of artifacts from travis

ManifestRetriever is a class that could be useful in other projects, such as dotify-studio

The plugin folder will only work if the current working directory contains that folder. It should be more robust.

Add an option to enable debugging.

If not set, only show the error message. If set, show the entire stack trace.

The folder specified in the find command's help is not the same that it subsequently uses (for some reason)

There should be an option to verify (and change) settings and emboss in the
same command, i.e.:

dotify emboss path_to_file -setup

Page-height and page-width are listed by several tasks, but the presets include rows/cols. This causes a conflict.

Package structure isn't ideal for modularization.

As epub/html is being supported, it would make sense to allow conversion of content directly from the Internet. For example:
convert http://www.example.com/my-article C:\result.pef

Support localized help texts etc.

Use the new validator API.

Add travis build (depends on releasing braille-utils.ui to maven central)

Some options (i.e. identifier, date, dateFormat) are not globally applicable, but rather specific to PEF output, and should consequently be moved to that task's options instead (as per dotify.task-api:2.2.0).

Validation of additional formats could be supported. OBFL is already implemented.

Blocked by #12.

It is difficult to understand how to use the find command. If no arguments are given, it starts the interactive mode, even when -i is not specified. Also -r doesn't seem to work without --folder

Make it possible to list input and output formats

There's logic in Dotify.java that handles the absence of identifier, date and dateFormat, but the actual code that suffers from this absence is in the PEFMediaWriter. This logic should move there, to make the ui code cleaner and the various use cases more similar.

Support the same user configurations as in Dotify Studio