Re: [Gajim-devel] Alternative UI support

2018-04-10 Thread defanor
> But as forenjunkie suggested, perhaps it indeed would be easier to pick
> some library, make a basic client providing D-Bus interface and no UI,
> and then proceed with that external UI.

On the other hand, using Gajim would still provide some advantages over
the libraries that I've checked so far: those don't provide additional
features such as encryption, and Gajim GUI would be used to have at hand
for more advanced features than just a chat (i.e., chatting from Emacs,
but using service discovery and such from Gajim).

AIUI, currently Gajim allows external programs (including gajim-remote)
to send messages, but allowing them to read incoming messages as well
would enable use cases like this.
___
Gajim-devel mailing list
Gajim-devel@gajim.org
https://lists.gajim.org/cgi-bin/listinfo/gajim-devel

Re: [Gajim-devel] Alternative UI support

2018-04-10 Thread Yann Leboulanger

Hi,

First, which version are you using? We are doing a lot of work on a new 
design. 1.0 version is the start for that, much more is coming.


Now I'm not sure to understand what you want to do exactly. If you want 
to write acompletly new UI (in curses or QT or whatever) then that 
should be possible. "Just" replace all files in src by the ui design you 
want. common folder is independant of GUI.


Explain a bit more what you want to change in the UI, we can be more 
precise.


--
Yann


On 10/04/2018 16:32, defanor wrote:

Hello,

Gajim has a rather good XMPP support, but I'd prefer a different UI
(particularly that of Emacs; the clients available from it have worse
XMPP support).

Gajim's D-Bus interface would be handy for that, but apparently some of
the important events (e.g., [decrypted-]message-received) are not
included into the interface. Seems like one can write a plugin to
provide those (since those are exposed to plugins), but since many
events are already provided by the core, maybe those (and perhaps a few
more) should be exposed by it too, unless there are security concerns or
other reasons not to.

If that will be implemented, it may also be desirable to run Gajim
"headless", so that it would be usable (even if somewhat restricted) in
environments without X.

Would those be desirable changes, or should I focus on a plugin, or
perhaps there are other ways to achieve it?
___
Gajim-devel mailing list
Gajim-devel@gajim.org
https://lists.gajim.org/cgi-bin/listinfo/gajim-devel


___
Gajim-devel mailing list
Gajim-devel@gajim.org
https://lists.gajim.org/cgi-bin/listinfo/gajim-devel

Re: [Gajim-devel] Alternative UI support

2018-04-10 Thread forenjunkie

Hello,

Why you dont download one of the various xmpp libs and write a GUI around it?

Instead of doing the work to make Gajim headless and then write a GUI around it?

Regards
Lovetox



Von: defanor
Gesendet: Dienstag, 10. April 2018 16:32
An: gajim-devel@gajim.org
Betreff: [Gajim-devel] Alternative UI support

Hello,

Gajim has a rather good XMPP support, but I'd prefer a different UI
(particularly that of Emacs; the clients available from it have worse
XMPP support).

Gajim's D-Bus interface would be handy for that, but apparently some of
the important events (e.g., [decrypted-]message-received) are not
included into the interface. Seems like one can write a plugin to
provide those (since those are exposed to plugins), but since many
events are already provided by the core, maybe those (and perhaps a few
more) should be exposed by it too, unless there are security concerns or
other reasons not to.

If that will be implemented, it may also be desirable to run Gajim
"headless", so that it would be usable (even if somewhat restricted) in
environments without X.

Would those be desirable changes, or should I focus on a plugin, or
perhaps there are other ways to achieve it?
___
Gajim-devel mailing list
Gajim-devel@gajim.org
https://lists.gajim.org/cgi-bin/listinfo/gajim-devel

___
Gajim-devel mailing list
Gajim-devel@gajim.org
https://lists.gajim.org/cgi-bin/listinfo/gajim-devel