Brendan Miller wrote:
Realistically, most mom and pop users are going to be leary about
installing
another browser on their system, and some will even be confused about which
browser they need to start up for which web application. Comparatively,
plugin installation is relatively automated and transparent to the user.
Most users are already familiar with a number of plugins (at the very
least,
flash). On the application developer side, displaying XUL to IE users would
be as simple as detecting ie and redirecting them to a page that contained
plugin tags pointing back to the XUL page they were redirected from.
Simpler than that, even: you can set up an activex component as a embedded
mimetype handler for the XUL MIME type. I've discussed this possibility
before, and it's technically feasible: just nobody has stepped up to do the
work. In order to make it useful in the real world, we would really have to
use an .exe style ActiveX control and use the regular Firefox profile
information (cache and whatnot).
via a plugin? Just as importantly, after all of the non essentials had been
stripped out, how large would the plug-in be?
It would be XULRunner (4.5MB on Windows), or Firefox (5MB on Windows).
--BDS
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
