mbilotta / julia Goto Github PK

This is a feature I'd really like and I think it should be possible to have it implemented without the need of support from representation plugins. Basically there should be a way to tell Julia to render 2, 3 or 4 times the size of the requested image and then scale it down averaging the colors inside blocks of 2x2, 3x3, 4x4 respectively. Of course this approach requires a huge amount of memory but could be applied to any representation transparently.

Currently, an error message is displayed with the UI left in some dirty state.

A better behaviour would be:

1. If there is only one control window, simply load the JIM data into that window and move that window to front.
2. If there are more than one control windows (even if they're all hidden), inform the user he/she must open this file from a control window and do nothing.
3. Simply open a new control window showing image data. That new window will have the same name as the file.

Currently, the only way to do that is by clicking the big floppy button inside a control window. That's not so obvious for the user.

Ok, I started to work on this using Commons CLI but that led to a dead-end. The biggest limit I've found is the fact there is no way to parse a command line entirely. If a command line contains an unrecognized option, you can choose if the parser should throw an exception or not, but parsing must always stop at the point that option is encountered. This behavior really doesn't help when you want your CLI to bifurcate basing on the presence of one option from a set of mutually exclusive ones. Julia CLI should work like this. At the highest level, user may choose between two options:

• Run Julia eventually passing a different profile directory than the default one (~/.juliafg).
• Create a JUP archive.

While looking for alternatives, I've found picocli that looks promising. This library seems to be much more powerful and elegant and also fits in a single .java file that I can directly embed in my code (as suggested by the author).

Sooner or later Swing will be deprecated in favor of JavaFX (or somewhat else) but I don't plan to rewrite the UI in the near future. That stated, a simple way to make Julia future-proof is to improve its CLI to provide users a complete headless experience.

Java annotations should be used instead for that purpose.

Would be very helpful.

Since JDK version 1.9, ImageIO has added compression level control. See the new PNGImageWriteParam class.

I'd like to have a way for users to throttle fractal image computation. Using this functionality users will be able to limit CPU utilization to keep resources for other programs running along with Julia.

If you hide all control windows, you feel like stuck.

Instead of Pin/Unpin, this button should be named something like "Disconnect from/Connect to main UI". The button should look pressed when the control window acts like connected (aka "unpinned"). This is the opposite of the current behaviour which is quite unintuitive. Of course, icons also should change.