Re: [PyKDE] Hello and PyKDE for KDE 3.1

2003-03-19 Thread Hans-Peter Jansen
Hi Ralph,

welcome in this beautiful niche.

On Tuesday 18 March 2003 21:47, Ralph Kaiser wrote:
 Hi Pete,

 Try this:

 ftp://ftp.kde.org/pub/kde/unstable/apps/KDE3.x/utils/PyKDE-3.3.2-rha3.1.tar
.bz2

Yup, found it, but failed to build it, because it looks like KDE 3.1.1 is 
a lot more different to 3.1.0 than I've expected. See my next mail, if you 
like.

 And while I'm here I'd like to thank you for your excellent SQL tutorial
 that is included in the PyQT distribution. It made it quite easy (and fun)
 for this newbie to get started.

Thanks a lot. I hoped, someone will find it useful. I plan to write some
articles in german journals about PyQt and friends.

 Peace,
 Ralph

Far-to-many-weapons-in-circulation-to-make-this-happen-soon-ly y'rs,
Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


[PyKDE] Problems with PyKDE 3.3.2 on KDE 3.1.1

2003-03-19 Thread Hans-Peter Jansen
Hi Jim and friends,

motivated by Roberto, I tried to build KyKDE 3.3.2 on top of KDE 3.1.1,
but failed so far. Robertos version fails in exactly the same way, but
it's hard to say what Roberto has changed without a proper context diff
hint, hint.

The problem boils down to the now private nature of some ctors/dtors
in a few KIO classes. I examined the first one: KService(const KService), 
which is used at least in syentrylist.sip and svctypes.sip for some type 
conversations.

kservice.h:

class KService : public KSycocaEntry
{
  K_SYCOCATYPE( KST_KService, KSycocaEntry )

  KService(const KService);

Unfortunately I have not enough insight in the inwards of KDE to rewrite 
those by now.

Attached is a patch of what I've done so far. Additionally, I've created
a few symlinks in my RPM spec, as always:

cd extraH
ln -s kde303 kde304
ln -s kde303 kde305
ln -s kde303 kde311
cd ..
cd sip
ln -s kde30 kde31
cd ..

Here is the full error log [Sorry for the long lines]:

make[1]: Entering directory `/usr/src/packages/BUILD/PyKDE-3.3.2/kio'
g++ -c -pipe -w -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -fPIC -DNO_DEBUG 
-D_REENTRANT -fPIC  -DSIP_MAKE_MODULE_
DLL -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -fno-exceptions -I/usr/lib/qt3/mkspecs/default 
-I. -I-I -I../extraH -I. -I../..
/../../../include/python2.2 -I/opt/kde3/include -I-I -I/opt/kde3/include/kio -I-I 
-I../kdecore -I../../../../../inclu
de -I/usr/lib/qt3/include -o kiohuge.o kiohuge.cpp
/opt/kde3/include/kservice.h: In function `PyObject* sipConvertFrom_SvcList(SvcList*)':
/opt/kde3/include/kservice.h:47: error: `KService::KService(const KService)' is 
private
sip/svctypes.sip:175: error: within this context
/opt/kde3/include/kservice.h: In constructor `sipKService::sipKService(const 
KService)':
/opt/kde3/include/kservice.h:47: error: `KService::KService(const KService)' is 
private
sipkioKShellCompletion.cpp:1861: error: within this context
/opt/kde3/include/kautomount.h: In constructor `sipKAutoUnmount::sipKAutoUnmount(const 
QString, const QString)':
/opt/kde3/include/kautomount.h:108: error: `KAutoUnmount::~KAutoUnmount()' is private
sipkioKDataTool.cpp:733: error: within this context
/opt/kde3/include/kautomount.h: In destructor `virtual 
sipKAutoUnmount::~sipKAutoUnmount()':
/opt/kde3/include/kautomount.h:108: error: `KAutoUnmount::~KAutoUnmount()' is private
sipkioKDataTool.cpp:738: error: within this context
/opt/kde3/include/kautomount.h: In function `void 
sipDealloc_KAutoUnmount(sipThisType*)':
/opt/kde3/include/kautomount.h:108: error: `virtual KAutoUnmount::~KAutoUnmount()' is 
private
sipkioKAutoUnmount.cpp:435: error: within this context
/opt/kde3/include/kautomount.h: In function `PyObject* sipNew_KAutoUnmount(PyObject*, 
PyObject*)':
/opt/kde3/include/kautomount.h:108: error: `virtual KAutoUnmount::~KAutoUnmount()' is 
private
sipkioKAutoUnmount.cpp:499: error: within this context
/opt/kde3/include/kautomount.h: In constructor `sipKAutoMount::sipKAutoMount(bool, 
const QString, const QString, co
nst QString, const QString, bool)':
/opt/kde3/include/kautomount.h:70: error: `KAutoMount::~KAutoMount()' is private
sipkioKAutoUnmount.cpp:607: error: within this context
/opt/kde3/include/kautomount.h: In destructor `virtual 
sipKAutoMount::~sipKAutoMount()':
/opt/kde3/include/kautomount.h:70: error: `KAutoMount::~KAutoMount()' is private
sipkioKAutoUnmount.cpp:612: error: within this context
/opt/kde3/include/kautomount.h: In function `void sipDealloc_KAutoMount(sipThisType*)':
/opt/kde3/include/kautomount.h:70: error: `virtual KAutoMount::~KAutoMount()' is 
private
sipkioKAutoMount.cpp:435: error: within this context
/opt/kde3/include/kautomount.h: In function `PyObject* sipNew_KAutoMount(PyObject*, 
PyObject*)':
/opt/kde3/include/kautomount.h:70: error: `virtual KAutoMount::~KAutoMount()' is 
private
sipkioKAutoMount.cpp:511: error: within this context
sipkioKIOMultiGetJob.cpp: In member function `void 
sipKIO_DeleteJob::sipProtect_startNextJob()':
sipkioKIOMultiGetJob.cpp:2516: error: 'class KIO::DeleteJob' has no member named 
'startNextJob'
/opt/kde3/include/kio/jobclasses.h: In member function `void 
sipKIO_DeleteJob::sipProtect_deleteNextFile()':
/opt/kde3/include/kio/jobclasses.h:1067: error: `void 
KIO::DeleteJob::deleteNextFile()' is private
sipkioKIOMultiGetJob.cpp:2521: error: within this context
/opt/kde3/include/kio/jobclasses.h: In member function `void 
sipKIO_DeleteJob::sipProtect_deleteNextDir()':
/opt/kde3/include/kio/jobclasses.h:1068: error: `void KIO::DeleteJob::deleteNextDir()' 
is private
sipkioKIOMultiGetJob.cpp:2526: error: within this context
make[1]: *** [kiohuge.o] Fehler 1
make[1]: Leaving directory `/usr/src/packages/BUILD/PyKDE-3.3.2/kio'
make: *** [sub-kio] Fehler 2

Looks like It's time to wait for your new version, but I will happily
take advises on how to preceed.

Bye,
Petediff -u5 -uNrx '*.[ao]' -x '*~' -x '*,v' -x '*.orig' -x '*.rej' -x tags -x '*.swp' -x '*.new' PyKDE-3.3.2/build.py PyKDE-3.3.2-hp/build.py

Re: [PyKDE] Editable QComboBox in QTable problem ?

2003-03-19 Thread david
  I put an editable QComboBox in a cell of QTable with setCellWidget() :
 
  self.combo = QComboBox(self.table)
  self.combo.setEditable(1)
  self.table.setCellWidget(line,col,self.combo)
 
  When I'm writing in comboBox, the first character is in the comboBox,
  and after, characters are in a other cell.
 
 Please provide a small self contained example of your problem.


Hello,

Here is a little example, I'm using PyQt 3.5 and Qt 2.3 :

import sys
from qttable import *
from qt import *


class Form(QDialog):
def __init__(self,parent = None,name = None,modal = 0,fl = 0):
QDialog.__init__(self,parent,name,modal,fl)

self.setProperty('caption',QVariant(self.tr(Form)))
self.table = QTable(self,'table')
self.table.setNumRows(4)
self.table.setNumCols(4)
combo = QComboBox(self.table)
combo.setEditable(1)
combo.insertItem('a')
combo.insertItem('b')
combo.insertItem('c')
self.table.setCellWidget(1,1,combo)

if __name__ == '__main__':
a = QApplication(sys.argv)
QObject.connect(a,SIGNAL('lastWindowClosed()'),a,SLOT('quit()'))
w = Form()
a.setMainWidget(w)
w.show()
a.exec_loop()


Thanks for your help.

David

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


[PyKDE] KIO::DeleteJob

2003-03-19 Thread Roberto H. Alsina

Ahem, I sent a mail saying things like KIO::DeleteJob is deprecated.
Sorry, it's 8AM and I just woke up, and that is completely wrong ;-)

 (\''/).__..-''`-. . Roberto Alsina
 `9_ 9  )   `-. ().`-._.`)  [EMAIL PROTECTED]
 (_Y_.)' ._   ) `._`.   -.-'   Former KDE Developer (MFCH)
  _..`-'_..-_/ /-'_.'   
(l)-'' ((i).' ((!.' Buenos Aires - Argentina
It was like being crushed by an airplane 
full of leeches (H. S. Thompson)

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] KIO::DeleteJob

2003-03-19 Thread Hans-Peter Jansen
On Wednesday 19 March 2003 12:45, Roberto H. Alsina wrote:
 Ahem, I sent a mail saying things like KIO::DeleteJob is deprecated.
 Sorry, it's 8AM and I just woke up, and that is completely wrong ;-)

So you mean: -ENOCAFFEINE

No problem, build is running now with your headers and sips, let's 
see how far it gets...

Jim, it would love to see your next version Makefiles working with
export MAKEFLAGS=-j2
Currently, they fail because of missing dependencies between some 
targets. 

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] Problems with PyKDE 3.3.2 on KDE 3.1.1

2003-03-19 Thread Hans-Peter Jansen
Follow up with Robertos headers/sips:

Since Roberto switched off kautomount completely, the problem is 
reduced to the private KService::KService(const KService). Please
can you check, if this is also the case for KDE 3.1.0?

g++ -c -pipe -w -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -fPIC -DNO_DEBUG 
-D_REENTRANT -fPIC  -DSIP_MAKE_MODULE_DLL -DQT_NO_DEBUG -DQT_THREAD_SUPPORT 
-fno-exceptions -I/usr/lib/qt3/mkspecs/default -I. -I-I -I../extraH -I. 
-I../../../../../include/python2.2 -I/opt/kde3/include -I-I 
-I/opt/kde3/include/kio -I-I -I../kdecore -I../../../../../include 
-I/usr/lib/qt3/include -o kiohuge.o kiohuge.cpp
/opt/kde3/include/kservice.h: In function `PyObject* 
sipConvertFrom_SycocaEntryList(SycocaEntryList*)':
/opt/kde3/include/kservice.h:47: error: `KService::KService(const KService)' 
is private
sip/syentrylist.sip:60: error: within this context
/opt/kde3/include/kservice.h: In function `PyObject* 
sipConvertFrom_SvcList(SvcList*)':
/opt/kde3/include/kservice.h:47: error: `KService::KService(const KService)' 
is private
sip/svctypes.sip:175: error: within this context
/opt/kde3/include/kservice.h: In constructor `sipKService::sipKService(const 
KService)':
/opt/kde3/include/kservice.h:47: error: `KService::KService(const KService)' 
is private
sipkioKShellCompletion.cpp:1861: error: within this context

I've tried to switch off the kio module, but then kfile cannot be built...

BTW: The KDE 3.1.1 is what I have found on SuSEs 8.2 beta 3, their latest 
release for us beta testers.

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] Editable QComboBox in QTable problem ?

2003-03-19 Thread Hans-Peter Jansen
Hi David,

please have a look into the smalltable.py example, and you will see,
what's wrong. Also reading the docs for QTableItem will help you here.

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] Editable QComboBox in QTable problem ?

2003-03-19 Thread Hans-Peter Jansen
On Wednesday 19 March 2003 17:20, david wrote:
 Le mer 19/03/2003 à 15:13, Hans-Peter Jansen a écrit :
  Hi David,
 
  please have a look into the smalltable.py example, and you will see,
  what's wrong. Also reading the docs for QTableItem will help you here.
 
  Pete

 Hello Pete,

 Thank you for your help.
 I looked smalltable.py, it's an example for Qt 3.x, with Qt 2.x, there
 isn't QComboTableItem().

Oups. My fault. Sorry, but Qt2 was before my PyQt era started.

 With Qt 2.x, I haven't other solution that using setCellWidget().

 True or wrong ?

Don't know. See above. 

 button, checkBox, comboBox works fine with setCellWidget() but with
 editable comboBox, when I'm writing, I lose my focus.

 any ideas ?

Does Qt2 has an QTableItem you can subclass from? Testing your example
here with Qt3 made the QCombo disappear as soon as I entered some text
in this field, independant from, how is was instanced, BTW. 

 Thanks Pete.

You're welcome.

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] Problems with PyKDE 3.3.2 on KDE 3.1.1

2003-03-19 Thread Jim Bublitz
On 19-Mar-03 Hans-Peter Jansen wrote:
 I've tried to switch off the kio module, but then kfile cannot be
 built...

Because kfile depends on kio.
 
 BTW: The KDE 3.1.1 is what I have found on SuSEs 8.2 beta 3,
 their latest release for us beta testers.

As far as I know, there is no official KDE 3.1.1 or even a beta or
release candidate.

Jim

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] Problems with PyKDE 3.3.2 on KDE 3.1.1

2003-03-19 Thread Frederick Polgardy Jr
On Wednesday 19 March 2003 10:44 am, Jim Bublitz wrote:
  BTW: The KDE 3.1.1 is what I have found on SuSEs 8.2 beta 3,
  their latest release for us beta testers.

 As far as I know, there is no official KDE 3.1.1 or even a beta or
 release candidate.

Many of the Debian unstable packages for KDE are at 3.1.1 now.

-- 
F R E D E R I C K   P O L G A R D Y   J R.
Bodacion Technologies
18-3 E Dundee Road - Suite 300 - Barrington, IL 60010
Phone: 847/842.9008 - Fax: 847/842-1731
Web: http://www.bodacion.com

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] Problems with PyKDE 3.3.2 on KDE 3.1.1

2003-03-19 Thread Jim Bublitz
On 19-Mar-03 Hans-Peter Jansen wrote:
 On Wednesday 19 March 2003 16:03, Jim Bublitz wrote:
 On 19-Mar-03 Hans-Peter Jansen wrote:

 I've had some conversation with Dirk Mueller today about this
 problem. He holds me, that instancing KService::KService(const
 KService) will crash anyway, therefore it was made private in
 KDE 3.1.1 (which will appear soonish). He told me that we need
 to use KService::Ptr,  since KService can only share explicitly,
 thus it cannot be deep copied.

(From memory) That should be what the new code for
QPtrListKService::Ptr (which is what SvcList or KService::List is)
does I think. If not, I'll fix it. Maybe that was part of the
problem with the older code ?? Thanks for the input though - it'll
be helpful to know when I'm testing/debugging this.

 svctypes.sip is handwritten code and SvcList is a mapped type
 meaning neither is really part of KDE, but are created to handle
 template classes within PyKDE. I'm not sure why the copy ctor is
 being invoked there, so I'm not sure how to fix it. Also, I'm
 not sure if that section of code even works, and it's been
 recoded already for the new version.
 
 Would you mind throwing that code on me?

I'd rather not, as I don't know if it works, and I don't have it
versioned past KDE 3.0 yet. There were problems with the code in
this area in past releases, and it's very easy to write code that
compiles but doesn't function here - it's tricky (for me anyway)
getting the dereferencing correct. At the moment it's probably
better if you just comment out that stuff - should only be a few
methods.

There's a lot of stuff in PyKDE that nobody uses (although there
was a bug report on the list about the above) so for an interim
release like you're doing, I'd just comment stuff out 'til it
works. You probably won't lose too much that way.

Jim
 

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


Re: [PyKDE] PyQt QScintilla Status

2003-03-19 Thread Phil Thompson
On Tuesday 18 March 2003 7:22 am, Serge wrote:
 On Sun, 16 Mar 2003 16:33:22 +

 Phil Thompson [EMAIL PROTECTED] wrote:
  SKIP
 
  I plan to release the final versions as soon as Python 2.3 is released.

 Will  3.6 versions  work with python 2.2 ?

Yes, and every version of Python back to 1.5. I don't actually test versions 
that old - but it's a bug if it doesn't work.

Phil

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


[PyKDE] Title bar

2003-03-19 Thread Matthew Singer
Title: Title bar






I know I'm just being stupid, but how come my pyqt dialog based apps havepython in the title bar instead of the dialog box caption? Also, how do I get the minimize button to show up?

Rookie.. I know..


Matt Singer





Re: [PyKDE] Problems with PyKDE 3.3.2 on KDE 3.1.1

2003-03-19 Thread Phil Thompson
On Wednesday 19 March 2003 3:03 pm, Jim Bublitz wrote:
 These are all the same kind of error - deleteNextDir() and
 deleteNextFile () in KIO::DeleteJob (jobclasses.sip) are now
 private. Just delete it - sip doesn't handle private methods.

Just to mention a bit of SIP lore...

Sometimes it is necessary to define private methods - they do have an effect 
(and are necessary) if they are re-implementations of methods in a super 
class.

Phil

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde


[PyKDE] Version numbers in pyuic generated file

2003-03-19 Thread Greg Fortune
Phil,

Any chance you can embed the version number into the comment header on pyuic 
generated files?  It would be easier for me to figure out differences between 
the files generated on my machines and it would probably help you answer 
questions when someone gets a really weird error.  :)

It would be nice to get this into 3.6 if possible.

Greg

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde