Hello 

On 02.02.10, you wrote:

> 
> However, as that work is extremely likely to require far more effort
> than a native Amiga OS 3 port (particularly given Chris' comments about
> the likely difficulty of backporting his Amiga OS 4 port) our strong
> preference is for a native port.

Of course first Artur begin to port the netsurf MorphOS Version, it have no
Cairo and
so should be less overhead and fast.
Also MUI (Morph OS netsurf use )is a nice looking skinnable GUI.Reaction GUI
(OS4
netsurf use), look very
very ugly on MOS, amiga OS3 and is not here on AROS.Reaction is total closed
source and not furtherdevelop and it contain Bugs, on amiga OS3 times there
are near no programs written with that GUI.
Most use MUI(so there are lots classes here) and some Storm Wizard.

AROS is btw a free amiga
compatible OS that run good Linux hostet, or in  vmware/Virtual Box or
native that
can use on X86 or some PPC Hardware.

To make a Netsurf for all Amiga that look nice, the MUI Interface is the
best choose.there is for AROS and 68k a opensoure solution here.

When port netsurf to AROS everybody here can test it.OWB is port to AROS.
Here is a nice ready to use install.

http://vmwaros.blogspot.com/2009/12/icaros-desktop-12-ready-for-download.html

Artur get the netsurf for MOS compile and ask for help, so normaly i spend
some hours to make the MOS build correct working on AOS3.

But i see that the MOS Dev of netsurf(itix) do not change netsurf to new
plotter interface and seem give up netsurf.

I see then that it was possible to build a netsurf for SDL and i suggest to
try this out.
And yeah great, after a few hours Artur get the SDL netsurf working.

first versions have wrong colors, so i add code that the Pixelformat work
well and sdl key repeat.I post all this changes btw to List here and some
of them are add in main source.

I read not that there is not plan to make out of the framebuffer netsurf a
full browser and netsurf Team does not like that and support only native
GUI and plotter interface.

the SDL Version miss much features to be useable

Artur enhance then the SDL version with nicer GUI, bookmarks, Hotbuttons add
download file and video View, so all what a user need important to surf is
in.Artur add also code now that shift+cursor and CTRL+ cursor work as
netsurf docu show.

I do some work in my spare time to update for AOS SDL, GCC and unix API lib
for amiga os 68k to make a port of a program same easy as for other Linux
System.

But when there must write a plotter Interface or a native GUI for somebody
that have not much fun in much programming but want use Linux software on a
amigaos its faster to use SDL or write 
a xlib to amiga OS wrapper and when this is done then can use xwindows based
programs without the overhead of the network driven xwindows server.maybe
its then easy to run chrome, firefox, netsurf and other Software.

gtk qt Blender and other all use xlib.this calls need wrap to native OS
commands or maybe SDL 1.3.

""""
s = DefaultScreen(d);
 
                        /* create window */
   w = XCreateSimpleWindow(d, RootWindow(d, s), 10, 10, 200, 200, 1,
                           BlackPixel(d, s), WhitePixel(d, s));
 
                        /* select kind of events we are interested in */
   XSelectInput(d, w, ExposureMask | KeyPressMask);
 
                        /* map (show) the window */
   XMapWindow(d, w);
 
                        /* event loop */
   while (1) {
     XNextEvent(d, &e);
                        /* draw or redraw the window */
     if (e.type == Expose) {
       XFillRectangle(d, w, DefaultGC(d, s), 20, 20, 10, 10);
       XDrawString(d, w, DefaultGC(d, s), 50, 50, msg, strlen(msg));
     }
                        /* exit on key press */
     if (e.type == KeyPress)
       break;
   }
 
                        /* close connection to server */
   XCloseDisplay(d);
 
   return 0;
""""

> 
>> so there need not write and keep upto date a own plotter interface
> 
> I really don't understand what is so difficult here.
> 
> Firstly, the plotter API is about as simple as it can possibly be --
> it's a very cut down and situation-specific variant of any vector
> graphics drawing API.
> 

The most problem is when there is something change to understand how it work
again.
every change even if it change can introduce new Bugs.

maybe thats the diffrence between a good programmer or a not so good
programmer.

a good programmer can maybe understand nestet ways correct fast by look at
code, how it work and wy it run slow, a not so good programmer need use a
good debugger and single step.

I dont want use develop on other than amiga os 68k, because here i have fast
full membound check and memtracking and nice debuggers.

and it help, when the code is short and direct written.
less code less bugs...

Its a hobby and then can use the system with that get fastest result.

and when see much code that do simple actions, motivate not to code

> 

> Additionally, when the most recent set of major changes to the plotter
> API were made, we went out of our way to ensure that platform frontends
> were not irrevocably broken. Certainly, we didn't quite succeed here,
> but I'm pretty certain that the remaining minor fallout did not cause
> frontend maintainers any great amount of pain.
> 
> 
> J.
> 
Regards


Reply via email to