Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » IApplication Support
IApplication Support [message #509508] Fri, 22 January 2010 16:25 Go to next message
Benjamin Wolff is currently offline Benjamin WolffFriend
Messages: 115
Registered: July 2009
Senior Member
Hi,

i read about the new IApplication Support in the N&N of RAP 1.3 M5 and tested it. I replaced the RAP-specific IEntryPoint mechanism with the RCP default IApplication mechanism. It even works with different IApplication classes, which can be selected by the "?startup=blabla" GET parameter in the URL.
I have some questions about the 3 additional parameters in the application extension point. There are "visible", "cardinality" and "thread". Do these parameters have an impact on the RAP application? What values should i set for these parameters?
It is also possible to set an icon, for what does RAP use this icon?

Greetings,
-ben
Re: IApplication Support [message #509664 is a reply to message #509508] Sun, 24 January 2010 14:19 Go to previous messageGo to next message
Benjamin Muskalla is currently offline Benjamin MuskallaFriend
Messages: 338
Registered: July 2009
Senior Member
Hi Ben,

nice to hear that it works as expected. Regarding your questions:
cardinality and thread are only used in the sense of regular OSGi
applications and will be ignored in RAP. Only the "visible" attribute
will be evaluated and "invisible" applications will not be registered as
entrypoints (eg. the equinox error application). As all three are
optional, you don't need to set any of them for RAP.

Regarding the icon: This is not possible as it is part of the branding
(same as for entrypoints). But you can use the full-qualified id of the
application to refer to it in the branding as you can do with entrypoints.

Regards,
Benny

Benjamin Wolff wrote:
> Hi,
>
> i read about the new IApplication Support in the N&N of RAP 1.3 M5 and
> tested it. I replaced the RAP-specific IEntryPoint mechanism with the
> RCP default IApplication mechanism. It even works with different
> IApplication classes, which can be selected by the "?startup=blabla" GET
> parameter in the URL.
> I have some questions about the 3 additional parameters in the
> application extension point. There are "visible", "cardinality" and
> "thread". Do these parameters have an impact on the RAP application?
> What values should i set for these parameters?
> It is also possible to set an icon, for what does RAP use this icon?
>
> Greetings,
> -ben
>


--
Benjamin Muskalla | EclipseSource Karlsruhe
http://www.eclipsesource.com | http://twitter.com/eclipsesource
Re: IApplication Support [message #509697 is a reply to message #509664] Sun, 24 January 2010 22:45 Go to previous messageGo to next message
Benjamin Wolff is currently offline Benjamin WolffFriend
Messages: 115
Registered: July 2009
Senior Member
Hi Benny,

ommiting the 3 variables seems to be a good solution, works as expected and prevents confusion :).
I have a question about this branding and application stuff. You mentioned that you can put the ID
of the application in the 'defaultEntrypointId' field. Lets assume the ID of my application (the short
part of the extension) is 'bla' and the name of my application is 'de.blubb', then the ID to be used
would be 'de.blubb.bla', correct?!
I realised, when ommiting the defaultEntrypoint in a branding, when there are several applications with
different IDs registered, the first application class is started. So how are the application classes
processed? Does the ID 'default' play any special role? What is the behaviour for finding the correct
application class to start, if there is no default entrypoint specified in the branding, no 'startup='
parameter specified in the URL and if there a several application classes contributed through the application
extension?

I hope you can understand what i'm questioning about ;)).

Greetings,
Ben



Am 24.01.2010 15:19, schrieb Benjamin Muskalla:
> Hi Ben,
>
> nice to hear that it works as expected. Regarding your questions:
> cardinality and thread are only used in the sense of regular OSGi
> applications and will be ignored in RAP. Only the "visible" attribute
> will be evaluated and "invisible" applications will not be registered as
> entrypoints (eg. the equinox error application). As all three are
> optional, you don't need to set any of them for RAP.
>
> Regarding the icon: This is not possible as it is part of the branding
> (same as for entrypoints). But you can use the full-qualified id of the
> application to refer to it in the branding as you can do with entrypoints.
>
> Regards,
> Benny
>
> Benjamin Wolff wrote:
>> Hi,
>>
>> i read about the new IApplication Support in the N&N of RAP 1.3 M5 and
>> tested it. I replaced the RAP-specific IEntryPoint mechanism with the
>> RCP default IApplication mechanism. It even works with different
>> IApplication classes, which can be selected by the "?startup=blabla"
>> GET parameter in the URL.
>> I have some questions about the 3 additional parameters in the
>> application extension point. There are "visible", "cardinality" and
>> "thread". Do these parameters have an impact on the RAP application?
>> What values should i set for these parameters?
>> It is also possible to set an icon, for what does RAP use this icon?
>>
>> Greetings,
>> -ben
>>
>
>
Re: IApplication Support [message #509699 is a reply to message #509697] Sun, 24 January 2010 18:38 Go to previous messageGo to next message
Benjamin Wolff is currently offline Benjamin WolffFriend
Messages: 115
Registered: July 2009
Senior Member
Ok, i ran some tests and looked in the RWT code and can now give the answer of two questions to myself ;).
Firstly, it is like i asked, and you stated before, that you can use the full qualifying ID of the application
extension to use it in the branding (e.g. de.blubb.bla). This leads me to a new question: will the next RAP
eclipse tooling version honor the new IApplication support by showing these extension in the browsing view
for entrypoints etc.?!
The second thing is, that the entrypoint ID 'default' is the hardcoded default value, which is used if there is no
entrypoint ID provided. neither in the URL nor in the branding as default entrypoint. good to know, especially for
deployed environments :).
So much for the questions ;)).

Greetings,
Ben



Am 24.01.2010 23:45, schrieb Benjamin Wolff:
> Hi Benny,
>
> ommiting the 3 variables seems to be a good solution, works as expected
> and prevents confusion :).
> I have a question about this branding and application stuff. You
> mentioned that you can put the ID
> of the application in the 'defaultEntrypointId' field. Lets assume the
> ID of my application (the short
> part of the extension) is 'bla' and the name of my application is
> 'de.blubb', then the ID to be used
> would be 'de.blubb.bla', correct?!
> I realised, when ommiting the defaultEntrypoint in a branding, when
> there are several applications with
> different IDs registered, the first application class is started. So how
> are the application classes
> processed? Does the ID 'default' play any special role? What is the
> behaviour for finding the correct
> application class to start, if there is no default entrypoint specified
> in the branding, no 'startup='
> parameter specified in the URL and if there a several application
> classes contributed through the application
> extension?
>
> I hope you can understand what i'm questioning about ;)).
>
> Greetings,
> Ben
>
>
>
> Am 24.01.2010 15:19, schrieb Benjamin Muskalla:
>> Hi Ben,
>>
>> nice to hear that it works as expected. Regarding your questions:
>> cardinality and thread are only used in the sense of regular OSGi
>> applications and will be ignored in RAP. Only the "visible" attribute
>> will be evaluated and "invisible" applications will not be registered as
>> entrypoints (eg. the equinox error application). As all three are
>> optional, you don't need to set any of them for RAP.
>>
>> Regarding the icon: This is not possible as it is part of the branding
>> (same as for entrypoints). But you can use the full-qualified id of the
>> application to refer to it in the branding as you can do with
>> entrypoints.
>>
>> Regards,
>> Benny
>>
>> Benjamin Wolff wrote:
>>> Hi,
>>>
>>> i read about the new IApplication Support in the N&N of RAP 1.3 M5 and
>>> tested it. I replaced the RAP-specific IEntryPoint mechanism with the
>>> RCP default IApplication mechanism. It even works with different
>>> IApplication classes, which can be selected by the "?startup=blabla"
>>> GET parameter in the URL.
>>> I have some questions about the 3 additional parameters in the
>>> application extension point. There are "visible", "cardinality" and
>>> "thread". Do these parameters have an impact on the RAP application?
>>> What values should i set for these parameters?
>>> It is also possible to set an icon, for what does RAP use this icon?
>>>
>>> Greetings,
>>> -ben
>>>
>>
>>
Re: IApplication Support [message #509743 is a reply to message #509699] Mon, 25 January 2010 09:39 Go to previous message
Benjamin Muskalla is currently offline Benjamin MuskallaFriend
Messages: 338
Registered: July 2009
Senior Member
Hi,

it seems we have to document the story a little bit better so people get
the idea without looking into the code ;-)

Regarding browsing IApplications - this will not be possible in the
Extension editor due to limitations in PDE. But for browsing them in the
Launch config, we already have a open enhancement request for that:

300366: [Tooling] Support browsing IApplications
https://bugs.eclipse.org/bugs/show_bug.cgi?id=300366

Regrards,
Benny

Benjamin Wolff wrote:
> Ok, i ran some tests and looked in the RWT code and can now give the
> answer of two questions to myself ;).
> Firstly, it is like i asked, and you stated before, that you can use the
> full qualifying ID of the application
> extension to use it in the branding (e.g. de.blubb.bla). This leads me
> to a new question: will the next RAP
> eclipse tooling version honor the new IApplication support by showing
> these extension in the browsing view
> for entrypoints etc.?!
> The second thing is, that the entrypoint ID 'default' is the hardcoded
> default value, which is used if there is no
> entrypoint ID provided. neither in the URL nor in the branding as
> default entrypoint. good to know, especially for
> deployed environments :).
> So much for the questions ;)).
>
> Greetings,
> Ben
>
>
>
> Am 24.01.2010 23:45, schrieb Benjamin Wolff:
>> Hi Benny,
>>
>> ommiting the 3 variables seems to be a good solution, works as expected
>> and prevents confusion :).
>> I have a question about this branding and application stuff. You
>> mentioned that you can put the ID
>> of the application in the 'defaultEntrypointId' field. Lets assume the
>> ID of my application (the short
>> part of the extension) is 'bla' and the name of my application is
>> 'de.blubb', then the ID to be used
>> would be 'de.blubb.bla', correct?!
>> I realised, when ommiting the defaultEntrypoint in a branding, when
>> there are several applications with
>> different IDs registered, the first application class is started. So how
>> are the application classes
>> processed? Does the ID 'default' play any special role? What is the
>> behaviour for finding the correct
>> application class to start, if there is no default entrypoint specified
>> in the branding, no 'startup='
>> parameter specified in the URL and if there a several application
>> classes contributed through the application
>> extension?
>>
>> I hope you can understand what i'm questioning about ;)).
>>
>> Greetings,
>> Ben
>>
>>
>>
>> Am 24.01.2010 15:19, schrieb Benjamin Muskalla:
>>> Hi Ben,
>>>
>>> nice to hear that it works as expected. Regarding your questions:
>>> cardinality and thread are only used in the sense of regular OSGi
>>> applications and will be ignored in RAP. Only the "visible" attribute
>>> will be evaluated and "invisible" applications will not be registered as
>>> entrypoints (eg. the equinox error application). As all three are
>>> optional, you don't need to set any of them for RAP.
>>>
>>> Regarding the icon: This is not possible as it is part of the branding
>>> (same as for entrypoints). But you can use the full-qualified id of the
>>> application to refer to it in the branding as you can do with
>>> entrypoints.
>>>
>>> Regards,
>>> Benny
>>>
>>> Benjamin Wolff wrote:
>>>> Hi,
>>>>
>>>> i read about the new IApplication Support in the N&N of RAP 1.3 M5 and
>>>> tested it. I replaced the RAP-specific IEntryPoint mechanism with the
>>>> RCP default IApplication mechanism. It even works with different
>>>> IApplication classes, which can be selected by the "?startup=blabla"
>>>> GET parameter in the URL.
>>>> I have some questions about the 3 additional parameters in the
>>>> application extension point. There are "visible", "cardinality" and
>>>> "thread". Do these parameters have an impact on the RAP application?
>>>> What values should i set for these parameters?
>>>> It is also possible to set an icon, for what does RAP use this icon?
>>>>
>>>> Greetings,
>>>> -ben
>>>>
>>>
>>>


--
Benjamin Muskalla | EclipseSource Karlsruhe
http://www.eclipsesource.com | http://twitter.com/eclipsesource
Previous Topic:table column resize/move problem - RAP 1.2.1 and Firefox 3.6.0
Next Topic:Enable and Dis-Able Paste Icons
Goto Forum:
  


Current Time: Fri Dec 03 16:57:42 GMT 2021

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

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

Back to the top