what is that for then? 1.0-beta7 on 11/01/2006 * New 'privmsg' parameter: this is an array of nicknames that you want to speak to (in a private chat) at first chat loading (thanks to Johnny for his sponsoring : $130 USD) [3h00]
Ok, im on it to implement /invite, but i need some additional information. How can i create a new channel? is there some list available, what commands the client can handle?
you have to look at the /privmsg command. Then you will see that it uses the "cmdtoplay" user metadata. You can use it to play commands on others users. For exemple: a "/join yourchannel"
i split the issue on three new commands: /sepnew to create a new separee (which allows to limit the number of open separees) /sepinv to issue invitations to other users and /sepjoin to join a specific separee.
Ok, im stuck at the /sepnew stuff now. The problem is, that i see in the filesystem, that the new channel "sep_foo" is created but no tab opens. Instead, a JS-Popup appears giving me a OK message. The /sepnew command is nearly the same as the /join command, except for the limitations (max channels and stuff)
- I dont understand why that hapens, can you help me please? (EDIT: the tabs open, if i reload the chat by pressing F5. But i need a separation between channels and separees) - Where is the right place for managing what separees a user has open? The userConfig?
Last edited by Beni on Wed Nov 22, 2006 8:59 pm, edited 1 time in total.
Because then i am not able to limit the number of such channels a user can open. Its better if that goes separate or if private chats arent limited to 2 ppl anymore.
Additionally, it is difficult to implement some kind like access control. everybody can join any channel, separees however should only be joinable iv a invitation was issued.
Last edited by Beni on Wed Nov 22, 2006 9:32 pm, edited 1 time in total.
I would like to have a IRC like chat, so Creating the "separees" channel type is not a good idea because this kind of channel doesn't exists on IRC.
I think that you should use normal channels and you should relie on maxchannel parameter to create or not the new invited channel. To limit the public/private flag I think that you should do like on IRC and add a channel password (your can store it in metadata).
i haven't thought of channel passwords - but this sounds far easier to implement. The question is, how is the invited chatter notified about the password? does he autojoin? or does the password need to be printet to him so he can enter the channel manually?
I think a new parameter (password) should be added to the /join command : /join channelname password
So when someone is invited you just have to add the "/join channel password" to his cmdtoplay list. He will be "autojoined" to the channel. But I see one problem : the channel name can contains some spaces so it will be impossible to know what is the password and what is the channel name. One solution is to forbide spaces in channel names or to forbid spaces in passwords.