[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    kdebindings/kjsembed/docs
From:       Ian Reinhart Geiser <geiseri () kde ! org>
Date:       2003-12-31 16:12:53
Message-ID: 20031231161253.49B7893DE () office ! kde ! org
[Download RAW message or body]

CVS commit by geiseri: 

updated todo list


  M +6 -9      TODO   1.2


--- kdebindings/kjsembed/docs/TODO  #1.1:1.2
@@ -36,7 +36,4 @@
 - Enable emission of signals from JS that can be connected in C++
 
-- Enable the handling of QVariants as QVariants.  This is agrivated in
-  tests/dcop.js.
-
 - DOM Level 2 support.
 
@@ -56,11 +53,11 @@
 =====================
 
-<kupid> I talked to Matthias and we'll have to explictly state somewhere in the \
                license that you're not 
-allowed to create the widgets with it. They way he saw it is that there should be \
                any problem because 
-if you write a script and it's internal and you don't redistribute it then it can be \
                whatever you want, if you 
-do redistribute it then it's a script and the code is right there so you might as \
well make it explicit that  +<kupid> I talked to Matthias and we'll have to explictly \
state somewhere in the license that you're not +allowed to create the widgets with \
it. They way he saw it is that there should be any problem because +if you write a \
script and it's internal and you don't redistribute it then it can be whatever you \
want, if you +do redistribute it then it's a script and the code is right there so \
you might as well make it explicit that  it's gpl or lgpl
 <richmoore> i don't quite follow
-<richmoore> are you saying that if you use the widget factory then the license \
degrades from LGPL to  +<richmoore> are you saying that if you use the widget factory \
then the license degrades from LGPL to  GPL?
 <richmoore> (this would make sense btw)
@@ -68,5 +65,5 @@
 <richmoore> that's fair enough
 <richmoore> i was aware of that
-<richmoore> i think the easiest solution is to allow a script to specify a license \
and use that to  +<richmoore> i think the easiest solution is to allow a script to \
specify a license and use that to  determine the available bindings (and to provide a \
pure-LGPL build target with no qt support)  <richmoore> a 'check-license' mode is \
also a good idea


[prev in list] [next in list] [prev in thread] [next in thread]