VK:
Had an idea this morning:
> > I think working on GUI data persistence on NID hierarchy freeze will
> > make it more robust and well designed. Even if I add data in the
> > registry I need the exact position of group and services NID data
> > structure as many modules get the data from NID data hierarchy with some
> > assumptions. The assumptions at present are: 1. First network will be
> > local 2. The network will have all the PCS. 3. All the printers will be
> > under the masterPC etc. I cannot just add the groups and services at any
> > place.
> >
> > Please suggest the remedy to the problem.
Would it work to create a new registry entry entirely,
that managed all the group info, separate from the NID? It would
record which device/service (aka, which "resource") was in which
group, what the group name was, what position it was, etc. If
this group entry didn't exist in the registry, it would be
created (only once). One of the groups (the last one selected?
the first one from the top that's not My Sevices?) would be
designated the "default" group that discovered devices would
go into after initial setup.
When we recast the NID structure, we'll roll this into
it, of course. But for now...I think this gets us there.
-Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
