I have started porting ABrowse. It is not hard, but I am not at my beos computer at the moment, so the porting has stopped. If anyone care to look at the code during the holiday, I would appreciate it. As I said... I dont think it is much left before the porting is finnished. It does not compile yet thouhg, so I guess there are a few bugs to squash too. Regards /Procton >Kurt did a KHTML port to Atheos. I think it has all the required support and >the API's a similar. Both are heavily threaded. Just a thought. >----- Original Message ----- >From: David Enderson <DEnderson@xxxxxxxxxxxxxx> >To: <openbeos@xxxxxxxxxxxxx> >Sent: Thursday, December 20, 2001 7:59 AM >Subject: [openbeos] Javascript-capable Browser > > >> >> I've been thinking for a while. I've heard it said several times here >> that a Java-script capable browser is KEY to an OS being used as a >> person's primary desktop OS. I know this is true in my case. >> >> I think it is in OpenBeOS's best interests to do whatever it takes to >> get a GOOD javascript browser released with R1 that is rock solid. I >> don't know which one that should be, it seems to me that whichever >> browser is chosen, that we in OpenBeOS should make our highest priority >> to either support the browser development, directly lend a hand, or >> create a development team to assume the development on a browser to make >> sure it makes release and is excellent quality. >> >> Thoughts? >> >> > Included should be only the tools and programs everyone needs=20 >> > - like a=20 >> > MediaPlayer, a browser, etc. >> > Something in the area of SpicyKeys. >> >=20 >> > And I don't think that there are much developers who would be really=20 >> > disappointed that his app didn't make it into the distro. >> > Never underestimate the power of BeBits - you can get almost every=20 >> > application for BeOS there. >> >=20 >> > Adios... >> > Axel. >> >=20 >> >=20 >> >=20 >> >=20 > > > >