Dashboard uses WebCore to do it's rendering - does anyone know if it could be fooled into using Camino instead - this might allow a Dashboard widget to do something like a login, then "transfer" the page to the Camino browser, and since the browser didn't change, authentication based on the HTTP header would (theoretically) still work.
Camino is an application, not a framework, so 'using Camino to do rendering in another application' doesn't make sense as a concept. On top of which, it's not like all applications using the same framework share all the same state information--the security implications if they did would be staggering (would you want any app that uses WebCore to have access to every secure site you went to in Safari?).
So what you'd need is an API for Camino to accept some serialized state information (a cookie, in most cases) and turn that into the corresponding internal application representation. Then you'd need a widget that did the reverse and sent the information to Camino... but it wouldn't matter what it used for HTML rendering. There are plenty of security issues there as well in terms of the two processes trusting each other, but you could presumably solve them if you really wanted to be able to have your logins be a two step process (bring up dashboard to login, then use Camino to surf with your authenticated status) rather than one step (log in and surf using Camino).
-Stuart
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
