Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Gulliver on January 22, 2010, 06:24:11 AM
-
Is it possible to develop an IBrowse plugin for CSS?
IBrowse supports plugins, so i was thinking, if it was possible to create a plugin that allows proper CSS web viewing?
If technically possible then we could create a bounty for it.
-
Theoriticaly it sound possible after all that's what the plugins are for.Practically now it is different.If the browser does not support css internally i don't think a plugin could make it render the pages that have css.
Who knows?
-
I would suppose the success depends upon how the browser interacts with the plugin. If the plugin intercepted and processed CSS, then converted it to HTML and JavaScript for the browser to parse, that might work.
-
How fast could that be for machines haveing a 68040 ?We are talking about classica amiga enviroments i think right?
-
I believe the idea of a proxy to filter/convert CSS stuff for processing into IBrowse-friendly form was mentioned in another thread, it sounds almost doable if you don't mind passing your traffic through a PC running the proxy first. The additional processing if it had to be done on the Amiga side might not be so horrible, if it's possible. It's not like it'd have to reencode images or anything.
-
Is it possible to develop an IBrowse plugin for CSS?
IBrowse supports plugins, so i was thinking, if it was possible to create a plugin that allows proper CSS web viewing?
If technically possible then we could create a bounty for it.
I think the answer would be have to be yes.
Look at the Flash plugin. It simply takes over the embedded portion of the screen. So I would presume that would be the extent of your CSS plugin.
What sort of cooperation the plugin feature supports? That were what were so important, IMO.
-
Is it possible to develop an IBrowse plugin for CSS?
I'd say no.
-
I think the answer would be have to be yes.
Look at the Flash plugin. It simply takes over the embedded portion of the screen. So I would presume that would be the extent of your CSS plugin.
What sort of cooperation the plugin feature supports? That were what were so important, IMO.
Depends on how the plugin is invoked. Existing examples are invoked after the HTML is parsed and the various embed / object / whatever tags are discovered, by which time, the page has already been rendered.
-
You know, it hit me that one could put up a proxy box equipped with the tools necessary to de-modernize HTML and CSS streams to something palatable to iBrowse. But services like this already exist in the form of alternative mobile browsers, like OperaMini and Bolt.
My head is too fuzzy right now to follow along the logic train here. But it seems to me that I am fussing about with two potential solutions: port an existing mobile or small-footprint browser which uses a proxy system to simplify the stream, or build a proxy which works with Amiga browsers to do the same.
The idea seems neat. If I had a class towards which I could apply the second solution, I would go for it. Alas, otherwise I have not the time to devote to the idea.