Eclipse Community Forums: Remote Application Platform (RAP) » Some questions about RAP limitations

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » Some questions about RAP limitations

Show: Today's Messages :: Show Polls :: Message Navigator

Some questions about RAP limitations [message #67306]

Wed, 26 December 2007 04:51

Boris Stepanov

Messages: 68
Registered: July 2009

Member

Hello,

I have several questions about RAP limitations:

1. What I can use instead of it?
2. When it will be implemented?

These questions apply to the following limitations:

1. StyledText widget.

2. ITextViewer, ISourceViewer, IDocument and other things which using
for text editors.

3. IPropertySource, IPropertySheet, IPropertyDescriptor.

--
Boris Stepanov

Report message to a moderator

Re: Some questions about RAP limitations [message #67426 is a reply to message #67306]

Fri, 28 December 2007 13:28

Benjamin Muskalla

Messages: 237
Registered: July 2009

Senior Member

Hi,

see comments inline

Boris Stepanov wrote:
> Hello,
>
> I have several questions about RAP limitations:
>
> 1. What I can use instead of it?
> 2. When it will be implemented?
>
> These questions apply to the following limitations:
>
> 1. StyledText widget.
1: I think there are several powerful replacements but depends on your
usecase. If you don't care about formatting/etc you should go with the
Text widget + SWT.MULTI. Alternatively you could use the browser widget
to render HTML which is at least for formatting really helpful but only
usable for readonly kind of stuff. An alternative would be to write a
custom widget which integrates one of the famous WYSIWYG editors (eg
FCKEditor) which is only an IFrame with some additionaly style flags and
thus the functionality is provided by the browser.
2: I don't think that StyledText will be implemented soon. But I think
this is a great opportunity for the community to help the RAP team and
contribute something back.
>
> 2. ITextViewer, ISourceViewer, IDocument and other things which using
> for text editors.
1: -
2: I think the everything around the text editor framework could be
easily ported as soon as there is a StyledText widget as the editor
framework heavily relies on it. Having a custom widget with the same api
as the styled text widget it could *maybe* work together. As I never
really looked into the details don't see this as an absolute answer.
>
> 3. IPropertySource, IPropertySheet, IPropertyDescriptor.
Take a look at the "org.eclipse.rap.ui.views" bundle. This is where the
property view lives. It is already usable in RAP. I would need to take
closer look at it to tell what's already implemented and what is not.
Just take a look!

>

Hope I could help you!
Benny

Report message to a moderator

Re: Some questions about RAP limitations [message #67552 is a reply to message #67426]

Sat, 29 December 2007 10:41

Boris Stepanov

Messages: 68
Registered: July 2009

Member

Benjamin,

Thank you very much for your answer. It will help me.

> Hi,
>
> see comments inline
>
> Boris Stepanov wrote:
>> Hello,
>>
>> I have several questions about RAP limitations:
>>
>> 1. What I can use instead of it?
>> 2. When it will be implemented?
>>
>> These questions apply to the following limitations:
>>
>> 1. StyledText widget.
> 1: I think there are several powerful replacements but depends on your
> usecase. If you don't care about formatting/etc you should go with the
> Text widget + SWT.MULTI. Alternatively you could use the browser widget
> to render HTML which is at least for formatting really helpful but only
> usable for readonly kind of stuff. An alternative would be to write a
> custom widget which integrates one of the famous WYSIWYG editors (eg
> FCKEditor) which is only an IFrame with some additionaly style flags and
> thus the functionality is provided by the browser.
> 2: I don't think that StyledText will be implemented soon. But I think
> this is a great opportunity for the community to help the RAP team and
> contribute something back.
>>
>> 2. ITextViewer, ISourceViewer, IDocument and other things which using
>> for text editors.
> 1: -
> 2: I think the everything around the text editor framework could be
> easily ported as soon as there is a StyledText widget as the editor
> framework heavily relies on it. Having a custom widget with the same api
> as the styled text widget it could *maybe* work together. As I never
> really looked into the details don't see this as an absolute answer.
>>
>> 3. IPropertySource, IPropertySheet, IPropertyDescriptor.
> Take a look at the "org.eclipse.rap.ui.views" bundle. This is where the
> property view lives. It is already usable in RAP. I would need to take
> closer look at it to tell what's already implemented and what is not.
> Just take a look!
>
>>
>
> Hope I could help you!
> Benny

--
Boris Stepanov

Report message to a moderator

Previous Topic:	How to use Activex in rap?
Next Topic:	Asserting component enability

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 05:55:47 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter