Charles M. wrote:
Hi, well I figured so but my point is that instead of following the
Swing API I was hoping to a perhaps more productive frameworks e.g.
MonkeyBars but I believe that those frameworks require you to layout by
No. Monkeybars was designed to play especially well with compiled Java
Swing code, such as what you can generate using the Netbeans WYSIWYG
editor. I’ve help build quite complex desktop programs with Monkeybars
and making the UI with by-hand Swing code would have been torture.
So long as you follow some basic naming conventions (because of some
dynamic lookups) you are good to go.
You can do the GUI part by hand for Monkeybars if you want.
Sometimes it is is easier to just define the UI using basic Swing and,
say, the MiG layout jar. That was the motivation behind Swingset-NG: to
offer a simple API for basic UI to avoid having to pop open Netbeans or
something just to create an “About” form or something.
The choice is yours either way. Larger programs benefit from using a
GUI editor to generate the Java or .class files to be used with the
Monkeybars controller and model files.
Monkeybars project admin
Neurogami - Avant-garage Research & Development