Am 04.03.2007 um 08:12 schrieb Gregory John Casamento:
Rogelio,
I dont think this is enough reason to invent a new ugly language.
So we
can render broken pages properly. For apple maybe.
Invent a new ugly language??? Heh. No one is doing anything of
the sort. ObjC++ has been around for a while.
Duplication cannot be avoided. Would you rather integrate c++, ada,
fortran, .net, java and cobol in obj-c so we can avoid duplicating
what
some super project in these language have done?
Heh, funny you should mention this. This type of thing is done in
commercial applications more often than you might think. I can
think of a few examples in my professional career where, yes, it
was necessary to integrate with a well tested, well known, library
that just happened to be written in another language. :)
If html is so easy to do wrong and so hard to handle then we put a
bullet in the s*****'s head and move on.
It's not that easy... it's nice to say that we will make a parser
that will only handle "correct" HTML, but when you consider that
this will make the browser virtually useless for navigating almost
half of the web pages out there, the idea looses it's appeal. If
you write a from scratch implementation you will need to handle
such pages, if you want anyone to actually use it.
To mention it one more time: If we really want and need to go pure
ObjC for this we should ask http://www.omnigroup.com/ if they hand us
their OmniWeb 4.2 implementation with a reasonable licence (and for a
reasonable price if they insist on this). This stuff is not up to the
latest in web rendering but it would save us a lot of time if used as
a starting point.
Later, GJC
regards, Lars
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
