Two considerations about xzibit
Oct. 16th, 2010 04:07 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
marnanelTwo things I'm considering about xzibit:
1) Permissions. At the moment there is no provision for the receiving side to reject the window. I could make a rule that you have to okay every new window, but then you would have a dialogue popping up for every dialogue, and even every menu. So I think I will make an accept dialogue that you have to reply to once, at the start of the connection, thus:
2) Doppelganger cursors. I already have a subsystem to make "doppelganger cursors" which track the mouse movements of the user on the other end of the connection. (Video of that here.) But RFB only has a way for the sending side to notify cursor movement, so we'll have to send the movements for the receiving side over the Xzibit protocol. I'm wondering whether I should just send all the movements over the Xzibit protocol and make things simpler. I'll probably accept RFB-based movement messages, either way.
1) Permissions. At the moment there is no provision for the receiving side to reject the window. I could make a rule that you have to okay every new window, but then you would have a dialogue popping up for every dialogue, and even every menu. So I think I will make an accept dialogue that you have to reply to once, at the start of the connection, thus:
2) Doppelganger cursors. I already have a subsystem to make "doppelganger cursors" which track the mouse movements of the user on the other end of the connection. (Video of that here.) But RFB only has a way for the sending side to notify cursor movement, so we'll have to send the movements for the receiving side over the Xzibit protocol. I'm wondering whether I should just send all the movements over the Xzibit protocol and make things simpler. I'll probably accept RFB-based movement messages, either way.
Another option
Date: 2010-10-17 03:30 am (UTC)Re: Another option
Date: 2010-10-17 03:44 am (UTC)