1:41 a.m.
No; I was suggesting to use the existing sheet-tab properties editor
infrastructure of eclipse. If you install the WTP SDK and try opening any
.xsd file, you will see some of the different things that can be done on the
Properties view. Normally it should automatically open up; else you may use
Windows -> Show View -> Properties. Since *ra.xml* needs an editor,
potentially we can extend the existing XML editor and also enhance it for
being able to address any changes made through the xml editor also and be
able to generate get/set as mentioned by Ramesh. So users may decide to
directly change the xml using the xml editor or use the properties view.
Enhancing the XML editor can also get fancy by content-assist,
problem-markers etc. and potentially this can be renamed as a specific
editor, similar to the plugin manifest editor, which knows how to handle
called *plugin.xml*
I am not sure if the current structure of ra.xml is complete; however based
on what I see, some meaningful tab segregations can be done; Ramesh would be
a better person to dictate how he would want to group the sections.
Thanks
Sanjay
On Sun, Oct 25, 2009 at 12:39 AM, Sumanth P K
<sumanth.technical(a)gmail.com>wrote:
Sanjay - Please proceed further with the CDK Contributor plugin. I
shall
start on the sheet-tab properties. From what I understand, we need to create
a tabbed display similar to the one that opens up when we open the
MANIFEST.mf or plugin.xml in the PDE. Physically there is a single file, but
the information is scattered across various tabs.
Is the sheet-tab properties going to be used for configuring the config
properties elements only or is it that we would need to have the support for
all the elements defined in the Connector 1.5 XSD (
http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd)?
Thanks,
Sumanth.
On Sun, Oct 25, 2009 at 4:37 AM, Sanjay Chaudhuri <
email2sanjayc(a)gmail.com> wrote:
> Hi Ramesh,
>
> Sure; shall look into it. No matter what the changes are, since I am
> maintaining a template file for each of the sources with some configurable
> parameters like package-name, etc, which will get substituted based on
> inputs by the user through wizard, I do not anticipate any issues. Also the
> necessary jars in question for classpaths will potentially be published by
> the contributor plugin through an extension point if we land up having
> different jar names probably because of different version numbers that gets
> appended. The plugin I am developing will be flexible as the dependencies
> are mostly loosely coupled except for the template directory structure and
> names as well as the files that gets generated. These are currently
> hard-coded in the program, which can be very well be put on an external
> properties file if we want those to be configurable as well in future.
>
> Yes, the properties editor definitely can be used to satisfy your
> use-cases; the newer sheet-tab properties editor best suits for this. Since
> an editor needs to be attached; we can extend the existing xml editor to
> display the content as is and intercept to provide our properties view with
> all syncs and get/set generated.
>
> I have a sourceforge account; sending it to you through a separate mail.
>
> Thanks
>
> Sanjay
> On Sat, Oct 24, 2009 at 5:22 PM, Ramesh Reddy <rareddy(a)redhat.com>wrote:
>
>> Sure, Thanks. At a minimum take look at the document see how it may
>> affect your stuff. There are some api changes, but you should be good.
>>
>> Eclipse property editor sounds good. Can it be extended for usecase I
>> was talking about?
>>
>> For Source forge, create an account and send me the user-id directly to
>> me separate email.
>>
>> Ramesh..
>>
>>
>>
>
> _______________________________________________
> teiid-dev mailing list
> teiid-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/teiid-dev
>
>