Disable dropping incompatible data on visualizations

[GoogleCodeExporter]

Sometimes, data cannot be displayed in certain visualizations, because the 
required data attributes are missing. For example, data that do not contain 
dates cannot be displayed on a timeline.

Under those circumstances, the drop targets should not be active, otherwise the 
user might get confused.

Right now, this is implemented in an ad-hoc fashion.

Related source code:
- ResourceSetAvatarDropController.canDrop

Original issue reported on code.google.com by Lars.Grammel on 12 Jul 2010 at 9:30

• Merged into: #5

[GoogleCodeExporter]

We could implement a simple interface for now which:

- uses view id & resources as inputs
- return whether the resources can be displayed in the view or not

This interface could be implemented by the different Choosel applications and 
set using dependency injection.

Original comment by Lars.Grammel on 12 Jul 2010 at 9:33

[GoogleCodeExporter]

Original comment by Lars.Grammel on 12 Jul 2010 at 9:33

[GoogleCodeExporter]

The implementation could be a map from the view ids to lists of the supported 
resource types, as returned by the resource categorizer of that Choosel 
application.

Original comment by Lars.Grammel on 12 Jul 2010 at 9:35

[GoogleCodeExporter]

When some resources in the resource set are compatible to the view and others 
are not, the resource set *cannot* be dropped onto the view.

Original comment by Lars.Grammel on 12 Jul 2010 at 9:39

[GoogleCodeExporter]

Original comment by Lars.Grammel on 22 Jul 2010 at 11:07

• Changed state: Duplicate