[Design] Thoughts on a browser parcel

[Heikki Toivonen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't think so. wxMozilla is (mostly) about embedding the Mozilla
engine inside a control that can be used easily from wxWindows framework
and wxPython. Sure, you could easily embed that in Chandler, but there
would still be tons of UI work that would need to happen to drive the
browser (buttons, URL bar, bookmarks, history, preferences, ...) - in
addition to doing the integration piece that collects interesting
browsing information and stuffs it into Chandler (and vice versa).

What Mitch (and I and several others at OSAF) think is better is to have
the browser(s) evolve on their own, and write *just* the integration
part. The downside is that you need to write the integration part for
every browser that you care about, and it might not be possible for some
closed source browsers. (It should be enough to write just one browser
integration parcel on Chandler side.)

Of course nothing is stopping you from creating a Chandler parcel that
does integrate a browser, but that just seems unnecessary work to me,
and you would not benefit from the UI work that the browser developers
were doing.

kapil thangavelu wrote:
| An alternative (better, imo) starting pointing would be wxmozilla

- --
~  Heikki Toivonen
~  PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x83FE26EC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zQBjb8x8KoP+JuwRAltZAKCSML6+fdVIThCGkwDa1ifus+a7qQCfdvrk
Yn8aSh/Ki/KMJeYt4dopmP4=
=ap0T
-----END PGP SIGNATURE-----