Home » Eclipse Projects » Remote Application Platform (RAP) » RAP for multi-user IDE-like application
| RAP for multi-user IDE-like application [message #505161] |
Mon, 28 December 2009 09:04  |
 Laurent Petit
Messages: 35
Registered: July 2009 |
Member |
|
|
Hello,
We have developed a set of Eclipse plugins to provide a kind of IDE for a language/runtime of our own.
So far, we have used SWT/JFace widget based development for certain editors, and for some editors extended SourceEditor.
We also use the "out-of-the-box" notions of Workspace, IResources, Builders, ProblemMarkers, etc.
I'm unsure about which amount of code we will be able to share between our future multi-user RAP application and our current single-user "Eclipse + custom plugin" application.
For example, I understand that for enabling the multi-user mode, a notion of "RAP session context" must be introduced, and our own code must be aware of this "RAP session context".
But what about the plugins I depend upon ?
Will I be able to provide extensions to "org.eclipse.core.resources.builders" in a "multi-user" fashion (that is, the builder is not shared by the users, each user gets its own private "workspace" on
which the builders, etc. work) ?
There's certainly some core concept of RAP I still don't "get" yet, and so I can't decide whether I'm facing very hard/impossible problems (apart rewriting a org.eclipse.core.resources.builders like
mechanism myself) ?
Can you help me understand better what I can and cannot expect from RAP ?
Cheers,
--
Laurent
|
|
|
| Re: RAP for multi-user IDE-like application [message #505162 is a reply to message #505161] |
Mon, 28 December 2009 04:10  |
Laurent Petit
Messages: 35
Registered: July 2009 |
Member |
|
|
Laurent Petit wrote:
> Hello,
>
> We have developed a set of Eclipse plugins to provide a kind of IDE for
> a language/runtime of our own.
> So far, we have used SWT/JFace widget based development for certain
> editors, and for some editors extended SourceEditor.
I forgot to mention that not having SourceEditors in a first version of our RAP - based application is an option, so not having TextEditors in RAP currently is not a stopper for us.
> We also use the "out-of-the-box" notions of Workspace, IResources,
> Builders, ProblemMarkers, etc.
>
>
> I'm unsure about which amount of code we will be able to share between
> our future multi-user RAP application and our current single-user
> "Eclipse + custom plugin" application.
>
> For example, I understand that for enabling the multi-user mode, a
> notion of "RAP session context" must be introduced, and our own code
> must be aware of this "RAP session context".
>
> But what about the plugins I depend upon ?
> Will I be able to provide extensions to
> "org.eclipse.core.resources.builders" in a "multi-user" fashion (that
> is, the builder is not shared by the users, each user gets its own
> private "workspace" on which the builders, etc. work) ?
>
> There's certainly some core concept of RAP I still don't "get" yet, and
> so I can't decide whether I'm facing very hard/impossible problems
> (apart rewriting a org.eclipse.core.resources.builders like mechanism
> myself) ?
>
> Can you help me understand better what I can and cannot expect from RAP ?
>
> Cheers,
>
|
|
|
| Re: RAP for multi-user IDE-like application [message #505493 is a reply to message #505162] |
Thu, 31 December 2009 06:00 |
Laurent Petit
Messages: 35
Registered: July 2009 |
Member |
|
|
OK, I've been able to figure out myself most of the questions addressed by this post.
I've created a new thread with more focused questions.
--
Laurent
Laurent Petit wrote:
> Laurent Petit wrote:
>> Hello,
>>
>> We have developed a set of Eclipse plugins to provide a kind of IDE
>> for a language/runtime of our own.
>> So far, we have used SWT/JFace widget based development for certain
>> editors, and for some editors extended SourceEditor.
>
> I forgot to mention that not having SourceEditors in a first version of
> our RAP - based application is an option, so not having TextEditors in
> RAP currently is not a stopper for us.
>
>> We also use the "out-of-the-box" notions of Workspace, IResources,
>> Builders, ProblemMarkers, etc.
>>
>>
>> I'm unsure about which amount of code we will be able to share between
>> our future multi-user RAP application and our current single-user
>> "Eclipse + custom plugin" application.
>>
>> For example, I understand that for enabling the multi-user mode, a
>> notion of "RAP session context" must be introduced, and our own code
>> must be aware of this "RAP session context".
>>
>> But what about the plugins I depend upon ?
>> Will I be able to provide extensions to
>> "org.eclipse.core.resources.builders" in a "multi-user" fashion (that
>> is, the builder is not shared by the users, each user gets its own
>> private "workspace" on which the builders, etc. work) ?
>>
>> There's certainly some core concept of RAP I still don't "get" yet,
>> and so I can't decide whether I'm facing very hard/impossible problems
>> (apart rewriting a org.eclipse.core.resources.builders like mechanism
>> myself) ?
>>
>> Can you help me understand better what I can and cannot expect from RAP ?
>>
>> Cheers,
>>
|
|
|
Goto Forum:
Current Time: Mon Dec 11 10:35:26 GMT 2023
Powered by FUDForum. Page generated in 0.01979 seconds |
] 
Search
Help
Register
Login
Home
