Alex:
        Hello! Thanks for the feedback. I've diced up your email and
have written some replies inline:

> I've thought of complaining about the interface graphics, but they kind
> of grow on you... and look low-bandwidth, too.  :)

        Honestly, I didn't like it all that much when it first came
out of the shop either. But yes, it grew on me too. :)

> I do have some things I wanted to ask about/suggest, and I thought I
> would do it in-forum to help raise people's "Kaboodle-awareness" levels.

        Perfect, thanks!

> (1) Service Selection
> I noticed on the VNC setup tab when you look at a node, it displays the
> path to the WinVNC executable.  Are you planning to add service startup
> parameters in there? It would be a logical place (even if duplicating
> functionality possibly) since there are several allowable switches for
> the server when running from the command line.

        Yes, it's exactly the place to put in some startup parameters.
It's actually putting some registry settings in there now, of course:
AllowLoopback to accommodate Kaboodle-tunneling, AuthHosts to accommodate
the Access-List, etc. What we're working on now, though, is an VNC
server startup process whereby Kaboodle starts up the VNC service (if
it needs to be) when another Kaboodle user initiates a VNC connection.
This solution can then accommodate other command line switches, the most
obvious one being the server's TCP port.
        Beyond that parameter, my perception is that ViewOnly would be
of the most interest. But I'm open for suggestions. I think 2 or 3
switches would accommodate 90-percent plus of the target userbase.

> (2) Visual Details
> I'm running XP Pro and also have ClearType enabled, which may
> contribute to the following as seen in the property sheets:
> (2a) When selecting text such as the displayed path in "Use this server:" the
> text after selection switches to my system font, but the background does not
> update - for example, I select:
> "C:\Program Files\ORL\VNC\WinVNC.Exe" - it flips to my system font for display,
> and still shows "C.Exe" at the end of the line in the font you have set up
> (Courier?)

        Ah, interesting. Can you email me (off list) a snapshot of
what you're seeing?

> (2b) I can't tell which tab I am on in the Properties sheet - all of the tabs
> have the thin white border separator below them, including the active tab

        Noted. On my list now.

> (3) Layout
> Just a general comment  - this is pretty slick!  I like the categories
> breakouts for everything including printers and appliances.

        Phew. :) The earlier versions (0.75 and prior) had a "flat"
layout, with no hierarchy. I started it up on my 20-something LAN and
was quickly redesigning. Part of what's coming in the next release
is a heuristic "OS detection" with 3 or 4 more icon types. So a
Printer will be put in the right place, as would a LinkSys box, as
would a iMac. Right now, I think only Services, PC's and Printers
get populated at startup (though you can drag devices to new groups,
and new position within groups, of course).

> I can't do much testing where I have it set up since I don't have any
> network appliances and the remote VNC nodes aren't VPN-accessible, but
> the overall structure is pretty nifty.

        Thanks; please keep the feature requests coming. My highest
priority for version 1.0 is getting the VNC tunnel going, in combination
with a VNC Gateway feature. This will allow users to open only one
TCP port on their firewall/router for Kaboodle's use, and then tunnel
an arbitrary number of simultaneous VNC connections via that tunnel.
This was much more difficult than I originally budgeted for. :)

cheers,
Scott
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to