[PyKDE] [job] Looking for PyQt engineer
I don't know of a better place to post this. if this is inappropriate, I apologize. If there is a better place to put this, let me know. I am using PyQt to write applications for optometrists in the Seattle/Tacoma area. There is a very good market for this kind of software. However, I need to get it done by May for an upcoming convention. So I am looking for help. I am looking for someone willing to work a few months for stock and promises. Unfortunately, that is all I have to offer for now. You won't have to quit your day job (if you have one). You will be able to work at home. I prefer you being in the Seattle/Tacoma area, but, hey, it's not critical. The skills I need most especially are Python, Qt, and PyQt. If you have experience working for very small companies, or working for yourself, that is a plus. If you have perl, postgreSQL, and Linux experience, that will be a bigger plus. I can give you more information if you email me personally. -- Jonathan Gardner [EMAIL PROTECTED] Python Qt perl apache and linux ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] solaris 7 unresolved symbol
Not yet working but just discovered that truncate is redefined as truncate64 in /usr/include/unistd.h file if __USE_FILE_OFFSET64 is defined !! Why the libqtcmodule.so refers to QString.truncate64() instead of QString.truncate() ? Does my gcc 2.95.2 preprocessor fail ? Laurent Claustre wrote: Help, have problem importing qt with following setup: platform: solaris7 compiler: gcc 2.95.3 Qt: 3.1.1 si: x11-gpl-snapshot-20030204 PyQt: x11-gpl-snapshot-20030125 Everything was compiled fine but : $python Python 2.2.2 (#8, Feb 17 2003, 13:40:18) [GCC 2.95.2 19991024 (release)] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> import qt Traceback (most recent call last): File "", line 1, in ? File "/segfs/bliss/depot/pythonbliss_1.0/solaris7/lib/python2.2/site-packages/qt.py", line 25, in ? import libqtc ImportError: ld.so.1: python: fatal: relocation error: file /segfs/bliss/depot/pythonbliss_1.0/solaris7/lib/python2.2/site-packages/libqtcmodule.so: symbol truncate64__7QStringUi: referenced symbol not found >>> I know it sounds like PyQt was compiled with a different qt version and python is trying to load with an other one, but I've checked my lib-path that is Ok. Regards. \===/ ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Fourth release of PythonCAD now available
I'd like to announce the fourth release of PythonCAD, a CAD package for open-source software users. As the name implies, PythonCAD is written entirely in Python. The goal of this project is to create a fully scriptable drafting program that will match and eventually exceed features found in commercial CAD software. PythonCAD is released under the GNU Public License (GPL). PythonCAD requires Python 2.2. The interface is GTK 2.0 based, and uses the PyGTK module for interfacing to GTK. The design of PythonCAD is built around the idea of separating the interface from the back end as much as possible. By doing this, it is hoped that both GNOME and KDE interfaces can be added to PythonCAD through usage of the appropriate Python module. Addition of other interfaces will depend on the availability of a Python module for that particular interface and developer interest and action. The fourth release has major improvements in dimensioning. Angular dimensions are now available, and linear dimensions will be displayed. There is also more visual feedback when creating any dimension, and the display of the dimension text has been improved. Check out the new screenshots on the PythonCAD screenshot page showing these changes. There is more visual feedback when creating arcs now, and various other user interface elements have been improved. The usual assortment of bug fixes and code improvements are added, and although not seen directly when using the program, these changes have increased the stability and robustness of PythonCAD. More routines have had been documented, and many routines have been updated to current code standards. This release coincides with providing read-only access to the PythonCAD Subversion repository. Subversion is similar to CVS, but is aiming to be the successor to that program. By making the repository available to everyone, it is hoped that downloading and developing PythonCAD will be simpler for more developers and users, and will increase the speed of PythonCAD development. Details about downloading PythonCAD with Subversion are found on the PythonCAD web site. For more details about Subversion, go to the program's home page: http://subversion.tigris.org Visit the PythonCAD web site for more information about what PythonCAD does and aims to be: http://www.pythoncad.org Come and join me in developing PythonCAD into a world class drafting program! Art Haas -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin, Historical Review of Pennsylvania, 1759 ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Some fundamentals
On Tuesday 25 February 2003 10:55 am, Tom Chance wrote: > Well thank you to all who replied - that's much clearer now. By the time > I'm finished with Python, I sweat I'm going to be half-way towards knowing > C/C++ as well, as so many docs (even the O'Reilly books) seem to assume > you're coming from it, and explain everything in terms of it! Anyway, I > understand that all now, and I've worked out how to use it which is the > important thing :) > > There's one other thing that has puzzled me lately, and I can only assume > that it's either a misunderstanding or a bug on my part. I've got some code > which, on the push of a button, scans the DVD device, then populates the > ListView with items for each track. Currently, the code works like so: > > > print "Scanning DVD" > > (popen command to get number of tracks) > for i in range(numtracks): > (popen command to get track info) > print (info about track) > (add ListViewItem) > > print "Finished" > > > Now I would expect that the ListViewItems would appear one by one as the > for loop scans each track. But what happens is that it prints out the info > for each track as it goes along, but only populates the ListView with the > items when it's done. Why is this? The screen gets updated when you return to the Qt event loop. Have a look at QApplication.processEvents(). Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Some fundamentals
Well thank you to all who replied - that's much clearer now. By the time I'm finished with Python, I sweat I'm going to be half-way towards knowing C/C++ as well, as so many docs (even the O'Reilly books) seem to assume you're coming from it, and explain everything in terms of it! Anyway, I understand that all now, and I've worked out how to use it which is the important thing :) There's one other thing that has puzzled me lately, and I can only assume that it's either a misunderstanding or a bug on my part. I've got some code which, on the push of a button, scans the DVD device, then populates the ListView with items for each track. Currently, the code works like so: print "Scanning DVD" (popen command to get number of tracks) for i in range(numtracks): (popen command to get track info) print (info about track) (add ListViewItem) print "Finished" Now I would expect that the ListViewItems would appear one by one as the for loop scans each track. But what happens is that it prints out the info for each track as it goes along, but only populates the ListView with the items when it's done. Why is this? Thanks again! Tom > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 25 February 2003 01:13, Tom Chance wrote: > > Hello, > > > > I've only just started out with PyQt, so please bear with me as I ask > some > > boring questions :) > > > > I've been reading through the book "GUI Programming with Python: QT > > Edition" by Boudewijn Rempt online (the paper copy is just too expensive > > for a poorly student like me :-), and though it covers a lot of ground, > > it's written in a very confusing order, jumping around between ideas. > > I guess it doesn't help that the online version misses all screenshots > and the helpful titlepages between sections. Start with > http://www.opendocs.org/pyqt/index.lxp?lxpwrap=c1036%2ehtm, that shows > how to write a simple script to start with. > > > Anyway, enough rambling. I'm using Qt Designer to create my GUI, and I'm > > then importing the class in my main program file. At the moment, the > main > > program file contains one class that inherits the GUI class, and that > > contains all my functions. I'm sure this isn't the best way to do things > - > > I'm used to creating multiple classes, each one for a different task, > and > > it seems a little messy having all my function code in one class. What's > > the best way of laying out the code? > > Doesn't matter much. You don't even need to inherit the gui class; there > are cases where simple instantiation is enough, if you connect the signals > >from the gui class widgets to slots in your own code. > > > > > > Also, I'm struggling with connecting signals and slots. I understand the > > principle, and I'm getting the hang of working wiht Qt Designer and my > code > > to create empty functions in Designer, and then create the actual > functions > > in my main code, but I don't really understand the signal parameter in a > > connection. > > > > E.g. I can guess what "pressed(QListViewItem*)" means? But why the > > QListViewItem with an asterisk? And what really confuses me is the "int, > > const Qstring&" stuff. What do they signify, and why are they in the > signal > > for a rightButtonClicked(), whilst clicked() has no parameters, and > pressed > > only has QListViewItem? > > > > > The signal parameter from C++ signals is a simple name. In C++, the > parameters > define the kind of data passed to the slot; but in Python it's simply used > to > distinguish between signals with the same name but different parameter > lists. > The funny things, like int, & and * are simply copied from C++, where they > denote the type of parameter. They're present in the Python bindings > because > it makes it easier to use the Qt C++ docs. > > > > Back to the docs for now! > > > > You might also want to take a look at the tutorial I wrote for Dr Dobbs > (January 2001 issue), which covers the first steps and principles, but in > a lot less detail than the book. > > - -- > Boudewijn Rempt | http://www.valdyas.org/index2.html > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE+WxJWdaCcgCmN5d8RAu/YAKC6ZWjNsBBIh8bXvTxeKrlDvNZMawCfdeU3 > XDZLoWcYxA7ozjJCPGAzgpQ= > =W8jp > -END PGP SIGNATURE- > > ___ > PyKDE mailing list[EMAIL PROTECTED] > http://mats.gmd.de/mailman/listinfo/pykde > -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Adding QListViewItems from a thread
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 25 February 2003 09:08, Mike Kinton wrote: > I have a function in the main thread that adds an item to a QListView. If > called from the main thread, this works fine. However if I call this same > function from a separate thread, the items are displayed in the lsit view, > but QlistView seems to lose the pointer(s) to the items in QListView. > > I have used the python thread module and have not put any locking in. > > this is my first effort at using of threads so I may have made some silly > mistake. Well, in almost all GUI libraries, you can only do things with the gui from the main thread. Your best bet would be a producer/consumer model with a Queue: have the sub thread add commands to a Queue that the main thread reads out and handles. See for some more discussion my recent article on www.informit.com (no permalink, I'm afraid, but if you login and search for my name, you'll find it). - -- Boudewijn Rempt | http://www.valdyas.org/index2.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+WybgdaCcgCmN5d8RAvfQAKCpI1LFryjP3DuJhWl/mx0X+PS7BgCgzo0f pWjktt2yir1QGvfnhrbz28Q= =jxLi -END PGP SIGNATURE- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Adding QListViewItems from a thread
I have a function in the main thread that adds an item to a QListView. If called from the main thread, this works fine. However if I call this same function from a separate thread, the items are displayed in the lsit view, but QlistView seems to lose the pointer(s) to the items in QListView. I have used the python thread module and have not put any locking in. this is my first effort at using of threads so I may have made some silly mistake.
