Re: [Vnc2swf-users] Project Future

[Olivier H. <oli...@wa...>]

What a wonderfull discussion ...

So if i resume ... there's two direction :
- some wants a recording tool (with or without GUI)
- some wants an authoring tool...

It's now time to choose.... I don't think that the same tool can do this two different things.

I love the idea to rename pyvnc2swf to pyvncrecorder.. and i think it sould be something like python remote recorder... because, with a modular architecture, and in the future, we will able to record remote protocols (not only vnc), and output this to several video format.

I'm agree, with other people, to take the lead on this project and "recode" pyvnc2swf in that way.

Authoring tool is a very exciting way too ... but it's not really in my interest to work on this kind of project.. So if someone wants to take the lead on this ... it will be great, and i will happy to collaborate :). 


----- Mail Original -----
De: "Reid Ellis" <ra...@tn...>
À: "General discussion about vnc2swf" <vnc...@li...>
Envoyé: Jeudi 16 Avril 2009 17h28:59 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [Vnc2swf-users] Project Future

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.


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Vnc2swf-users mailing list
Vnc...@li...
https://lists.sourceforge.net/lists/listinfo/vnc2swf-users