Re: [PyKDE] SIP, PyQt, PyKDE and friends is KDE CVS
On Tue, Jun 22, 2004 at 08:38:19AM +0200, Simon Edwards wrote: I commited a copy of SIP, PyQt and PyKDE to KDE CVS on the weekend . . . Major milestone! Kudos! ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] eric3 possible annomoly ?
Hi, thanks for supplying your little test app. I found the bug. The correction will be in the next snapshot. In the mean time, the workaround shown below will overcome the problem. Am Montag, 21. Juni 2004 19:41 schrieb Dave S: Detlev Offenbach wrote: Hi, Am Sonntag, 20. Juni 2004 13:13 schrieb Dave S: Im using eric3.4.2 quite heavily have found an annomoly. I write a simple test script, right click showprofile data, it is greyed out as expected ... :-) I 'Ps' run the script within eric3 I now right click showprofile data, it is still greyed out - not as expected :-( I just tried to reproduce your problem with my testscripts and everything was working ok. Please mail your script, which is showing the described behavior. Sure thing ... its pretty simple ... #!/usr/bin/env python A testbed app import sys def testbed(): print 'hi I am a test print' def test(): for a in range(100): testbed() test() sys.exit(0) The last line causes the atexit handler to fire, which writes the profiling data. Its not a great problem, I just shut down eric and re-start it. Then the datas there. Exiting the client will fire the atexit handler as well. python 2.3.3 qt 3.3.2 pyqt 3.8.1 qcintilla 1.2 eric 3.4.2 If I shut down eric3 re-boot it, right click showprofile data and it is there, click it and the profile data is there. If I then right click erase all info the info stays on the display. Click OK, right click showprofile data, it is again greyed out as expected ... The Erase ... entries erase the profile and/or timing data on disk, not the display. That's why the menu entry is grayed out. Ahh that explains it ... This is not a serious problem .. In fact with my steep learning curve it could be me not operating eric3 properly. Can anyone shed any light ? Dave Detlev Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] large tables problem
Hi, I'm working on a viewer for large tabular datasets. The underlying application from which my viewer read data is a hierarchical database that can deal with really large datasets (tipically too large to be managed with relational databases). Following the advises of Qt documentation and the Qt Quarterly article http://doc.trolltech.com/qq/qq07-big-tables.html I've written my own table class by deriving QTable class and overwriting several functions. In particular the resizeData() function has been reimplemented to do nothing. In addition, I use buffers so just a small part of the displayed dataset is in memory at a given time. However the amount of memory allocated by my application is still too big when I create large tables (you can see a summary at the bottom of the message). Does anybody know what else can I do in order to reduce the amount of allocated memory? Help would be really appreciated. Thanks in advance. Some useful info: Debian box (kernel 2.6.2) python 2.3.4 qt 3.2.3 pyqt 3.12 The following table is based on the output of command ps u -C python. ROWS %CPU %MEM VSZ(KB) RSS TIME COMMAND 0 9.74.040652 20796 0:53 python main.py 10**5 1.2 4.5 43332 23412 0:03 python main.py 10**6 1.3 9.5 69168 49208 0:04 python main.py 10**7 7.4 59.4326512 306584 0:35 python main.py Of course main.py is the script that launches my application and the ROWS column gives the number of rows of the opened table :). For testing purposes columns have been fixed to 4 and cells contain strings of 1 character length. -- Share what you know, learn what you don't ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Eric3
Am Dienstag, 22. Juni 2004 17:58 schrieb Douglas: Hi ! This is a feedback for the new eric release... The new logo is GREAT !! And the bug that i have reported - input() - got resolved in this release. This is to say that im looking forward to help. In this case, how i can help the project ? How about a translation of the interface for your native language (Brasilian?)? I can translate docs and i can do some python code too. Note: Im a python novice who discovered eric3 the is wanting so much to help in any way. Im waiting instructions ! See you all and keep the wonderful work. See Ya ! Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [review] [PyKDE] large tables problem
On Tuesday 22 June 2004 11:50, Vicent Mas wrote: I'm working on a viewer for large tabular datasets. The underlying application from which my viewer read data is a hierarchical database that can deal with really large datasets (tipically too large to be managed with relational databases). Following the advises of Qt documentation and the Qt Quarterly article http://doc.trolltech.com/qq/qq07-big-tables.html I've written my own table class by deriving QTable class and overwriting several functions. In particular the resizeData() function has been reimplemented to do nothing. In addition, I use buffers so just a small part of the displayed dataset is in memory at a given time. However the amount of memory allocated by my application is still too big when I create large tables (you can see a summary at the bottom of the message). Does anybody know what else can I do in order to reduce the amount of allocated memory? Help would be really appreciated. Thanks in advance. Some useful info: Debian box (kernel 2.6.2) python 2.3.4 qt 3.2.3 pyqt 3.12 The following table is based on the output of command ps u -C python. ROWS %CPU%MEM VSZ(KB) RSS TIME COMMAND 0 9.74.040652 20796 0:53 python main.py 10**5 1.24.5 43332 23412 0:03 python main.py 10**6 1.39.5 69168 49208 0:04 python main.py 10**7 7.459.4326512 306584 0:35 python main.py Of course main.py is the script that launches my application and the ROWS column gives the number of rows of the opened table :). For testing purposes columns have been fixed to 4 and cells contain strings of 1 character length. If your application allows it, you can operate the table with fixed number of cells/fixed amount of memory, reload the cells as necessary (don't destroy/construct new cells), and overload the navigation methods (cursor up/down, page up/down, home, end, and the equivalent mouse/scrollbar/button operations) to cause a page fault and reload the table when navigation is about to go outside the range of rows currently displayed. There are probably some ways to minimize data movement, but the limiting factor for speed is probably redraws. The memory used should then be independent of the table size. I used to support the display of a 3-5M row database that way, but it was all custom code (DB, table widget, page fault mgmt) written in C++. I think Delphi worked basically the same way (paging). I'm not sure QTable makes this especially easy though, but I haven't looked into it in a long time. Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
