Created attachment 8928 [details]
native msgbox for Qt/KDE

SBA: Reassigned to Christoph.

the attachment seems to contain just the sentence /root/msgbox.cpp .
this is useless unfortunately. Bernhard, please check.

Created attachment 9099 [details]
Looks like Issuezilla and Lynx don't like each other?!

Looks like lynx messed up the attachment. 
Re-attached. 

cp->pl: please take care of this one. I'm not quite sure wether the
source file makes sense as is. I think we need at least to have an
option for the makefile. Please check if we have a copyright assignment. 

Bernhard: i looked at your source file and it looks very good as far
as i can see; it mirrors exactly what messagebox-gnome does.

For submission of significant code patches (which is somewhere defined
as more than 10 lines of code i think) we'd need a Joint Copyright
Agreement (please look at http://www.openoffice.org/contributing.html
); the code would be dual licensed under LGPL/SISSL if it were to go
into OOo's CVS.

The legal status of derivative works based on Qt-free is not entirely
clear to me; the question concerning me is whether commercial
contributors may compile the code and contribute it to OpebOffice.org
without violating the Qt-free license - which is what Sun would have
to do since Sun provides the downloadable install sets that are
available through OpenOffice.org's website.

Also, please let me explain what messagebox-gnome is (currently i
should say) used for: if OOo's accessibility bridge (the bridge
connecting tools like screen readers and such that help disabled
people to use software) decides it cannot initialize - for what reason
ever - it puts up a native message box telling OOo will not be
accessible, hoping that the native message box is accessible even if
OOo is not. But for KDE there is no accessibility bridge since KDE's
accessibility is "not there yet" and hence no bridge to the java API
OOo uses for accessibility. So there currently is no use case for a Qt
based message box executable - which may of course change in future.
On the other hand the external processes (like messagebox-gnome) using
the native toolkit will vanish anyway as the native toolkit will be
used inside OpenOffice.org itself (if you're interested please have a
look at the corresponding thread on dev@gsl.openoffice.org).

So all that said i'm not sure whether you want to go through the
hassle of signing the JCA. On the other hand if you do we could use
this as a test case to see what happens with the legal implications.

If you want to further help with KDE integration for OOo you might be
interested in subscribing to the dev@openoffice.org mailing list
(possibly also to gev@gsl.openoffice.org); Jan Holesovsky is in the
process of starting an incubator project that is all about moving OOo
onto KDE.

No JCL existant, no answer, so i'll close the issue

closing issue