Reimplement "About the book" outside of the preview using JavaFX components. This would enable a move away from AJUI, see #14.

Make it possible to open the user manual from within the application

Perform accessibility tests to make sure everything works as expected.

Simplex numbering appears to start from 2 (not 1)

Add a list of recently closed files to the file menu

An XML-editor component could be useful to edit PEF-files directly or edit the source document from inside the application. It could also replace the current feature "view source".

While the software is built to support 8 dot in principal, some components do not support 8 dot even if they could.

It would be useful if the user could save templates and use them when opening, similar to the functionality in Pipeline 2 webui.

When the file has been edited outside of Dotify Studio, the application asks: "The file has been modified by another program. Do you want to reload it and lose the changes made here?" even if no changes have been made.

The wording should be different if there are no changes to lose.

Pef is the output format, and should be excluded from the input list.

The application should perhaps prevent the same file from being open in several tabs

• PreviewController and related (don't forget resource-files)
• method=do
• method=test

If the application is started multiple times, several windows are opened. Instead, the started instance should be reused.

When starting the application with a file argument, the name of the tab includes the full path, this is not the case when the file is opened from within the application.

If a single plugin has dependencies, then it would be nice to keep those packaged together so that an individual plugin can be removed if needed.

When deleting a custom paper, a confirmation dialog would be nice.

Supported languages are English, Swedish and Norwegian.

The console view should be possible to hide.

It would be useful if a progress bar was showing when importing a big file. Currently, there is progress in the console view, but there could be a more graphical progress bar (perhaps including a time to completion estimate).

See also ologolo/streamline-engine#2

Javafx version is missing cut length.

Add possibility to batch convert or convert without opening. This feature would allow other output formats than pef.

Previously, there was a warning when opening or trying to emboss a file with 8-dot patterns. This has been lost when moving to JavaFX. Restore this, so that paper isn't wasted on files that cannot be embossed.

Note that even if #5 is fixed, there could still be situations where a warning could be necessary, for example when a specific embosser cannot support 8-dot.

Using the Windows file integration still opens the embedded embossing dialog.

Add a tools tab where the character tools from devtools.gui could be included.

There should be some information in the generated pef-files about the system that created them.

Add a Norwegian translation to the GUI.

The menu item “Open in browser” causes Dotify Studio to hang on Linux (CentOs/Ubuntu).

Dragging and dropping a pef file should be supported

1. Open search view
2. Type in a search that gives a result
3. Select a result
4. Click button to choose a new directory
5. Hit cancel

Expected result: nothing changes
Actual result: file is opened

Adding a sheet paper results in a tractor paper and vice versa

Setup builder isn't used to create the exe for windows. This creates a conflict with building dmg, because the shortcuts are manually created with a wix template, but the dmg task requires information that creates an automatic shortcut on Windows which doesn't work because either it doesn't know about the exe that is manually created or it doesn't include the jre although it should or it creates the shortcut in the wrong place.

Ask before quitting application with unsaved changes

The newest version of ajui has more advanced capabilities. These could be used in Dotify Studio. It is also possible that AJUI isn't needed at all in Dotify Studio when remaining dialogs have been rewritten (print and about book) and the preview code has been updated.

Add icons to tabs to make it easier to differentiate between pef and source material

A tab with unsaved changes can be closed without a confirmation dialog by using the shortcut CTRL+F4 or SHORTCUT+W.

Doing Event.fireEvent(t, new Event(Tab.TAB_CLOSE_REQUEST_EVENT)) doesn't work, because it doesn't close the tab.

See https://bugs.openjdk.java.net/browse/JDK-8091261 for a possible workaround.

Currently there's no way to remember the previous print settings. This was possible in Easy Embossing Utility. A workaround is to use the "Open in browser" command and print from there. That way it is possible to go back using the browser navigation. It is also possible to right click in the view and select "go back" or hit backspace on the keyboard.

The wiki is out of date and needs updating.

Some log messages should probably have a lower level than info. If desired, a logging configuration can restore these for development purposes.

XSLT is a bit slow. Using a single pass stax together with the info from PEFInfo, would be much faster.

External links in the user guide are currently opened in the web view, this is problematic as there isn't any "back" button.

Associate extension with e2u
for example:
mimeopen -d

add new command:
java -jar [path to jar] -open

Add icon
Create svg image
http://askubuntu.com/questions/52138/how-do-i-change-the-icon-for-a-particular-file-type
application/x-pef+xml

Create an enhanced web view with a search field and previous/next match and location navigation buttons (forward, backward).

See https://bugs.openjdk.java.net/browse/JDK-8167282

Opening a help tab enables file actions that should still be disabled (e.g. save as...).

No editor is opened for text on MacOS (probably has to do with supported mime types)

Template can be selected when the file is opened, but it would be useful if it could be done afterwards too.

Add the possibility to set the console limit (in settings)

Editor might not be marked as changed when it should be:

1. Open file
2. Open file in another program, make a change and save
3. Go back to Dotify Studio, and activate the editor. Answer "abort".

The state of the editor is now "unchanged" when it shouldn't be (because it differs from the state on disk).

When generating a test document, embosser limitations are not considered. For
example, Braillo 400SR cannot produce more than 31 cells on an A4 paper, but
when using this embosser and setting it for A4 sized paper, the software
produces a test file that is 35 cells wide, which cannot be embossed on an A4
paper with that embosser.

When changing a source file that is open in the application, the update fails to complete.