NetSurf 3.11 has been released!

@joerg

Quote:

While we are on the subject of text editors there has already been work on it and a working version of Tea, so if you do it right including support for Amiga paths it should already be possible with little effort.

See: https://www.amigans.net/modules/newbb/ ... id=151114#forumpost151114

Qt TextEditor Tea:



Source:

https://github.com/psemiletov/tea-qt

I would be very interested in being able to use such a TextEditor under AmigaOs4.1, but I don't think anyone will.

I'm interested in a modern opensource text editor for OS4.
Above basic features it needs to support Amiga flavors programming languages indentation, black theme and possibility to build macro to run compilers and other stuff and become a sort of IDE just like Flowstudio on MOS.
..Something native AmigaOS lightweight and fast, not porting from other systems usually too much slow and full of bugs.
If some developer is interested I can get involved and support in my spare time.

Thanks everybody for the suggestions and info!

However, I'm realizing we have long been off topic in this thread, so we should probably end this discussion.

Best regards,

Niels

Hey All,

Just did an Amiupdate and it suggested there a new Netsurf available.

I was a bit skeptical as I was on the latest build 6772.

Went ahead with it, updated it and it installed fine.

But it installed build 28/12/23.

None of the sites work on that build.

You will want to remove it from Amiupdate.

Thanks.

@Boabster

It's because of the version numbering. The official releases have a higher version number than the auto-builds (even if they are older).

What I could do is start using subrevisions, but because AmigaOS doesn't officially support them, I'm reluctant to do this.

edit I've just realised, I need to be a bit careful to not jump backwards. My preferred new approach would be revision*100000 + build number. I think it's OK to go above 65535. That would make the next release 3.1200000 and any CI build something like 3.1206773

@Chris
Quote:Could cause problems, version and revision in libraries are 16 bit and software parsing $VER: strings might use the same data types.