|
Re: Eclipse WindowBuilder [message #646248 is a reply to message #645542] |
Wed, 22 December 2010 21:34 |
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 22:23 |
Eric Clayberg Messages: 979 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 #653875 is a reply to message #653872] |
Fri, 11 February 2011 16:41 |
Eric Clayberg Messages: 979 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
|
|
|
|
Powered by
FUDForum. Page generated in 0.04064 seconds