| [FAQ] Update General question 1 [message #108538] |
Fri, 30 September 2005 17:51  |
 test
Messages: 51
Registered: July 2009 |
Member |
|
|
I suggest something like this. In a few cases my wording may be awkward, or
i might be slightly incorrect, but it is better than
what is there now. If you would like, you can try to write a better
description that gets across the points I outline below.
1. What is VE?
VE is a platform for running GUI builders in Eclipse. It consists of a set
of standard classes that can be used by GUI builders,
allowing them to be more consistant, as well as easier to develop. It comes
with two example (but fully functioning) GUI builders
for generation of SWT or Swing/JFC GUIs. These example builders generate
Java code. The VE is not limited to GUI builders
for Java. A VE-based GUI builder could be created to design QT, Motif, or
GTK GUI builders that output C code, or a
Tk GUI builder that outputs code for Python *and* for Tcl. An SDK is
available for the creation of new VE-based GUI builders.
---------------
The points I tried to get across: (I feel these points are important because
the nature of VE can be fairly confusing)
VE is not a GUI builder.
VE is a platform that can be used by GUI builders so that the builders
integrate well with Eclipse.
VE is distributed with example VE-based GUI builders, which may be useful
for devlopers using JDT.
VE is not a system for generating GUI builders [upon reading its description
originally, this is what I thought VE was], but rather is a platform used by
GUI builders, and its existance makes it easier to develop GUI builders that
integrate with Eclipse.
VE-based GUI builders can generate code for languages other than Java.
Ideally the question's answer would leave people with the understanding that
VE is the interface that GUI Builders that integrate into Eclipse use. Most
end users need not know that VE does much more than just provide the display
interface used by GUI builders, as that will at least help end users
understand that if they want a GUI builder they want VE and also possibly
annother plugin that contains the desired GUI builder.
|
|
|
| Re: [FAQ] Update General question 1 [message #108949 is a reply to message #108538] |
Tue, 04 October 2005 23:17  |
Joe Winchester
Messages: 496
Registered: July 2009 |
Senior Member |
|
|
Hi test,
Thanks for your note. What the VE is and who its customers are is
something that we are always re-evaluating. The VE has customers who
use it to build production GUIs and want Visual Basic type out of the
box functionality, customers who want to extend it to support custom
JavaBeans or layout managers, XML serialization, or non Java languages.
We try to move the VE forward on all fronts as the key to any project's
success lies in listening to its users and responding to their requests
to features and enhancements. Some of the customers who do the more
advanced VE extension become involved with the VE team on the dev
mailing list where more detail about the APIs can be discussed and in
some situations the VE team engages individuals or companies who wish to
become VE extenders in a 1 on 1 basis to help their projects succeed.
One thing however that we are aware of is that you can't be a jack of
all trades and a master of none. The biggest thing I think the VE has
is that it is open-source and has a growing base of comitters and
contributors. The most rewarding thing for the VE is when there is
sometone who begins with an interest and desire to use the VE, asks
qestions on newsgroups and learns more about the VE internals,
contributes ideas, then begins to maybe extend the VE and contribute
code and hopefully will graduate to commit status. Open-source's
succeed lies in inclusion, and while you're right that the VE needs to
possibly define more rigidly what its different usages are, this will
always be a fluid definition as the project evoles driven by user
requests and the community of comitters who contribute to its core codebase.
Best regards,
Joe Winchester
|
|
|
| Re: [FAQ] Update General question 1 [message #610930 is a reply to message #108538] |
Tue, 04 October 2005 23:17 |
Joe Winchester
Messages: 496
Registered: July 2009 |
Senior Member |
|
|
Hi test,
Thanks for your note. What the VE is and who its customers are is
something that we are always re-evaluating. The VE has customers who
use it to build production GUIs and want Visual Basic type out of the
box functionality, customers who want to extend it to support custom
JavaBeans or layout managers, XML serialization, or non Java languages.
We try to move the VE forward on all fronts as the key to any project's
success lies in listening to its users and responding to their requests
to features and enhancements. Some of the customers who do the more
advanced VE extension become involved with the VE team on the dev
mailing list where more detail about the APIs can be discussed and in
some situations the VE team engages individuals or companies who wish to
become VE extenders in a 1 on 1 basis to help their projects succeed.
One thing however that we are aware of is that you can't be a jack of
all trades and a master of none. The biggest thing I think the VE has
is that it is open-source and has a growing base of comitters and
contributors. The most rewarding thing for the VE is when there is
sometone who begins with an interest and desire to use the VE, asks
qestions on newsgroups and learns more about the VE internals,
contributes ideas, then begins to maybe extend the VE and contribute
code and hopefully will graduate to commit status. Open-source's
succeed lies in inclusion, and while you're right that the VE needs to
possibly define more rigidly what its different usages are, this will
always be a fluid definition as the project evoles driven by user
requests and the community of comitters who contribute to its core codebase.
Best regards,
Joe Winchester
|
|
|
Powered by
FUDForum. Page generated in 0.04054 seconds
] 
Search
Help
Register
Login
Home
