On 4/4/11 9:02 AM, Glen Gray wrote:
I'll need to know what my options are going forward and how we will be able to
control the browsers functionality (custom uri's trigger application launching,
restricted access to uri's based on users credits etc.).
Do I focus on using a swapping out GtkMozEmbed for a webkit browser or come up
with something different.
That is of course up to you. You could continue to maintain and use
gtkmozembed yourself, or in combination with other people who want to
try and maintain that code. You could switch to writing your kiosk as a
XULRunner app, or you could attempt to switch to webkit (plus all the
other libraries webkit requires, such as networking etc).
What is the current status as regards xulrunner 2.0 ?
This announcement has nothing to do with XULRunner 2.0. It does mean
that the next following XULRunner will not contain gtkmozembed or the
ActiveX control code.
--BDS
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
