http://www.amigasoft.net/misc/amizilla.png

Go Afxgroup go!

Make it so!

_________________
Site admins are people too..pooff!

@tomazkid

113Mo for the exe

Anyway for your work !

@tomazkid

That screenshot only show that he managed to get it compiled. That's a pretty big milestone though. It also show that it runs with certain command line options that spit out text data.

What we're waiting for is a screenshot/video showing him executing "firefox" without extra parameters, and having it load up fully.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

X11

@lionstorm

Quote:

lionstorm wrote: @tomazkid 113Mo for the exe Anyway for your work !

Relax, it's the debug version. Debug versions are almost always several times the size they should be.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Kicko

X11 is the right way to go about it, at least initially.

I've got high hopes for this, well done Afxgroup.

Cheers,
Bean.

_________________
OS4.1 + SAM Flex
RIP my A1XE.. that used to have an appetite for batteries!

@Kicko

What really me is that probably this thread will get less comments than any of the useless court threads.

_________________
No PowerPC, No Fun
Make Amiga Great Again

@Fransexy

Court threads? What court threads?

You're probably right though!

_________________
OS4.1 + SAM Flex
RIP my A1XE.. that used to have an appetite for batteries!

@tomazkid

I hope Afxgroup can pull this off, and can claim the bounty:

http://www.discreetfx.com/AmiZilla.html

They deserve it - a decent browser will really push the platform forward :D

@tomazkid

so did he some progress?
that screenshot seems to be dated 22nd of may 2007, unless he set a wrong system date he's hopefully a little closer to run firefox fully

AFX... what can I say. I am speechless.
You proved that one man could do what 20 ####ers couldn't! Endless RESPECT!

I hope you will release all linklibs too. I guess other ports could benefit from them.

_________________
AOS4 Betatester, Peg2, G4@1ghz, Radeon 9250 256mb, 1gb RAM.

http://www.asciiarena.com
http://www.uprough.net

Let me have it, Let me have it..... And I'll show them what AMIGA really means

Well done. Keep up the good work man.

_________________
Amiga-Look.org - Beautify your Workbench

This wasn't what I was expecting You roxx!

Last edited by Akiko on 12-Jul-2007 at 12:08 AM.

_________________
4000T/BFG9060
CD32/Elsat ProModule, TF360
CD32/ Edu's CD32 <> A1200 Adapter, Vampire V2
CD32/ FMV Module

@tomazkid,

I'd say that this is quite a good step considering that the OO.org team has had to rely on a X11 port for OSX for some time. X11 ports are not that bad. I've been using them on my Mac for awhile now

_________________
600Mhz G3 AmigaOne in a custom Commodore case.

What is exactly X11 on the Amiga?. Onlinux it's the GUI, but is a certain app on the Amiga?
I really want to know as i'm now with no clue.
Thanks!!!

_________________
Amiga 1200 desktop. Apollo 030/50 Mhz 8mb ram + ClassicWB + Wb 3.1
Amiga 500 + ACA500plus 8mb + 30gb CF
Raspberry Pi 3b+ and Amibian 1.4
Mac Mini G4 1GB Ram with the butterfly!!

@_ThEcRoW

As far as I know this installs on os4, but I haven't tried it yet.

Readme on os4 depot:
What is X11?
------------

The X Window System is the base for the all graphical user interfaces on unix
or linux systems. No matter which GUI-toolkit is used, on the lowest level
works X11.
The system is splitted into a server and in a client part, which is typical
for unix like systems. The server is responsible for processing the graphics
and handles the user events like mouse-moves or key-events. The client
finally is an application (e.g. a paint-program or a text-editor), which is
using this system for displaying his windows.

What is the advantage to have this on an amiga-system? It makes it easier to
port open source software to the amiga, because the sources for the GUI part
can be compiled without any (or at least very few) changes.

Last edited by sundown on 12-Jul-2007 at 02:03 AM.

_________________
Hate tends to make you look stupid...

@tomazkid

Quote:

tomazkid wrote: http://www.amigasoft.net/misc/amizilla.png Go Afxgroup go! Make it so!

Same here!

_________________
'unfixed' A1XE, 512mb RAM, plug-in USB card, Sil 0680 IDE card, Radeon 9250, built-in sound, OS4.1 update 5.

@Hans

Quote:

Relax, it's the debug version. Debug versions are almost always several times the size they should be.

Another reason is that on AmigaOS everything has to be statically linked (x11 client, gtk, gdk, etc.) because AOS doesn't support dynamic linking like on Linux/UNIX. It has already been stated though that the next OS4 update will have dynamic linking and the ability to make/use .so (shared object) files (f.e. there already is a libpython.so). Making use of this should make the exe a lot smaller than it is now.

Last edited by salass00 on 12-Jul-2007 at 06:42 AM.
Last edited by salass00 on 12-Jul-2007 at 06:41 AM.

@salass00

Quote:

salass00 wrote: Another reason is that on AmigaOS everything has to be statically linked (x11 client, gtk, gdk, etc.) because AOS doesn't support dynamic linking like on Linux/UNIX. It has already been stated though that the next OS4 update will have dynamic linking and the ability to make/use .so (shared object) files (f.e. there already is a libpython.so). Making use of this should make the exe a lot smaller than it is now.

So, what is the difference between a shared library and one of these shared object files? Is .so just another name for a shared library?

_________________
Peter Swallow.
A1XEG3-800 [IBM 750FX PowerPC], running OS4.1FE, using ac97 onboard sound.

"There are 10 types of people in the world: those who understand binary, and those who don't."

@Swoop

An AmigaOS exec shared library doesn't use dynamic linking, instead the library code is loaded programmatically (OpenLibrary) and a library base (on OS4 an interface pointer is again retrieved from this (GetInterface)). Also the library only needs to be loaded into memory once (saves memory if it is used by many programs).

In the OS3.x case the base address contains 68k jmp instructions at specific negative offsets (the term jumptable comes from this), these are then called through the library base pointer placed in A6 (f.e. to call a function at offset -36: jsr -36(a6)).

On OS4 the interface pointer used is simply a structure containing pointers to the functions code. The pointer is retrieved from it and then a function call is made to it.

Dynamic linking is the same as static linking except that the linking is done when the program is run by the OS rather than being done by the compiler. Shared object (.so) are I think sometimes also referred to as "shared libraries" which may cause some confusion as AOS-style libraries are also referred to using this name.

Also because an exec-style shared library is only loaded into memory once and can be use by more than one program the programmer has to ensure that all functions are re-entrant (can be used by several programs at the same time). This somewhat limits how global and static variables can be used in the code since these would be the same for all programs.

Last edited by salass00 on 12-Jul-2007 at 10:58 AM.