Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
20 user(s) are online (15 user(s) are browsing Forums)

Members: 0
Guests: 20

more...

Support us!

Headlines

 
  Register To Post  

« 1 (2) 3 4 5 ... 7 »
Re: WebKit based browser initiative
Quite a regular
Quite a regular


See User information
@walkero

Good luck guys! ☺️

Amiga x5000 ı o2o ı 4GB RAM ı RadeonRX580 | SBlaster Audigy Fx - AmigaOS4.1 FInal Edition

A1200 sandwich

Warp - Croatian Amiga portal
Go to top
Re: WebKit based browser initiative
Site Builder
Site Builder


See User information
In case you do not follow our progress, rjd324 worked hard the previous weeks and brought us a necessary fix to our gcc 11 compiler, which is for the long-standing issue at https://github.com/sba1/adtools/issues/82 and has to do with the call_once().

His work is already merged into adtools repo, and the changes can be seen at https://github.com/sba1/adtools/pull/127

Also, rjd324 made the necessary changes so that the adtools project uses the latest SDK 54.16.

All these are necessary for our work with the WebKit port and the development environment preparation, pushing our tools a little bit further.

Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: WebKit based browser initiative
Home away from home
Home away from home


See User information
@walkero
Quote:

which is for the long-standing issue at https://github.com/sba1/adtools/issues/82 and has to do with the call_once().


That something ! Nice to see such an important progress in this area.

I also do check a bit your progress page, etc, and find out that you meet with morphos specific changes in the core of webkit (there a little bit of them, but still), and in most cases (at least in Odyssey) i do use the same code, with just adding __USE_INLINE__ to avoid me adding interfaces in the face of os3-kind functions.

And you go right route when firstly build webkit core for x86/linux and pass the tests. In terms of webkit itself port to os4 was (At least with odyssey again), almost with no changes , most of issues and changes were in GUI part. So, as far as you will build only core to make it as class or as shared library it should be not very hard. Then just some simple native test-window to render something by this class/shared library, and browser almost ready :)

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: WebKit based browser initiative
Site Builder
Site Builder


See User information
This weekend I will present on Amiwest about this initiative and will talk about the team and our plans. Don't miss it.

If you have questions that you would like to be answered, please write them down and I will answer all of them.

Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: WebKit based browser initiative
Quite a regular
Quite a regular


See User information
@walkero

Great to hear that - you are the man!

Amiga x5000 ı o2o ı 4GB RAM ı RadeonRX580 | SBlaster Audigy Fx - AmigaOS4.1 FInal Edition

A1200 sandwich

Warp - Croatian Amiga portal
Go to top
Re: WebKit based browser initiative
Just popping in
Just popping in


See User information
Great!

Go to top
Re: WebKit based browser initiative
Just can't stay away
Just can't stay away


See User information
@walkero
Great! Are you attending in person?

AmigaOne X1000.
Radeon RX550

http://www.tinylife.org.uk/
Go to top
Re: WebKit based browser initiative
Just can't stay away
Just can't stay away


See User information
@TSK

Quote:
What jacadcaps said that you need some 12 core machine with 32 gb memory to even compile WebKit. I don't have even that heavy Windows machines.
Things may have changed a lot in the past about 10 years, but I used an Amiga (initially an AmigaOne XE with 750FX CPU, later even a Sam440ep, none of them had more than 256 MB RAM) to build OWB natively, I never used a cross compiler for it.
Requirements very likely did increase, but not that much.

@SinanSam460
Quote:
I guess the port will be clib2 based ?
Wont work, way too much is still missing in it. Current versions of newlib.library probably aren't usable anymore either, but creating a new and usable port of newlib is, as it always was, very easy...

With OWB porting the browser itself, incl. implementing an AmigaOS GUI for, was only about 5% of the work, 95% of the work was porting the required libraries to AmigaOS. When I ported OWB to AmigaOS 3.x/m68k and 4.x/PPC at least half of those libraries were already available, partially in too old versions but easy to update, but I guess now at most 10% of the required libraries are available in usable versions.
Before even starting such a browser project first you have to get the required libraries ported, but I very much doubt there are still enough AmigaOS developers left for that work.

@afxgroup
Quote:
Maybe you can compile it natively on OS4.. But it will took 4 years..
For OWB it took me at most 4 days to build it natively on OS4


Edited by joerg on 2022/10/19 18:22:46
Edited by joerg on 2022/10/19 18:29:53
Edited by joerg on 2022/10/19 18:32:46
Edited by joerg on 2022/10/19 18:33:09
Edited by joerg on 2022/10/19 18:40:29
Go to top
Re: WebKit based browser initiative
Home away from home
Home away from home


See User information
@joerg

You for sure know that most of those libs was just about make and compile with little or none modifications needed, and they were already ported when the work of OWB and then Odyssey started.

jpeg
png
webp
xslt
sqlite
xml2
pthreads
libICU
curl
cairo

If as you said 95% of the real work is just about porting the required libraries to AmigaOS, then maybe we are already pretty close to have Wayfarer...

Go to top
Re: WebKit based browser initiative
Site Builder
Site Builder


See User information
Thanks everyone for your interest and for this discussion.

Quote:
Wont work, way too much is still missing in it. Current versions of newlib.library probably aren't usable anymore either, but creating a new and usable port of newlib is, as it always was, very easy...

We have cross compiling dev environments with both the new clib2 and the latest newlib. I plan to compile it for both and if something works on one and not on the other, that knowledge or issue will be shared with the maintainers. Having afxgroup on the team I am confident that if something is needed, we will be able to add it.

Quote:
Before even starting such a browser project first you have to get the required libraries ported, but I very much doubt there are still enough AmigaOS developers left for that work.

I agree that this needs to be addressed first, and that's what we actually do (https://github.com/walkero-gr/webkitty/issues/4) by porting the libICU. I also spoke with salass00 about his port of libCairo which we will use for a start and maybe later we might proceed with porting the latest version of it, which will benefit us all.

But we are still in our first steps. We need to familiarize ourselves with the project and do the work. It will take some time. I hope we will come up with something that will be useful and set the base for something great.

Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: WebKit based browser initiative
Amigans Defender
Amigans Defender


See User information
@joerg

Wont workway too much is still missing in it.


clib2 (newest version) has almost all glibc functions (except the usual one.. fork, waitpid and so on) and if someone find something missing it can be added (if possible).
It supports also shared objects (even if they needs to be debugged heavily) so even the problem to have a single monolith exe is not a problem.

For OWB it took me at most 4 days to build it natively on OS4

Yes I know.. :) it was just a way to tell that it is crazy.. And if you change an include file most probably you have to recompile everything all the time..

The main problems in my opinion are gcc/exec/elf. But while the first one can be patched if something is missing or needed in the two other one, we have to wait forever..
Another problem could be your missing.. :D but if you have some spare time (even 10 minutes a day) would be great.. :)

i'm really tired...
Go to top
Re: WebKit based browser initiative
Site Builder
Site Builder


See User information
Quote:
Another problem could be your missing.. :D but if you have some spare time (even 10 minutes a day) would be great.. :)

I would like to double on that. When the time comes, I am sure we will need experienced people like joerg.

But also, if we discuss that we need a c library free from anyone, contributing to the new clib2, or even the old one, is the way to get rid of the newlib and move forward. So if anyone has time to contribute, there is plenty of space to do so.

Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: WebKit based browser initiative
Just can't stay away
Just can't stay away


See User information
@walkero

Quote:
I also spoke with salass00 about his port of libCairo which we will use for a start
Is Cairo still enough? AmigaOS graphics.library functions and Cairo, with OWB optionally even SDL, was enough when Pleyo created OBW, but for example Chromium uses Skia.

Quote:
But also, if we discuss that we need a c library free from anyone, contributing to the new clib2, or even the old one, is the way to get rid of the newlib and move forward.
Doesn't make any sense, newlib is free software.
Unless you want to get rid of updates, bugfixes, etc., from non-AmigaOS developers (Linux, Windows, etc. which use newlib as well) and do everything yourself instead, in that case using clib2 is better, and much more work, than creating a new newlib port
In any case you need a C library with IPv6 support, and of course a new TCP/IP stack with IPv6 support in case there is none for AmigaOS 4.x yet.

Go to top
Re: WebKit based browser initiative
Just can't stay away
Just can't stay away


See User information
@afxgroup

Quote:
Quote:
For OWB it took me at most 4 days to build it natively on OS4

Yes I know.. :) it was just a way to tell that it is crazy.. And if you change an include file most probably you have to recompile everything all the time..
It was very crazy using an A1XE, and even worse with the Sam440ep which took several days for a complete rebuild (about 5-10 of the source files needed a lot of RAM, much more than the A1XE and Sam440ep had, and using the pager instead took several hours compiling each of them), but a X1000 or X5000 with 4 GB RAM should be able to rebuild it completely in less than a day.

Go to top
Re: WebKit based browser initiative
Home away from home
Home away from home


See User information
@joerg

Aren't all NG systems limited to 2 GB RAM no matter what is installed?

I know about the extmem feature but I was under the impression our SDK tool chain wasn't aware of that...please correct me if I'm wrong.

I'd love to finally use the 8GB I have installed on my x1k

Go to top
Re: WebKit based browser initiative
Not too shy to talk
Not too shy to talk


See User information
There are probably only 2 programs that use ExtMem Sketchblock and Rave. I don't know if it could be used for a Web browser, but 4GB would be very useful for today's heavy sites.

Go to top
Re: WebKit based browser initiative
Home away from home
Home away from home


See User information
@mufa

You can have a lots of texture memory, on the RX/HD graphic cards, not sure about normal 2D graphics.

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top
Re: WebKit based browser initiative
Amigans Defender
Amigans Defender


See User information
@Raziel

Quote:
I know about the extmem feature but I was under the impression our SDK tool chain wasn't aware of that

No worries, the SDK is perfectly ready to use ExtMem.

The Rear Window blog

AmigaOne X5000 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition
Go to top
Re: WebKit based browser initiative
Home away from home
Home away from home


See User information
@trixie

Nice, what about the gcc tools, gmake and linker?

Go to top
Re: WebKit based browser initiative
Home away from home
Home away from home


See User information
@Raziel
What Trixie mean, that if you want to use ExtMem functionality, SDK already provide you with everything. But as it matter of writing special code to handle extMem for every case, it mean that if programms did not rewriten to use it, then it will be not used.

So to answer : of course no one add support of extMem to gcc tools, gmake or to linker. That hell of work, and we should be happy anyone ever fix someting even simple in gcc , taking aside adding of extMem :)


@all
Not only Rave and Sketchblock use extMem : as i aware MultiViewer/MiltiEdit did use it (can be wrong if both, but one of them for sure).

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top

  Register To Post
« 1 (2) 3 4 5 ... 7 »

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project