GUI and JNI primer

[GoogleCodeExporter]

*Mock-up GUI
**MS paint or Swing
**Google UI editor 

*Self extracting JNI
**NRJavaSerial for example
**MineCraft sources for 3D

Original issue reported on code.google.com by Mad.Hephaestus@gmail.com on 17 Dec 2011 at 5:25

[GoogleCodeExporter]

Any progress on this?

Original comment by Mad.Hephaestus@gmail.com on 1 Jan 2012 at 9:52

[GoogleCodeExporter]

I am learning about the Google UI Editor and playing around with some mock 
layouts for the GUI using that. I haven't been able to locate the MineCraft 
sources and I have only very briefly looked at NRJavaSerial. This is my 
vacation week so the next couple of days are set aside for a good deal of work 
on this.

Original comment by msimm...@gmail.com on 2 Jan 2012 at 8:28

[GoogleCodeExporter]

Just wanted to comment to say I didn't forget about posting the mock layouts. I 
sat down to upload some screen shots and commenting on the functionality helped 
me recognize some problems with the designs. My accompanying comment was 
turning into a list of things I was going to change so I figured It'd be better 
to just make the changes first and post tomorrow. 

Original comment by msimm...@gmail.com on 10 Jan 2012 at 7:00

[GoogleCodeExporter]

This is the current general idea for the Desktop version of the GUI. Obviously 
this is nowhere near the final product but this is my basic plan for how the 
GUI will be set up. Anyone who is familiar with Eclipse may note the 
similarities and that is the basic model. 

Like in Eclipse, the idea is to allow the user to organize a workspace filled 
with projects that store stl files they've already created/downloaded. 
Additionally, as was noted at the last meeting, preparing the slices, g-code, 
etc. to actually send to the printer may be a somewhat time consuming process 
and provided the stl file has not been altered since the last print, we can 
save the user time by saving those files with the project (which of course 
means the drivers need to be written such that this data is available). 

Most likely, the toolbar, once again, similar to Eclipse, will have more 
aesthetically pleasing pictures instead of "Tool 1", "Tool 2". As a side note 
to this, the print and cancel buttons, instead of staying where they currently 
are, may reside exclusively in the toolbar but I figured I'd leave them there 
for now and see if anyone had comments. My original thinking was to make these 
buttons more immediately obvious to the user than other functions as they are 
the main functions. 

Everything else is pretty straight forward, I think. Obviously the File bar 
options will expand to more than just File and Help and there will be text 
labels on elements where appropriate. I'd also like to add an easy way to turn 
off automatic loading of a model preview as this may or may not be needlessly 
time/memory consuming for some users.

So that's the general idea. Comments and questions welcome. I'm still playing 
around with some ideas on the Android version, which will obviously be much 
simpler and should have some sort of preview soon. 

Original comment by msimm...@gmail.com on 11 Jan 2012 at 5:59

Attachments:

• DesktopGui.jpg

[GoogleCodeExporter]

Original comment by msimm...@gmail.com on 28 Jan 2012 at 6:52

• Changed state: Started
• Added labels: Component-UI, Milestone-Design