Wow, they are even smaller then we are, less POSIX and it was more or less a one man team. He posts at AW.net and asks what has taken us so long to get a port. Maybe he can halp share some tips to get it working?

http://www.riscos.info/unix/firefox/

http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=12922&forum=4&start=0&viewmode=flat&order=0

I have Firefox running on my 300Mhz RiscPC. It is slow
and very unstable,but very complete..

The real advatage of the RISC OS port is that is uses
a library that translates X windows calls to RISC OS
wimp calls. It is created with the GCCSDK wich runs on x86
linux and makes it possible to port unix programs
without modifications to RISC OS.

Wow, we need something like that!

we have too much faith in bounties, mugs and tshirts.

A screenshoot :)

 Attached file(s) 

Now we need to open a bounty for a RISCOS emulator

micken,

Do RiscOS have Java ?

Gunne

@Gunne

Yes there is a fully working recent Kaffe port without awt. And we,yes I am a riscos user,have a old jvm with awt that Acorn produced, but it is version 1.0.x. It is usable in as a plugin in most riscos browsers at least in Oregano and Browse.

X11 -> MUI API wrapper:
http://www.aminet.net/package.php?package=dev/misc/libx11.lha

Old and far from perfect but proving it's possible.
People really have no memory :-)

So contact the developer and have it worked on again! Or point him to the bountie and see if we can get more money into it!

He hasn't port FireFox to RiscOS but has port RiscOS to FireFox...
The file is 17Mo fat because It has linked in static a lot of system libraries.

I'm not interested to port half the linux system to mos. A khtml engine in AWeb would be enough and far lighter. Because If for example you need to load 17Mo of linux stuff to show an URL directly in an ambient window, It's more in the windows's way of thinking

[ Edited by tetuzo on 2005/6/22 18:06 ]

I think it is good to get unix stuff to be ported. It is better to do this without changing the source.

In MorphOS we don't need to have everything static linked, but in RISC OS it is the only way , I think.

Right. But if I would have a choice, I would like to use 50MB FireFox than 500kB AWeb...

I don't believe, someone will port khtml for our platform in reasonable time.

We just need some components like css/khtml to begin. It's a little job for a ten members team.
Everybody say that they need a good browser but no coders joins the aweb team.

RiscOS has fewer coders than us, if you want a good browser, just code it and if only ten people think like you, It can be done within 6 months.

MOS has enough developers to do this, this is not the problem

Quote:

Amen! If MorphOS is a different operating system, it should have it's own software. I'd rather use my own limited tools.

Quote:

If you can write good unique software yes, but there's already 3 browsers which run on MorphOS and none of them are even close to Firefox.

There's no point developing a huge piece of software from scratch to do something everyone else can do already if it'd be quicker and easier to port it.

they have less coders and users on RiscOS but they are united and don't spend time on useless wars and stuff. They are mature. The amiga community is not. Too many super-egos in our community. they prefer to masturbate on their little pieces of code instead of working together.

[ Edited by SoundSquare on 2005/6/23 12:38 ]

SoundSquare wrote:

Bonjour, (Je suis dans le 20ème)

Quote:

That's not quite true, they too had wars but they seem to have united and calmed down for now.

Quote:

that's what i just said, they are mature now. It's not gonna happen in a near future for the amiga community.

The paihia project is an perfect example of re-coding existing amiga stuff.
Coders doesn't want a browser but their own browser.
Why not just helping AWeb team, the only open-source amiga browser???
If FireFox and lots of other applications can be ported without changing anything, why not, but I'll never be an amiga browser, just a 17Mo fat static linked elephant on a 10000$ bounty!!!

[ Edited by tetuzo on 2005/6/23 18:24 ]

Reasons why not help AWeb? Because it needs to be rewritten anyway.

Not all need to be rewritten... The goal is not to port konqueror or safari, just the rendering engine.
The layout and many other stuffs won't change.

For a browser the main part is the render engine.
And since all current amiga browsers are not uptodate
it really does not matter if you start from scratch
or put your energy in one of the old ones.

But AWeb would be really the last of choices if
I could program in c ... I cant think of a single
feature of it to keep ... It's unconfigurable, ugly,
non-intuitiv ...

I'm a big fan of Voyager ... but I fear it's dead,too

I think there are only two projects that can lead to
a modern browser ... Amizilla (First MUI/GTK stuff is compiling)
and Pahia (sorry not sure this is the right name)
written from scratch with the important things done
first (CSS,JS,etc) ...

Quote:

Why are we writing our own browser and haven't joined one of the porting teams?

1. Porting a visual application or library such as Mozilla or KHTML has never been done before, despite many attempts. Nobody is sure that it's even possible.

2. Paihia is a lot smaller and faster than Mozilla and KHTML.

3. The leadership and overall direction of the Amizilla project seems disoriented and confused. Progress reports are few and there seems to be an information black-out whenever anybody asks about the status.

4. AWeb/KHTML seems rather well organised, but then, see (1).

5. Programming and designing new code is more fun than porting.

There is simply no quick route to a web browser with proper support for modern web standards. Things are going to be difficult and complex and timetaking either way you try it.

The simple fact is that our way is certainly no more timetaking than a port.

A quick risk/benefit analysis concluded us to start work on Paihia. Other people decided on a different route, but even had we all joined forces regardless, then even with an extra dozen manhours per week, with the cost of coordination and management of the project it wouldn't make masses of difference.


[ Edited by smithy on 2005/6/25 12:19 ]