Re: Choosing standalone tech: SWT / Swing ??
By the way... if i wanted to make it J2EE compliant, ...
Please refrain from top-posting, I find it most confusing.
J2EE is Sun's name for stuff that generally occurs on the
server. A web site generated by Java would use J2EE.
J2SE is Sun's name for 'core and desktop' API's, the
GUI parts include AWT (uses native components) and
Swing (has richer toolset). SWT is another GUI toolkit
A J2EE powered server might put output to a browser,
(AWT) Applet, or a (Swing) JApplet, or an AWT or
Swing based application, or the web started versions
of the same. I am not sure about SWT (shrugs).
A J2SE based GUI to would usually be refered to as a
rich client, and the HTML equivalent, a 'thin client' (as
opposed to a 'poor client' ;).
J2EE is important to understand, but before you attempt
it, you should have a good understanding of (at least) the
non-GUI parts of the J2SE, because in J2EE programming,
you often find yourself importing J2SE classes!
..how should it be ?
... Anybody knows a good tutorial ?.
For the J2SE, I recommend Sun's own 'Java Tutorial'.
It be downloaded or browsed on-line.
My guess is, please correct me if i'm wrong, Swing in the front end
(presentation tier), and Tomcat running logic tier (implemented by me)
and business tier (hibernate).
The big question is... how do you 'glue' Swing and the logic'n
..hmm. Just checking, but you do realise that you
can do all of 'purely desktop' applications *without*
a server at all, right? What is the application?
If you need a server, what do you actually need it for?
What information for the application changes?
Does the app. offer the viewing/editing of information
held in a central location?
Message posted via JavaKB.com