Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » Editor support ported

Thu, 14 June 2007 23:05

Eclipse User

I just spent the day doing an initial port of editor functionality.
Most of the work was copying over classes from the 3.3RC4 source base
and cleaning up compile errors. Anyways, I have it to a point where my
once-an-RCP app is displaying its custom editors (the reason for my
hasty port.) More work still needs to be done (like allowing the
closing of editors :)

Is there any interest in this? I'd guess that the code could be checked
in and the extension point simply disabled to prevent the code from
running. I'm new here so I'm asking what I should do with it.

-Aaron

Re: Editor support ported [message #33524 is a reply to message #33490]

Fri, 15 June 2007 04:28

Eclipse User

Originally posted by: b.muskalla.gmx.net

Hi Aaron,

that's great! I think the best way to handle this case would be to open
a feature request for it and attach a patch against current HEAD. But be
patient because we have many other things to do at the moment and need
some time to review the patch.

Cheers and thanks for your work
Benny

Aaron Siri wrote:
> I just spent the day doing an initial port of editor functionality. Most
> of the work was copying over classes from the 3.3RC4 source base and
> cleaning up compile errors. Anyways, I have it to a point where my
> once-an-RCP app is displaying its custom editors (the reason for my
> hasty port.) More work still needs to be done (like allowing the
> closing of editors :)
>
> Is there any interest in this? I'd guess that the code could be checked
> in and the extension point simply disabled to prevent the code from
> running. I'm new here so I'm asking what I should do with it.
>
> -Aaron

Re: Editor support ported [message #33951 is a reply to message #33524]

Mon, 18 June 2007 11:26

Eclipse User

Is submitting a feature request the same as submitting a bug via
bugzilla? I wan't to follow the correct procedure for this.

-Aaron

Benjamin Muskalla wrote:
> Hi Aaron,
>
> that's great! I think the best way to handle this case would be to open
> a feature request for it and attach a patch against current HEAD. But be
> patient because we have many other things to do at the moment and need
> some time to review the patch.
>
> Cheers and thanks for your work
> Benny
>
> Aaron Siri wrote:
>> I just spent the day doing an initial port of editor functionality.
>> Most of the work was copying over classes from the 3.3RC4 source base
>> and cleaning up compile errors. Anyways, I have it to a point where
>> my once-an-RCP app is displaying its custom editors (the reason for my
>> hasty port.) More work still needs to be done (like allowing the
>> closing of editors :)
>>
>> Is there any interest in this? I'd guess that the code could be
>> checked in and the extension point simply disabled to prevent the code
>> from running. I'm new here so I'm asking what I should do with it.
>>
>> -Aaron

Re: Editor support ported [message #33971 is a reply to message #33951]

Mon, 18 June 2007 11:35

Eclipse User

Same procedure :) Just change the severity field to enhancement and use
workbench as component.

Greets
Benny

Aaron Siri wrote:
> Is submitting a feature request the same as submitting a bug via
> bugzilla? I wan't to follow the correct procedure for this.
>
> -Aaron
>
> Benjamin Muskalla wrote:
>> Hi Aaron,
>>
>> that's great! I think the best way to handle this case would be to
>> open a feature request for it and attach a patch against current HEAD.
>> But be patient because we have many other things to do at the moment
>> and need some time to review the patch.
>>
>> Cheers and thanks for your work
>> Benny
>>
>> Aaron Siri wrote:
>>> I just spent the day doing an initial port of editor functionality.
>>> Most of the work was copying over classes from the 3.3RC4 source base
>>> and cleaning up compile errors. Anyways, I have it to a point where
>>> my once-an-RCP app is displaying its custom editors (the reason for
>>> my hasty port.) More work still needs to be done (like allowing the
>>> closing of editors :)
>>>
>>> Is there any interest in this? I'd guess that the code could be
>>> checked in and the extension point simply disabled to prevent the
>>> code from running. I'm new here so I'm asking what I should do with it.
>>>
>>> -Aaron

Re: Editor support ported [message #34036 is a reply to message #33971]

Mon, 18 June 2007 11:48

Eclipse User

Just submitted it. Bug 193131 :)

-Aaron

Benjamin Muskalla wrote:
> Same procedure :) Just change the severity field to enhancement and use
> workbench as component.
>
> Greets
> Benny
>
> Aaron Siri wrote:
>> Is submitting a feature request the same as submitting a bug via
>> bugzilla? I wan't to follow the correct procedure for this.
>>
>> -Aaron
>>
>> Benjamin Muskalla wrote:
>>> Hi Aaron,
>>>
>>> that's great! I think the best way to handle this case would be to
>>> open a feature request for it and attach a patch against current
>>> HEAD. But be patient because we have many other things to do at the
>>> moment and need some time to review the patch.
>>>
>>> Cheers and thanks for your work
>>> Benny
>>>
>>> Aaron Siri wrote:
>>>> I just spent the day doing an initial port of editor functionality.
>>>> Most of the work was copying over classes from the 3.3RC4 source
>>>> base and cleaning up compile errors. Anyways, I have it to a point
>>>> where my once-an-RCP app is displaying its custom editors (the
>>>> reason for my hasty port.) More work still needs to be done (like
>>>> allowing the closing of editors :)
>>>>
>>>> Is there any interest in this? I'd guess that the code could be
>>>> checked in and the extension point simply disabled to prevent the
>>>> code from running. I'm new here so I'm asking what I should do with
>>>> it.
>>>>
>>>> -Aaron

Previous Topic:	Handling bundle lifecycle?
Next Topic:	New widget

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Oct 20 05:53:49 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter