Hey there,
I really have to say that this modul went a big step forward in the last weeks ;). Great Job with the muc_submodul. But what I realy miss, which is already integrated into the xmpp-framework-modul is the noded based muc.

Is it possible to create a muc by creating a node and to get a overview about existing channels?

cheers

Comments

darklrd’s picture

darklrd commented

Hi IckZ,

Thank you. :)

Yes this seems like a nice feature(having node based mucs instead of regular bottom bar). But right now some must-have features are being implemented in the module(according to this timeline) in order to make a beta release.

Will try to include this at a later stage.

Regards

darklrd

IckZ’s picture

IckZ commented

Hey darklrd,
thanks for your reply! I'm "excited" what you are doin in the future! Great Job so far, I will try this module at the weekend!

best regards!
Chris

IckZ’s picture

IckZ commented

Hey darklrd,
whats with your roadmap - are you still working? I already looked at the modul and got the idea to set the channel name via var about the block.. I think that it should be easy to create a second block for node based mucs. You could activate this where ever you want or use the standard block to get into the "hall - room".

The second block easily gets the nid and the content of a special cck field wich provides the muc-name. If the cck field is empty you should also be able to join only the hall room..

Do you think that should work?

that0n3guy’s picture

that0n3guy commented

subscribing

IckZ’s picture

IckZ commented

my idea from #3 does not really work. I can change the server connections for the muc-room in the .tpl file but I think the .js file still wants to connect to the "muc-room-var" entered in the backend. Have to find out how to override this also in a template-file ;)

KeVroN’s picture

KeVroN commented

This is a pretty crucial use case for persistent MUC's. +1 and keep up the good work!