We've decided that it's about time we release Timberwolf's source code to the public.

To that end, I've set up a project on github here:

https://github.com/tfrieden/timberwolf

If you want to become a contributor, let me know and tell me your github user name so I can add you.

The code is licensed under MPL, naturally, but we kindly ask that changes or additions should be returned to the project, in a true open source spirit.

Build instructions will be added later.

Good news. Thanks.

Good move, i hope we get someone to fix some bugs :)

bugs: maybe not the case here, but handling events like this:



it's easy to run into problem that for example HandleEvent when reacting on IDCMP_CLOSEWINDOW kills the window and when HandleEvent() returns window is no longer valid and the ReplyMsg() will do bad things.

@tfrieden

Thank You, great news! \o/

@tfrieden

Great news. Sorry if I came across as bit abrupt when I posted the Amiwest question for Steve Solie.

@tfrieden

Thank you Thomas and Hans-Joerg!

Yah good move finally ...

@tfrieden

Just a quick question.

There seems to be some ambiguity over the included license text. Is it still valid or do you have no objections to a cross platform initiative.

@Rob

If you mean this:
/* ***** BEGIN LICENSE BLOCK *****
*
* The contents of this file is copyrighted by Thomas and Hans-Joerg Frieden.
* It's content is not open source and may not be redistributed, modified or adapted
* without permission of the above-mentioned copyright holders.
*
* Since this code was originally developed under an AmigaOS related bounty, any derived
* version of this file may only be used on an official AmigaOS system.
*
* Contributor(s):
* Thomas Frieden
* Hans-Joerg Frieden
*
* ***** END LICENSE BLOCK ***** */

Then it is not ambiguous at all since its it is in amigos_process.c, which is not a part of the original Firefox source.

@tfrieden

Thanks for sharing.
Waiting for build instructions...

OS4 native try :

 /Dev/timberwolf-master> ./configure
configure[15]: .: ././build/autoconf/mozconfig2configure: not found

@tfrieden

I've been waiting for this for a while...definitely going to clone it out and take a walk through.

same nickname using gmail.com for my username on github.com
definitely interested in adding any patches and changes that can help this project become more up to date or better in any small way I can.

Thank you again for making this available.

Is there any chance of making the python source changes available as well in a similar fashion?

I'd like to see if it is possible to update the system python with the 2.7 or 3.5 series sources using the AOS4 changes applied there

Still waiting for two more Years with a printing facility..

Donations went there..

What about a virus+adfree fast browser with laser printing. Could be the "KillerApp"?

@Belxjander

Did you apply to the A-Eon looking for Amiga devs yet?

@Raziel

Yes I did, actually using TimberWolf to do so...

I have minimal TimberWolf problems myself...mostly to do with shutting it down or random startup faults.

Now the code is available I'll look through and see if there is anything I can do for building it myself.

One thing I have noticed... "Linux Hosted Cross-Compiler" is mandatory (lots of autotools in the configure scripting).

Kind of makes it a problem in trying to build TimberWolf for AOS4 natively on AOS4.

I have a number of items now that I have put aside needing me to work out how to deal with cross-compiler built "installation" and verification of whether the dammed thing is "AOS4 native" or actually host-as-target built...and a mix of the same with a recent adtools build.

when everything is automated with a walkthrough...great...
when I have to go hunting myself...definitely more awkward since I have only got remote access to non-AOS4 hardware through ssh/scp and editing the files remotely is definitely out of the question ("amiga" termcap definition is majorly broken in Linux by default currently).
not an AOS4 issue...but definitely something I can resolve...

Once I build myself a local x86 server machine to use for building with a cross-compiler.

Timberwolf need a lot of work, on my X1000 with FE works it very bad

@Belxjander
Quote:

Sometimes it's possible to create Amiga specific makefiles once the sources have been configured on a Linux system. Personally, I've never been able to commit anything to github repositories with Amiga tools (like sgit etc.) but that might just be my lack of knowledge. Contributing to TImberwolf with an OS4 computer doesn't look likely to me. If you find a way, let us know.

How difficult would it be to move the Amiga changes over to the latest Firefox sources: 42.0?

Would be cool if someone was able to "make a leap" with Timberwolf on Amiga

@xenic

Two things need to be known...

because "sgit init" and "sgit clone" are for creating a barebones/copy-of-existing repository setup...

1= Writing to the repository using "sgit push origin master"
where origin and master are the host and branch references.

2= Reading from a repository "git pull"(no pull so alternate)
"sgit fetch <repo>"
"sgit merge origin/master"
"sgit rebase master"
are the magic commands to update collaborator changes.

at least according to the information I got when asking as an issue against the sgit github project.

very very awkward for the sgit workflow in this way.

standard "git" is "init/clone/push/pull" with other operations as "extra features"

very very strange that we need to workaround a default feature using alternate extra functions.

Just my own opinion in using sgit for Perception-IME and Polymorph-VMM on github myself including some collobarative work with perception-ime (which I am very grateful for).

about HW requirements...
When using quad core 1.33Ghz Intel BayTrail device, observed some things...

The performance is ok for firefox and chrome etc.
The performance is ok also for LibreOffice.
The performance is bad with Open Office.

IIRC, LibreOffice is being slowly ported to AOS4, so it should be ok to use on some 1.2Ghz device, especially with some help of other cores. Good that open office was not chosen.

When using web browsers I think java / java script JIT makes relatively slow intel chip perform ok. But timberwolf should be good to use at least on x5000 caliber HW, even without JIT.

For speedy experience, most likely CinnamonWriter etc. more "original" Amiga implementations are very welcome.


Sorry for about (almost) offtopic post.