is Single Click not open source ?

ronan · Post by **ronan** » 2004-12-22 06:37

SC is just great, but I would like to access source code. I am not talking about the packaging tool created by Rudi (which is great and perfect for most people who can customize it without efforts and/or programming knowledge), but the source code of the light ultravnc server it embeds.

This would allow to tweak it a little more (either for specific needs, either for global improvements).

Moreover, speaking about such a sensitive tool, I'd rather know what it contains before using it in my company (no offense to development team, who is dedicated to us and who I trust, but just a wise concern in a professional environment).

I searched in CVS but was not able to find it. I asked this question a few times already within other topics with no success (no answer, I mean).
Is there a problem with sharing this specific part of the code ?

Regards,

Ronan

pgmoney · Post by **pgmoney** » 2004-12-22 08:45

ronan wrote: I searched in CVS but was not able to find it. I asked this question a few times already within other topics with no success (no answer, I mean).
Is there a problem with sharing this specific part of the code ?

Regards,

Ronan

It's in the RC19 source files, not a separate project...

#ifdef SINGLECLICKULTRA

Post by **Rudi De Vos** » 2004-12-22 08:47

SC was a code split RC19-3, to do it fast i just erase parts.

The problem is that i'm blocked for updates, the auto merging does not work.
The SC needs to be implemented as
#ifdef
#endif
in the general sourcecode.

This is already partly done, but was waiting for RC19 (stable)
to continue.
The manual cross check of all changed files is not done in 5 minutes, but #ifdef is the only way to keep it maintainable.

RC19 (stable) end december
SC in code tree january.

ronan · Post by **ronan** » 2004-12-22 09:51

OK: silly me for not thinking it might already be there !

Thank you for your answer guys.

Actually, using conditional compilation is perfect for my needs. So to generate my customized SC version, I just need to add/uncomment a #define somewhere, or is there a specific project file as well ?

Regards,

Ronan

californiajeff · Post by **californiajeff** » 2005-01-11 04:41

where can I download source for RC19? I looked in CVS and it did not show source for RC 19. It did show it for RC 18 though...

Post by **Rudi De Vos** » 2005-01-11 10:09

As i told in the previous mail....

SC source will be implemented in the RC19 tree, but we have give priority to finish RC19. (only partly done)
As soon we have a stable RC19, the SC code will be added as
#define in the normal tree.

Current SC test was just a hack, code parts removed, added...
This way it is just impossible to keep the source up to date and
put all new fixes in it.

Guest · Post by **Guest** » 2005-01-11 16:29

[quote="Rudi De Vos"]As soon we have a stable RC19, the SC code will be added as
#define in the normal tree.
[/quote]

I hope you know diff and patch!

diff -bruw ultravnc-RC18 ultravnc-SC > SC18
cp -r ultravnc-RC19 ultravnc-RC19+SC
patch -D SINGLECLICKULTRA -d ultravnc-RC19+SC -p1 < SC18

will do
#ifdef SINGLECLICKULTRA
// this is SC
#else
// this is VNC
#endif

Post by **Rudi De Vos** » 2005-01-11 18:05

Diff only works between
Orig code and SC and not between SC and the current cvs.....
All code changes in cvs after SC split are also considered as diffs but are actual bug fixes.

The only way is manual labor....
Anyway, a good time to cleanup and recheck some parts.

SC was just some tryout...if i would have known that people like it, all changes would have been added to cvs from start.

californiajeff · Post by **californiajeff** » 2005-01-12 18:53

Rudi De Vos wrote:Diff only works between
SC was just some tryout...if i would have known that people like it, all changes would have been added to cvs from start.

Single Click rulez!!! More ULtraVNC SC!!!

hardyx · Post by **hardyx** » 2005-03-11 09:29

Hello Rudi,

Thanks for creating this easy version, is a great help for computer people and their friends !!!

In my oppinion the easy way is create a new project in sourceforge. You can name it UltraVNC SC or choose a different name if you like.

As you say, is based in VNC but you are removing and adding your own lines of code. There is a lot of changes in the UltraVNC source and it will be more in the future.

What do you think?

Post by **Rudi De Vos** » 2005-03-11 10:14

I'm current adding it via
#ifdef SC
#ifndef SC
(50% done)

A seperate project is to hard to maintain, merging with the
standard ultravnc, to import bug fixes does not work. Code
become unusable after merge

Better one tree with seperate compiler options

Post by **Rudi De Vos** » 2005-03-13 15:34

SC added to cvs as
ultravnc/winvnc/winvncsc
(subproject of winvnc)

UltraVNC

is Single Click not open source ?

is Single Click not open source ?

Re: is Single Click not open source ?

I think SC must be a new project

SC added to cvs as