Re: So what is happening with Safari Patches?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: So what is happening with Safari Patches?
by foobie on Wednesday 06/Oct/2004, @22:49

Thanks again for your answer-

A couple more questions:

Where are the mailing lists? (If you have the link to the developer you mentioned that would be great)

Also is it possible to do the same thing they did to us back to them? (Basically take their fork and wrap it back in as a KHTML replacement. Call it KHTML2.0 or something.)

It just seems like there should be some sort of expose on this. Someone needs to put a writeup in a blog somewhere and get /. or osnews to link to it.

Related Links

·   Articles on Interviews
·   Also by foobie
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: So what is happening with Safari Patches?
by Anonymous on Thursday 07/Oct/2004, @01:11

> Where are the mailing lists?

https://mail.kde.org/mailman/listinfo/khtml-devel
https://mail.kde.org/mailman/listinfo/kfm-devel

[ Reply To This | View ]

Re: So what is happening with Safari Patches?
by NeonDiet on Thursday 07/Oct/2004, @17:31

Of cause it's possible to take as much of Apple's WebCore/JavaScriptCore source code as you like and do what you want with it. Create a KHTML 2.0 with it if you want.

However, the problem is not down to access to the code, or any kind of legal obstacle, it's purely man hours (or the current shortage of) on the KHTML devel side. That's not Apple's fault.

You seem to think that Apple should write for two different sets of source trees, just because they took the Open Source code from KDE in the first place. Why should they do that? They didn't ask the KDE team to re-write KHTML for them in the first place so they could easily integrate it into OSX. They did all the leg work themselves. Now they've merged that code into their own framework, and that's the framework they're writing to. The source code for WebCore/JavaScriptCore is Open Source, so others can take that and make use of it for themselves if they want to. That can be the KDE team, or someone completely different. That's what Open Source means!! What it doesn't mean, is that you have to write someone else's applications for them, as you seem to want.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"In my free time I try to avoid computers as far as possible." -- Matthias Elter
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.