Hi

What do you think about opening bounty for a FireFox port for MorphOS? Worth of trying?

I agree with most of the folks here. OWB is way better then I expected!. I don't really think Firefox is needed.

Quote:

Let's say we wait with that until you've found someone actually capable and willing to start work on such a bounty. If amizilla is anything to go by, I wouldn't hold my breath.

Thanks for all your replies. I was quite suprised i have to say but I'm not dissapointed at all. So, when FireFox port to MorphOS is not needed at all - let's open bounty for HW accellerated Cairo :)

@pampers

Quote:

Fast cairo would actually be a nice milestone for a Firefox port since that's what FF is using to do its rendering.

You can laught at me, but I prefer to see new versions of Sputnik instead of FF :(

@pampers

That's a very good idea. OWB is really great. HW accelerated Cairo is what we really need right now.
Just my 2 euro cents ;)

Quote:

I'm not laughing at all.

BTW, I just Googled about it, and came up with:

http://groups.google.com/group/comp.sys.amiga.morphos/browse_thread/thread/a9f531f58b21528f

That was some time though. Marcin, are you reading this? Are you still with us?

Let's open 2 bounties and see how it works:

1. Cairo with HW support for Pegasos, Efika and Mac Mini

2. Native Thunderbird port for MorphOS

@takemehomegrandma

Old news... But I have a hope now!

@pampers

Look at bounties page. Do you remember this spring? "We need GTK! We need universal IM-client! BOUNTY! BOUNTY!" And so what? 150 euros for half of year. Look at list of open, but not assigned bounties.

What do you think now about new bounties?

[ Edited by mobydick on 2009/10/24 16:10 ]

@mobydick

Meaby we should do a little bit more of advertisement on the other MorphOS related pages? People might not be aware of bounty system in MOSZone?

I just don't want to wait until some will decide to do program X or Y. Meaby our community is too small to handle bounty system in proper way, i don't know..

When I started the bounty system here the plan was to give me access to the module to keep it up to dat, that never happened and Dave is to busy. So it basically sat and died. So getting more people to come look at it or know its here wont help solve much.

[ Edited by Acill on 2009/10/24 7:06 ]

Quote:



html 5 and javascript support is needed, in addition to flash, and other plugins

Maybe the guys of TenFourFox could be persuaded to help get Firefox to MorphOS

I think it is better to polish the existing browser that is already working on MOS - OWB - rather then starting another browser to port just from scratch. This all bounds capacities which even OWB does not have. There will hardly be any benefit of a Firefox port. Even more it will split interested devs to not know which browser they should continue. So better support OWB. Then no one has to dig out 6 year old threads

OWB for X64 should probably be our focus now.

Flash will always be problematic.
Pampers suggestion about hardware accelerated Cairo definitely deserves consideration.

[ Edited by Jim 25.09.2015 - 10:35 ]

>> There's nothing Firefox does that OWB does not once it gets flash support.

> html 5 and javascript support is needed

OWB has these of course.

> OWB for X64 should probably be our focus now.

You mean "our" as in "AROS/x64 users'"? ;-)

> OWB for X64 should probably be our focus now.

OWB for PPC should be our focus now as MOS for X64 is still years to go and we should not have to wait for the switch to X64 in order to get OWB updates.

That's for sure, we cannot let OWB fall behind current website technology and media types, or what's the point of having an outdated browser that can't load a proportion of websites as it doesn't support current web technology/features - You Tube currently is an issue, just one of a good few, as it can only be watched with OWB in fullscreen view, AFAIK, and the files cannot be downloaded using the scripts.

However, if there is not going to be an OWB update to keep up with current WebKit releases, considering Fab's current workload, and gamily life, and the incompatability of the current source code/JavaScript implementation, AFAIK, then a port to Firefox or some other browser should be seriously considered, IMHO.

If someone finds the time to port full Firefox then he should be able to upgrade OWB to get rid of the stoppers in a fraction of time. And who says that Firefox does not have other limitations? I prefer OWB, it is relatively well integrated in MOS and kind of unique to our platform.

I like OWB, I really do, but if this is where the OWB versions stop, then that would be something that needs to be side-stepped to stay current, that's my only concern.

Quote:

Gee Andreas, I should have specified X64 MorphOS as I have no interest in a perpetually unfinished operating system. ;)

And guys, Fab was pretty specific as to why further webkit based browser updates aren't going to happen on our platform, this includes Firefox, deal with it.
The current version of OWB works.


[ Edited by Jim 24.09.2015 - 14:21 ]

Quote:

Was he really that terminal about it?

Quote:

Isn't Firefox based on Gecko...?

>>> OWB for X64 should probably be our focus now.

>> You mean "our" as in "AROS/x64 users'"? ;-)

> I should have specified X64 MorphOS

As there is no x64 MorphOS, nobody can focus on OWB for x64 MorphOS now.

> this includes Firefox

As takemehomegrandma said, Firefox isn't WebKit-based.

> The current version of OWB works.

...as do the current versions of AWeb, IBrowse and Voyager ;-)

Firefox is just a slow, google-inspired bloatware monster these days.