Community
Participate
Working Groups
I20051129 If a content-type changes and more file extensions are added to this content-type, it is not possible to efficiently update a model that relies on this content-type. The whole model has to be recomputed. Platform should provide a delta on a resource basis. For example, if one adds a 'abc' file extension to the Java source content-type, Platform should broadcast a delta for each .abc file and say that this file is affected by a change to the Java source content-type.
*** Bug 120643 has been marked as a duplicate of this bug. ***
*** Bug 120645 has been marked as a duplicate of this bug. ***
Could this be investigated before M5? The solution might require new API.
I can't promise anything because we don't have an active committer with knowledge of content types... Rafael, is there any way to find out from a content type change event exactly what file associations were added/removed/changed? The workspace doesn't eagerly compute the content type associations for each resource, so I suspect it is difficult to determine if the content type has changed for a resource even if we know what file associations have changed.
Nope, no detail information is available off the change event object. The content type change event API was added at the last minute in 3.0 to support the notification of encoding changes as resource change events, and for that scenario there was no way of figuring out what resources were actually affected so we end up broadcasting (potential) encoding changes for every single file in the workspace when any content type change occurs. A similar approach could be taken for content type changes, but for it to be reasonably efficient (which is the main point here) the content type change event would have to describe file spec changes as well.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
