justinthomas1 / inkdeck Goto Github PK

When the text is printed onto the text field after being decrypted, special block characters appear. This does not occur with the three fonts Java is built to use.

Due to the way the program is currently coded, unicode characters will cause the program to crash. This may or may not be fixed later.

Since the private key never needs to be sent, it shouldn't be accessible to the user (to avoid confusion). The public key should be stored automatically in the "Keys" directory.

It could also be stored in the preferences file.

The user should be able to choose from any fonts they already have installed, rather than just the four I've selected.

This may be help users who aren't very technical. It gets them used to the idea of getting public keys from fellow users.

There should be a dialogue box that prompts the user if they want to keep the same codename.

If I do go along with making the private key only in the preferences file, I need to rewrite the sidebar. It could look something like this:

Blank
Current Recipient: (codename, takes before "-public").
Blank (maybe something else here?)
Button to choose public key
Blank

Might implement this as part of the menubar, as it seems somewhat bare right now.

The Keymaker should open the first time the software is opened, determined by the lack/prescence of a config file. This could also allow for the creation of a save/save as distinction.

This should also save the previously used private/public key.

The program won't understand photos that are included in the jar file. This includes the icon and all splash messages that should be displayed when the program is opened.

Would help the user to use the software with quick access.

If you cancel out of the option, you can't open the dialog boxes again.

For the next version, the public key button text should read "Select Recipient's Public Key" so as to eliminate any confusion.

When you press RSA>Generate New Keys, it should automatically set the private key to your new one.

This may or may not be implemented. I'll have to look into how effective multithreading would be here.

In place of the "Select Recipient's Public Key" button that opens a file selector, there should be a dropdown list with all the Public Keys in the "Keys" directory. This would be much easier for non-technical users.

This could be a Gridview with a label on top that has the current button text, and the dropdown list could be placed below it.

Edit (3/27): It could also have a button called "add new key" that opens a dialog box where the user can add new keys from a location such as the downloads file or their desktop to the "Keys" directory.

Edit (4/3): Maybe the gridview on the side could become 5 rows again and have the order: blank, recipient name, select recipient, add new public key, blank. Also, the dialog box for when the Keys folder is empty should instruct the user to generate a new key for themselves, as they likely don't have one if the folder is empty.

There should be a dialogue box warning the user not to send plaintext messages if they save a file as plaintext.

It would be best if the preferences could be stored in the .jar or somewhere out of the way. This would make the software less confusing for the user.

I noticed that the algorithm can take some time to encrypt a message. I think a pop-up with a progress bar would fit here.

InkDeck will not run if the codename is null. This requires deleting the preferences file.

There should be a manual in PDF format with pictures and better descriptions of how to use the software.