fixes #6668 - very exciting stuff - _Widget.destroy(true) will preserve the domNode (does NOT work with _Templated yet, but that's the plan). This is a compromise between a "widget" and "named behaviors", where you can use _Widget to create  structured "behavioral" widgets around a single domNode. This is a great inclusion, though we be unnecessary if  dojo.behavior had a .remove() method (perhaps based on a handle returned from add()?) 
fixes #6668 - very exciting stuff - _Widget.destroy(true) will preserve the domNode (does NOT work with _Templated yet, but
that's the plan). This is a compromise between a "widget" and "named behaviors", where you can use _Widget to create 
structured "behavioral" widgets around a single domNode. This is a great inclusion, though we be unnecessary if 
dojo.behavior had a .remove() method (perhaps based on a handle returned from add()?) 

noteworthy: this technically changes the API of an unsupported, unused param "finalize" (probably used in older days for
global cleanup, but unused since 0.9) to "preserveDom" ... true meaning "leave the node alone". 

includes simple testcase to check widget count in registry, could easily be converted to unit test. 

!strict



git-svn-id: 674a2d6b1e32e53f607eb824547723f32280967e@13683 560b804f-0ae3-0310-86f3-f6aa0a117693

kitsonk/delite,harbalk/delite,Sam-Cummins/delite,harbalk/delite,kitsonk/delite,Sam-Cummins/delite