Extending DeleteResourceAction [message #331859] |
Thu, 25 September 2008 13:58 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: andreas-scharf.gmx.de
Hi,
I have view using the CNF which currently does almost the same as the
Resource Explorer. In my special application I have dependent resources
and if the user deletes resource A the dependent resource B (which is a
file which only contains UI information) also should be deleted. I
thought of using my own MyDeleteResourceAction in which I execute 2
DeleteResourceActions (one to actually delete the resource the user
selected and one to delete the dependent UI information resource).
Is that approach applicable or is there another (better) way to do this?
Greetings,
Andreas
|
|
|
|
Re: Extending DeleteResourceAction [message #331878 is a reply to message #331869] |
Fri, 26 September 2008 09:19 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: andreas-scharf.gmx.de
Paul,
thanks for pointing me to the ltk (never heard about that before). I'll
check this out.
Andreas
Paul Webster schrieb:
> Check out adding an LTK delete participant, which in 3.4 the Package
> Explorer, Project Explorer and Resource navigator will honour.
>
> PW
>
>
|
|
|
Re: Extending DeleteResourceAction [message #331900 is a reply to message #331878] |
Sat, 27 September 2008 10:18 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: andreas-scharf.gmx.de
Paul,
I implemented extending the DeleteResourceAction using the ltk stuff.
But I've got some question about the correct implementation of a
participant. One of my participants also deletes a corresponding file
which contains UI related information about the file the user wants to
delete. Now what happens is, when the user e.g. selects A.file AND
A.fileUI my participant should not add a Change. I've implemented it
checking in the createChange() method if getProcessor().getElements()
already contains the element my participant wants to delete. Now the
question is if this is the right place to do it. Or is there another
mechanism to not add a second change to delete the resource?
Andreas
Andreas Scharf schrieb:
> Paul,
>
> thanks for pointing me to the ltk (never heard about that before). I'll
> check this out.
>
> Andreas
>
> Paul Webster schrieb:
>> Check out adding an LTK delete participant, which in 3.4 the Package
>> Explorer, Project Explorer and Resource navigator will honour.
>>
>> PW
>>
>>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03061 seconds