Steve, I'm sorry that I won't be able to discuss this with you further. Your response misrepresents what I have previously said on these subjects, is misleading as to the feature set we provide and our relationship with the open-source projects based on our code, and of an abusive tone.
Wez @ RealVNC Ltd. > -----Original Message----- > From: Steve Bostedor [mailto:[EMAIL PROTECTED] > Sent: 09 August 2005 12:36 > To: James Weatherall; John Aldrich; [email protected] > Subject: RE: Printing > > James, > > I have been a member of this list for years and I've seen many feature > requests that where "shot down" using some pretty harsh wording. I > never said that all feature requests where turned down due to cross > platform reasons, James. I said most. That's an observation > and not an > assumption. :) A good example is Microsoft authentication > such as the > one found in UltraVNC (http://www.ultraVNC.com). > > I have often given you much credit for your hard work and > generosity of > releasing VNC as a GPL product. My gratitude has never been silent. > However, to call the hard work of those that have built upon that > foundation "bloat" is not fair to them or the hundreds of thousands of > their users and supporters. I know that you have never > directly called > UltraVNC bloatware but you have implied it many times by calling the > features that they have painstakingly written into their version > "bloat". > > The guys at UltraVNC and TighVNC have spent many hours writing in > features that you call "bloat" and that I have seen turned > down on this > list and debated into the ground. Cross platform reasons > where the most > often sited. Sometimes these debates became very heated. > They deserve > a lot of credit for listening to their users. They have a huge (and > growing) loyal user base because of this. Their hard work > deserves just > as much praise as yours and does not deserve the term > "bloat". It runs > just as fast as RealVNC and has a very small footprint. > > When I see a feature request on the UltraVNC forums, the > developers take > the time to understand the request and a friendly discussion > is started. > I have never seen an UltraVNC developer say "do it yourself > if you want > it." They are always friendly and professional. > > Now, are you in favor of adding file transfer to the free version of > VNC? If not, please explain why. I don't see how it can be debated > that it wouldn't be used by enough people when just about every other > remote management solution out there has a file transfer > function built > in. It obviously has some mass appeal. > > - Steve > > -----Original Message----- > From: James Weatherall [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 09, 2005 6:56 AM > To: Steve Bostedor; 'John Aldrich'; [email protected] > Subject: RE: Printing > > Steve, > > I think it's a little unfair to say that feature suggestions are "shot > down". We work very hard to provide the refine and improve > the core VNC > system, and make that available under the GPL, enabling people to try > new > features as they see fit (this is how TightVNC et al exist). So when > considering feature suggestions, priority has to go to those that will > be > most widely useful and cause least code bloat, etc. > > I address the mail to you because it was a reply to your email. > > I have never said that remote printing won't feature in the > standard VNC > distribution, nor has anyone else, to the best of my knowledge. > > Cheers, > > Wez @ RealVNC Ltd. > > > > -----Original Message----- > > From: Steve Bostedor [mailto:[EMAIL PROTECTED] > > Sent: 09 August 2005 11:41 > > To: James Weatherall; John Aldrich; [email protected] > > Subject: RE: Printing > > > > Wez, > > > > It's not an assumption. I often see feature requests shot down on > > this list, and the most common reasons given relate to > cross platform > > issues. > > > > I'm not sure why this was addressed directly to me. John > > appeared to > > think so, also. I was simply agreeing with him. > > > > If you disagree, then please let us know why something like remote > > printing will never make its way into RealVNC so that we > don't have to > > assume. > > > > Thank you, > > > > Steve Bostedor > > > > -----Original Message----- > > From: James Weatherall [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, August 09, 2005 6:19 AM > > To: Steve Bostedor; 'John Aldrich'; [email protected] > > Subject: RE: Printing > > > > Steve, > > > > Why do you assume that the cross-platform nature of the standard VNC > > system > > prevents us from adding new features? > > > > Cheers, > > > > Wez @ RealVNC Ltd. > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Steve Bostedor > > > Sent: 08 August 2005 14:22 > > > To: John Aldrich; [email protected] > > > Subject: RE: Printing > > > > > > Yes, I'm sure that you are correct. I think that the RealVNC and > > > probably the TightVNC developers are more concerned with > > > cross platform > > > design than added functionality. > > > > > > The cross platform nature of VNC has always been one of its > > hallmarks. > > > It's understandable why they would be reluctant to add new > > > features with > > > this being the philosophy. > > > > > > - Steve Bostedor > > > http://www.vncscan.com > > > > > > > > > -----Original Message----- > > > From: John Aldrich [mailto:[EMAIL PROTECTED] > > > Sent: Monday, August 08, 2005 9:13 AM > > > To: Steve Bostedor; [email protected] > > > Subject: RE: Printing > > > > > > Steve, et al: > > > I am just guessing here, but I think the reason that VNC > > > isn't including > > > this sort of thing is because it would probably be hard to do > > > cross-platform, especially when printing from a *nix > > machine which you > > > are > > > viewing from a Windows desktop. :-) > > > John > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > > Behalf Of Steve Bostedor > > > Sent: Monday, August 08, 2005 8:30 AM > > > To: [email protected] > > > Subject: RE: Printing > > > [snip] > > > If you're on a LAN, you can share your printer and then print > > > to it from > > > the remote computer. For example, if you have an HP > > LaserJet 1100 on > > > your admin PC and you want to print to it from \\Computer1, > > just share > > > your printer on the network. > > > > > > On the remote computer do a "net use \\admin\laserjet1100" > > where admin > > > is your computer name and laserjet1100 is the assumed name of > > > the share. > > > That is basically how Windows Terminal services pulls the > trick off > > > except that it encapsulates the traffic along with the screen > > > traffic. > > > > > > It would be nice if VNC had this same feature but it looks > > > like there is > > > no real interest to include it. Until then, you need to use > > > the tactic > > > described above or the IP print server suggestion. > > > > > > Steve Bostedor > > > http://www.vncscan.com > > > _______________________________________________ > > > VNC-List mailing list > > > [email protected] > > > To remove yourself from the list visit: > > > http://www.realvnc.com/mailman/listinfo/vnc-list > > > _______________________________________________ > > > VNC-List mailing list > > > [email protected] > > > To remove yourself from the list visit: > > > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
