Re: [MiNT] www-browser engines (was: This must be an gcc / ld error!)

["Ole Loots" <ole@monochrom.net>]

Hello,

Am Sa, 29.05.2010, 11:04 schrieb Paul Wratt:
>>
>> Have you checked out the SDL-port of Origyn? It's based on WebKit and
>> targeted at embedded devices. An Amiga-port already exists. IMO Origyn
>> would be a better choice than NetSurf if the speed is acceptable, simply
>> because it has a really big userbase. Also, it supports Javascript which
>> I suspect is a lot of work to implement in NetSurf.
>>
>> Jo Even
>>
>
> I have investigated Origyn. It is a really good option especially now
> that webkit is going through size an speed enhancements, both will
> increase its usability on low spec machines.

I did not know about Origyn, but I heard about WebKit, of course.
I checked both websites, netsurf and the official WebKit page, and somehow
the Netsurf page grabbed my attention...

I thought the WebKit page is somewhat confusing... and I couldn't get an
quick overview about the situation on how it would be portable to other
platforms. It seems to be more complex...

I should also have a look at the Origyn webbrowser,... But it seems
webkits porting requires a lot more coding just for a PoC... Maybe that's
not true for SDL framebuffer ports...?

Speed Improvements often comes with higher usage of the system resources -
If these resources are not available, then these "modern" speed
improvements will not work well. I think the speed is coming with
utilisation of many system resources (large memory blocks, too) :)

I really don't know which way would be the right way, but somehow I like
netsurf:

- It is coded with RiscOS in mind
- It hast support for relative wide spread web standards
- It has some developers
- It is coded in C (not C++)
- It seems to be coded clean and really portable.

I also ported SpiderMonkey for Atari - so I thought maybe this missing
part could be integrated somehow... maybe we could push the JS integration
somehow ;) But to be honest, the netsurf developers say: "It's a long way
until JS integration". BUT it parses the HTML code into a DOM tree -
something which is not done by the well known Atari browsers higwire &
LoA.
This seems to be a must for modern JS webpages...

If someone forwards good arguments for having a closer look at
WebKit/Origyn port (from the developer / porter point of view) I would
like to have a deeper look at it :) Somehow I can't sympathise with WebKit
today...