Hi Eric, Thus far I haven't worried about namespacing filters. Remember that you control which ones are loaded and which ones are in effect. Behavior instances can have local filters that override globals, etc.
If, however, you want to be safe, you could use any of the examples below. I don't know if I have a preference. Are you going to release these behaviors? I'd love to see more people publishing them... On Wed, Sep 14, 2011 at 10:09 AM, Eric Patrick <[email protected]> wrote: > Thanks for the Behavior / BehaviorAPI Aaron; it's great to work with! > > I am developing a bunch of behaviors centered on dealing with AJAX- > loaded data grids: > > - Paginate: handles creation of DOM elements for a pagination row, > raising an event when a page or display size is changed > - OrderBy: handles making column headers sortable > - Filter: handles modification of JSON from a form to re-submit via > Request.HTML or Request.JSON > > It occurs to me others may do something similar. Any thoughts or > advice on "name spacing" behaviors? > > <div data-behaviors="Paginate, Filter"/> > > vs. my name space (mns) > > <div data-behaviors="mns.Paginate, mns.Filter"/> > > vs. > > <div data-behaviors="mns-Paginate, mns-Filter"/> > > vs. > > <div data-behaviors="mnsPaginate, mnsFilter"/> > > Thanks in advance, > > Eric >
