On 15.01.10, you wrote:
Throwing such functionality into the frame buffer front end defeats its
purpose. It is not difficult to write a proper front end.
I think it is too difficult and need lots time for me.I need only look in
the amigaos Folder and the filesize and how often Chris add code to SVN.I
guess he work more than 500 hours on it yet.
So when i have maybe 10 hours/month time to code on netsurf, then 500 hours
are reach in 5 years.I dont have the patience to do a 5 year project.And
when not have enough time. then the train is loose.
luckily the SDL Netsurf miss not too much features so it can use without
I think btw write of a XUL backend for Firefox (which is btw availaible for
the common used AOS GUI System MUI)can do in less work and firefox can show
more pages(java frames).So when there is Netsurf in future not working with
SDL, i try better to get this working.
On amigaos there are no browsers that have CSS, but there are browsers with
some limit java script and working frames.ome pages NetSurf can show better
some pages can work with amiga browsers, (but they look ugly)
A great reason to use Netsurf or help on code is when it is easy and fast
compileable and keep upto date.
and thats now possible with SDL.
Luckily i need not resize window, i also do not resize window when i use
firefox on windows, because when i make a win smaller than 1024 i need
I have only a AMD64 3000+ (with real 1,8 GHZ)X86 CPU, here compile firefox
or OWB because of C++ over 50 minutes i think.And when port it, and change
headers,then much need recompile.
netsurf compile in only 45 sec and here make much more fun to keep it upto
date, than on this C++ monsters where need wait long time after every
And when the Netsurf come out with Cache i like test too.