VK:
        Hello! The icons are reattached in a zipfile. I
hope they reach you this time. To your questions:

1. You're right that the NID is not in the code anywhere while
   it runs. Am working on that...

2. You should use the registry for data persistence until the
   NID is stored within the memory space of the application
   (or, until the NID is written into a file that is pointed
   to by the registry).

        I'm not sure I understand the "customized serialization"
benefit you mention, though. Could you describe this to me in
general terms? Thanks!

-Scott


On Mon, 18 Mar 2002, mailbox wrote:

> Hello Scott,
>
> There is couple of problems with NID:
>
>   1.. The NID file is not read anywhere in the code. It is used just to
> store the data in it on shutdown. The XML can have only one root, which is
> <network> in the current file format so adding remote network for simulating
> of the VPN is not possible.
>   2.. If I use NID for data persitence I will neither get the benefit of the
> serialization feature in the VC6.0 nor the customized serialization, which
> is the part of the code at present.  Please give me the way in which I
> should handle the data persistence. (Registry or NID?)
> I had asked you about the binary file because all the information required
> is stored in the registry and read from the registry on the kaboodle restart
> in the current version. (MSDN says that the value in a value entry can be
> data of a size up to 1 MB in any datatype except REG_DWORD, including
> arbitrary strings and raw binary data. However, to be efficient, values
> larger than 2048 bytes should be stored as files, with the filenames stored
> in the Registry.)
>
>
> Could you please send the group icon files again?  Some of them got
> corrupted.
>
> Regards,
> VK
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "mailbox" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, March 18, 2002 2:45 AM
> Subject: Re: Queries
>
>
> > VK:
> > Hello! Some answers and some feedback on your most
> > recent code:
> >
> > >   1.. How do I run VPN? I could not run it at my end. Please give me
> > > the instructions to make it running so that I can test the GUI for
> > > remote networks.
> >
> > The VPN has a bug somewhere in the current code that
> > prevents it from working. If you go back to version 0.72
> > (ftp.echogent.com/EchoFree) you can get a VPN working. There
> > are instructions in that ftp directory which explain how to
> > startup the VPN.
> > For now, you will have to simulate a VPN by putting
> > multiple Network entries in the xml NID.
> >
> > >   2.. How can I identify the VPN and VNC services running in the
> > > system? Will these components be the part of windows registry? In
> > > current  system the component manager gets the components from the
> > > registry. But since the application is not installed with all the system
> > > components it does not create the registry entries. Can you please give
> > > me the structure of registry entries for a component?
> >
> > Services will be stored in as just another resource entry
> > in the NID, like a PC or Printer. The VPN and VNC services will
> > ship with Kaboodle by default. The "component manager" part of
> > Kaboodle is old and will be revised in the future.
> >
> > > 3.. Can I create some binary file to make GUI (organization changes)
> > > persistent?
> >
> > It would be better to store this GUI information directly in
> > the NID. Please keep in mind that multiple instances of Kaboodle will
> > be running on the same LAN, and if one user changes a (for example)
> > "Group Name" in one instance of Kaboodle, these changes should
> > propagate to the other instances on the LAN. The "NID synchronization"
> > thread is a separate part of the app, of course.
> >
> > Some feedback now on the source code you sent:
> >
> > 1. I'm working now on some new icons for the Groups. I will send
> >    them along ASAP.
> >
> > 2. When I have a group selected, an "up arrow" should move the
> >    selection state to the group above, while a "down arrow"
> >    should move me to the group below. When I've selected a
> >    device *within* a group, the up-down arrows work correctly.
> >
> > 3. When a device or group is selected, a <RETURN> should open
> >    the PropPanel, and <ESCAPE> should be treated like a CANCEL
> >    to close that PropPanel.
> >
> > 4. As you imply in your 3rd question, the GUI changes are not
> >    persistent. If Kaboodle discovers a new device member, it
> >    refreshes the screen to the startup default, discarding any
> >    changes already made. In general, the startup default needs
> >    to happen only once: when the app first starts. After that,
> >    it should get the GUI organization from the NID file.
> >
> > Thanks!
> >
> > -Scott
> >
> >
> >
>
>

Attachment: GroupPC.zip
Description: Zip archive

Reply via email to