Explicitly not supported.
^^
Yes, the way forward is open standards!
However, are there some serious efforts in the direction of an IDE like Adobe has for flash, to create HTML5 animations, and working with js?
That you have successfully ported Webkit to FLTK is just amazing!
It's the obvious way forward for FLTK browsing. And I've wanted Dillo improved to at least get the site formatting better implemented.
But to have Webkit, we have a standard, complete implementation of HTML5 and js. Which is just magnificent!
To use FLTK Webkit for a full-time browser is something I want to do. But the only browser I've considered replacing with Firefox is Midori. But it constantly crashes.
Midori has a sidebar for plugins, like script-addons plugin (js addons), and style-addons plugin (css addons).
And then has a C API for writing plugins.
Just with these plugins, and the plugins for ad-blocking and script-blocking, I could start using Midori -- if it didn't always crash, that is.
It comes by default with these excellent plugins, so it's easy to get set up.
From the DESIGN file of Fifth:
No native video support. Every embedded player generally sucks. Instead,
we will offer two buttons in place of HTML5 video elements: download
(as $GOD intended) and stream (ie, launch in your favorite player such
as mplayer).
I really like that, but can't we have mplayer in slave mode for an "embedded" player?
And if there are plugins, we could have a simple plugin for extracting the video from a flash file for streaming/downloading.
Then we could have it act just like any browser, by embedding mplayer (of course just by executing the binary).
I like all of the
http://fifth-browser.sourceforge.net/features.htmlI will download the latest TC to get Fifth and test it soon (as compiling it would take too long).
But from the screenshots, I have one thing I would like added: to have downloads in a drop-down window, instead of a whole tab. But perhaps there already is such a thing..?
And of course for speeding up community contributions, and involvement, plugins would be great.
No need for an extensive API, just having an icon added for a plugin, and a drop-down window.
Wait... if you want to access FLTK Webkit from a plugin, you'd need to have it dynamically linked...
Well, FLTK Webkit is great, and I will be able to implement it in my GUI integration tool (written in FLTK), so plugins for the web can be written in my own plugin API.
So you would have a complete GUI environment, with web browsing integrated.
But I'm not sure about it, as I've always planned to have just an "information browser", with link containers/menus presented as drop-down windows.
To have text presented in 60-80 characters wide, for easy reading by pretty much just placing your eyes in the middle of the text, and scrolling.
Anyways, great work!