Ich möchte sagen, von "sorry für meine schlechte Deutsch" zu starten, aber ich kann nicht, ich weiß nicht vorhanden, wird diese Google übersetzt ...
If peeps would rather I used google to translate into German further posts, fine..
Fisrt off..
Arthur: I think you have your answer, believe it or not..
Second..
Big "ups" to Jens for uploading the new sources, I found the previous ones by accident..
Right, on with the show..
HighWirecvs, open source
no JS
no SSL
incomplete (and unstable) CSS2
now (for about a week) crashes on google results page
need immediate intervenion, at least to stop these CSS based crashes
PeterS does NOT have CVS access yet, and even when he does, will only (to start with) be looking at form and text (cut & paste) related issues.
Adamscvs, open source
v1 JS only (ie, no DOM support, or style object)
SSL support
no CSS2 support (CSS1?)
no current development (yet)
CABclosed source
no JS
SSL support
no CSS support
no future development
Linkscvs, open source
JS support, except for CSS (ie forms only)
SSL support optional (but it works)
no CSS support
semi-active development at main trunk..
semi-active atari development, on a "as needed" basis
OK, so (most of) the above have source access, and so can be developed further. ALL suffer from "modern" short comings (ie no JS, CSS, CSS2, CSS3, SSL, HTML5, plugins, etc)
Before I read this thread, I was planing to update the CSS and renderer in HighWire, with or without CVS access. And to add SSL, and "login-methods" and evenually JS, enough to be able to use the "standard" Google Mail inteface (like Konqueror does)
However, having read some of the links here, and taking into account the fact that Google have dropped MSIE support in GoogleWave, it seems pointless NOT to develop a WebKit compatible browser.
So now my idea is to develop a few (yes more than one) WebKit based ports, and when they are up to scratch, pull webkit compatibility back into HighWire, keep it its own creation, but drawing on the nessescary parts of WebKit to fill the gaps, and allw "modern" web browsing at a "standards" level..
WebKit Based Browsers: all dependecies are based on current sparemint RPM's only, and does not take ino account the many other packages already ported or updated..
QtWebKitrequires:
Qt v4.4+
libxslt
(probably) an new bison
OWBwith the following ports:
GTK
Qt
SDL
There are undoubtedly other WebKit based open source web browsers that can be adapted, but these are both light, and proven to work on various platforms
There are probably other web browsers worthy of porting to TOS/GEM/MiNT , but I would look very closely at the the level of CSS, JS, and "modern web application" support before I would even consider giving them a go.
And unfortunately, I would not even consider a modern Mozilla port, maybe a 1.7, possibly 2.0, but definitly nothing grater, its just to much of a bloat, even on modern systems that are state of the art, it just not worth the hassle at the moment
--
So there it is, a general overview of the current state of things, as the needs outlined in the initial post.
If anyone else has a descent "modern" web browser that would do us justice, let me know (there are a few). Most of them are not up to the "modern web app" level though, even thought they are nice to use, and may look good too. I would consider porting them, AFTER there is a WebKit based browser working.
I believe there would be a use for multiple browsers, in the "different strokes for different folks".
I also believe the "people paying for Atari style software" is NOT a viable option, as there is just not enough "regular users" for the percentages to pay off. Especially at the moment, its like asking people to pay to breathe air, these are ESSENTIAL APPS, not OPTIONAL APPS
But that is not a good enough reason NOT to develop for Atari compatible platforms. If the community chooses to support my efforts, well and good. I am in a position to be able to work full time on this (and other) efforts, unlike most other developers. So if someone wants to give me some money to make this development easier, I would welcome it, but its not essential (I have already learned to live without a home and without an income, so living without the support of others would not be something new to me)
If there are enough "modern apps" to make using (at least) ARAnyM/AFROS LiveCD a viable choice for "new" users, then there is more chance of more development being applied to the plaform in general, and that means indirect support for CTxx, PAH, ACP other Coldfire platforms, and potential customers for those projects that require munitary investment.
BTW, if its going to happen, now is the time to do it, left any longer, and Atari platforms will be left in the last millennium. I would rather put the effort in now..
I have other reasons for doing this, see:
http://afros-update.sourceforge.net/
Umfrage