Khalid A. Mughal wrote:Theory and Practice
As a guest author this week, maybe I can pose a couple of questions (it will turn out they are quite a few) in this forum.
I am very much interested in views on the following observation made by some of the readers.
People can pass the Programmer Certification exam without having written any code.
Is this what the present Programmer Certification exam encouraging?
Emphasizing theory and no practice?
Should the exam be changed?
Do employers know or care that they are getting "theoretical" programmers?
In a similar vain, one could ask the following questions:
Would you feel safe if people, who had only read the driving manual and never driven a real car, were unleased onto the unsuspecting rush-hour down-town traffic?
Would you vote for a sheriff that had practiced horse-riding only on a rocking horse?
(I know at least which horse to bet on.)
[Disclaimer: No innuendos to the sheriffs that go galloping on this site.]
What do you think?
Cheers.
-- khalid
Ulf Dittmer wrote:
The main use for Java GUIs at this point is probably specialized in-house GUIs, for which it's hard to gauge how wide-spread thy are (somewhat similar to the niche Motif used to inhabit). Those would generally use some network technology to access server-side resources, so Swing would be used alongside JAX-RS, JAX-WS, sockets, RMI, EJB etc. If for some reason companies want to build a desktop app instead of a web app for some of their systems, there's value in using the same programming language.
Jeanne Boyarsky wrote:
Pamela Hendersen wrote:So why does Java even have swing in the first place ? Only so that java developers can have something besides the console to control their programs ? Looks like Java itself was meant to be an ONLY back-end language.
Three to eight years ago, the financial industry was writing Swing UIs for the traders. I don't know if they still do.
Steve Myers wrote:MigLayout's is pretty popular, here's where I heard of it - I have had no issues with it so far. Link also has quite a bit of discussion on layout managers in general.
Steve Luke wrote:The first thing to do is read The Swing Trail in the Java tutorials, or a Swing book. There are a lot of components, and you should become familiar with them, or at least comfortable in your ability to discover them.
Of particular note are the Layout Managers. Being comfortable with your options here makes building the GUI much easier - you have to learn to pick the correct layout for what you want to display, rather than using one or two you know about and trying to force them to work in all situations. What I do when laying out GUIs is to try to consider different portions of the layout independently - I create different panels and initially different windows for each layout portion, until I get it right. Then, when I have all the parts correct independently, I take the panels where each is laid out and combine them into the final layout. That helps me from trying to make everything fit into one super-layout control which tends to be hard to put together and modify. And if you keep the independent layouts in different classes/objects, it can make it easier to re-use the same layouts in different views.