| [Compare] DiffEngine: Modifying when Conflicting EReferences occur [message #118975] |
Fri, 18 April 2008 03:31  |
Eclipse User |
|
|
|
When running a Diff, I need (non-containment) EReferences to be
evaluated just by the *URIs* they point to. For example, I'd like
references only to appear conflicted if they point to diffent URIs,
irregardless of the content of that Resolved references point to (or
even if the reference is still a Proxy). I believe the current
behavior shows a conflict when the referenced objects aren't "equal".
So, my question would be, what is the best approach to customizing the
DiffEngine behavior in this way? (create a new DiffExtension, extend
GenericDiffEngine, put in a enhancement request for new options passed
to GenericDiffEngine, etc).
Thanks,
Matt
|
|
|
|
| Re: [Compare] DiffEngine: Modifying when Conflicting EReferences occur [message #119065 is a reply to message #118989] |
Fri, 18 April 2008 11:30  |
| Eclipse User |
|
|
|
Thanks for the quick reply! I'll reply to this thread if I find issues
extending the GenericDiffEngine.
Thanks again,
Matt
laurent Goubet wrote:
> Matt,
>
> I think the best way of defining such a behavior would be to extend
> GenericDiffEngine through the extension point
> org.eclipse.emf.compare.diff.engine and to override
> GenericDiffEngine#checkReferencesUpdates(DiffGroup, Match3Element).
>
> We tried and make the generic diff engine extensible for such needs so
> that clients won't need to create a whole new IDiffEngine for trivial
> modifications of the generic behavior. Feel free to give us any feedback
> you would have about lack of extensibility or functionalities about the
> generic engines.
>
> About options that could be passed on to the Differencing engine ...
> This could probably be a cool feature but we need to think about how to
> implement it if it can be done ;).
>
> Cheers
> Laurent Goubet
> Obeo
>
> Matt Seashore a écrit :
>> When running a Diff, I need (non-containment) EReferences to be
>> evaluated just by the *URIs* they point to. For example, I'd like
>> references only to appear conflicted if they point to diffent URIs,
>> irregardless of the content of that Resolved references point to (or
>> even if the reference is still a Proxy). I believe the current
>> behavior shows a conflict when the referenced objects aren't "equal".
>>
>> So, my question would be, what is the best approach to customizing the
>> DiffEngine behavior in this way? (create a new DiffExtension, extend
>> GenericDiffEngine, put in a enhancement request for new options passed
>> to GenericDiffEngine, etc).
>>
>>
>> Thanks,
>>
>> Matt
>
|
|
|
| Re: [Compare] DiffEngine: Modifying when Conflicting EReferences occur [message #617833 is a reply to message #118975] |
Fri, 18 April 2008 04:28 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------020003050108090005000507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Matt,
I think the best way of defining such a behavior would be to extend
GenericDiffEngine through the extension point
org.eclipse.emf.compare.diff.engine and to override
GenericDiffEngine#checkReferencesUpdates(DiffGroup, Match3Element).
We tried and make the generic diff engine extensible for such needs so
that clients won't need to create a whole new IDiffEngine for trivial
modifications of the generic behavior. Feel free to give us any feedback
you would have about lack of extensibility or functionalities about the
generic engines.
About options that could be passed on to the Differencing engine ...
This could probably be a cool feature but we need to think about how to
implement it if it can be done ;).
Cheers
Laurent Goubet
Obeo
Matt Seashore a
|
|
|
| Re: [Compare] DiffEngine: Modifying when Conflicting EReferences occur [message #617839 is a reply to message #118989] |
Fri, 18 April 2008 11:30 |
| Eclipse User |
|
|
|
Thanks for the quick reply! I'll reply to this thread if I find issues
extending the GenericDiffEngine.
Thanks again,
Matt
laurent Goubet wrote:
> Matt,
>
> I think the best way of defining such a behavior would be to extend
> GenericDiffEngine through the extension point
> org.eclipse.emf.compare.diff.engine and to override
> GenericDiffEngine#checkReferencesUpdates(DiffGroup, Match3Element).
>
> We tried and make the generic diff engine extensible for such needs so
> that clients won't need to create a whole new IDiffEngine for trivial
> modifications of the generic behavior. Feel free to give us any feedback
> you would have about lack of extensibility or functionalities about the
> generic engines.
>
> About options that could be passed on to the Differencing engine ...
> This could probably be a cool feature but we need to think about how to
> implement it if it can be done ;).
>
> Cheers
> Laurent Goubet
> Obeo
>
> Matt Seashore a écrit :
>> When running a Diff, I need (non-containment) EReferences to be
>> evaluated just by the *URIs* they point to. For example, I'd like
>> references only to appear conflicted if they point to diffent URIs,
>> irregardless of the content of that Resolved references point to (or
>> even if the reference is still a Proxy). I believe the current
>> behavior shows a conflict when the referenced objects aren't "equal".
>>
>> So, my question would be, what is the best approach to customizing the
>> DiffEngine behavior in this way? (create a new DiffExtension, extend
>> GenericDiffEngine, put in a enhancement request for new options passed
>> to GenericDiffEngine, etc).
>>
>>
>> Thanks,
>>
>> Matt
>
|
|
|
Powered by
FUDForum. Page generated in 0.03344 seconds
Home