Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Proposals » Eclipse WindowBuilder
Eclipse WindowBuilder [message #645542] Fri, 17 December 2010 13:59 Go to next message
Mike Milinkovich is currently offline Mike Milinkovich
Messages: 258
Registered: July 2009
Senior Member
The WindowBuilder proposal has been posted. You can find it at http://www.eclipse.org/proposals/tools.windowbuilder/
Re: Eclipse WindowBuilder [message #646248 is a reply to message #645542] Wed, 22 December 2010 16:34 Go to previous messageGo to next message
David Williams is currently offline David Williams
Messages: 176
Registered: July 2009
Senior Member
> The WindowBuilder proposal has been posted. You can find it at
> http://www.eclipse.org/proposals/tools.windowbuilder/

Great proposal, and will make a nice addition to Eclipse.

A couple of questions/suggestions came to mind as I read it.

What namespace will you use? I assume (or, hope!) you plan to move to
"org.eclipse...." packages, but thought I'd ask explicitly since this
code has existed outside of Eclipse (as has been true for many
contributions, which all moved to "org.eclipse...").

Similarly, I'd assume you use other Eclipse frameworks/code "as is" ...
and no "patched" versions of existing bundles or features with special
customizations? I ask partially just since my intuition is that "windows
building" and "reverse engineering" would be some areas that might
require some special hooks into SWT or JDT ... so, just thought I'd ask
explicitly.

You talk a lot about the tools from an end-user point of view. It would
improve the proposal a little (IMHO) to include a little more
description of how adopters might be able to extend your tools ... what
kind of APIs or extension points you provide. I'm not asking for deep
technical details ... just a few sentences on the general nature of the
extensibility ... for example, would/could adopters provide subclasses
of your editors and wizards? Are there hooks to provide custom widgets?
Etc. My main interest is for you to confirm or state the general Eclipse
mission of "providing extensible frameworks and exemplary tools", and
you currently have the "exemplary tools" part covered well. I'm sure
you do plan to include extensibility ... just thought the proposal might
be a little better with some words around that.

Thanks,
Re: Eclipse WindowBuilder [message #647190 is a reply to message #646248] Tue, 04 January 2011 17:23 Go to previous messageGo to next message
Eric Clayberg is currently offline Eric Clayberg
Messages: 832
Registered: July 2009
Location: Boston, MA
Senior Member
David Williams
What namespace will you use?

All of it is moving to "org.eclipse.wb.*".

David Williams
Similarly, I'd assume you use other Eclipse frameworks/code "as is" ...

Yes.

While we don't ship a modified version of the JDT, we do have a JDT fragment that is used to get better access to the JDT AST model.

David Williams
what kind of APIs or extension points you provide.

There are several dozen extension points in the core framework and tools. There are extension poins for adding new widgets, layout managers, NLS patterns, property types & editors, code formatting patterns, databinding patterns, custom class loaders, expression evaluators, additional editor tabs, parsers, branding, Swing L&Fs, and many, many more.
Re: Eclipse WindowBuilder [message #647193 is a reply to message #647190] Tue, 04 January 2011 17:35 Go to previous messageGo to next message
David Williams is currently offline David Williams
Messages: 176
Registered: July 2009
Senior Member
> ... and
> many, many more.

Sounds great. Thanks.
Re: Eclipse WindowBuilder [message #653872 is a reply to message #647190] Fri, 11 February 2011 11:11 Go to previous messageGo to next message
Werner Keil is currently offline Werner Keil
Messages: 1081
Registered: July 2009
Senior Member
Eric/all,

"WB" does seem a little short. I had similar API design discussions e.g. in
various JSR proposals at JCP.org.
Where initial ultra-brief attempts like "javax.cp" ended up as
"javax.constraints" or "javax.tp" as "javax.trustedprogramming".

Considering the nearly as short "SWT" already exists at Eclipse, I think
people could more easily live with it than if it was "java.wb", "javax.wb"
or "orb.wb" ;-)

Regards,
Werner Keil
Re: Eclipse WindowBuilder [message #653875 is a reply to message #653872] Fri, 11 February 2011 11:41 Go to previous messageGo to next message
Eric Clayberg is currently offline Eric Clayberg
Messages: 832
Registered: July 2009
Location: Boston, MA
Senior Member
WindowBuilder has been frequently referred to as just "WB" for many years now, so I think that abbreviation is well known. Looking at my Eclipse /plugins directory, it seems to me that short names like this are much more common than long ones...jdt, pde, wst, swt, rcp, jst, ltk, emf, ecf, etc.

In any case, the namespace conversion is already done and the code has been submitted to Eclipse.org for review.

-Eric
Re: Eclipse WindowBuilder [message #654280 is a reply to message #653875] Mon, 14 February 2011 16:07 Go to previous message
Werner Keil is currently offline Werner Keil
Messages: 1081
Registered: July 2009
Senior Member
Although it's a 4 digit acronym, "UOMo" is also an abbreviation inspired by
e.g. OOo once used for OpenOffice.org, or OSGi, another 4 digit acronym well
known at Eclipse ;-)

So as long as there is nothing that would be too similar like wbx or awb
(both made up), I don't see a problem.

Werner
Previous Topic:Do you have any interest in a opensource feature to preconfigure distributions
Next Topic:Eclipse Runtime Analysis Tools
Goto Forum:
  


Current Time: Thu Apr 24 14:57:25 EDT 2014

Powered by FUDForum. Page generated in 0.09752 seconds