Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » limitations of RAP compared to PDE
limitations of RAP compared to PDE [message #60477] Mon, 19 November 2007 15:25 Go to next message
Eclipse UserFriend
Originally posted by: e.bork.yahoo.com

Hello,
I would like to find out, what is possible using RAP compared to any PDE
plugin project.

For example, would it be possible, to have a whole Eclipse environment
(including JDT) running from a website allowing me to develop Java
projects "online"? If this is too ambitious (why?) would it principally be
possible to build other RAP projects that support debugging through the
org.eclipse.debug.core.* extensions?

If not, which plugins won't work and why? I understand that probably not
all UI plugins exist in RAP. Do you have a list, which plugins work or
don't work?

In particular, is syntax highlighting (through org.eclipse.ui.editors
extension point) available to RAP projects?

Eike
Re: limitations of RAP compared to PDE [message #61077 is a reply to message #60477] Tue, 20 November 2007 09:44 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: fappel.innoopract.com

Hi,

there are several limiting factors that reduce the functionality of RAP
compared to RCP (list may not be complete):
- missing API: some functionality is not implemented yet due to limited
resources, e.g. drag and drop support
- distributed Environment: some functionality can't be provided due to
environmental limitations, e.g. serverside event-handling for mouse over
events
- security limitations of Browsers: e.g. local filesystem access

It's obvious that because of this limitations RAP can only support a subset
of the RCP functionalities. Because of this plug-ins ported from RCP to RAP
can only support a subset of their functionalities they usually provide in
RCP. Whether this subset is still usefull has to be decided from case to
case. It may be that some stuff seems to work but it doesn't care about
sessions, sometimes user sessions are no problem, but there is too much API
missing to get it doing something usefull...

Out of the box only the available plug-ins in the RAP CVS will work. To make
existing RCP UI plug-ins work with RAP at least the dependencies
declarations of those plug-ins must be changed to use the RAP UI base
plug-ins. Most of the time this will lead to compile errors due to missing
API, which have to be resolved.

As texteditor (and it's infrastructure) is not supported, syntax
highlighting like it is available in RCP will not be possible. From my
current point of view, I don't know whether there are to much limitations or
not to support this in the future.


Ciao
Frank


"Eike" <e.bork@yahoo.com> schrieb im Newsbeitrag
news:25deffdfb55346851dd8dff690f15ec3$1@www.eclipse.org...
> Hello,
> I would like to find out, what is possible using RAP compared to any PDE
> plugin project.
>
> For example, would it be possible, to have a whole Eclipse environment
> (including JDT) running from a website allowing me to develop Java
> projects "online"? If this is too ambitious (why?) would it principally be
> possible to build other RAP projects that support debugging through the
> org.eclipse.debug.core.* extensions?
>
> If not, which plugins won't work and why? I understand that probably not
> all UI plugins exist in RAP. Do you have a list, which plugins work or
> don't work?
>
> In particular, is syntax highlighting (through org.eclipse.ui.editors
> extension point) available to RAP projects?
>
> Eike
>
>
>
Re: limitations of RAP compared to PDE [message #61220 is a reply to message #61077] Tue, 20 November 2007 13:39 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: newsclient.server32212.xantronnet.de

On 2007-11-20, Frank Appel <fappel@innoopract.com> wrote:
> Hi,
>
> there are several limiting factors that reduce the functionality of RAP
> compared to RCP (list may not be complete):
> ...

Thank you! This overview was very helpful to me.

>
> As texteditor (and it's infrastructure) is not supported, syntax

Oh, didn't know that. Can you give a rough idea what would be required to
implement a very basic RAP texteditor? Including, let's say "Open" and "Save"
functionality for files on the server side?

Eike
Re: limitations of RAP compared to PDE [message #61243 is a reply to message #61220] Tue, 20 November 2007 13:42 Go to previous message
Benjamin Muskalla is currently offline Benjamin MuskallaFriend
Messages: 237
Registered: July 2009
Senior Member
Hi,

newsclient@server32212.xantronnet.de wrote:
> On 2007-11-20, Frank Appel <fappel@innoopract.com> wrote:
>> Hi,
>>
>> there are several limiting factors that reduce the functionality of RAP
>> compared to RCP (list may not be complete):
>> ...
>
> Thank you! This overview was very helpful to me.
>
>> As texteditor (and it's infrastructure) is not supported, syntax
>
> Oh, didn't know that. Can you give a rough idea what would be required to
> implement a very basic RAP texteditor? Including, let's say "Open" and "Save"
> functionality for files on the server side?
>
A very basic editor without the text framework can you see in the demo
application (see org.eclipse.rap.demo). It's just a MULTI-line textfield
which reacts on ModifyEvents to make the editor dirty.
The textframework itself isn't that easy to port as RAP doesn't have a
StyledText widget yet which is responsible for stuff like colors etc in
texteditors.


> Eike

Greets
Benny
Previous Topic:two dialogs in one method PROBLEM?!
Next Topic:sort table does not work on demo application when table is VIRTUAL
Goto Forum:
  


Current Time: Sat Nov 09 01:44:04 GMT 2024

Powered by FUDForum. Page generated in 0.03005 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top