B wrote:As an aside on the subject, it's moderately hilarious that in the midst of this "open source" VNC ecosystem it's still the few little closed source parts that cause real problems. I just noticed that CAD.EXE, in particular, is causing some cert-related problems that it seems could be easily rectified with access to the source.
Sigh. Here we go, yet again. Apparently, instead of moving towards a more open code base with the next version, Rudi and the development team are going to use yet another restrictively licensed technology and release the next UltraVNC with a modified GPL license.
This is just not good. In my opinion, at least. The intentions (better performance, I gather) are noble, but it really hampers the reputation, adoption rate, compatibility, and expandability of UltraVNC.
many of which actually work a bit better than the current VNC series of programs
The concept of "free/libre" open source software promises a lot more than a simple free ride for cheap people, but perhaps you have not yet come to understand any of that promise
I think what B means is creating an open source cad.exe by utilizing SASLibEx.
supercoe wrote:The biggest problem is I (at this point in time) don't have time to do a rewrite and learn a different language. I like the ease of use that UltraVNC and AutoIt gives me and I'm willing to give up open source "pureness" to get that (for now).
Enjoy nearly complete backward compatibility with AutoIt v2. <b>There is no need to learn new syntax and commands unless you want to.</b>
B wrote:Is he permitted to host a copy himself? It would be bad to be reliant on multiple sites to put a real-time user package together (in case the other site moves files, closes, etc.).
Users browsing this forum: No registered users and 0 guests