[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.platform] Re: How to exit RCP during start up?
|
- From: Joel Rosi-Schwartz <Joel.Rosi-Schwartz@xxxxxxxxx>
- Date: Tue, 04 Nov 2008 18:16:30 +0000
- Newsgroups: eclipse.platform.rcp, eclipse.platform
- Organization: EclipseCorner
- Posted-and-mailed: yes
- Thread-index: Ack+qXWXpK1XqICSDkCAp42fAlkhLQ==
- Thread-topic: How to exit RCP during start up?
- User-agent: Microsoft-Entourage/12.14.0.081024
On 04/11/2008 18:03, in article geq2q5$pav$1@xxxxxxxxxxxxxxxxx, "Eric Rizzo"
<eclipse-news@xxxxxxxxxxxx> wrote:
> On 11/4/2008 12:44 PM, Joel Rosi-Schwartz wrote:
>> I also have a further issue. My architecture is split up with an app, core
>> and ui bundles. I would really not like to pollute the app bundle with UI
>> stuff if I can help it. Once I pull this File dialog into the app bundle, I
>> also have to pull up my preferences. This means that all of my dialogs that
>> access preferences also (and I have not many but a few) these have be pulled
>> up to access the plug-ins preference store. This is getting too sloppy for
>> my taste.
>>
>> The only solution I have come up with so far is to put the resource check in
>> the Activator.start() method of my ui bundle. This also seems brutish,
>> but...
>>
>> Anyone have a idea for a cleaner solution?
>
> You could define your own extension point in the app bundle and have it
> delegate to some interface (defined by that extension point) to do the
> real work. Something like ResourceSelectionHandler. Then your UI plugin
> implements that extension point and provides and implementation of the
> interface.
>
> You could also do it with a fragment that is hosted by the app plugin;
> the fragment can have UI dependencies but keep them out of the plugin
> itself.
>
> Hope this helps,
> Eric
The first is a very interesting idea, I will give it whirl. The second, i.e.
using a fragment, doesn't actually solve my issues.
Thanks,
Joel