Disclaimer â€“ newbie developer, so I hope I'm not going to write nonsense.
I was thinking on how to integrate Views in the attribute options? Why should we have this? Because options can change, either we need the user to enter some data - like I stated here, or maybe I'll have a stock table which I'd like to query and return only the options which I have in stock. Maybe later add a feature 'If view returns an empty query disable the Add to cart button'?
In other words, have the views power.
I've got some comments/ questions/ thoughts:
1. Do we really need such a feature, or am I just projecting my needs ?
2. View per option (not View per attribute) allows a certain view to have all the price/ weight adjustments.
3. We need to define a name for the option but also an arbitrary ID. For example, in my T-shirt example I'd like the Views to show the node title, but when I as the admin get the order, I'd like to have the NID as well.
So, what do you think?