Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Service Oriented Architecture Tools Platform (STP) » Hiding property pages of an editor
Hiding property pages of an editor [message #374723] Fri, 09 May 2008 05:06 Go to next message
Till Essers is currently offline Till Essers
Messages: 92
Registered: July 2009
Member
Hi

I'm using the STP.BPMN modeller in an RCP application. The problem is,
that the "Advanced" tab should be hidden, but how can I do this without
changing anything in the modeller?

Thanks
Till
Re: Hiding property pages of an editor [message #374724 is a reply to message #374723] Fri, 09 May 2008 05:18 Go to previous messageGo to next message
Eclipse User
Originally posted by: atoulme.intalio.com

Hi Till, you will need to do some coding, and most likely will run into
limitations of that API.

If you have your own version of the modeler, you can change the
contributor id of the modeler, and then redeclare the tabs that interest
you in the plugin.xml file, with new filters that you will have created
if that is needed.

Thanks,

Antoine

Till Essers wrote:
> Hi
>
> I'm using the STP.BPMN modeller in an RCP application. The problem is,
> that the "Advanced" tab should be hidden, but how can I do this without
> changing anything in the modeller?
>
> Thanks
> Till
Re: Hiding property pages of an editor [message #615841 is a reply to message #374723] Fri, 09 May 2008 05:18 Go to previous messageGo to next message
Eclipse User
Originally posted by: atoulme.intalio.com

Hi Till, you will need to do some coding, and most likely will run into
limitations of that API.

If you have your own version of the modeler, you can change the
contributor id of the modeler, and then redeclare the tabs that interest
you in the plugin.xml file, with new filters that you will have created
if that is needed.

Thanks,

Antoine

Till Essers wrote:
> Hi
>
> I'm using the STP.BPMN modeller in an RCP application. The problem is,
> that the "Advanced" tab should be hidden, but how can I do this without
> changing anything in the modeller?
>
> Thanks
> Till
Re: Hiding property pages of an editor [message #615842 is a reply to message #374724] Fri, 09 May 2008 06:05 Go to previous messageGo to next message
Till Essers is currently offline Till Essers
Messages: 92
Registered: July 2009
Member
Hi Antoine,
I'm using the latest modeler from SVN, but without modifications. If I
change something in your modeler I have to publish the changes, right?
This is a problem, I don't have the resources to do so and publishing
the modeller with just one property tab missing would be exaggerated.

Or did you mean with "your own version" that I'm making my own modeler
based on your samples (hide annotation)? Because that is what I have to
do... hide shapes due to permissions of the user.
If there is a way to hide it in my own modeler... how?

Thanks
Till

Antoine Toulme schrieb:
> Hi Till, you will need to do some coding, and most likely will run into
> limitations of that API.
>
> If you have your own version of the modeler, you can change the
> contributor id of the modeler, and then redeclare the tabs that interest
> you in the plugin.xml file, with new filters that you will have created
> if that is needed.
>
> Thanks,
>
> Antoine
>
> Till Essers wrote:
>> Hi
>>
>> I'm using the STP.BPMN modeller in an RCP application. The problem is,
>> that the "Advanced" tab should be hidden, but how can I do this
>> without changing anything in the modeller?
>>
>> Thanks
>> Till
Re: Hiding property pages of an editor [message #615843 is a reply to message #615842] Fri, 09 May 2008 07:29 Go to previous messageGo to next message
Eclipse User
Originally posted by: atoulme.intalio.com

Till Essers wrote:
> Hi Antoine,
> I'm using the latest modeler from SVN, but without modifications. If I
> change something in your modeler I have to publish the changes, right?
Not sure I follow what you mean. Do you mean you will have to give the
code back as we are open source ? Since we are not GPL that is not the case.
> This is a problem, I don't have the resources to do so and publishing
> the modeller with just one property tab missing would be exaggerated.
>
Well, that's up to you. I would certainly appreciate to have you
contribute to the modeler.

> Or did you mean with "your own version" that I'm making my own modeler
> based on your samples (hide annotation)? Because that is what I have to
> do... hide shapes due to permissions of the user.
Look at the EclipseCon 2008 tutorial. What I meant here was to subclass
the editor class and have your own editor.
> If there is a way to hide it in my own modeler... how?
>
I see three possibilities:
1. You don't code nothing. You open a bug against the BPMN modeler and
ask for us to remove this damn advanced tab, or at least filter it out.
We will eventually take a look at it, but we can't commit for a specific
time.

2. You have coded your own modeler using our tutorial to extend the
modeler, subclassing the BpmnDiagramEditor class. You just need to
override getContributorId() in this class, then use the tabbed
properties extension points to add the tabs you want to your own modeler.

3. The way the properties page is created today is that the
BpmnDiagramEditor class is asked for it through the getAdapter() class.
You override that method and return your own properties page.

Let me know what you think is worthwhile. Please assign the bug to me if
you create one, so I get notified!

Thanks,

Antoine
Re: Hiding property pages of an editor [message #615844 is a reply to message #615843] Fri, 09 May 2008 08:19 Go to previous messageGo to next message
Till Essers is currently offline Till Essers
Messages: 92
Registered: July 2009
Member
I think I'll take option 2 :)
Seems to be the easiest way.

Thanks
Till

Antoine Toulme schrieb:
> Till Essers wrote:
>> Hi Antoine,
>> I'm using the latest modeler from SVN, but without modifications. If I
>> change something in your modeler I have to publish the changes, right?
> Not sure I follow what you mean. Do you mean you will have to give the
> code back as we are open source ? Since we are not GPL that is not the
> case.
>> This is a problem, I don't have the resources to do so and publishing
>> the modeller with just one property tab missing would be exaggerated.
>>
> Well, that's up to you. I would certainly appreciate to have you
> contribute to the modeler.
>
>> Or did you mean with "your own version" that I'm making my own modeler
>> based on your samples (hide annotation)? Because that is what I have
>> to do... hide shapes due to permissions of the user.
> Look at the EclipseCon 2008 tutorial. What I meant here was to subclass
> the editor class and have your own editor.
>> If there is a way to hide it in my own modeler... how?
>>
> I see three possibilities:
> 1. You don't code nothing. You open a bug against the BPMN modeler and
> ask for us to remove this damn advanced tab, or at least filter it out.
> We will eventually take a look at it, but we can't commit for a specific
> time.
>
> 2. You have coded your own modeler using our tutorial to extend the
> modeler, subclassing the BpmnDiagramEditor class. You just need to
> override getContributorId() in this class, then use the tabbed
> properties extension points to add the tabs you want to your own modeler.
>
> 3. The way the properties page is created today is that the
> BpmnDiagramEditor class is asked for it through the getAdapter() class.
> You override that method and return your own properties page.
>
> Let me know what you think is worthwhile. Please assign the bug to me if
> you create one, so I get notified!
>
> Thanks,
>
> Antoine
Re: Hiding property pages of an editor [message #616109 is a reply to message #615844] Wed, 14 May 2008 08:37 Go to previous messageGo to next message
Till Essers is currently offline Till Essers
Messages: 92
Registered: July 2009
Member
Hi

I've done option 2 as mentioned before. I've wrote a small tutorial
about how to take control over all tabs. Maybe it will be helpful for
others with the same problem, but where should I send it?

Thanks
Till


Till Essers schrieb:
> I think I'll take option 2 :)
> Seems to be the easiest way.
>
> Thanks
> Till
>
> Antoine Toulme schrieb:
>> Till Essers wrote:
>>> Hi Antoine,
>>> I'm using the latest modeler from SVN, but without modifications. If
>>> I change something in your modeler I have to publish the changes, right?
>> Not sure I follow what you mean. Do you mean you will have to give the
>> code back as we are open source ? Since we are not GPL that is not the
>> case.
>>> This is a problem, I don't have the resources to do so and publishing
>>> the modeller with just one property tab missing would be exaggerated.
>>>
>> Well, that's up to you. I would certainly appreciate to have you
>> contribute to the modeler.
>>
>>> Or did you mean with "your own version" that I'm making my own
>>> modeler based on your samples (hide annotation)? Because that is what
>>> I have to do... hide shapes due to permissions of the user.
>> Look at the EclipseCon 2008 tutorial. What I meant here was to
>> subclass the editor class and have your own editor.
>>> If there is a way to hide it in my own modeler... how?
>>>
>> I see three possibilities:
>> 1. You don't code nothing. You open a bug against the BPMN modeler and
>> ask for us to remove this damn advanced tab, or at least filter it
>> out. We will eventually take a look at it, but we can't commit for a
>> specific time.
>>
>> 2. You have coded your own modeler using our tutorial to extend the
>> modeler, subclassing the BpmnDiagramEditor class. You just need to
>> override getContributorId() in this class, then use the tabbed
>> properties extension points to add the tabs you want to your own modeler.
>>
>> 3. The way the properties page is created today is that the
>> BpmnDiagramEditor class is asked for it through the getAdapter()
>> class. You override that method and return your own properties page.
>>
>> Let me know what you think is worthwhile. Please assign the bug to me
>> if you create one, so I get notified!
>>
>> Thanks,
>>
>> Antoine
Re: Hiding property pages of an editor [message #616112 is a reply to message #616109] Wed, 14 May 2008 08:45 Go to previous message
Eclipse User
Originally posted by: atoulme.intalio.com

Till, the painless way is to create a wiki page.

You can relate it to BPMN by adding those tags:

[[Category:BPMN]]
[[Category:STP]]

You can also open a bug to submit your tutorial as an article for
Eclipse Corner. I will be happy to review it, please add me in CC if you
do that.

Thanks,

Antoine


Till Essers wrote:
> Hi
>
> I've done option 2 as mentioned before. I've wrote a small tutorial
> about how to take control over all tabs. Maybe it will be helpful for
> others with the same problem, but where should I send it?
>
> Thanks
> Till
>
>
> Till Essers schrieb:
>> I think I'll take option 2 :)
>> Seems to be the easiest way.
>>
>> Thanks
>> Till
>>
>> Antoine Toulme schrieb:
>>> Till Essers wrote:
>>>> Hi Antoine,
>>>> I'm using the latest modeler from SVN, but without modifications. If
>>>> I change something in your modeler I have to publish the changes,
>>>> right?
>>> Not sure I follow what you mean. Do you mean you will have to give
>>> the code back as we are open source ? Since we are not GPL that is
>>> not the case.
>>>> This is a problem, I don't have the resources to do so and
>>>> publishing the modeller with just one property tab missing would be
>>>> exaggerated.
>>>>
>>> Well, that's up to you. I would certainly appreciate to have you
>>> contribute to the modeler.
>>>
>>>> Or did you mean with "your own version" that I'm making my own
>>>> modeler based on your samples (hide annotation)? Because that is
>>>> what I have to do... hide shapes due to permissions of the user.
>>> Look at the EclipseCon 2008 tutorial. What I meant here was to
>>> subclass the editor class and have your own editor.
>>>> If there is a way to hide it in my own modeler... how?
>>>>
>>> I see three possibilities:
>>> 1. You don't code nothing. You open a bug against the BPMN modeler
>>> and ask for us to remove this damn advanced tab, or at least filter
>>> it out. We will eventually take a look at it, but we can't commit for
>>> a specific time.
>>>
>>> 2. You have coded your own modeler using our tutorial to extend the
>>> modeler, subclassing the BpmnDiagramEditor class. You just need to
>>> override getContributorId() in this class, then use the tabbed
>>> properties extension points to add the tabs you want to your own
>>> modeler.
>>>
>>> 3. The way the properties page is created today is that the
>>> BpmnDiagramEditor class is asked for it through the getAdapter()
>>> class. You override that method and return your own properties page.
>>>
>>> Let me know what you think is worthwhile. Please assign the bug to me
>>> if you create one, so I get notified!
>>>
>>> Thanks,
>>>
>>> Antoine
Previous Topic:Hiding property pages of an editor
Next Topic:JBoss
Goto Forum:
  


Current Time: Wed Apr 23 19:44:23 EDT 2014

Powered by FUDForum. Page generated in 0.01702 seconds