I understand the current implementation uses the screen twice in the
tags table. First, a tag is create with a name and a screen. Then an
array of screens is created where each array element is a table of
tags.

Does anyone else see value in divorcing the tag from the screen? My
original impression was that each tag was an independent entity, and
that each client was assigned one or more tags, where screens would
subscribe to one or more tags and display any client with a matching
tag.

Right now I've defined my tags tables and frustrated by my inability
to move tags across screens. I'm not as familiar with the code, would
altering the screen behavior be a huge project or just a tweak?

Thanks.

------------------------------------------------------------------
Russell Adams                            [email protected]

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

-- 
To unsubscribe, send mail to [email protected].

Reply via email to