Decision made (finally!).
I split out the HTMLView into separate modules - one for GTKHTML and one for Mozilla.
This way, you can choose which one you want to use, or not.
Doing it this way removes a dependency on an external library if you don't intend using an HTMLView in an application. For example a typical game wouldn't need it.
I believe (perhaps mis-guidedly) that this now makes the GTK module that bit tidier and self-contained (only core GTK specific stuff is in the GTK module).
btw, if you try to run an app that creates an html view that hasn't imported one of them it will throw an exception stating such. (better to have "nice" error messages, me thinks)
:o)
I split out the HTMLView into separate modules - one for GTKHTML and one for Mozilla.
This way, you can choose which one you want to use, or not.
Doing it this way removes a dependency on an external library if you don't intend using an HTMLView in an application. For example a typical game wouldn't need it.
I believe (perhaps mis-guidedly) that this now makes the GTK module that bit tidier and self-contained (only core GTK specific stuff is in the GTK module).
btw, if you try to run an app that creates an html view that hasn't imported one of them it will throw an exception stating such. (better to have "nice" error messages, me thinks)
:o)