I just randomly have ideas sometimes and I just make a prototype first so I can see what kind of problems arise,
because when I just think about it I can't determine what I will need in order to make the app.
For example, all the functions that I found to do this type of stuff.
>_>
Yeah, I don't plan ahead.
Which is why I might fail my Software Engineering class when I'm a senior.
Ah well.
I'm in the process of learning how to make requirements sheets and such,
and unit tests. I'm not good at that kind of stuff right at the moment.
Well, the long and short of it is,
I don't have anything that would be of help to you, except ideas about how things can be done.
And the guy who wrote that vnc client probably has thought through all of these things more thoroughly than I have.
One thing I was also trying to make a prototype of, so I could integrate it into the VNC app if I ever got around to it,
was a VoIP client/server.
I was going to use Speex as the audio codec, and use pyMedia as the microphone input.
The only problem I had was that the pySpeex bindings were only compiled for python 2.2,
and I'm trying to get them to compile for 2.4.
I installed Visual Studio .net 2003, which is supposedly the compiler they used for python 2.4,
but I still haven't managed to get the kinks worked out well enough for a compile to work.
I think the speex guys changed around where all the source codes are located,
so I've been trying to re-arrange everything into the directory structure the python compile script expects.
So yeah.
If I get that working, the actual VoIP part shouldn't be too hard.
pySpeex looks like it should be able to integrate with pyMedia, and pyMedia makes microphone input super-easy.
I'm not sure what version of Visual Studio 2.5 was built with, but if I can get a copy of it, I'll probably try to compile pySpeex for 2.5 also.
On 11/4/06, Chris Hengge <
[EMAIL PROTECTED]> wrote:
Wow, that hasn't come up in my searching, thanks!
Looks like you are right and the project is dead, but the author did toss there code up for viewing so I can stumble around a bit there.On 11/3/06, Jonathon Sisson <[EMAIL PROTECTED]> wrote:Chris,
I don't know if this has been mentioned yet, but this site might be useful:
http://bdash.net.nz/blog/2003/12/24/python-vnc-client/
The code base has (last I heard) fallen stagnant, but it may very well
be worth a look as a starting point for your VNC project idea.
Jonathon
Chris Hengge wrote:
> Wow.. I have visions of writing a little wanna-be VNC client/server now
> using the ImageGrab.grab() =D
> This ImageGrab trick does exactly what I wanted. Thanks for the tip!
>
> Actually, I want to write a little package for the learning experience
> sometime over the holidays (plus I use VNC fairly often), but I can't
> find any direction, or any already made packages for python for the VNC
> protocol (no libs?).
>
> On 11/2/06, *Luke Paireepinart* < [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>
> >> Anyone know of a way to capture special keys like "Print Screen"?
> >> I have a small script to grab all they keycodes, but it doesn't
> seem to
> >> catch several keys on the keyboard. I've got a utility that I'd
> like to
> >> be able to automagically get a screenshot when something goes
> wrong so I
> >> dont have to hope the user can re-create the error. Universal
> support
> >> would be best, but WinXP is the main OS
> >>
> >>
> >
> > I'm not exactly sure what you want here :-) but if you want to
> capture
> > when the 'Print Screen' key (or any other key) has actually been
> > pressed, try pyHook. Note: pyHook only works on Windows!
> >
> Also note that if you want all of the keypresses, but you _don't_ care
> about the application with focus
> receiving the input, you can do a complete key grab using TKInter or
> Pygame, and probably the other GUI packages too.
> But, like I said, if you were, for example, typing an e-mail and you
> started a script that did a complete grab like this, you'd no longer be
> able to type
> into the e-mail window. Using pyHook, your program could see all the
> keypresses, but they'd also still be sent to the e-mail program.
> Actually, I've never tried it, but I'm pretty sure that's how the GUI
> packages' key capturing works.
> You may be asking 'well, it sounds like pyHook does a better job of
> this
> anyway!'
> Yeah, you're right.
> However, as Alan exclaimed, pyHook works only on Windows!
> So the solution I offered would be more portable.
> Hope that helps,
> -Luke
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Tutor maillist - Tutor@python.org
> http://mail.python.org/mailman/listinfo/tutor
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
_______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
