RE: [Visualswing-developers] New proposal to feature list

[Scott C. <sc...@mi...>]

Timo said -


> I was wondering might it be possible to use visual swing like 
> "plugin" in another software. So, there should not be necessary need
to 
> build another GUI builder.

> To be honest, for my personally it would be nice if visual swing can
be
> implemented as "Java Bean" or so that it can be added  e.g. to JPanel
(I
> mean that visual swing is e.g. derived from JComponent and can be
added   > e.g. to the JPanel). It should be also possible to "start"
visual swing 
> from the main-method like any other normal stand-alone java
application as > planned earlier.

Other than IDE plugin, what other sort of application would you imagine
VisualSwing be embedded into?

I think the possibility of making visual swing into an IDE plugin is not
a bad idea (and has been mentioned by several others in earlier
postings); it would keep us from having to author a text editor for
example, if we were a plugin to something that already contained a text
editor.  But that means that we must tie ourselves to the development of
that other product.  If we do decide to become a plugin, I think we
should stick to Eclipse, JEdit, etc. - namely something open source with
a fairly stable API.

Timo said [regarding layouts...]

> But, probably this is too far compared to the original ideas. 

Do the original designers of this project have an opinion on supporting
layout managers in the project?  Because I agree with Timo, I think
including layouts is critical to any GUI design tool for Java.  I also
think that most developers familiar with Swing would find the project
lacking if it didn't support them (even if it wasn't the default
behavior).

Now that we have a list of possible features, can we come to any
agreement on what should go in a first release for the project - so that
some more thought might be put into design?

Scott Corley