kfwong / elvis Goto Github PK

Current UI is meant for quick prototyping. It is usable but not appealing.

I'm looking for a high fidelity sketch (Adobe Photoshop/Illustrator/Hand-drawn) for the overall look & feel. Post your design here as image attachment and we'll have a look!

Knowledge of FXML is a bonus but not necessary. Post your sketch here and we'll look for Frontend Programmer to implement the UI. Otherwise if you are capable of coding it yourself that'll be perfect!

Basic UI elements:

• Message Log View
• Login Button
• Login Dialog
• Download Button
• Force Download Button
• Change Directory Button
• Change Directory Dialog
• Exit Button

You can also propose other elements in your design, we'll see if it's feasible to implement it!

Just realize TornadoFX library has built in EventBus to handle pub-sub between UI and controller. Need to explore the possibility to replace the Guava's EventBus (Library is too fat).

Need to restyle the Webview (login) to closely resemble the UI theme. Log message need some proper formatting and syntax highlight to easily identify them

Been quite lazy to explain the function of the code.

Hard to verify PR without it!

need to write a user manual

as title mentioned.

as mentioned in the title.

• Display user's name or nusnet id when login instead of "user has login"
• Need to explore IVLE User API

as title mentioned.

duhhh!!!

Might need to check the ecistence of the file. Relying on registry is not enough.

write a developer manual on the architecture and setting up instructions

• test for each LAPI endpoint
• Integration test

as title mentioned.

Fuel download api spawn a new thread for different URL. Current 1.0.0 version will see obvious lag when downloading when the multiple spawning happen at the same time. Can't figure out the synchronous version, might need to use OkHttp to do synchronous download on a single thread instead.

Note: Force download can rectify the issue.

As mentioned in the title. The registry (using Preferences API) is not updated.

Possible solutions:

1. Check the files physically instead of over-relying on registry. Update the registry when the directory changed.
2. Create different registry for different directory. (Not feasible maybe?)

Still need to explore other options to improve tracking.