VK:
Hello! Some answers:
> Scott I have finished the group property pages and the bugs that you
> have listed down. But I am stuck up with the data persistence and
> service icon group property panels. Need your help.
>
> data persistence:
> -----------------
> Could you please send me the NID file hierarchy structure including the
> groups, Macs and services? And how are you planning to assign the group
> attribute to each device? What information will go in the Group node of
> the NID file?
Before your work started, Kaboodle's NID knew nothing about
groups. They didn't exist. You are going to have to implement something
using your best judgment. Please document what your decisions were,
of course.
In the NID hierarchy, I would think Groups should somewhere
"below" Network and somewhere "above" Devices. A Network would have a
list of Groups, in vertical display order. A Group entry needs a Group
Name and a Group ID. Each device in the NID could then have a Group field
to indicate its association, and a GroupPosition to indicate where it
is placed. These are all just suggestions.
Dimiter's team (<[EMAIL PROTECTED]>) is working on the
NID storage and inter-communication. Perhaps he has some suggestions?
> Service icons:
> --------------
> The code behind getting the tabs operational for the service icon is
> beyond the scope of my knowledge about the VNC and VPN. I will create
> the placeholders for the tabs and GUI associated with them. Is this
> adequate?
Yes, a one-page "information placeholder" is adequate. So if
I open the PropertyPanel for GetEngaged (the VPN piece) it would have
a little writeup on what the service is and how to start it. Same thing
for the "VNC" Service PropertyPanel. I'll speak with Igor's team about
adding PropertyTabs to make those Property Panels actually usable.
cheers,
Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
