You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(8) |
Sep
(10) |
Oct
(28) |
Nov
(6) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(14) |
Jun
(8) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Brian P. <br...@us...> - 2007-07-11 14:48:31
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/07/11 07:48:34
Log message:
disable assertion in release_group()
Modified files:
vncproxy/src/:
sync.c
Revision Changes Path
1.12 +2 -0 vncproxy/src/sync.c
|
|
From: Brian P. <br...@us...> - 2007-07-09 17:23:50
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/07/09 10:23:51
Log message:
Replace assertion with conditional in release_group() to fix problem when
one server has exited, but another is sending its (last) rfb update.
Modified files:
vncproxy/src/:
sync.c
Revision Changes Path
1.11 +6 -5 vncproxy/src/sync.c
|
|
From: Brian P. <br...@us...> - 2007-07-06 19:16:13
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/07/06 12:16:16
Log message:
check for zero-size rect, fixes failed assertion
Modified files:
vncproxy/src/:
encode_tight.c
Revision Changes Path
1.11 +6 -1 vncproxy/src/encode_tight.c
|
|
From: Brian P. <br...@us...> - 2007-07-06 18:08:59
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/07/06 11:09:01
Log message:
Tight encoding was pretty much broke when using resolution scaling.
Need to pass around an extra rect with x/y bias info so we send the right
coords in the RFB message.
Modified files:
vncproxy/src/:
encode_tight.c
Revision Changes Path
1.10 +53 -33 vncproxy/src/encode_tight.c
|
|
From: Brian P. <br...@us...> - 2007-06-29 15:18:47
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/06/29 08:18:49
Log message:
Check if client is actually connected in update_client() before calling send_update(). Fixes fp exception (div by zero) since cl->res_scale isn't initialized yet.
Modified files:
vncproxy/src/:
sync.c
Revision Changes Path
1.10 +1 -1 vncproxy/src/sync.c
|
|
From: Brian P. <br...@us...> - 2007-06-21 20:18:07
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/06/21 13:18:08
Log message:
fix option error handling, again
Modified files:
vncproxy/src/:
main.c
Revision Changes Path
1.24 +2 -2 vncproxy/src/main.c
|
|
From: Brian P. <br...@us...> - 2007-06-20 15:28:56
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/06/20 08:28:59
Log message:
fix cmd line error handling bug
Modified files:
vncproxy/src/:
main.c
Revision Changes Path
1.23 +2 -2 vncproxy/src/main.c
|
|
From: Brian P. <br...@us...> - 2007-06-15 19:38:40
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/06/15 12:38:43
Log message:
disable an assertion for now
Modified files:
vncproxy/src/:
sync.c
Revision Changes Path
1.9 +2 -0 vncproxy/src/sync.c
|
|
From: Brian P. <bri...@tu...> - 2007-06-14 21:04:35
|
Dan Phung wrote: > Hi all, > > (apologies if I'm posting to the wrong mailing list, just let me know > and i'll post to the chromium list. I posted here since the documentation > I read was from vncproxy.) > > From http://vncproxy.sourceforge.net/setup.html, under section 4.3 > Chromium Runtime Configuration, I read that if I set things up > correctly...I will be able to run OpenGL application from my shell > simply by running them (ie. I shouldn't have to explicitly run > crappfaker). Is there any more documenation on how to do this? Yes, see the chromium docs "Auto-start / Auto-config". > I set > my environment as shown on the page...but I don't understand some > things, such as: > > - when do I startup the mothership? > > - when do I startup the crservers? > > - how do my applications know to use the crfaker libs? (I didn't > install chromium into /usr/lib, but rather it's sitting in > /home/foobar/src/cr-1.9/bin/Linux) You'll need to make a symlink pointing from libGL.so.1 to libcrfaker.so and one from libGL.so to libcrfaker.so That way, your app will actually link with libcrfaker.so instead of the normal libGL. -Brian |
|
From: Brian P. <br...@us...> - 2007-06-14 20:24:48
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/06/14 13:24:51
Log message:
make -d 1 the lowest debug level so errors are always printed
Modified files:
vncproxy/src/:
main.c
Revision Changes Path
1.22 +4 -2 vncproxy/src/main.c
|
|
From: Dan P. <ph...@cs...> - 2007-06-14 16:38:47
|
Hi all, (apologies if I'm posting to the wrong mailing list, just let me know and i'll post to the chromium list. I posted here since the documentation I read was from vncproxy.) From http://vncproxy.sourceforge.net/setup.html, under section 4.3 Chromium Runtime Configuration, I read that if I set things up correctly...I will be able to run OpenGL application from my shell simply by running them (ie. I shouldn't have to explicitly run crappfaker). Is there any more documenation on how to do this? I set my environment as shown on the page...but I don't understand some things, such as: - when do I startup the mothership? - when do I startup the crservers? - how do my applications know to use the crfaker libs? (I didn't install chromium into /usr/lib, but rather it's sitting in /home/foobar/src/cr-1.9/bin/Linux) regards, dan |
|
From: Brian P. <br...@us...> - 2007-06-12 20:52:18
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/06/12 13:52:20
Log message:
additional debug stuff
Modified files:
vncproxy/src/:
sync.c
Revision Changes Path
1.8 +12 -4 vncproxy/src/sync.c
|
|
From: Brian P. <br...@us...> - 2007-05-29 16:10:40
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/29 09:10:40
Log message:
generate an error if both -H and a command-line server/host are given
Modified files:
vncproxy/src/:
main.c
Revision Changes Path
1.21 +7 -1 vncproxy/src/main.c
|
|
From: Brian P. <br...@us...> - 2007-05-29 15:55:27
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/doc/
Changes by: br...@sc....(none) 07/05/29 08:55:26
Log message:
clarify how -H option works
Modified files:
vncproxy/doc/:
proxy.html
Revision Changes Path
1.8 +6 -1 vncproxy/doc/proxy.html
|
|
From: Brian P. <br...@us...> - 2007-05-28 17:01:25
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/28 10:01:27
Log message:
additional debug/logging for connect_to_display()
Modified files:
vncproxy/src/:
host_connect.c
Revision Changes Path
1.26 +9 -1 vncproxy/src/host_connect.c
|
|
From: Brian P. <br...@us...> - 2007-05-28 15:42:44
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/28 08:42:46
Log message:
emit debug msg when proxy compiled w/out DMX support
Modified files:
vncproxy/src/:
host_connect.c
Revision Changes Path
1.25 +3 -1 vncproxy/src/host_connect.c
|
|
From: Brian P. <br...@us...> - 2007-05-25 17:10:07
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/doc/
Changes by: br...@sc....(none) 07/05/25 10:10:08
Log message:
point out that Cr's DMX_INCDIR and DMX_LIB vars may need to be set in options.mk
Modified files:
vncproxy/doc/:
setup.html
Revision Changes Path
1.8 +6 -4 vncproxy/doc/setup.html
|
|
From: Brian P. <br...@us...> - 2007-05-24 14:51:39
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/24 07:51:41
Log message:
update some strings to say Proxy
Modified files:
vncproxy/src/:
main.c
Revision Changes Path
1.20 +5 -3 vncproxy/src/main.c
|
|
From: Brian P. <br...@us...> - 2007-05-24 14:43:57
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/24 07:43:58
Log message:
check remote_minor version, not local minor version in rf_host_ver() - fixes VNC SPU connection failure
Modified files:
vncproxy/src/:
host_connect.c
Revision Changes Path
1.24 +3 -3 vncproxy/src/host_connect.c
|
|
From: Brian P. <br...@us...> - 2007-05-16 22:02:19
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/16 15:02:10
Log message:
Implement the RFB 3.7 protocol to support unix-style login/authentication
to remote servers. Currently, the loginID used is the vncproxy's process
owner. We could specify a different ID on the command line or in a file.
Modified files:
vncproxy/src/:
host_connect.c host_io.h rfblib.h
Revision Changes Path
1.23 +252 -7 vncproxy/src/host_connect.c
1.4 +2 -1 vncproxy/src/host_io.h
1.6 +14 -1 vncproxy/src/rfblib.h
|
|
From: Brian P. <br...@us...> - 2007-05-15 20:53:48
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/15 13:53:49
Log message:
When authentication failed we were mis-handling the message from the server
indicating why. The message is handled properly now.
Modified files:
vncproxy/src/:
host_connect.c
Revision Changes Path
1.22 +14 -9 vncproxy/src/host_connect.c
|
|
From: Brian P. <br...@us...> - 2007-05-14 19:46:04
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/14 12:46:06
Log message:
Fix parsing in parse_host_info(). Before, a hostname like "foobar:1" was
parsed as hostname "foobar" with s_host_port=5901. Instead we really
want the full X display name like "foobar:1".
Get rid of unused s_host_port var.
Modified files:
vncproxy/src/:
host_connect.c
Revision Changes Path
1.21 +4 -23 vncproxy/src/host_connect.c
|
|
From: Brian P. <br...@us...> - 2007-05-14 15:47:48
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/14 08:47:48
Log message:
check for zero-sized rect in SendSubrect()
Modified files:
vncproxy/src/:
encode_tight.c
Revision Changes Path
1.9 +4 -1 vncproxy/src/encode_tight.c
|
|
From: Brian P. <br...@us...> - 2007-05-13 16:22:11
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/13 09:22:12
Log message:
added some temporary assertions to test for non-zero sized rect
Modified files:
vncproxy/src/:
encode_tight.c
Revision Changes Path
1.8 +3 -1 vncproxy/src/encode_tight.c
|
|
From: Brian P. <br...@us...> - 2007-05-13 16:22:06
|
CVSROOT: /cvsroot/vncproxy
Module name: vncproxy
Repository: vncproxy/src/
Changes by: br...@sc....(none) 07/05/13 09:22:05
Log message:
fix comment (s/F1/F9/)
Modified files:
vncproxy/src/:
client_io.c
Revision Changes Path
1.18 +2 -2 vncproxy/src/client_io.c
|