| A beginners question about dependesie naming [message #520815] |
Mon, 15 March 2010 13:35  |
|
Hi,
I maybe have a dumb question about RAP. I search the documentation about it but I am just curious why we have org.eclipse.rap.ui instead of org.eclipse.ui. I ask this because if your Single sourcing a RCP/PDE project with a RAP project you always heave to set both to optional. Because they don't know each other in the environments. And it would be more logical for single Sourcing purposes to have both the UI elements being named org.eclipse.ui.
I was just wondering why this is done like this and not having the same name.
Kind regards,
Martijn Cremer
hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is.
|
|
|
| Re: A beginners question about dependesie naming [message #520868 is a reply to message #520815] |
Mon, 15 March 2010 10:58  |
|
Hi Martijn,
we also had this discussion several times. It's true that single
sourcing would be easier if the org.eclipse.rap.ui bundle would fake
itself as org.eclipse.ui. But org.eclipse.rap.ui is not just a name,
it's an id. Having different bundles with the same id around would
violate the concept of identity.
When you assemble different target platforms, it could become hard to
distinguish the rap.ui bundles from their eclipse.ui counterparts. Or
think of a bundle repository: there would be no way to distinguish
org.eclipse.ui and org.eclipse.rap.ui. For these reasons I think we
should not go this last step in single sourcing. Does this make sense?
Regards, Ralf
Martijn Cremer wrote:
> Hi,
>
> I maybe have a dumb question about RAP. I search the documentation about
> it but I am just curious why we have org.eclipse.rap.ui instead of
> org.eclipse.ui. I ask this because if your Single sourcing a RCP/PDE
> project with a RAP project you always heave to set both to optional.
> Because they don't know each other in the environments. And it would be
> more logical for single Sourcing purposes to have both the UI elements
> being named org.eclipse.ui.
>
> I was just wondering why this is done like this and not having the same
> name.
>
> Kind regards,
>
> Martijn Cremer
|
|
|
| Re: A beginners question about dependesie naming [message #520872 is a reply to message #520868] |
Mon, 15 March 2010 16:00 |
|
Hi Ralf,
It does, I was just curious because the RWT package fakes it self as org.eclipse.SWT and i was just wondering why it wasn't done with the UI part. But its logical if you put it like that. And I just got use to adding both the rap and he rcp version of the UI and making them optional till someone actually asked my why do you do that. And I coud not give him a decent answer.
Thanks for the information and keep up the great work.
Regards,
Martijn Cremer
| Ralf Sternberg wrote on Mon, 15 March 2010 11:58 | Hi Martijn,
we also had this discussion several times. It's true that single
sourcing would be easier if the org.eclipse.rap.ui bundle would fake
itself as org.eclipse.ui. But org.eclipse.rap.ui is not just a name,
it's an id. Having different bundles with the same id around would
violate the concept of identity.
When you assemble different target platforms, it could become hard to
distinguish the rap.ui bundles from their eclipse.ui counterparts. Or
think of a bundle repository: there would be no way to distinguish
org.eclipse.ui and org.eclipse.rap.ui. For these reasons I think we
should not go this last step in single sourcing. Does this make sense?
Regards, Ralf
|
hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is.
|
|
|
Powered by
FUDForum. Page generated in 0.05183 seconds
] 
Search
Help
Register
Login
Home
