> One possibility action mappings as you mention, but a first step might just > be to refactor out as much logic as possible from the ComponentKeyListener > methods into public methods that a user can easily call from their own key > handlers or actions. Simple examples might be things like 'select all' and > 'deselect all'.
FYI, there is already a selectAll() method; deselect all would simply be setSelection(0, 0). >> FWIW, I think the priority right now should be getting a stable 2.0 release >> out the door. We're seeing a lot of new interest in Pivot at the moment, and >> there is a lot of great stuff in this release that these developers will be >> able to take advantage of. We don't have to try to squeeze everything in >> right now - the changes we have already made for 2.0 will give us a very >> solid foundation for moving forward. >> > I totally agree. Far less verbose BXML thanks in itself is almost a reason > to push out 2.0 right now :) Yup. :-) The new namespace binding stuff and stylesheet support is also nice, as are the other enhancements to BXMLSerializer and Bindable.
