On Sun, Mar 24, 2002 at 06:06:01PM +0100, Michael Polak wrote:
> On Sun, 24 Mar 2002, Mithgol the Webmaster wrote:
>
> > > Can't say about Flash (I just don't use it ;) but news support may be must
> > instead.
> >
> > I won't even try to code any of it ;-)
> >
> > Let's hope Michael will go crazy enough to make at least an attempt.
>
> 1) Java is becoming relatively obsolete, it isn't even included in Windows
> XP by default, and I never really like java (probably because early
> Java applets in Netscape 3.x were very unimpressive: slow and crashing
> entire system very often..)
>
> 2) Flash client can be licensed, and it is relatively
> portable; Suntech/Nexwave licensed Flash and ported it into their
> kernel-less OS. They maybe even use it together with their licensed clone
> of Arachne. As there is server-side dynamic generation of SWF files
> possible (PHP module; installed on arachne.cz), Flash seems to be realy
> only alternative for vector-based graphics which is available
> today. Unfortunately, it's binary only, ignores W3C recommendations, and
> client is not open source. Linux plug-ins can be forced to run inside
> non-netscape browsers (like Konqueror), but it is probably restricted to
> X11 enviroment, while I want Linux Arachne to be X-friendly as well as
> X-independent..
>
> 3) Let's talk about open source Arachne instead.... and how to force OEM
> customers to subsidize Arachne development anyway... ;-)
Let's talk about it.
I have some concepts and ideas how should it (browser) be done, but I'm still
not enough enthusiastic to do it by myself.
It should be layered, modularized, with use of Unix principle of "Makefiles"
and "pipes".
eg.
INPUT --> parser --> JS-like structures --> internal_structures --> rendering
of data
any change before "-->" regenerates structures after "-->"
The goal is to do it in similar way like Makefiles:
after change on the left side, only necessary part on right side
is regenerated.
INPUT could be been not only network, but eg. keyboard.
Arachne in addition to "browser" could be WYSIWYG HTML editor, or even
word processor (Keyboard is much slower than network).
OUTPUT -> graphic screen, text terminal, Postscript
Structures of data should be universal to many uses.
Such "-->" could be much more than on diagram, but all converters "-->" should
be simple as possible.
Events from User should be treated in similar way.
First step is to:
- define structures "after parser" and "before render"
WF
