Don Park’s Daily Habit

Posts Mentioning RSS Toggle Comment Threads | Keyboard Shortcuts

• 

  donpark 3:30 am on July 23, 2009 Permalink | Reply
  Tags: Components.utils.import, firefox, NS_ERROR_FAILURE, tips, XPCOM   

  Firefox Extension Developer Tips 

  Just a couple of tips for Firefox extension developers, hard earned after many hours of head scratching. Not adhering to either tips will confuse Firefox and XPCOM component will fail to load.

  XPCOM components get loaded before chromes are loaded.

  [Update: The most common problem related to this is Components.utils.import call fails during launch with NS_ERROR_FAILURE exception. To fix, wait until app-startup notification is received before importing javascript modules.]

  This means anything defined in chrome.manifest won’t be available until “app-startup” event is observed. Note that Resource URI scheme “resource://” introduced in Firefox 3 uses resource directives in chrome.manifest which means you should defer Components.utils.import calls until “app-startup“.

  XPCOM components implemented using Javascript should be defined as a pure object, not function.
  

  So it should look something like this:

  var MyServiceModule = {
    registerSelf: function(compMgr, fileSpec, location, type) {
      ..
    },
    ..
  };

   

  Reply Click here to cancel reply.

  Name (required)

  Email (required)

  Web Site

  Notify me of follow-up comments via email.

  Notify me of new posts via email.

   
• 

  donpark 6:28 am on July 9, 2009 Permalink | Reply
  Tags: realtime, stream, ui   

  Real-Time State of Mind 

  I need to get back to blogging more often. Having to type more than 140 characters feels wierd.

  Given that I’ll be attending TechCrunch’s Real-Time Stream CrunchUp this Friday, I thought a blog post on a key real-time stream problem would help me into a real-time state of mind.

  Real-time streams have many technical problems to overcome many of which are thankfully being resolved by advances in technology and infrastructure but the problem that interests me the most is the user experience problems:

  Information, real-time or otherwise, is meaningless if users are drowned within it.

  Typical Twitter users see only a fraction of tweets from people they follow. The notion of Top Friends (related to my social radar diagram from 8 years ago) will help but at the cost of additional chores users have to do separate the greens from weeds.

  The financial industry has used real-time streams for a long time so there is a lot to learn there technically. But, when it comes to user experience, they haven’t cracked the nut either, forcing traders to use bewildering number of charts and numbers on multiple displays and input devices to trade. So the emerging consumer real-time stream developers will have to break new grounds ourselves.

  donpark, A "Karriem" Khan, and Mike Wilson are discussing. Toggle Comments

   
  • 

    Mike Wilson 6:44 am on July 9, 2009 Permalink

    Well, people can absorb both far more and far less information than they think. Following about 350 people is a nice sweet spot for me while I’m online.

    Financial data streaming is an interesting case of “if you dump the data at them, they will figure out what to do with it.” (Ok, it’s not “if you build it, they will come” but close.)

    The data overload can be mitigated pretty well with an effective software layer. TweetDeck’s columns, ThinkOrSwim’s analytics, etc. But “the naked stream” I think needs to be classified as a tool rather than an end product for users.

    Hmm… still a half baked thought on my part.

  • 

    A "Karriem" Khan 4:24 pm on July 10, 2009 Permalink

    Can I buy your Party Ticket to the August Capital Party

  • 

    donpark 4:38 pm on July 10, 2009 Permalink

    It’s not transferable and the ‘ticket’ is a wristband which can’t be taken off w/o cutting. Sorry.