| extend ve [message #23695] |
Tue, 09 March 2004 07:25  |
Eclipse User |
|
|
|
Hello,
is possible to extend the visual editor?
I.E.
I have a gui defined in xml. I will load this xml and put the gui
components in the eclipse visual editor.
Then I will perform some layout changes, but the changes should affect
only the xml and no java classes has to be created/changed.
I need API to put components in the editor, API to get the actual state
of the editor (components&layout info) to perform changes on the xml.
There is docs or javadocs on sdk ve plugin?
thanks,
Luca
|
|
|
|
|
|
|
| Re: extend ve [message #25624 is a reply to message #25505] |
Fri, 12 March 2004 10:41  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Looking at this, the model is not a java model, so anything above the
CDE level is not really appropriate. It would add unnecessary complexity
trying to force-fit your model into the "java" model.
The advantage of the CDE level, especially when working with EMF model,
is that it allows for extensibility. Others can contribute. What you do
is decorate the EMF metamodel of your model with annotations which
describe what property editors, GEF edit parts, layout managers, etc
should be used. That way others just contribute there model and code and
the CDE picks these up.
The unfortunate thing is that the CDE is not fully formed yet. And we
barely have our heads above the water (this is a small group of only
5-10 workers) trying to get the SWT and java VE fleshed out and working
at a production level.
There is an examples download available as a separate download on the
download page, but it's actually a lame example. I'm not blaming anybody
else, I wrote it. :-)
--
Thanks, Rich Kulp
|
|
|
| Re: extend ve [message #25902 is a reply to message #25624] |
Tue, 16 March 2004 06:03 |
| Eclipse User |
|
|
|
Hello,
Rich Kulp wrote:
> Looking at this, the model is not a java model, so anything above the
> CDE level is not really appropriate. It would add unnecessary complexity
> trying to force-fit your model into the "java" model.
>
> The advantage of the CDE level, especially when working with EMF model,
> is that it allows for extensibility. Others can contribute. What you do
> is decorate the EMF metamodel of your model with annotations which
> describe what property editors, GEF edit parts, layout managers, etc
> should be used. That way others just contribute there model and code and
> the CDE picks these up.
thanks we wil try it.
>
> The unfortunate thing is that the CDE is not fully formed yet. And we
> barely have our heads above the water (this is a small group of only
> 5-10 workers) trying to get the SWT and java VE fleshed out and working
> at a production level.
>
> There is an examples download available as a separate download on the
> download page, but it's actually a lame example. I'm not blaming anybody
> else, I wrote it. :-)
>
Sorry but I don't find examlples and VE-SDK on the ve download page:
http://download.eclipse.org/tools/ve/downloads/index.php
bye,
Luca
|
|
|
|
| Re: extend ve [message #25984 is a reply to message #25902] |
Tue, 16 March 2004 11:53 |
| Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
click on one of the builds, like "I20040226", and a page will come up
for the particular build with the SDK and examples. you probably want a
stable build or integration build, not a nightly build.
norwood sisson
Luca Di Stefano wrote:
>
> Hello,
>
> Rich Kulp wrote:
>
>> Looking at this, the model is not a java model, so anything above the
>> CDE level is not really appropriate. It would add unnecessary
>> complexity trying to force-fit your model into the "java" model.
>>
>> The advantage of the CDE level, especially when working with EMF
>> model, is that it allows for extensibility. Others can contribute.
>> What you do is decorate the EMF metamodel of your model with
>> annotations which describe what property editors, GEF edit parts,
>> layout managers, etc should be used. That way others just contribute
>> there model and code and the CDE picks these up.
>
>
> thanks we wil try it.
>
>>
>> The unfortunate thing is that the CDE is not fully formed yet. And we
>> barely have our heads above the water (this is a small group of only
>> 5-10 workers) trying to get the SWT and java VE fleshed out and
>> working at a production level.
>>
>> There is an examples download available as a separate download on the
>> download page, but it's actually a lame example. I'm not blaming
>> anybody else, I wrote it. :-)
>>
>
> Sorry but I don't find examlples and VE-SDK on the ve download page:
> http://download.eclipse.org/tools/ve/downloads/index.php
>
> bye,
>
> Luca
|
|
|
| Re: extend ve [message #26067 is a reply to message #25943] |
Tue, 16 March 2004 16:31 |
| Eclipse User |
|
|
|
Rich Kulp wrote:
> You need to go one more level down on the download page. Each driver has
> the examples built and available from it.
>
>
OOPS!
sorry I'm fused ... :-))
thanks,
Luca
|
|
|
| Re: extend ve [message #583884 is a reply to message #23695] |
Tue, 09 March 2004 11:04 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
That is the intention of the VE, however we only really have good
support for the java ve portion. AS we go forward we intent to increase
the general support.
If your components are non-java components then all of the support is in
the CDE plugin. The ve examples download has some rudimentary examples.
If your model can be converted from xml to EMF then the support is much
stronger because we use EMF to model the java ve and so we've done a lot
there.
However since we are still in development we don't have any docs.
--
Thanks, Rich Kulp
|
|
|
| Re: extend ve [message #584032 is a reply to message #23825] |
Wed, 10 March 2004 03:00 |
| Eclipse User |
|
|
|
Thanks for the quick answer!
Rich Kulp wrote:
> That is the intention of the VE, however we only really have good
> support for the java ve portion. AS we go forward we intent to increase
> the general support.
>
> If your components are non-java components then all of the support is in
> the CDE plugin.
What do you mean about component? You mean the visual components that
are shown in visual panel or the edited java file?
Our visual components are java but not directly swing (they are proxy to
swing), but in case I can directly use swing components if you think is
better.
Our first problem is put the components in the visual panel editing
(generating) an xml instead a java source.
I should write an xml parser that will be activated when an xml file is
opened in the eclipse workspace. This step can be simple and is well
documented.
Then I need API to open visual panel, and API to put the from xml parsed
visual components in the visual panel.
> The ve examples download has some rudimentary examples.
where I can find those examples? I have searched in ve download page but
not found.
> If your model can be converted from xml to EMF then the support is much
> stronger because we use EMF to model the java ve and so we've done a lot
> there.
>
Thanks I will see if and how our xml can be converted in EMF.
> However since we are still in development we don't have any docs.
>
>
>
It is very important for us to clarify if we are able to develop on top
of VEP or not.
thanks again
Luca
|
|
|
| Re: extend ve [message #584094 is a reply to message #24224] |
Wed, 10 March 2004 09:15 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
It is the intent to allow such in the future. but at the moment the
support is not very strong.
What exactly does you xml represent. Is it java classes with property
settings that get hooked together or is it something else. A quick
little snippet of xml code and what it means would be helpful for
answering the questions.
--
Thanks, Rich Kulp
|
|
|
| Re: extend ve [message #584412 is a reply to message #24390] |
Fri, 12 March 2004 09:04 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------010200080207090208070405
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Rich Kulp wrote:
> It is the intent to allow such in the future. but at the moment the
> support is not very strong.
>
> What exactly does you xml represent. Is it java classes with property
> settings that get hooked together or is it something else.
The structure is very complex.
It consist in
1) definition of the business pane for the generation of controllers and
models
2) definition the presentation that contains the visual components that
are bound with the generated models
3) a layout that defines how the presentation is shown
Eeach business pane have a presentation
Each presentation can have 0 or more layouts
A business pane can contain other business panes
The presentation contain the visual components that at runtime are
matherialized with swing components.
The layout is a gridbaglayout.
> A quick
> little snippet of xml code and what it means would be helpful for
> answering the questions.
>
In the sample I omitted the first definition
In this xml they are associations between tags and navigations.
I think the sample can be very complicated: please don't anger :-)) !!
It could be very helpfull to know API to open visual workbench, put in
swing components and get out the layout informations (maybe through
callbacks), and then try & catch !
thanks again,
Luca
--------------010200080207090208070405
Content-Type: text/xml;
name="sample-tasks.xml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="sample-tasks.xml"
<?xml version='1.0' encoding='us-ascii' ?>
<!DOCTYPE Component SYSTEM 'file:./Etna.DTD'>
<Component>
<!-- Start Presentation
here are defined business panes presentation with input/output components
-->
<PPane id="Search1">
<PPanePresentation>
<PLabel id="Search1.InputLabel1" label="@Input1"/>
<PTextField id="Search1.InputTextField1" length="10">
</PTextField>
<PButton id="Search1.SearchAction1" label="@Search">
</PButton>
<PTable id="Search1.Result" height="5">
<PTableColumn id="Result.Column1" header="@Header1" tooltip="@Header1Tooltip">
</PTableColumn>
<PTableColumn id="Result.Column2" header="@Header2" tooltip="@Header2Tooltip">
</PTableColumn>
</PTable>
</PPanePresentation>
</PPane>
<PPane id="Search2">
<PPanePresentation>
<PLabel id="Search2.SelectLabel" label="@Selected"/>
<PTextField id="Search2.SelectTextField" length="10">
</PTextField>
<PButton id="Search2.SearchAction1" label="@Search">
</PButton>
</PPanePresentation>
</PPane>
<PPane id="Search3">
<PSubPane id="Search3.Search1" >
<Association>
<PPane id="Search1"/>
</Association>
</PSubPane>
<PSubPane id="Search3.Search2" >
<Association>
<PPane id="Search2"/>
</Association>
</PSubPane>
</PPane>
<PPane id="Search3">
<PPanePresentation>
</PPanePresentation>
</PPane>
<!-- End Presentation -->
<!-- Start Layout
here are layouts of tasks (dialogs).
each layout can refer to component defined in in presentation
-->
<PPane id="Search2">
<PPanePresentation>
<Association>
<PDomainLayout id="Search2.Layout"/>
</Association>
</PPanePresentation>
</PPane>
<PDomainLayout id="Search2.Layout">
<PLayoutContainer id="Search2" columns="2" align="1" rows="5" title="@Search">
<PLayoutConstraint id="Search2.SelectLabel" column="0" row="0">
<Association>
<PPane id="Search2">
<PPanePresentation>
<PLabel id="Search2.SelectLabel"/></PPanePresentation>
</PPane>
</Association>
</PLayoutConstraint>
<PLayoutConstraint id="Search2.SelectTextField" column="1" row="0">
<Association>
<PPane id="Search2">
<PPanePresentation>
<PTextField id="Search2.SelectTextField"/>
</PPanePresentation>
</PPane>
</Association>
</PLayoutConstraint>
<PLayoutConstraint id="Search2.SearchAction1" column="1" row="1">
<Association>
<PPane id="Search2">
<PPanePresentation>
<PButton id="Search2.SearchAction1"/>
</PPanePresentation>
</PPane>
</Association>
</PLayoutConstraint>
</PLayoutContainer>
</PDomainLayout>
<PPane id="Search1">
<PPanePresentation>
<Association>
<PDomainLayout id="Search1.Layout"/>
</Association>
</PPanePresentation>
</PPane>
<PDomainLayout id="Search1.Layout">
<PLayoutContainer id="Search1" columns="2" rows="7" title="@Search1">
<PLayoutConstraint id="Search1.InputLabel1" column="0" row="0">
<Association><PPane id="Search1"><PPanePresentation><PLabel id="Search1.InputLabel1"/></PPanePresentation></PPane></Association >
</PLayoutConstraint>
<PLayoutConstraint id="Search1.InputTextField1" align="7" column="1" row="0">
<Association><PPane id="Search1"><PPanePresentation><PTextField id="Search1.InputTextField1"/></PPanePresentation></PPane ></Association>
</PLayoutConstraint>
<PLayoutConstraint id="Search1.Search1" column="0" row="0">
<Association>
<PPane id="Search1">
<PPanePresentation>
<PButton id="Search1.SearchAction1"/>
</PPanePresentation>
</PPane>
</Association>
</PLayoutConstraint>
</PLayoutContainer>
</PDomainLayout>
<PPane id="Search3">
<PPanePresentation>
<Association>
<PDomainLayout id="Search3.Layout"/>
</Association>
</PPanePresentation>
</PPane>
<PDomainLayout id="Search3.Layout">
<PLayoutContainer id="Search1" columns="2" rows="7" title="@Search3">
<PLayoutConstraint id="Search1.InputLabel1" instancename="Search3.Search1" column="0" row="0">
<Association>
<PPane id="Search1">
<PPanePresentation>
<PLabel id="Search1.InputLabel1"/>
</PPanePresentation>
</PPane>
</Association>
</PLayoutConstraint>
<PLayoutConstraint id="Search2.SelectTextField" instancename="Search3.Search2" column="0" row="0">
<Association>
<PPane id="Search2">
<PPanePresentation>
<PTextField id="Search2.SelectTextField"/>
</PPanePresentation>
</PPane>
</Association>
</PLayoutConstraint>
</PLayoutContainer>
</PDomainLayout>
<!-- End Layout -->
</Component>
--------------010200080207090208070405--
|
|
|
| Re: extend ve [message #584450 is a reply to message #25505] |
Fri, 12 March 2004 10:41 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Looking at this, the model is not a java model, so anything above the
CDE level is not really appropriate. It would add unnecessary complexity
trying to force-fit your model into the "java" model.
The advantage of the CDE level, especially when working with EMF model,
is that it allows for extensibility. Others can contribute. What you do
is decorate the EMF metamodel of your model with annotations which
describe what property editors, GEF edit parts, layout managers, etc
should be used. That way others just contribute there model and code and
the CDE picks these up.
The unfortunate thing is that the CDE is not fully formed yet. And we
barely have our heads above the water (this is a small group of only
5-10 workers) trying to get the SWT and java VE fleshed out and working
at a production level.
There is an examples download available as a separate download on the
download page, but it's actually a lame example. I'm not blaming anybody
else, I wrote it. :-)
--
Thanks, Rich Kulp
|
|
|
| Re: extend ve [message #584641 is a reply to message #25624] |
Tue, 16 March 2004 06:03 |
| Eclipse User |
|
|
|
Hello,
Rich Kulp wrote:
> Looking at this, the model is not a java model, so anything above the
> CDE level is not really appropriate. It would add unnecessary complexity
> trying to force-fit your model into the "java" model.
>
> The advantage of the CDE level, especially when working with EMF model,
> is that it allows for extensibility. Others can contribute. What you do
> is decorate the EMF metamodel of your model with annotations which
> describe what property editors, GEF edit parts, layout managers, etc
> should be used. That way others just contribute there model and code and
> the CDE picks these up.
thanks we wil try it.
>
> The unfortunate thing is that the CDE is not fully formed yet. And we
> barely have our heads above the water (this is a small group of only
> 5-10 workers) trying to get the SWT and java VE fleshed out and working
> at a production level.
>
> There is an examples download available as a separate download on the
> download page, but it's actually a lame example. I'm not blaming anybody
> else, I wrote it. :-)
>
Sorry but I don't find examlples and VE-SDK on the ve download page:
http://download.eclipse.org/tools/ve/downloads/index.php
bye,
Luca
|
|
|
| Re: extend ve [message #584648 is a reply to message #25902] |
Tue, 16 March 2004 09:33 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
You need to go one more level down on the download page. Each driver has
the examples built and available from it.
--
Thanks, Rich Kulp
|
|
|
| Re: extend ve [message #584664 is a reply to message #25902] |
Tue, 16 March 2004 11:53 |
| Eclipse User |
|
|
|
click on one of the builds, like "I20040226", and a page will come up
for the particular build with the SDK and examples. you probably want a
stable build or integration build, not a nightly build.
norwood sisson
Luca Di Stefano wrote:
>
> Hello,
>
> Rich Kulp wrote:
>
>> Looking at this, the model is not a java model, so anything above the
>> CDE level is not really appropriate. It would add unnecessary
>> complexity trying to force-fit your model into the "java" model.
>>
>> The advantage of the CDE level, especially when working with EMF
>> model, is that it allows for extensibility. Others can contribute.
>> What you do is decorate the EMF metamodel of your model with
>> annotations which describe what property editors, GEF edit parts,
>> layout managers, etc should be used. That way others just contribute
>> there model and code and the CDE picks these up.
>
>
> thanks we wil try it.
>
>>
>> The unfortunate thing is that the CDE is not fully formed yet. And we
>> barely have our heads above the water (this is a small group of only
>> 5-10 workers) trying to get the SWT and java VE fleshed out and
>> working at a production level.
>>
>> There is an examples download available as a separate download on the
>> download page, but it's actually a lame example. I'm not blaming
>> anybody else, I wrote it. :-)
>>
>
> Sorry but I don't find examlples and VE-SDK on the ve download page:
> http://download.eclipse.org/tools/ve/downloads/index.php
>
> bye,
>
> Luca
|
|
|
| Re: extend ve [message #584692 is a reply to message #25943] |
Tue, 16 March 2004 16:31 |
| Eclipse User |
|
|
|
Rich Kulp wrote:
> You need to go one more level down on the download page. Each driver has
> the examples built and available from it.
>
>
OOPS!
sorry I'm fused ... :-))
thanks,
Luca
|
|
|
Powered by
FUDForum. Page generated in 0.08307 seconds
Home