Tickets :: Comment on [#2011] Add Virtual Contact Lists

* Your Email Address
* Spam protection	Enter the letters below: .___..__ .__ . .. . \| [__)\| \\|__\|\| \| \| \| \|__/\| \|\|/\\|
Comment	> > >> Right, per above, the fact that different types of containers exist > >> is a fact, but can that maybe be handled in code? I would anticipate > >> that Turba would become contextually smart and not show UI elements > >> that don't make sense. > > > > IMO, it would be confusing for a typical user to just see a list of > "containers" that they have access to, yet in different areas of > Turba some of those lists would be there, and other times they > wouldn't be. If you don't differentiate them to the user, he/she > would have no way of knowing why sometimes the "Building A" list is > displayed and sometimes it's not. Your also leaving it up to the > user to remember on their own which lists are the "virtuals" that > they created... > > > >> In the case where you have to show options in > >> a mix of entries, you could throw an error if you tried to perform an > >> unsupported event on an item. > > > > Again, I think this would be much more confusing to the user as to > why he/she is getting errors when performing tasks on only some > sources. IMO, this would be like not telling a user that an > addressbook is readonly until he tries to write to it...when we give > him an error. He has just wasted time and effort on something the UI > should have told him wasn't doable from the beginning. > >
Attachment
Watch this ticket