Quote:

Stating the obvious, eh? If we get R600 AGP support for our G5 and this? Hey, the man needs some time for a vacation.
BTW - How much was the bounty?

[ Edited by Jim 22.05.2018 - 19:34 ]

> How much was the bounty?

See comment #30 :-)

Hmm, I had to do a zolty to USD conversion and then compare that the to euro equivalent listed to wrap my head around that, but that isn't bad.

Not a fortune, but still cool to see Mark get some compensation.
He is a great guy, and he's made some magnificent contributions to the OS.

Quote:

Not that it really matters, but it's zloty (złoty, to be precise). Zolty (żółty) would mean "yellow", while "złoty" means "golden".

Quote:

Sorry, Polish of all languages defeats me so often.
I should have checked that, but even a translation program would have left me clueless.
It gets worse if you try to use a Polish to English translator.
Curiously enough, German and French are comparatively easy, its probably due more to crappy programming then anything else.

Just out of curiosity, what are the roots of the language?
Many credit English, French, and Spanish as having common roots as so called "romance" languages, but there is a strong German influence there that doesn't always get acknowledged.

> Many credit English [...] as having [...] roots as so called "romance" languages,
> but there is a strong German influence there

There's a strong German influence in the English language because English is a Germanic language, not a Romance language.

Quote:

Good point, English is sort of a "mutt", born in part from the Anglo Saxon period, but with influences from the later Anglo Norman period (which explains the French influence)
So there are common points with the so called "Romance" languages (although some of these might reflect Germanic influences as well).
For a country that prides itself on its independence, it seems to have been occupied a fair number of times (from the days of Roman occupation on).

But that still doesn't tell me anything about the roots of the Polish language.
And I actually was interested in that.
Its one of the countries we didn't focus on in our educational system (actually, there were a lot of those).

Edit - So...why ask for education from you guys when I can just Google it? Fascinating, quite along history, and a Slavic base for the language (which explain why it sounds like Russian to me).

[ Edited by Jim 23.05.2018 - 19:00 ]

Hi everyone,

I just wanted to give an update on this project.

When I started working on the OWB JIT project, the source code I had available was for OWB 1.23, so that was the version my work was based on. I've successfully implemented the JIT for OWB 1.23, and as far as I can tell, it works without any hiccups.

Next step has been (and still is) making the JIT code work with OWB 1.24. Long story short, the Webkit version in OWB 1.24 requires more work to be done which wasn't necessary for OWB 1.23. I do now have a build of OWB 1.24 with JIT enabled, but there are still some sites that exhibit problems with this version. I however don't foresee these problems to take very long to fix. My hope is that some time next week, I can release a version of OWB 1.24 with JIT enabled for public testing.

Please note, however, that this public test will only have the first level of JIT enabled. In my own tests, the first level of JIT is about 3 times as fast as the non-JIT version in a graphical Javascript test. The second level of JIT is still on my to-do list.

Excellent news !!!

Thanks a lot bigfoot for these informations and for this great project !!!

Quote:
That's the version I use, as the OWB v1.24 that was released with MorphOS v3.10 just doesn't, for me at least, "cut the mustard"/work well, and on some websites it works a lot worse on than v1.23 does, so for me I'd like to get to use the v1.23 initially as/when you feel happy to let us all have a go with that.
Quote:
You've certainly worked efficiently to have made such progress in such a short space of time .... SuperMan ... err. SuperMark
Quote:
You the Man !!

Quote:
Noob question, how many levels of JIT are there?

This is so cool I feel frozen. I cannot wait to try out the beta.

Quote:


Excellent news!

Eventually would be nice if all three versions of Odyssey could be merged into one code base.

Quote:


Whatever. In RGB values golden is actually yellow.

hexaco1-1_2018-06-16.png

Quote:

Of course, you read the right article on
wikipedia

Yez, koszer covered much of that and some other points in a few exchanged PMs.
Facinating country.
Here, outside of native americans, history is so much briefer.

It's like a science experiment where we are patting ourselves on the back in success when we have just started.

Just curious... would it be possible to re-use some of the PPC JIT JavaScript VM work done on TenFourFox?

http://tenfourfox.blogspot.com/
http://www.floodgap.com/software/tenfourfox/

I know that's the Mozilla codebase rather than the WebKit codebase, but I also know he's done a lot of work on PowerPC-ifying its JIT JavaScript VM.

> would it be possible to re-use some of the PPC JIT JavaScript VM
> work done on TenFourFox?

There was an attempt by the Leopard WebKit author some years back but didn't work out apparently:

https://morph.zone/modules/newbb_plus/viewtopic.php?forum=3&topic_id=9462&start=13
https://morph.zone/modules/newbb_plus/viewtopic.php?forum=9&topic_id=9950&start=40

> he's done a lot of work on PowerPC-ifying its JIT JavaScript VM.

As "PowerPC-ifying" a JavaScript-to-x86(_64) JIT compiler essentially equals rewriting it from scratch, the TenFourFox author did exactly that, i.e. rewriting a JavaScript-to-PPC JIT compiler from scratch :-)

Surely it wouldn't do any harm for someone from the MorphOS Development Team to approach Cameron Kaiser, if he's still the main maintainer and person to offer any useable assistance with TenFourFox, to be able as the legal owner of such code, and offer any agreement to authorise the MorphOS Development Team to utilise such code.

Quote:
Surely there is also no harm in asking Bill Gates for the Windows source code. Unfortunately, it would yield about as much results.

You cannot just use the Javascript interpreter / compiler from one web browser and "bolt" it on to a completely different web browser engine. If it was easy, you can rest assured that internetzel would have done it by now.

Considering that another Javascript JIT compiler has already been in development for MorphOS and should become available in the foreseeable future, as stated in this very discussion thread, what would be the point in starting work on porting another one? I am sorry but what you are proposing makes no sense.

> authorise the MorphOS Development Team to utilise such code

TenFourFox is licensed under MPL2 open-source license, so no authorization required.

Quote:
My thought is that all of code that relates to TenFourFox may be useful to developers for OWB, as a reference, AND , as Andreas_Wolf has since pointed out, Quote:
Quote:
As I mentioned above, I wasn't just thinking of only the JavaScript, that I am fully aware Mark Olsen (bigfoot) is currently working on for us, but the whole code that Cameron Kaiser has worked on, as he may be sympathetic to our cause as there are not so/as many PPC systems left to utilise any PPC code, let alone his PPC code, and he may like to see it still get utilised by others, and offer us some help in understanding it, implementing it for our benefit, considering all the hours of hard work he must have put in to get it to where it is now, rather than he see it end up in the digital data wasteland, that is becoming larger year by year.
Quote:
The JavaScript part above I already referred to, so I'll not mention that further, but I am not, and I feel you must be in the same position - unsure as to whether it makes any sense or not, to ask the question, because if it is not asked how can anyone know if the question was worth asking or not until it has been asked?

Quote:
With regard to Odyssey, it is generally not.

Quote:
Unlike you, I already knew the license as well as the fact that it is based on Firefox (ESR). The Firefox sources have always been open.

Quote:
If you would like to see Cameron Kaiser's work be used on other platforms, please feel free to find volunteers who will port Firefox / TenFourFox to MorphOS. Before you do, you might want to try it on MacOS first, however.

Quote:
You did not ask a question. If you had asked "Is there any value in the TenFourFox source code with regard to MorphOS?", that would have been perfectly fine.

Instead, you specifically addessed the MorphOS development team and requested that they use their personal free time to contact another developer simply because you instinctively felt that it must be a good idea...

> My thought is that all of code that relates to TenFourFox
> may be useful to developers for OWB, as a reference

I don't think this is the case. As the browser components are heavily intertwined, being able to use code from one browser for another browser based on a completely different code base is more the exception rather than the rule, even as reference.

> the whole code that Cameron Kaiser has worked on, as he may be
> sympathetic to our cause as there are not so/as many PPC systems
> left to utilise any PPC code, let alone his PPC code

TenFourFox is written in C++, not in "PPC code". Exceptions to this are the JavaScript JIT compiler and AltiVec/VMX vectorizations of some decoders (audio/video, images etc.).

> I am not [...] unsure as to whether it makes any sense or not

;-)

It's been a bit more than a month since I last posted, and obviously my last prediction didn't come true. The remaining 1.24/1.25 bugs were quite a bit tougher to debug than I had expected, but we're getting closer, and it's ready for the first round of public testing.

First the caveats:

1) This still only has the first level JIT enabled, as the second level still needs some debug work. The first level of JIT is not super fast compared to the non-JIT version, so it won't feel super snappy compared to before. Don't expect miracles.

2) Some things might still be broken. If you discover things that don't work with the JIT version, but do work with the non-JIT version, please let me know. Let me just emphasise that I can't do anything about things that also don't work with the non-JIT version right now, so I'm only looking for reports of things that work with the non-JIT version but don't with the JIT version.

3) You need OWB 1.25 (from MorphOS 3.11) already installed. Extract the archive in your OWB directory, and then run OWB-JIT to test the JIT version.

And then the link: https://bigfoot.morphos-team.net/test/OWB-JIT.lha

I'm not done working on this, and there will be more updates in the future, hopefully with the second level JIT enabled as well at the very least. However, I will be unable to do any work on OWB for the next 3-4 weeks, so any further updates will happen in the second half of August at the earliest.

[ Edited by bigfoot 18.07.2018 - 13:35 ]