From MyWikiContainers
In tabSRMM terminology, message windows are often called containers. So whenever you see this term, it basically means a top level message window. It is called a container, because it acts as the top level parent window for the actual message session windows. The container implements a tabbed user interface and can hold any number of children and each child can be either a standard IM window (for 1:1 instant messaging chats) or a group chat window. TabSRMM also supports multiple containers. You can have as many as you want and there are 3 different ways for assigning a chat session to a particular container. A special case is the single window mode which disables the tabbed user interface. When active, each chat session will get its own top level window and any container window will hold exactly one child. ConfigurationMany options in tabSRMM are implemented on a per container basis, which means that different container windows can act or look different from each other. This is useful when you want to group and organize your chat sessions in one or another way. Identifying containersAny container is identified by its name, which must be unique. How container names are assigned depends on the way container windows are used in the plugin:
Auto opening message windowsThere are a few methods to configure the way, new message windows are opened when a message is received from some contact. By default, tabSRMM will not automatically open the message window. The message event will flash in the system tray until you click the tray icon or manually open the message window for the contact from whom you received the message. Some people find it more convent to have message windows created automatically when new messages arrive. You can configure this behaviour under Message Sessions->Tabs and layout[tab] with the following settings, all of them in the section "Message tab and window creation options:
How to assign contacts to a containerAs mentioned, you can have multiple containers which may or may not be wanted and can help you with organizing your chat sessions. In a fresh install, only one container is defined and it is called the default container. Also, there are 4 different methods to tell tabSRMM how it should assign chat sessions to a container. These modes can be chosen under Message Sessions->Containers[tab] Use contact list group names for organizing container namesThis option will tell tabSRMM to automatically create one container for each contact list group and add chat sessions as tabs. Let's assume you have a contact list group with the name Friends which holds a few of your more important contacts. Whenever you open a message window for one of the contacts in this group, tabSRMM will open the container with the name "Friends" and add the chat tab to it. If the container is already open, the chat window will be added as a new tab. This mode is fully automatic. Maximum number of tabs per containerThis mode, which is also fully automatic, will just limit the number of sessions per container window to the given number. Whenever a new session is created, it is added to the current container, unless this container already has reached the session limit, in which case, a new container will be created. Use single window mode (one tab per container)This mode will effectively disable the tabbed user interface. When active, each message session will be opened in its own top level window. Also, in this mode, container settings are global for all message windows. Only the size and position of the window will be saved individually for each contact or chat room. Default container mode (manual assignment)This is probably the most flexible method of using multiple containers. In this mode, you have full control over how many different containers you want to use and in which container a given contact should be placed when you open a message session. In a fresh install, only one named container is available. This is called the default container and it is used for any new message session, unless the contact had been assigned to a different container. However, you can change the assignment for any contact
Related reading
Revision: 1770
Last modified: 2009 / 12 / 16
|