Hello Scott.
I implemented the "Components" tab as you asked.
Both status "ZeBeDee" and "Wpcap" components are the part of NID data now.
Each Kaboodle instance checks statuses of above components at startup
and keeps them as a part of itself "device attributes".
Via NID data updating others Kaboodle instances know these statuses.
The list of Components already was scrollable.
That list implemented by a standard Windows common control *SysListView32*
(the right window of the standard application "Windows Explorer").
That control has a scrollbar, which will appear
when we'll insert a sufficiently great count of Components into it.
The "VNC" tab implemented as you asked also.
- Igor
----- Original Message -----
From: "Scott C. Best" <[EMAIL PROTECTED]>
To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, September 25, 2002 9:36 AM
Subject: Re: 21 Sept bug report
> Igor:
> Heya. That bug does look fixed now, thanks. Sniffing
> works well too.
>
> Going forward, here are the tasks I see ahead for you:
>
> 1. The "master node" setup. Only the master node pings. Only
> the master node connects with Gnutella to the GetEngaged
> servers. Registration and Partnership files only need to
> be installed on the master node.
>
> 2. Rework of the "Components" tab. I'd like to move the text
> to the top of the page going across, rather than at the side
> going down. I also want the list of Components to be shrunk,
> and made scrollable. Lastly, each of the 4 binaries can now
> be actively detected, instead of using just placeholders.
>
> 3. While we're at it, lets change the appearence of the VNC
> Service icon main tab as well, so that the text is at the
> top going across, not at the side going down.
>
> 4. We need a way for users to generate Partnership files without
> going to our servers. Presume that users also have GPG
> installed, and have each other's public keys already. They
> need a way to generate the file via Kaboodle and we need
> a way for Kaboodle to verify the integrity of the file when
> it's received (ie, checking it against their GPG private
> key). We should also add GPG to the Components list.
>
>
> That gets us to version 1.0. Thanks!
>
> -Scott
>
> On Mon, 23 Sep 2002, Igor Kotelevsky wrote:
>
> > Hello Scott.
> > I see the bug that you wrote.
> > The bug is fixed.
> >
> > About "List of Active LAN subnets".
> > We can use the function for that goal.
> > *void CCheckLan::GetMyNetworkInfo(CArrNetworkInfo& ArrMyNetworkInfo)*
> > Above function returns the array of struct
> > ST_NETWORK_INFO
> > {
> > DWORD dwIPAddr; // IP address
> > DWORD dwSubnetMask; // Subnet mask
> > }
> > which contains LAN subnets.
> >
> > - Igor
> >
> >
> > ----- Original Message -----
> > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > Sent: Sunday, September 22, 2002 9:01 PM
> > Subject: 21 Sept bug report
> >
> >
> > > Igor:
> > >
> > > Heya. Quick bug report. The latest code doesn't ping
> > > the class-C subnet correctly. Here's the tcpdump output when
> > > I hit "Refresh":
> > >
> > > 01:34:50.252383 192.168.123.130 > 193.168.123.0: icmp: echo request
> > > 01:34:50.252441 192.168.123.130 > 194.168.123.0: icmp: echo request
> > > 01:34:50.252496 192.168.123.130 > 195.168.123.0: icmp: echo request
> > > 01:34:50.252607 192.168.123.130 > 196.168.123.0: icmp: echo request
> > > 01:34:50.252660 192.168.123.130 > 197.168.123.0: icmp: echo request
> > > 01:34:50.252748 192.168.123.130 > 198.168.123.0: icmp: echo request
> > > 01:34:50.252840 192.168.123.130 > 199.168.123.0: icmp: echo request
> > > 01:34:50.252893 192.168.123.130 > 200.168.123.0: icmp: echo request
> > > 01:34:50.252982 192.168.123.130 > 201.168.123.0: icmp: echo request
> > > 01:34:50.253071 192.168.123.130 > 202.168.123.0: icmp: echo request
> > > 01:34:50.253165 192.168.123.130 > 203.168.123.0: icmp: echo request
> > > 01:34:50.253217 192.168.123.130 > 204.168.123.0: icmp: echo request
> > > 01:34:50.253308 192.168.123.130 > 205.168.123.0: icmp: echo request
> > > 01:34:50.253403 192.168.123.130 > 206.168.123.0: icmp: echo request
> > > 01:34:50.253493 192.168.123.130 > 207.168.123.0: icmp: echo request
> > > 01:34:50.253544 192.168.123.130 > 208.168.123.0: icmp: echo request
> > > 01:34:50.253633 192.168.123.130 > 209.168.123.0: icmp: echo request
> > > 01:34:50.253727 192.168.123.130 > 210.168.123.0: icmp: echo request
> > > 01:34:50.253819 192.168.123.130 > 211.168.123.0: icmp: echo request
> > > 01:34:50.253871 192.168.123.130 > 212.168.123.0: icmp: echo request
> > > 01:34:50.253964 192.168.123.130 > 213.168.123.0: icmp: echo request
> > > 01:34:50.254054 192.168.123.130 > 214.168.123.0: icmp: echo request
> > > 01:34:50.254144 192.168.123.130 > 215.168.123.0: icmp: echo request
> > > 01:34:50.254195 192.168.123.130 > 216.168.123.0: icmp: echo request
> > > ...
> > >
> > > The Kaboodle machine is "192.168.123.130".
> > >
> > > Also, can you please comment on the status of the
> > > "List of Active LAN subnets" function that VK needs. Thanks!
> > >
> > > -Scott
> > >
> > >
> >
> >
> >
>
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
