🚀 go-pugleaf

Greg Hamer wrote:
> You used the wrong wizard. If you use the override Methods wizard, (just
> press OK, an obscure thing to do since it is asking you to choose a method
> and none of the abstract methods show up in the list) it will generate stub
> methods for all the abstract methods that need to be implemented. 

This worked just fine, thanks!  I have used the new bean wizard as you
have suggested in the past.  I have been exploring several different
ways to make working with the models behind the swing components a
little easier, even expanding on the functionality of the model in
places.  In some cases, I am just trying to explain how MVC works and
how to develop GUI in Java with Swing by showing how it all works behind
the scenes so to speak.

To perform some tasks, accessing the model directly becomes necessary. 
Looking for methods to expose the properties and events of the models,
writing document listeners, and perhaps building on the default models
attributes and methods to create a class of Super Model JavaBeans
(similar to dataexpress, but not database centric) is the goal here. 
Accessing the model's api through the gui's (painter) interface is not
always the best way to go about it.

> We intend to add a feature so that any class (already on the classpath) can
> specified and then dropped into the designer without first adding it to the
> palette or adding to the code by hand. Then you could select jTable1 and set
> the model from the inspector to the model that you dropped from the
> designer. Does this sound ok?
 
Could you provide a screen print of just how this will look?  ;)  

It sounds as if you are talking about creating a _real_ palette.  Like
any other artist's palette, what colors one squeezes out of the tubes of
paint and mixes up will depend on the subject matter being painted. 
Giving developers a easier mechanism to custom build their design
palette options for each project they may be working on rather than
giving every developer in the world the same deluxe box of crayola
crayons for every project they could possibly create.

Would this mechanism be in some way related to the libraries?  Depending
on which libraries a project had the available options for the custom
designer palette would change.  Some libraries would have the option
selected "add to design palette" where others may not.  What will happen
mid way through a project when a developer decides to add a new library
to the project or switch a library on?  How will JBuilder handle the
loading and unloading of objects that are being created in the current
project?  Currently if you are developing JavaBeans and are placing the
JavaBeans on the palette, recompiling just does not cut it. Sometimes
you have to shut down the just the project or sometimes all of JBuilder
before the palette is updated.

Thanks for the post!
-Geoff