You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tdebindings/xparts
Timothy Pearson e63beeb5bd
Fix incorrect conversion
13 years ago
..
doc Initial TQt conversion 13 years ago
mozilla Fix incorrect conversion 13 years ago
src Fix incorrect conversion 13 years ago
xpart_notepad Fix incorrect conversion 13 years ago
AUTHORS Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
COPYING Fix automake problem 13 years ago
Makefile.am Fix compilation of Mozilla plugin for Konqueror 13 years ago
README Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
TODO Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
configure.in.in Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago

README

You will find here the XPart technology, as implemented by Simon Haussman,
Mathias Ettrich and Lars Knoll. Basically, XPart allows out of process
embedding. For more information, see:
http://trolls.troll.no/~lars/xparts/doc/xparts.html

Currently XPart is more a proof of concept than a stabilized and maintained
technology. The only application using it is kmozilla, which makes the
Gecko html/browser (the one of mozilla) available as a kpart.

The technology is not used enough to guarantee that the current state is the
best, so it might develop it further. Understand by that, that 
_binary compatibility might not be kept between releases_ .

But don't be afraid by that. XPart is a very promising technology and the api
looks good for the moment. We do not plan any change. 

If you are developing something with XPart, please make yourself known to the
kde development mailing lists, so that we can help you and get feedback.  I'm
working on a xpart notepad to show how to develop a xpart editor component.
This editor will be committed after the 2.1 release though. I am also working
on making vim available as a xpart/kpart component.

	Philippe Fremy <pfremy@chez.com>