Based on my limited understanding of the views api, I believe you hook your module into views by letting it view the data in your modules table.
This module does not create any tables. The data association for images to options is based on the name of the file that is saved to the files table: option_image_5_2_4 which corresponds to node 5, attribute 2, option 4.
I believe for this module to hook into views, it needs to create its own table to store this data instead of using naming convention. Someone with more views experience can add more here if I'm wrong.
Comments
Comment #1
acouch commentedComment #2
summit commentedSubscribing, would love correct views support, to be able to use this to get overview pages of all option images available for a certain product.
EDIT: May be related to: http://drupal.org/node/550344#comment-2312020? I do not see the option images available within views.
greetings, Martijn
Comment #3
khakistocracy commentedThis is a very old thread, but I'm struggling to find a solution to getting option images available in views to allow for showing colour variations in a listing page view of products. Any ideas if this is being maintained or some help would be appreciated.