Hello Noriaki-san, The RFB protocol specification already defines the range of encodings used by the TightVNC project, including the "quality-level" encodings. So as long as your use of them is compatible with TightVNC's use of them, that won't be a problem.
Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: Hitachi Systems & Services, Ltd. > [mailto:[EMAIL PROTECTED] > Sent: 06 February 2007 01:31 > To: [EMAIL PROTECTED]; vnc-list@realvnc.com > Subject: Re: Hitachi-ZYWRLE Encoding Number (was RE: > Introduction of NewVNCcodec) > > > Hi, > > In message <[EMAIL PROTECTED]> > "Re: Hitachi-ZYWRLE Encoding Number (was RE: Introduction > of NewVNCcodec)" > ""Hitachi Systems & Services, Ltd." > <[EMAIL PROTECTED]>" wrote: > > >I think that the patch for RealVNC 4.x is meaningful and porting > >isn't difficult. So, I try it: > > > > * In rfb project, > > * Copy ZRLEEncoder.[cxx|h]/ZRLEDecoder.[cxx|h] to > > ZYWRLEEncoder.[cxx|h]/ZYWRLEDecoder.[cxx|h] and modify it. > > * register them in Encoder.cxx/Decoder.cxx. > > * Modify zrleEncode.h/zrleDecode.h for ZYWRLE. The modification > > is only functionable when include from ZYWRLEEncoder.cxx/ > > ZYWRLEDecoder.cxx. > > * Add our zywrletemplate.c. > > * Modify a bit of viewer for selecting our encoding. > > I forgot to say about another modification. > > * ZYWRLE need quality specification. we use Tight JPEG quality > pseudo encoding for this purpose. > So, I add pseudoEncodingQualityLevel0-9 to encodings.h and > add qualtyLevel member to ConnParams.[cxx|h] > > > Regards, > > --- > Noriaki Yamazaki > Administrator of micro-VNC > > Research & Developement center > Hitachi Systems & Services, Ltd. _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
