@6:59 putzing around with my monoprice tablet, installed pencil, which is awesome but had a bug (installing qt supposed to help?)... can't get pressure sensitivity to work in gimp but am probably doing something wrong as it seems to know about the  pen.

Onto some serious code which I've also putzed with... decided yesterday to take a couple weeks vacation, woot woot.

(don't like ch ristmas... bah humbug!)

Did I link this page yet? Threading Diagrams

I have the callback message going back correctly (callback fires in background.js then generates a message) but I'm not dispatching it on the content script side atm.  I want to solve that, get the DB back to the old performance and implement a summary page, then a subscription system.

@10:45 making slow progress... I need to set in mind the whole exchange... one issue, I have send go through the options looking for functions, making a function table, assigning ids.  All quite clear, but then debugging when the callback is generated it does a send and the structure has both the new callback table (for background.js calling send) and the table originally sent from the client.  I was calling this _sender_callback_dict and that was confusing.  Now it's _client_callback_dict and it's mort clear, because of the nesting level, which was the client (i.e. the _client_callback_dict in the event structure is the client of the event, one step above, it's the message client (which is the current sender).

It will be nice when it's done.

Then i want to do a subscribe feature and a summary page.