| When will VE API be usable? [message #75193] |
Thu, 16 December 2004 15:45  |
Eclipse User |
|
|
|
Originally posted by: bandrews.nospam_bphnx.com
Hi,
From the VE 1.1 project plan:
"API documentation. Currently, all Visual Editor Project APIs are
internal APIs. We will begin the process of solidifying and documenting
APIs. This work depends on the Platform Performance work, because some
of the performance optimizations we consider may have the effect of
breaking our current (internal) APIs."
As of the current release, is it just the documentation that is missing
for the API, or is there a possibility of the API changing for 1.1? I am
just trying to get a feel for how hard it would be to extend VE to be
something like a JSF builder for example. Without documentation, it will
be difficult, but if the API is a moving target it would be almost
impossible I think. Is it possible for the API to be solid by M1? (Maybe
with some documentation? )
thanks,
Barry
|
|
|
| Re: When will VE API be usable? [message #75242 is a reply to message #75193] |
Fri, 17 December 2004 11:14  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Sorry, but the API will be changing. At the very least pieces of it will
be moved from internal packages to API packages, which will cause
renames. Other pieces of it will be changed entirely as we find better
ways of doing it. Much of it won't change and will stay internal. It
will be done on an as-can-do basis.
However, most of the changes will be JEM and things in the Java VE. The
base VE stuff in cde and propertysheet won't be changing that much. The
basic concepts probably won't change much, though renames as they become
API will occur. And some things will moved down from Java ve to base VE
for all to use. I can't put a limit on the changes for you though. We
want to get things to be API so that they can be counted on, but there
is so much to do, and so little time. :-)
You can use it now, but you should add yourself to the ve mailing list
so that you can be notified of when we are making something API. Or of
any other major changes.
However, if you are doing this for JSF, I wouldn't use anything higher
in the plugin architecture than org.eclipse.ve.Java.core (including
org.eclipse.ve.Java.core itself). These plugins are exclusively for the
Java visual editor. Since JSF is not Java, you would be imposing an
unnecessary restriction on your editor. You would be requiring your
project to be a Java project, and JSF doesn't require that.
--
Thanks,
Rich Kulp
|
|
|
| Re: When will VE API be usable? [message #603955 is a reply to message #75193] |
Fri, 17 December 2004 11:14 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Sorry, but the API will be changing. At the very least pieces of it will
be moved from internal packages to API packages, which will cause
renames. Other pieces of it will be changed entirely as we find better
ways of doing it. Much of it won't change and will stay internal. It
will be done on an as-can-do basis.
However, most of the changes will be JEM and things in the Java VE. The
base VE stuff in cde and propertysheet won't be changing that much. The
basic concepts probably won't change much, though renames as they become
API will occur. And some things will moved down from Java ve to base VE
for all to use. I can't put a limit on the changes for you though. We
want to get things to be API so that they can be counted on, but there
is so much to do, and so little time. :-)
You can use it now, but you should add yourself to the ve mailing list
so that you can be notified of when we are making something API. Or of
any other major changes.
However, if you are doing this for JSF, I wouldn't use anything higher
in the plugin architecture than org.eclipse.ve.Java.core (including
org.eclipse.ve.Java.core itself). These plugins are exclusively for the
Java visual editor. Since JSF is not Java, you would be imposing an
unnecessary restriction on your editor. You would be requiring your
project to be a Java project, and JSF doesn't require that.
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.52188 seconds
Home