View Single Post
Posts: 114 | Thanked: 201 times | Joined on Apr 2009
#998
Originally Posted by xiojason View Post
I've developed an alternative, more generalized mechanism for launching Tear instead of osso_browser.
Here are some proposed patches for the browser-proxy script, which fix a bug, improve performance, and add a few new features.
  • 01-fix-multiple-window-bug.patch: workaround for the bug where trying to open a URL when Tear isn't running results in two browser windows.
  • 02-use-gobject-instead-of-gtk-for-main-loop.patch: use a GObject main loop instead of the GTK+ main loop. This reduces memory usage by a few megabytes and removes the dependency on python2.5-gtk2 (you now need python2.5-gobject, which is already installed if you have python2.5-gtk2).
  • 03-use-python-dbus-interface-instead-of-dbus-send.patch: use dbus-python's interface to D-Bus instead of running the external dbus-send utility. Might be a small performance win.
  • 04-add-continuous-mode.patch: adds support for staying open in the background, which makes opening URLs via D-Bus faster. Has about a 2 MB memory footprint when doing so.
  • 05-kill-browserd-if-we-launched-it.patch: if we have to start browserd when launching MicroB, kill it when MicroB exits instead of letting it continue as the script currently does. The script has to stay running while MicroB is in use, so more memory is used when MicroB is running and continuous mode is off, but we save memory when MicroB isn't in use and browserd is disabled.
 

The Following 6 Users Say Thank You to steven676 For This Useful Post: