Issue 191: Preferences Override
Project Member Reported by jeff.johnston.mn@gmail.com, Apr 27, 2009
An idea came up on the groups to make the Preferences overridable.

http://groups.google.com/group/jmesa/browse_thread/thread/d9b444193191e28e

Apr 27, 2009
Project Member #1 jeff.johnston.mn@gmail.com
If methods called jQuery.jmesa.onInvokeAction()
directly then only the view would have to worry about setting what the
actual onInvokeAction is. I think that is a good improvement in general!

Setting what the actual onInvokeAction is other than at the global level
would still require a lot of cut and paste, in a custom view, of the
HtmlSnippets.initJavascriptLimit() method. That makes your other idea of
making the Preferences overridable on a per table basis very appealing, and
brilliant! It would actually be more of a proxy though as the new Object
would control access to the underlying Preferences, which would be perfect.
So that means that the TableFacade would create a PreferencesProxy and there
would be two new methods on the TableFacade to set the onInvokeAction() and
onInvokeExportAction().