r2 - 10 Dec 2005 - 00:05:14 - KatieCappsParlanteYou are here: OSAF >  Journal Web  >  ContributorNotes > KatieParlanteNotes > KatieParlante20051207

brainstorming with Ted about scripting

Elements of scripting

  • Actions (Commands)
    • menus
    • should be able to invoke commands from scripts, including other scripts

  • Find well known items
    • UI elements
    • Collections
    • Misc items like "me", accounts, etc.

  • Alter/adjust/customize presentation
    • script friendly way to tweak views
    • can probably get away with this being a matter of tweaking well known items, data driven

  • Change domain model
    • Items (content items)
    • Collections

  • Triggers to fire off scripts
    • Reminders (time based)
    • Data into the app
    • Data leaving the app
    • Some data condition is triggered

questions

  • scripts vs parcels
    • scripts are lightweight
    • should be able to write them quickly
    • enable web 2.0 mashup

script examples/ideas

  • move things around based on calendar data (content of items)
  • reminder goes off, script runs
  • Ted scripts omnioutliner (will write it up)
    • builds views by gathering data (not customizing the presentation, more the data)
    • setup: in chandler would create kinds/attributes before writing the script, script can depend on these
  • Cusomize searching
    • baseline you might want to start searching from, custom to your personal data
  • Mail filtering
  • Intercept input/output of command
    • Wrap RSS item with some processing
  • Spreadsheet like computations: counting
  • Filtering input into the app
  • import/export time processing
    • feeds/email/flickr tags
    • keyboard entry: shortcuts for marking up data
  • trigger a script from outside the app and pass data into the script
    • webserver listening on a port, punch data into chandler
    • quicksilver type in text --> applescript --> put data into omnioutliner (do something similar for chandler)
  • integration with other apps
    • clipboard/dnd --> process info coming into the app, or before it leaves the app
  • glue different apps together
    • pass data in, execute command, get results back
    • notification comments on spam, some processing before notifications
  • glue parts of chandler together
    • bidirectional refs between data types
  • export --> format data as it leaves chandler (different ways for data to leave chandler)
    • export as vcard/etc.
    • chandler as webserver
    • interception point
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.