Specify confirmation per operation instead of per view

Looking briefly at the code, it seems pretty straight forward inside views_bulk_operations.module itself. Instead of testing $plugin->options['skip_confirmation'], we could be testing something like $plugin->options['skip_confirmation'][$operation].

The bigger question appears to be the UI for the views style plugin. Seems like we need a table instead of the current pile of checkboxes and operations. I'm trying to figure out how easy that is from merlinofchaos in IRC right now. ;) Not trivial. For an initial attempt, this just duplicates the operations with another set of checkboxes to control the confirm form. I know it's lame, but I'm just getting it started.

Another tricky part is the upgrade path, since existing views will have an integer saved for this option, instead of an array. This patch completely ignores this problem.

Otherwise, it works fine -- it's just ugly and doesn't handle existing views that think skip_operation is an int, not an array.

Oh interesting. I hadn't thought of doing a site-wide setting to globally specify confirmation for each operation. I suppose that any operation that's "destructive" and would often want a confirmation step would probably always want it. However, that would introduce a lot of site-wide variables, which are more expensive overall for the site than these per-view settings which are only loaded with the view when needed, instead of on every page no matter what. Also, I could dream up use-cases where you'd want confirmation on an operation in some cases but not others. For example, what about an "expert mode" admin view somewhere that assumes you know what you're doing, vs. the standard admin view that people get by default.

So, I think it'd probably make sense to just continue down the current path and see how nasty the theme function stuff to get the UI better is. If it's a huge can of worms, we can reconsider, but since the actual functionality now works in the more fine-grained approach, we might as well keep it. ;)

That said, I'll certainly defer to the community -- we should probably get some other VBO users/developers to weigh in here.

Thanks!
-Derek