Hi Ashkan,

I was catching up on some mail today, and realized I could have answered my own questions if I had kept up with my mail. Sorry for the need for you to repeat. Comments below.

On Jul 13, 2006, at 9:47 AM, Ashkan Soltani wrote:

Hi Ted

The output of the instrumentation code is configurable, but currently I have it just reporting the high-level blockEvent and its arguments (i.e. collection or item displayName):

2006-07-05 17:41:38.997397, ReminderTime - {'sender': <ReminderTimer: ebb9a85a-f747-11da-bcc4-b69075e12c22>, 'results': None} - - 2006-07-05 17:41:45.680046, SelectItemsBroadcast - {'items': [], 'sender': <TimedEventsCanvas: ec4a1368-f747-11da-bcc4- b69075e12c22>, 'collection': <SmartCollection: e4061b44-fbc9-11da- be68-96b5896d6896>, 'results': None} - - 2006-07-05 17:41:48.515094, SelectItemsBroadcast - {'items': [<ListCollection: trashCollection e50a47c6-f747-11da-bcc4- b69075e12c22>], 'sender': <SidebarBlock: ebbb9570-f747-11da-bcc4- b69075e12c22>, 'collection': None, 'results': None} - Trash - 2006-07-05 17:41:51.463844, SelectItemsBroadcast - {'items': [<SmartCollection: inCollection e53752fc-f747-11da-bcc4- b69075e12c22>], 'sender': <SidebarBlock: ebbb9570-f747-11da-bcc4- b69075e12c22>, 'collection': None, 'results': None} - In - 2006-07-05 17:41:55.435157, ApplicationBarTask - {'buttonState': True, 'sender': <ToolbarItem: ebba66e6-f747-11da-bcc4- b69075e12c22>, 'results': None} - - 2006-07-05 17:42:01.979833, SelectItemsBroadcast - {'items': [<MailedTask: 75b91d78-fcc1-11da-b8c9-ba38dce6ea47>], 'sender': <DashboardBlock: ec4718b4-fcc1-11da-b8c9-ba38dce6ea47>, 'collection': <SmartCollection: inCollection e53752fc-f747-11da- bcc4-b69075e12c22>, 'results': None} - chandler cats framework - In 2006-07-05 17:42:06.434139, ApplicationBarMail - {'buttonState': True, 'sender': <ToolbarItem: ebba47a6-f747-11da-bcc4- b69075e12c22>, 'results': None} - - 2006-07-05 17:42:15.857399, SelectItemsBroadcast - {'items': [<MailMessage: 7683bd44-fcc1-11da-b8c9-ba38dce6ea47>], 'sender': <DashboardBlock: 716b3a9e-fcc1-11da-b8c9-ba38dce6ea47>, 'collection': <SmartCollection: inCollection e53752fc-f747-11da- bcc4-b69075e12c22>, 'results': None} - [kei - whole office] Weekly and Upcoming Events (with additions) - In 2006-07-05 17:42:22.284905, SelectItemsBroadcast - {'items': [<MailMessage: 788ccb62-fcc1-11da-b8c9-ba38dce6ea47>], 'sender': <DashboardBlock: 716b3a9e-fcc1-11da-b8c9-ba38dce6ea47>, 'collection': <SmartCollection: inCollection e53752fc-f747-11da- bcc4-b69075e12c22>, 'results': None} - Workflows for data analysis - In

My plan is to dump everything notable to a file, then later analyze this information using some post processing scripts. The thinking behind this is:
+ Simpler implementation/Reduced processing overhead for chandler
+ Ability to go back and examine data that we originally weren't considering + Allows for the blockEvent code to evolve w/o the need for evolving the instrumentation code (new events will just be ignored by the reporting scripts until the hooks are created, but things will go on processing)
+ Ability to have an immutable/raw record of user activity

It's quite likely that we can collaborate on making this output quite usable by the 'attention recorder' component. Can you tell me a bit more about exactly specifically what you'd be looking for in this case.

Post processing scripts seems fine. The big thing that I am interested in is more "semantic level" events. "User created a new task <reference to the task>", "user changed the date of an event <reference to the event>", "user created new contact <reference tot he contact>". This way, a service that is trying to process your "attention stream" can get an idea of when your interest in something begins or changes.

Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to