Links 2.3 - Web browser

[medmed]

Hi folks,

I've ported links on mint with ssl support (Openssl): binary for 020, original code with patch and build instructions here

I got started with this application very quickly without using the mouse, navigating using the keys on my keyboard. This application pleasantly surprised me!

It can be used in GUI mode via X11 or in terminal mode (no X11) the best being the latter. I was able to download without problems.

An important point: I think that developers will have to take into account the http and ftp paths Links can start applications with the url in argument via the app/media association (conf is easy, via menu).

In short, I'll let you torture the beast.

Have fun!

For x11 mode use the following command

Code: Select all

 links -driver x

Type ESC for showing the menu. There're many tweaks to do in there.
Use arrows keys & enter to navigate, download...

[marss]

Thanks

[mikro]

Maybe you could try to backport Didier's GEM frontend there? http://didier.mequignon.free.fr/links/index.html

[BlankVector]

Excellent

[medmed]

Thx guys

@Mikro I'll take a look.

[medmed]

Maybe you could try to backport Didier's GEM frontend there? http://didier.mequignon.free.fr/links/index.html

Hi,

The uploaded archive links-2.3-gem.tar.xz is ready to build (just type make) with gem support once the gem.c file will be cleaned.

I don't really want to handle this (cf. screenshot).

To configure I used

Code: Select all

PKG_CONFIG_LIBDIR=/opt/cross-mint/m68k-atari-mint/lib/pkgconfig PKG_CONFIG=pkg-config \
LT_SYS_LIBRARY_PATH=/opt/cross-mint/m68k-atari-mint/lib/ \
CXX=m68k-atari-mint-g++ \
CC=m68k-atari-mint-gcc \
AR=m68k-atari-mint-ar \
LD=m68k-atari-mint-ld \
AS=m68k-atari-mint-as \
STRIP=m68k-atari-mint-strip \
NM=m68k-atari-mint-nm \
CFLAGS="-m68020-60 -fomit-frame-pointer -fno-strict-aliasing -O2 -DGRDRV_GEM" \
CXXFLAGS="-m68020-60 -fomit-frame-pointer -fno-strict-aliasing -O2 -DGRDRV_GEM " \
./configure --target=m68k-atari-mint --host=m68k-atari-mint --build=x86_64-apple-darwin22.3.0 --enable-graphics --with-ssl=/opt/cross-mint/m68k-atari-mint/lib/ --with-gem

Once the code will be build

Code: Select all

links -driver gem

should start the gem windowed version of links.

Regards,

[ThorstenOtto]

Sorry but that was not your best try

- you only patched the configure script, but not configure.in. That script will be regenerated when you run autoconf, loosing your changes
- same for Makefile.in, which will be overwritten when you run automake
- the gem.c does not compile at all
- your editor seem to have messed up some files (e.g gem.c & links.h), replacing the iso-8859-1 characters by utf8 sequences.

[ThorstenOtto]

BTW, where did you get the archive from? On http://links.twibright.com/download/, there are much newer versions

[medmed]

Sorry but that was not your best try

- you only patched the configure script, but not configure.in. That script will be regenerated when you run autoconf, loosing your changes
- same for Makefile.in, which will be overwritten when you run automake
- the gem.c does not compile at all
- your editor seem to have messed up some files (e.g gem.c & links.h), replacing the iso-8859-1 characters by utf8 sequences.

Haha,

Indeed I became too lazy when I saw gem.c

EDIT: If I autoreconf I've got many warnings then erros, seems the macros are too old, so I had to keep the original configure script.
Thanks for the characters suequences trick, I didn't figure out that my editor could handle it. Whatever the right gem.c file is in Didier's links source code.

[medmed]

BTW, where did you get the archive from? On http://links.twibright.com/download/, there are much newer versions

Oh well found Many thanks Thorsten.
I downloaded this archive several months ago and left it waiting in my todo list.

[medmed]

Cleaned gem.c but it still remains some trouble...

Code: Select all

... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x2178): undefined reference to `Atari_table_c2p'
... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x2260): undefined reference to `Atari_table_c2p'
... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x2824): undefined reference to `Atari_C2pConvert4'
... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x289a): undefined reference to `Atari_C2pConvert8'
... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x49aa): undefined reference to `Atari_C2pConvert8'
... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x4ae2): undefined reference to `Atari_C2pConvert4'

Edit: latest X11 version 2.29 seems ok but slower than v2.3 - I prefer use the terminal for now.

Edit: Is there a version of X11 for Coldfire?

[ragnar76]

Edit: Is there a version of X11 for Coldfire?

Long, long time ago i had EasyMiNT (https://atari.grossmaggul.de/home.php?v ... e=easymint) running on my firebee which had X11. I was running xchat with it back then.

[medmed]

Edit: Is there a version of X11 for Coldfire?

Long, long time ago i had EasyMiNT (https://atari.grossmaggul.de/home.php?v ... e=easymint) running on my firebee which had X11. I was running xchat with it back then.

The most recent version (4.0.3). I found it at Thorsten here

[ThorstenOtto]

Cleaned gem.c but it still remains some trouble...
... m68k-atari-mint/bin/ld: gem.o:gem.o:(.text+0x2178): undefined reference to `Atari_table_c2p'

Yes, you also need the ataric2p.S from didiers version. But there seem to be some other tricks involved, dunno whether that can easily be ported to current versions.

Edit: Is there a version of X11 for Coldfire?

https://tho-otto.de/download/rpm/RPMS/m5475/index.php

If I autoreconf I've got many warnings then erros

Running autoupdate should handle most of the issues.

[ThorstenOtto]

Made some progress:

Screenshot_20240524_100957.png

Colors look wrong, and occasionally i get "fixed point overflow in rgb to gray screen coefficient" from libpng.

[medmed]

Made some progress:

Screenshot_20240524_100957.png

Colors look wrong, and occasionally i get "fixed point overflow in rgb to gray screen coefficient" from libpng.

In all cases well done, it's already not bad!

The wrong color and overflow makes me think of the wrong type of var at first glance.

[medmed]

Made some progress:

Screenshot_20240524_100957.png

Colors look wrong, and occasionally i get "fixed point overflow in rgb to gray screen coefficient" from libpng.

Did you tried in 16bpp or 32bpp.
It seems that links with X can’t start with more than 16bpp for me.

[ThorstenOtto]

Screenshot above was for 32bpp, but for 16bpp it's currently even worse:

Screenshot_20240524_121747.png

With 8bpp it looks better:

Screenshot_20240524_122129.png

All with aranym + fvdi.

[medmed]

Oh great

[Eero Tamminen]

Screenshot above was for 32bpp, but for 16bpp it's currently even worse:

Looks like it's wrong-endian?

[medmed]

Yes, and one site can't be reliable. Did other websites have the same behavior? I'll check tomorrow what I get with the X version (2.29) on this website.

EDIT: I've tested with links 2.29 for X11 and colors are ok.

[ThorstenOtto]

The overflow in libpng is from

Code: Select all

			png_set_rgb_to_gray(png_ptr,1,54.0*256,183.0*256);

(at 2 places). The formula there should divide by 256, not multiply by it. But that line(s) seem to have changed in newer version of links.

What irritates me also: Didiers version claims to support javascript, and his archive actually contains the sources. But the Makefile there does not compile them, in the configure script there is no option to activate javascript, and neither links-2.1pre33.tar.bz2 nor links-2.3.tar.bz2 contain the sources. Wtf? Where did he get the sources from, when that was added much later?

The problem with the colors still persists (seems indeed have to do with endianness, have to do some more tests)

And i've got another strange effect: when using Aranym+JIT, the window background seems to not being drawn. That happens in all resolutions, but only when using the JIT version. That clearly seems to indicate that it is a JIT bug, however i've never encountered that with any other program.

[medmed]

The overflow in libpng is from

Code: Select all

			png_set_rgb_to_gray(png_ptr,1,54.0*256,183.0*256);

(at 2 places). The formula there should divide by 256, not multiply by it. But that line(s) seem to have changed in newer version of links.

What irritates me also: Didiers version claims to support javascript, and his archive actually contains the sources. But the Makefile there does not compile them, in the configure script there is no option to activate javascript, and neither links-2.1pre33.tar.bz2 nor links-2.3.tar.bz2 contain the sources. Wtf? Where did he get the sources from, when that was added much later?

The problem with the colors still persists (seems indeed have to do with endianness, have to do some more tests)

And i've got another strange effect: when using Aranym+JIT, the window background seems to not being drawn. That happens in all resolutions, but only when using the JIT version. That clearly seems to indicate that it is a JIT bug, however i've never encountered that with any other program.

Hum... I guess he took from previous version 2.1pre28

Code: Select all

Mon Apr 16 01:49:07 MET DST 2007 mikulas:

	Javascript was removed. The reason is that it is very buggy, Martin
	Pergel doesn't have time to develop it and code is so messy that no one
	else can understand it.

	If you use links for special purposes (embedded devices, etc.), you can
	bring javascript back by copying javascript files from previous release,
	removing "dnl javascript" lines from configure.in, adding *.c and *.h
	files to Makefile.am and re-running automake and autoconf.
	
	Javascript hooks from main code were not removed --- they just won't be
	maintained.

=== RELEASE 2.1pre28 ===

Wed Apr 11 01:39:36 cet 2007 mikulas:
[/code}

[ThorstenOtto]

Hm ok, thats possible.

Issue with wrong colors is solved: if you set "scrninfo fb" in the fvdi.sys file, fVDI reports a little-endian mode (because that is was is actually used on the host). But that does not seem to work with the way graphics are handled in links, i think it should also take into account the endianness of the m68k, but doesn't. So just ignoring the swapped flag from vq_scrninfo seems to work:

Screenshot_20240525_164914.png

Before looking into the background issue, i think i'll try to port the changes to current version (2.29) first.

[medmed]

Great, well done! I can't wait to try it.