Message-Capable vs. Non-Message-Capable UIs

Hey,

So, I am working on my tiered object wrapper for connecting to the
eb-lite core, and am currently specifically working on the
non-message-capable part. I was wondering about some things, that
maybe could be answered here. Basically, what exactly is the difference
between a message-capable GUI and a non-message-capable GUI? Clearly,
they both need to do a lot of the same things. However, there is no
clear distinction for what makes sense for the non-message-capable one
to do, outside of "cannot send messages". For instance, some of the
questions that I have for a non-message-capable GUI are:

- Should we get the buddy list tree?
- Should we care about managing accounts?
- Contacts list management if we do care to get the contacts list?
- Do we care about the list of available services and their caps?
- What about managing our local account status?
- Do we care about receiving messages since we can't send them? logging?
- What aspects of the queuing system should we care about?
- Should we bother with preferences management here?
- What about actions? Would they be useful in a non-message GUI?

Thanks.

-- dobey