Timberwolf is now open source

@Belxjander

Quote:

Actually "git pull" is just a shortcut for "git fetch" followed by "git merge".

sgit isn't there yet with a lot of features, but the fault is partly down to said features not being present in libgit2. It's thanks to that that we have any sort of Git support, as the original Git behemoth is unportable.

@tfrieden

great move to speed up improvements hopefully so many thanks!

Anyone working on it?

@Joeled

That's a danger to ask that question,

So let say that someone is working on it, then everyone else think they don't need to, have a look. If some is not working on it, then it might discourage people/users.

Anyway if there is developer who is interested in it, he should have at least try compile it, because there is not granite anyone else does.

Developers are not dumb, they know it is a lot of work, there are not that many that have the skills, to do it, this will be lot work updating the code to latest, and too, setup the cross compiler environment, I expect it be hard to even get the code to compile.

Do not assume developers are lazy.

@Joeled
In the original post in this topic it says: "Build instructions will be added later." but it looks like nothing has been added since the initial release at github. You can click the link that was provided in the original post and you will see 1 contributor listed for the project. That means nobody else has signed up to work on the project.

@xenic

You don't need to sign up, you can download a tar file.

@LiveForIt
You need to join the project to contribute fixes, changes, improvements to the code. SVN, Git etc. are designed for multiple programmers to work on the same code and take advantage of improvements commited by other team members. If people just D/L the code and work on it, you end up with a bunch of different versions with different changes and fixes. The whole idea behind putting the code into a repository is to make it a team effort where the changes make by everyone are combined. Otherwise the author could have just uploaded the code to Aminet or Os4Depot.

is it dying?

@BitBuster

no

for that it would have to be alive before

Github page disappeared ....

@samo79

The original page has disappeared, but I found it here.

Hans

@Hans

Thank you

was working so good at one point then all stopped working after FE came out ....that was 3 years ago

@328gts

I read that every now and then and I'm puzzled every time. I have three running AmigaOS 4.1FEu1 systems. Timberwolf work on *all* of them. "Work" means inside the usual Timberwolf-relevant definition of "it runs and does what it's supposed to do, but sometimes does some funny things".

And this is the usual behavior since the beginning and hasn't changed from whatever OS update came in the meantime. So "stopped working" is at least here not really the case.

@samo79

And if you click the number near "fork" you will find that user sahlberg has provided commit history so you should be able to see what Thomas changed:

https://github.com/sahlberg/timberwolf

Hey guys,

For what little it's worth, TW has continued to work here
on my X1K and X5K too. Typically it wants a reboot before
and it doesn't like to run at the same time as Oddity.

I also find deleting "CurrentUserProfile/#?" also helps.
I added it to the beginning of the "Timberworlf" CLI script
that starts TW.

The problem I've most recently found is that TW rarely
ever works anymore on HTTPS:// sites. Old SSL I expect.

Thanks,

PJS

Any chance Timberwolf will get an update anytime soon? It just crashes when I try to boot it on my X5000. On MorphOS their new web browser is really nice and functions well. It would be nice to see this same type of functionality on OS 4.1.

@DiscreetFX

Any chance Timberwolf will get an update anytime soon?

No, becouse Mozila now use Rust programming language.

We don’t have Rust, so you can forget Gecko web engine.
Rust needs LLVM and we do not have LLVM.

We have trouble keeping C/C++ libs up to date and bug free, the toolchain used to port stuff to AmigaOS is also pretty bad, and its really not easy to work with.

Working with cross compilers might work, but then we need RUST cross compiler.

Personally I find it hard to iterate if I’m not working natively. Its extremely important to be able to compile quickly, and test often. To be productive, as programmer.

It sounds like no one is porting the open source Rust language to OS 4.1. That’s a bummer.

@DiscreetFX

The question should be is anyone working on the toolchain or the LLVM, if this is the case, then in x months/years, in the future the likelihood of something like this increases.