Re: [Vnc2swf-users] Project Future

[Reid E. <ra...@tn...>]

I agree about the GUI. That can be done as a separate project that  
perhaps uses pyvnc code. (I'm a big PyQt fan myself).

About the file formats -- I wasn't saying to support them all, just  
architect it so that others can add more as they like. Once you have  
to support two formats, architecting to support N formats is not a lot  
of extra work. Good design and all that.

Wow, this discussion certainly stirred up some action on the list. :-)

Reid

On Thu Apr 16, 2009, at 11:18 AM, Yusuke Shinyama wrote:
> Hi Olivier,
>
> Thanks for your reply.  Okay... so first I think
> I have to state my opinion about the project:
>
> * I don't want to touch GUI. Getting involved with GUI is not  
> worthwhile because
>   we'd have to spend most of the time for just debugging the interface
>   rather than adding or stablizing the core functions.
>   (Actually, I think that adding the GUI interface to pyvnc2swf was  
> a mistake.)
>
> * Depending less external libraries is better.
>   We're currently using only Python and Pygame and we already have
>   compatilibty problems (between python 2.3/2.4/2.5 and pygame 1.7/1.8
>   and minor platform issues). If we start using other GUI libraries
>   (Tk/Gtk/Qt/Wx or whatever) or crypto/encoding libraries, I'd expect
>   a big mess. I personally do not want to get involved with that.
>
> * Just support a few rock-solid core functions is enough.
>   After all, this is a spare-time project. I just want something  
> that is
>   simple and working. Nothing fancy. I like a Unixy way.
>
> So there you go. I don't have much desire to take a control of
> this project, but this is how I can support it.  After spending
> several years on this I'm now realizing my interest is somewhat
> shifted.  So if anyone really wants to be ambitious and expand the
> whole functionality, go for it and I'll try to help it as much as
> possible.  Maybe it's the time to split the project or restart
> from scratch.
>
> Yusuke
>
> On Thu, 16 Apr 2009 12:21:37 +0200 (CEST), Olivier Hervieu <oli...@wa... 
> > wrote:
>>
>> So ... why don't we use this thread to discut about the future of  
>> pyvnc2swf and establish a wishlist?
>>
>> I begin :
>>
>> - safe file writer (every frames is write before the tool quit on a  
>> SIGINT or SIGTERM...).
>> - full flv support (cue points, keyframes)
>> - streaming (flv?, gstreamer?)
>> - better performance
>> - remove GUI from the pyvnc2swf core (we can write later a GUI when  
>> all in the command-line is ok and it remove also dependencies to  
>> useless packages for frame recording)
>> - removing the d3des.py and use something like pyCrypto for  
>> encryption purpose
>> - write more readable code (and use correct indentation (pyvnc2swf  
>> is indent with 2 char ... )
>>
>> Olivier Hervieu.