headers
Konstantin Klyagin | 1 Jul 2004 10:06

Re: XML console + input

On Thu, Jul 01, 2004 at 05:01:32AM -0300, Dami?n Viano wrote:

> I have to say, being a jabber admin, I would love this feature
> deeply. This precise feature is what makes me fire up some other
> jabber client, time to time, when I have to debug something or do
> some administrative jabber thing. ;-)

You are welcome to participate in the discussion on how this
feature should look like. The main requirements for it are:

- to be useful and intuitive;
- to utilize same or almost same controls that are already present
  in centericq's interface. such as dialogs, scroll areas, buttons,
  menus, etc.
- to work not only for jabber, but for any other protocol that
  allows protocol dump output (leave this one to me).

> Being my first post, I think I'm allowed to say: "Great IM client
> konst!, thanks for all your hard work. I really enjoy it."

Yep. Glad you enjoy it.

--

-- 
konst at http://thekonst.net/
_______________________________________________
Cicq mailing list
Cicq@...
http://mailman.linuxpl.org/mailman/listinfo/cicq
Questions? Check the FAQ first: http://centericq.de/faq/
(Continue reading)

Permalink | Reply |
headers
Wolfram Schlich | 5 Jul 2004 23:48
X-Face

Re: XML console + input

* Konstantin Klyagin <k@...> [2004-07-01 10:07]:
> On Thu, Jul 01, 2004 at 05:01:32AM -0300, Dami?n Viano wrote:
> > I have to say, being a jabber admin, I would love this feature
> > deeply. This precise feature is what makes me fire up some other
> > jabber client, time to time, when I have to debug something or do
> > some administrative jabber thing. ;-)
> 
> You are welcome to participate in the discussion on how this
> feature should look like. The main requirements for it are:
> 
> - to be useful and intuitive;

Not necessarily. Most people I recommend to use CenterICQ start
whining that CICQ isn't intuitive at all, so... ;)

> - to utilize same or almost same controls that are already present
>   in centericq's interface. such as dialogs, scroll areas, buttons,
>   menus, etc.

This should be no problem.

> - to work not only for jabber, but for any other protocol that
>   allows protocol dump output (leave this one to me).

No.
We don't need that for other protocols, since Jabber is, to my
knowledge, the _only_ available IM protocol which is free,
decentralized and allows one to operate an own server _by design_.

Let's move on to the details:
(Continue reading)

Permalink | Reply |
headers
Iulian Ciorascu | 6 Jul 2004 00:23
Picon

Re: XML console + input

Wolfram Schlich wrote:

>No.
>We don't need that for other protocols, since Jabber is, to my
>knowledge, the _only_ available IM protocol which is free,
>decentralized and allows one to operate an own server _by design_.
>
>Let's move on to the details:
>
>I propose a new "subtype" of jabber contact, a jabber _server_
>contact. One can just treat it as a "normal" contact to send to and
>receive messages from.
>Showing _all_ protocol commands should be an option which can be
>toggled. If disabled, it only shows replies to explicitly sent
>commands (and the commands sent, of course).
>
>Want me to fake some screenshots? :o)
>  
>
You took the words from my keyboard :) . Yes, I think this is pretty 
intuitive (for a sys admin :) ) and not that hard to implement. But I 
wouldn't enable it by default. Instead of the enabled/disabled flag, I 
would put a disabled/all/related state, or something like this. Or even 
disabled/all/related/both :) .
But if you want to edit it in full screen (which seem very necessary 
since you would want to do a lot of copy/paste) it will need some work I 
assume. And a way to notify you if there are messages from other users 
(since you no longer have the contacts window).

Regards,
(Continue reading)

Permalink | Reply |
headers
Damián Viano | 1 Jul 2004 10:32
Picon

Re: XML console + input

On Thu, Jul 01, 2004 at 11:06:18AM +0300, Konstantin Klyagin wrote:
> You are welcome to participate in the discussion on how this
> feature should look like. The main requirements for it are:

  Thanks.

> - to be useful and intuitive;
> - to utilize same or almost same controls that are already present
>   in centericq's interface. such as dialogs, scroll areas, buttons,
>   menus, etc.
> - to work not only for jabber, but for any other protocol that
>   allows protocol dump output (leave this one to me).

  Well... whith all these requirements in mind, I'm thinking in a
'General option' like 'Protocol debug contact for' where you get to
choose the protocols you want (and are posible to dump). That would
create contacts named after the protocols (maybe the server hostname?) from
which you can see all the protocols actions as normal I/O IM messages, and
of course you can send them as you normally send messages.

  This would not require any interface change, and would be usefull...
but (there is always a "but"), because of the protocols verbosity,
maybe, the (proportionally speaking) small window for normal IM
messages could not be apropiate. 

  The only solution I see to this problem is to use the dialog available
from F9, but adapt it to show more than one message and include a text
area for input. This would be like a 'hide contact list and log window'
feature.
(Continue reading)

Permalink | Reply |

Gmane