[PyKDE] ActiveX

[Hihn, Jason]

Well my work on this assignment is drawing to a close. What we have
works really well. In a few months, I expect to be brought back on so
our work can be made to work in a browser.

What we have now is a x-platform solution. We store python scripts & ui
files on our device (ppc), and they are fetched by the PC application.
We then run them in an interpreter that is embedded in our application.
The output of the dialogs is collected and sent back to the unit. On the
unit, there is a user interface that launches the scripts locally. It
really is a superb solution - we don't need to know what firmware
version the unit is, and we don't have to be backwards or forward
compatible.

The idea would be to point a browser at the unit and be able to operate
the interface, a menu of dialogs, and run the selected dialog. To that
end, we import qt, and qtui. We use signals and slots, and have a rich
user interface with validation, run-time enable/disable and such.


> -----Original Message-----
> From: Phil Thompson [mailto:phil at riverbankcomputing.co.uk]
> Sent: Wednesday, December 08, 2004 11:59 AM
> To: Hihn, Jason
> Cc: pykde at mats.imk.fraunhofer.de
> Subject: Re: [PyKDE] ActiveX
>
> >
> > Does anyone know what it would take to get a QDialog  to display in
a
> > browser via PyQt? I'm hoping there's a simple example somewhere.
>
> The ActiveX support, which will require SIP v4.2, is only for
QAxWidget.
> In other words, it's to allow you to embed ActiveX controls in Qt
> applications and not the other way round.
>
> The reason for this is that some of the stuff is difficult to wrap and
I
> need people who really want to use this stuff to identify exactly what
> needs wrapping to make it useful.
>
> So - can you tell me exactly which classes and methods need to be
wrapped
> for you to do what you want?
>
> Phil
>



__________________________________________________________________________________________
This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries.
The information is intended to be for the use of the individual(s) or
entity(ies) named above.  If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message.  If you have received this electronic message in error, please notify us by replying to this e-mail. (1)