On Thu, Mar 13, 2014 at 6:59 PM, Jason Etheridge <[email protected]>wrote:
> > I just posted a wordy update to the browser client dev log with a call > for > > input on how we build our UI grids (tables, lists, etc.). See the first > > section titled "User Interface Grids / Tables". This particular > component > > will be used heavily, so I want to make sure we explore all options > before > > we pick a path. > > Bill, one thing I liked about the XUL lists is the standard set of > "list actions", like exporting to a file in CSV format, printing, > invoking the clipboard, etc. I'm not sure what other folks think. > I'm also not advocating for you to expose such options in any > particular way. Folks may want them to be a mix-in/overlay to > interface-specific menus for each list, or some icon next to a column > picker icon, etc. > Good points, Jason, and I agree we should keep (most of) these. Though I'm assuming features like exporting, printing, persistence, and custom menus will have to built by us, regardless of the underlying markup, it's a good idea to air everything in case it may affect the outcome. Regarding the clipboard, though, I'm really hoping users can copy/paste directly from the page so we can avoid the extra step of launching a clipboard selector. Note to self: related to copy/paste, this is a good reason to avoid double-click-on-row-opens-data actions in grids (like I did with the patron search UI in the prototype), since double-click is the fastest way to select a string of text for copy... -b -- Bill Erickson | Senior Software Developer | phone: 877-OPEN-ILS (673-6457) | email: [email protected] | web: http://esilibrary.com | Equinox Software, Inc. / The Open Source Experts
