origyn or odyssey

[salvatore]

as I understand update odyssey is very difficult even for experienced programmers I talked to one of them8 recently) so why not take origyn into consideration, who wants to use aros natively currently cannot do it with profitable origyn is not odyssey but it worked for a long time after its abandonment, for videos you can always create scripts that activate mplayer

what do you think

[wawa]

orygin engine (webkit somewhere around 2009), along with its aros front end: aros owb is pretty outdated, but still a part of contribs. odyssey is a few years newer webkit engine than orygin was based on, its aros version is the newest webkit found on amiga like systems. botha are actually kind of maintained. but is is unrealistic to think its easier to update the older engine than the newer.

[Amiwell]

ok i understand

[Amiwell]

I thought it was easier to work with origyn

[wawa]

orygin (aros owb) frontend is less complex, which might be a btetter starting point to adopt an updated engine while resigning on odyssey's features. but its already complex enough..

[Amiwell]

I do not know what to say now to enter some sites I am also using puppy linux on a flash drive, resetting aros and entering the linux environment, about odyssey something is moving so much to know

[Amiwell]

@wawa

but do not open a bounty,at least we start to pay something in anticipation that someone can work on it seriously, we need to talk to someone in particular about these things

hi

[Yanosh]

I'm not a coder, so I don't understand much of this... but what's so complex updating Webkit on OWB? Why our gui can't work on a newer version of Webkit?

[miker1264]

It has been said before that updating a web browser is not a trivial matter even for experienced programmers. It's probably much like updating Mesa/Gallium drivers. It's labor intensive and time consuming. There are only a few people that could handle that and they are very busy with other important projects for AROS 64bit.

It's not that an updated web browser is unimportant but there are more important things to do at the moment. I have no experience with web browsers so I wouldn't take on that task. And I have many smaller projects to finish right now. And I consider myself to be a junior programmer.

It's important but everyone's already very busy.

[Amiwell]

but meanwhile opening a bounty would not hurt, maybe the sum collected could attract some programmer like it happened with the very first version of owb, I don't want to force the work that is being done but to lay the foundations for a project

[deadwood]

It has been said before that updating a web browser is not a trivial matter even for experienced programmers. It's probably much like updating Mesa/Gallium drivers.

From my experience (and I brought both Mesa and Odyssey to AROS), updating Mesa is "walk in the park" compared to updating WebKit engine in Odyssey.

[Amiwell]

 

[wawa]

even though morphos glue code is mostly separated from the webkit engine in a separate set of files, heck a different dir, there is still enough, that is interwoven and one needs to know a lot about how these interface. as you see even morphos team seems only to be able to fix their old version probably partly backporting bits and pieces from a newer engine.

speaking as a noob, this is all a whole lot of mess when debugging and stuff and we have nit even proper meand to do that with such a huge apps it seems.

[Amiwell]

it's a huge job