| RE: [jwt-dev] Plugin mode check |
|
Hi Florian, Along with the views the “workflow
perspective” lays out, I think there are other JWT behaviors too dependent
upon the plugin mode like the “New Workflow Wizard” which presents
a dialog box to select a folder within your workspace if JWT is running within Eclipse. My RCP app also implements a
view to user’s local workspace using Common Navigator framework. Hence, I
would like the “New Workflow Wizard” to not skip the first page
which lets the user select a folder within the workspace when running within an
RCP application. I think an extension point
approach would definitely be more suitable to override such default behaviors
but since I do not have much experience with defining them maybe Chris can shed
some more light on the issue. Regards, Ravi From: jwt-dev-bounces@xxxxxxxxxxx
[mailto:jwt-dev-bounces@xxxxxxxxxxx] On Behalf Of Florian Lautenbacher Hi Ravi, I also stumbled about that a few
weeks ago. Actually, this is in my opinion a bug. I have it on my to do list to
open a new bug for that in the Eclipse bugzilla. In my solution (where I also
built an RCP application on top of JWT), I changed the JWT locally and said
that if the name contains “RCP” then it should be in another mode
than if only in plugin-mode. But I didn’t commit that
patch yet and are not completely sure that it is the best way to work with
that. Maybe there is a better idea? Something which is always present when
having an application? Maybe we could create an extension point for that? As Chris implemented this, I
guess, he might have further ideas... Best regards, Florian Von:
jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag
von RAVI K. THAPLIYAL Hi, The plugin mode check
done by GeneralHelper has been hard coded for “agilpro” as
below: if
(Platform.getProduct().getName() != null &&
Platform.getProduct().getName().toLowerCase().contains("agilpro"))
//$NON-NLS-1$ {
return false; } else {
return true; } I’m trying to integrate JWT with my RCP app and unless
I have “agilpro” in my product name the “workflow
editor” perspective opens up the “Package Explorer” view
which fails. In JWT 0.5 the code checked for “eclipse” in the
product name which seems to be the right approach. So, how do I get around this in JWT 0.6? Regards, Ravi
|