| Why I can reference source code form a Property Editor class? [message #15973] |
Wed, 21 January 2004 09:43  |
Eclipse User |
|
|
|
Hi!
I've a JavaBean that uses a PropertyEditor class to show and manipulate
some properties. I need show the code of the class that are being edited
with VE in this property editor.
Example: I've a TFrame (extends from JFrame) that contains a TPanel (a
simple class that extends form JPanel). This TPanel has a property that
open a Property Editor. Then I must show the source code of the TFrame
(same code that I'm seeing in the editor) in this Property Editor.
Can I do this?
Many thanks.
|
|
|
| Re: Why I can reference source code form a Property Editor class? [message #16063 is a reply to message #15973] |
Wed, 21 January 2004 14:01  |
| Eclipse User |
|
|
|
Hi David,
> I've a JavaBean that uses a PropertyEditor class to show and manipulate
> some properties. I need show the code of the class that are being edited
> with VE in this property editor.
No easy way to do this at the moment. To do this would require a plugin and
having a cellEditor associated with the Java bean's property that was used
by the VE instead of the java.beans.PropertyDescriptor. We do this for a
number of property values and types already so there is an internal API,
however this seems to be a popular question at the moment for people to want
documentation of and to have the extension made public.
What I'd like to ask is if you could subscribe to the ve-dev mailing list
where we should possibly discuss this as one of the first extensions to be
documented. Dave Orme (the VE project lead) is very keen to see more VE
APIs opened up, and the mailing list allows all the developers to contribute
their ideas so we can begin by describing the current (internal - not public
API way of doing this), blue sky how it would work in a perfect world, and
then try and settle on a satisfactory API that gets published. Having this
kind of discussion on the mailing list is just better than the newsgroup so
we can track the dialog and make sure VE design decisions are recorded
centrally and agreed on according to the VE project charter.
Best regards,
Joe Winchester
|
|
|
| Re: Why I can reference source code form a Property Editor class? [message #578906 is a reply to message #15973] |
Wed, 21 January 2004 14:01 |
| Eclipse User |
|
|
|
Hi David,
> I've a JavaBean that uses a PropertyEditor class to show and manipulate
> some properties. I need show the code of the class that are being edited
> with VE in this property editor.
No easy way to do this at the moment. To do this would require a plugin and
having a cellEditor associated with the Java bean's property that was used
by the VE instead of the java.beans.PropertyDescriptor. We do this for a
number of property values and types already so there is an internal API,
however this seems to be a popular question at the moment for people to want
documentation of and to have the extension made public.
What I'd like to ask is if you could subscribe to the ve-dev mailing list
where we should possibly discuss this as one of the first extensions to be
documented. Dave Orme (the VE project lead) is very keen to see more VE
APIs opened up, and the mailing list allows all the developers to contribute
their ideas so we can begin by describing the current (internal - not public
API way of doing this), blue sky how it would work in a perfect world, and
then try and settle on a satisfactory API that gets published. Having this
kind of discussion on the mailing list is just better than the newsgroup so
we can track the dialog and make sure VE design decisions are recorded
centrally and agreed on according to the VE project charter.
Best regards,
Joe Winchester
|
|
|
Powered by
FUDForum. Page generated in 0.02806 seconds
Home