I'm interested in helping to port the beast.. i once had a look at the khtml sources myself, but decided its way too much work for one man alone (who doesn't have 24 h a day for porting.. ).

So.. who have i to hug for becoming a part of the KHTML porting team? ;)

_________________
Regards, Cyborg.
AmigaOS4 development team member

"In the beginning was CAOS.."
-- Andy Finkel, 1988 (ViewPort article, Oct. 1993)

It's very nice to see a new development for the amiga-like systems in general. Here are some suggestions and others:


- Please not use GTK, use native widgets, see what occured with QNX: Photon (an interesting an fast widgets system of QNX) Its now being marginated because people do easy ports with GTK, so now QNX seems like a linux distribution. Amiga-like system must have their own identify using their widgets and others, not a linux-qannabe because its the easy way of getting tons of software, those things kill the platform, a lot more than emulators.

- Why not use MUI instead of reaction? MUI is supported natively in AmigaOS 3.x, MorphOS, AmigaOS 4.x and AROS (using a GPL MUI clone). MUI seems better in many aspects, its more difficult than reaction but provides interesting advantages, ask to some MUI programmers about this (Im still dont know about that too much).

- About modernizing aweb interface: For me the aweb interface seems old and lack of some widely used features, remembers me to mosaic or something....

- What about collaboring with AmiZilla? There are the same main goals...



As you can see, I was repeated the last one because you dont replied me in the other message, and I was not said nothing about the other replied interesting ideas.

Here is the MZ's equivalent of this thread:
http://www.morphzone.org/modules/newbb_plus/viewtopic.php?topic_id=2981&forum=9

Quote:

So.. who have i to hug for becoming a part of the KHTML porting team? ;)

That won't be necessary. Just read this: aweb.sunsite.dk/dev/docs/policy.html

Quote:

Please not use GTK, use native widgets, see what occured with QNX: Photon (an interesting an fast widgets system of QNX) Its now being marginated because people do easy ports with GTK, so now QNX seems like a linux distribution. Amiga-like system must have their own identify using their widgets and others, not a linux-qannabe because its the easy way of getting tons of software, those things kill the platform, a lot more than emulators.

The goal is to have KHTML as a completely Amiga like part of the OS. There will be a few libraries (khtml.library, maybe) and a finished browser would look like an Amiga browser. No hokey stuff with GUI emulation. Plain Amiga GUI engines will be used. It will look and feel like an Amiga program.

Quote:

Why not use MUI instead of reaction? MUI is supported natively in AmigaOS 3.x, MorphOS, AmigaOS 4.x and AROS (using a GPL MUI clone). MUI seems better in many aspects, its more difficult than reaction but provides interesting advantages, ask to some MUI programmers about this (Im still dont know about that too much).

It's very likely that AWeb 4 APL will use MUI for the reason that MUI programs can be run on all AmigaOS clones. Not as much if it's a better GUI engine (which I won't discuss here), but simply because it runs where we need it.

Quote:

About modernizing aweb interface: For me the aweb interface seems old and lack of some widely used features, remembers me to mosaic or something....

AWeb 4 APL will also likely sport a completely different interface. This hasn't been decided yet as the important task right now is to get KHTML into a usable state on AmigaOS and make it developer friendly.

Quote:

What about collaboring with AmiZilla? There are the same main goals...

Sorry, missed the question...

AFAIR, Amizilla is a funded effort to getting Mozilla/Netscape ported, which I think is technically non-optimal and has a direction which is not as developer friendly. It just doesn't really work in the same direction. Also since money is involved, there will be problems in splitting the income fairly. If it were me, I'd probably send that money to DigitalDisaster to fund the development of that G5 board instead.

Quote:

How about starting a bit smaller and listing the library and tool dependencies for a KHTML port? Some of us may be interested in porting individual libraries and tools.

You might want to follow this thread: http://lists.sunsite.dk/cgi-bin/list?list=aweb-dev&cmd=threadindex&month=200410&threadid=ijcjmbglcphjlibdfkmj

@MHK

Not only Mozilla/Firefox, the money it will be for the people that do a updated to actual standards amiga browser and ported to other platforms... So probably these money can go for the one(s) that port KHTML and do a browser (that is the easy task comparing with port khtml).

Its very interesting doing it developer-friendly, what about doing a class for MUI or something?


What are the main differences of Webcore and KHTML? Why not port Webcore?

Last edited by timofonic on 21-Oct-2004 at 11:58 PM.

Quote:

Its very interesting doing it developer-friendly, what about doing a class for MUI or something?

It might get done that way. I don't know yet how it will work. It needs to be as flexible as possible.

Quote:

What are the main differences of Webcore and KHTML? Why not port Webcore?

We might just do that. Webcore is interesting in that it represents what needs to be done in the porting process. If Webcore didn't exist, we might not have any blueprint for inspiration and it wouldn't be done.

Regards,
Henrik Mikael Kristensen
AWeb Development Team

I think that doing the library/libraries later the MUI class(es) will be the most flexible solution. This is as is done in many libraries with their mui equivalents (render.library I think and some others).


So what is webcore, the macosx dependant part for use KHTML?

About the link to those messages of the mailing list, when I click on one of them it says
Quote:

You don't have permission to access /cgi-bin/ on this server

What about put this information into the webpage in a detailed form? Maybe the webpage needs some logged-wiki (only can edit it the registered ones) with the available information or something...

Last edited by timofonic on 22-Oct-2004 at 01:48 AM.

Quote:

That won't be necessary. Just read this: aweb.sunsite.dk/dev/docs/policy.html

Application sent.. to you, i guess

Oh, BTW: Ignore the subject of the mail... of course i meant "application" and not "appliance".. just noticed it too late after the message was already sent

Last edited by Cyborg on 22-Oct-2004 at 10:47 AM.

_________________
Regards, Cyborg.
AmigaOS4 development team member

"In the beginning was CAOS.."
-- Andy Finkel, 1988 (ViewPort article, Oct. 1993)

Posting the link again. This one works every time for me:

http://lists.sunsite.dk/cgi-bin/list?list=aweb-dev&cmd=threadindex&month=200410&threadid=ijcjmbglcphjlibdfkmj

Or try this one:

http://lists.sunsite.dk/cgi-bin/ezmlm-cgi?1:sss:3075:200410:ijcjmbglcphjlibdfkmj#b

Quote:

So what is webcore, the macosx dependant part for use KHTML?

Webcore consists of KHTML, KJS and KWQ. KJS is the javascript engine and KWQ is the middle layer between KHTML and MacOSX. This one is the bugger that basically needs to be rewritten. It's only a rough explanation though.

this sounds like we infact can have a browser anytime soon.....

join up guys and make us a browser that we can be uptodate with!

rock on!

_________________
See my blog and collection website! . https://www.blog.amigaguru.com