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

[todd r. <tod...@ya...>]

--- Scott Corley <sc...@mi...> wrote:
> 
> 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.

Personally, I'd like to see a standalone IDE, at least
initially.  As I've mentioned before though, I love
Eclipse and fully support building VS as a plugin.  I
agree that limiting the scope would be wise as trying
to make this work for every editor out there will be
impossible.  

If an Eclipse plugin or standalone IDE won't work for
you Timo, try to keep reminding the team to keep
things modular.  That way, you should be able to pull
out major portions to integrate into your other
project. 


> 
> 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?  

To be honest, I don't think it matters.  If anyone
feels strongly one way or the other, let them make a
case for it.  Many of us joined this project because
we wanted to create a free, open source java IDE, but
knew we couldn't make it by ourselves.  With that in
mind, whatever the group as a whole decides, is what
will be supported. 

> 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).


Seems to me the group has spoken - support for layout
managers is in. 

> 
> 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, are you willing to write something up?  Maybe
something we can post?

> 
> Scott Corley
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Visualswing-developers mailing list
> Vis...@li...
>
https://lists.sourceforge.net/lists/listinfo/visualswing-developers


=====
The only "dumb question" is the one you were too afraid to ask.

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com