[PyKDE] Qt / PyQt Developer (freelancer/for hire) seeked in Duesseldorf/Germany or Vienna/Austria

[Andrew Smart]

Hi,

we are seeking Qt and/or PyQt developers with a strong C++/Python
background for support of our database based IDE development team.

The screen design frontend is written with C++/Qt, but a Python integration
(embedded / extended, probably with Boost) is on the agenda, as well
as supporting tools which will be build with PyQt.

The team is split into two locations:
- Duesseldorf, Germany
- Vienna, Austria

We are quite Open Source fans, we are using IRC, CVS and TWiki for
collaboration, for example. It is a young team with 8 members (currently).
I'm the project leader, I have deep experience in developing myself
as well as working in and managing of large teams. I'm a pythonic
(founding member of the PBF - Python Business Forum, speaker on the
last EPC) :-)

German language skills are a must.

If you are interested you can contact me under:

Andrew.Smart at smart-knowhow.de
A. Smart Team Consulting GmbH
Flurstrasse 77
40235 Duesseldorf, Germany
Phone: +49 211 60 15 699

Regards,
Andrew Smart


-----Ursprungliche Nachricht-----
Von: pykde-admin at mats.imk.fraunhofer.de
[mailto:pykde-admin at mats.imk.fraunhofer.de]Im Auftrag von Gerard
Vermeulen
Gesendet: Mittwoch, 8. Oktober 2003 16:50
An: phil at riverbankcomputing.co.uk
Cc: pykde at mats.imk.fraunhofer.de
Betreff: Re: [PyKDE] Changes in Current SIP & PyQt Snapshots


Great, the SIP's changelog scared me off.

On the other hand, there is a changelog for PyQt, but no source code (I know
this is supposed to be fixed, but it is broken again).

Gerard

On Wed, 8 Oct 2003 15:19:08 +0100
Phil Thompson <phil at riverbankcomputing.co.uk> wrote:

> With SIP v4 getting closer, there are a some major changes in current SIP
and
> PyQt snapshots.
>
> The first thing to say is that if you are using SIP v3.8 to generate your
own
> extension modules then the snapshots should continue to work - it's a bug
if
> they don't. I've stopped introducing incompatibilities to SIP v3 in order
to
> align it to SIP v4. Instead SIP v3 will support the old way of doing
things
> as well as the new (SIP v4) way of doing things.
>
> SIP now takes a -w flag which will issue warnings if you are using
features
> that will not appear in SIP v4. It doesn't identify all of them (eg.
utility
> functions called from handwritten code) but it's better than nothing.
>
> The biggest changes are that %MemberCode and %VirtualCode are deprecated
and
> replaced with %MethodCode and %VirtualCatcherCode. The result is that the
> amount of handwritten code needed is greatly reduced and much simpler.
>
> The sip.h file has been updated to properly identify which utility
functions
> are part of the SIP v4 API. If, when you have ported your handwritten code
to
> the v4 style, you think that there are v3 specific functions you still
need
> then let me know.
>
> The other area of change is build.py for both SIP and PyQt. The SIP
build.py
> now creates and installs a module called sipconfig.py. This contains
> information about the system configuration and utilities for use by
extension
> modules' own build.py. As a result PyQt's build.py is now 600 lines,
rather
> than 1600 lines, and takes fewer command line arguments. Eventually this
> mechanism will be extended so that PyQt's build.py will install a
> pyqtconfig.py module for use by extension modules that are built on top of
> PyQt.
>
> The current PyQt snapshot has been fully migrated to the new scheme. It
will
> work unchanged with both SIP v3 and v4 and contains no "If v3 ... else
..."
> sort of code.
>
> No date yet on when SIP v4 snapshots will be made available, but I hope it
> will be weeks rather than months.
>
> Phil
>
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
>

_______________________________________________
PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde