wish.txt

-- copy icon to copy content from one buffer row

-- remove row, update badge...
-- oss license
-- content script to use shadow dom; but first need to get react to play shadow games.
-- chrome.commands https://developer.chrome.com/extensions/commands
-- https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension

future
-- https://nadbm.github.io/react-datasheet/
-- direct integration with google sheets
-- easy mark clear (shift+click on mark?)
-- on upgrade, updating indexeddb schemas v dexie??
-- when pushing combined range to buffer, collapse whitespace, convert p, br *c to newlines
-- sticky buffer surviving refreshes and navigations
-- bg port disconnect scenarios (eg on plugin update, ...others?)
-- include pseudo-element content in selections?
-- download csv gets filename
-- scrollable buffer
-- capture simple styles in the selection
    - tinymce integration in table
    - http://stackoverflow.com/questions/5084713/copying-styled-text-from-a-page-to-the-clipboard-with-javascript
-- rapid visiting of urls in a list
-- capture element metadata as well
-- separately named tables, active table, etc
-- buffer splits, joins, manipulations, separate buffers, etc
-- better ux animations (e.g. buffer adds/removes animates badly)
-- multilang testing

code
-- fully replace custom externs w/ oops
-- optimize ui tree w/ components for mark, over (over queries/refreshes on [client-x, client-y] or scroll forces)
    -- org om components for minimal odm diffs/updates

other
-- fix dev-build profile
-- O/n of traversals
-- reconnect to bg page after extension refresh/update!
-- save-buffer! and other buffer ops handled via remotes
-- lose jquery, use goog.dom,*; document.querySelector(), etc.
-- lose dexie
-- react devtools?
-- unit testing?

ideas
-- modes: simple, magic, pro
-- color inversion
-- user-defined table schemas
-- optionally convert smart quotes elipses etc?

om/next?
-- bug? if state.flag = nil, component *not* rendered but
    subsequent merge will not yield initial component render
-- how does om/next decide when/to call remotes