discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNUstep Web browser (was Re: WebKit Bounty)


From: Richard Frith-Macdonald
Subject: Re: GNUstep Web browser (was Re: WebKit Bounty)
Date: Sun, 4 Mar 2007 14:42:35 +0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 4 Mar 2007, at 14:08, Rogelio M. Serrano Jr. wrote:

Gregory John Casamento wrote:
we still have uses for an xhtml only application right?


Of course, but if we're going to write a browser or an html viewer, we may as well write one that will work in the general case. I'm not discouraging anyone from writing their own. If you want to, then that's up to you. All I am saying is that it's wise to leverage the work of others when you can.

GJC



Well its a mar of getting a usable xhtml application within certain
constraints. I would like to ttehave it as soon as possible. How long would
it take to port webkit?

From what's been said already in this thread, it sounds like this is in the region of several days to several weeks. Using the SimpleWebKit from QuantumStep, sounds more like a process of hours (posibly little more than writing some gnustep make files).

So of course the question really is, what is 'a usable xhtml application' for you? If I needed quick html support for a specific problem in an application of mine, I know my first resort would be to try SimpleWebKit ... then make a decision based on how well that works:
It might do what I want ... so I'd just use it.
It might come really close ... so enhancing it to do exactly what I needed would probably be my choice It might be a long way from what I want ... then I'd have to spend serious time evaluating whether to enhance it or port WebKit or try something else.

My point is really that academic discussion on this list is fairly fruitless beyond getting a rough idea of what the options are. After that, you *have* to get your hands dirty with some coding/ experimentation, looking at the easiest options first, and deciding what to do based on the knowledge you gain.

If your motivation is to get the bounty for porting WebKit, then the decision making process is simplified ... you port WebKit (unless you talk to Jesse and find that some other course of action is acceptable to him). If your motivation is to get specific html functionality as quickly as possible, then you have to work out exactly what you need and see what the easiest solution is.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFF6truSZ/wVHjv7MIRAktfAJ9X0xcg+8prDCnii+JPJvhTLDR0BQCfSlZz
5WaGIlPOCBUbM5zVwQ66s4o=
=UyOR
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]