GUI doubt to use with embedded PApplet: AWT or SWING?

cravista

GUI doubt to use with embedded PApplet: AWT or SWING?

in Integration and Hardware • 2 years ago

Hi, i'm starting to make an personal App to manage audio and video controls with
an embedded PApplet in this App;

I have doubts (once i'm only hobbist, not programmer) in which library
use to implement a GUI, pure AWT or SWING? (i have no experience with these two libs)

In PApplet javadoc, we can see that "Swing is a bloated piece of crap",
and I have doubts which the best choice to implement my GUI

Awt can be a better choice than Swing? or it's only a point of view?

Thanks

/////////////////////////
SWT option
////////////////////////

I found this: i think this be useful

http://christian.liljedahl.dk/guides/processing-and-swt-in-eclipse

Replies(5)

PhiLho

Re: GUI doubt to use with embedded PApplet: AWT or SWING?

2 years ago

If you want to have a GUI inside a sketch, you should use one of the GUI libraries, like controlP5 or G4P or Interfacia.

cravista

Re: GUI doubt to use with embedded PApplet: AWT or SWING?

2 years ago

No, I want a separated GUI from processing;
this will be control other things that not in P5 :)

PhiLho

Re: GUI doubt to use with embedded PApplet: AWT or SWING?

2 years ago

Then Swing is the way to go. AWT is old and limited... It is a low level layer over native system controls. Swing is a layer above AWT, not using the controls but recreating them, by drawing them. So it uses Java2D for the graphics, and AWT event system to get user input.
SWT can be used too, but it will be a large library to ship with your application, while AWT/Swing comes with a JRE.
JavaFX can be another option, more modern, but it is still beta...

cravista

Re: GUI doubt to use with embedded PApplet: AWT or SWING?

2 years ago

SWT can be used too, but it will be a large library to ship with your application

You mean, if is suposed, to export my App to a runnable jar?

PhiLho

Re: GUI doubt to use with embedded PApplet: AWT or SWING?

2 years ago

I don't understand your question.
But basically you will make a classical Java application, which can be bundled in a jar with lot of companion jars (the libraries it uses), or in a so called fat jar, bundling all the jars together.

Top Reply