The Future of JavaXPCOM

This is a public service announcement for those people interested in the future of JavaXPCOM. JavaXPCOM has been disabled and will likely to removed from the Mozilla source tree in the future. See Benjamin Smedberg’s newsgroup post for more details.

Please follow up (add comments) to the newsgroup post.

4 Comments

  1. Anonymous said,

    July 28, 2010 @ 9:57 am

    Hey Mark, I know with Gecko 2.0 you guys are making strides in add-ons registering with Fx, I’m wondering how things are going in relation to no-restart-if-you-write-a-special-manifest-or-something-file? It has been discussed on your blog earlier. I’m only asking if there is anything you can say, it might no be a good idea in case a news outlet caught wind of it.

  2. Mardeg said,

    July 28, 2010 @ 3:44 pm

    Bless you Mark and many blessings on Benjamin too, thank you :)

  3. Mark Finkle said,

    July 28, 2010 @ 4:26 pm

    @Anonymous – “No XPCOM restart after add-ons are installed” already landed. Also, restart-less add-ons are also functional in Firefox 4 beta 2. Any add-on can be restart-less, not just Jetpacks. See https://wiki.mozilla.org/Extension_Manager:Bootstrapped_Extensions

  4. Anonymous said,

    July 29, 2010 @ 8:41 am

    Cool. Yes those bootstrapped add-ons is what I meant. Goodluck with improving Fennec, I’m also excited by the growing power of Jetpack.

RSS feed for comments on this post