making components consistent with the user's role: if the user is a participant, he won't see the control buttons (add, save, load), the lock button will be always disabled and the layouts combo will be enable only when the layouts aren't locked

added an attribute to the layout module to show or hide the module control buttons (add, save and load)

it still needs some refactoring, but it's working fine; this is the client side of the layout module which interacts with the server in order to (un)lock the windows layout

first version of the server side layout module - it allows users to lock and unlock the current layout; the layout is defined as a String, which should be a XML String but may be anything, this way is much easy to extend the layout management, since it won't need to change the server code

final version of the layout module before start to implement the mechanism to lock the windows layout

implemented ability to include the current layout to the list and to save all the layouts to a text file - now I'm implementing the ability to load the layouts from file (the inverse operation)

setup a default layout, that is applied in the beginning of the session; improved the animations; ignoring the video windows for the layouts - in the future we will be able to set a layout for the presenter window, for example, but now they are all ignored by the module

implements the very first prototype of the layout module; the admin put the layout definitions in a XML file, and the user may apply the layouts independently; the users also can extract the current layout to add directly to the xml file with the layout definitions

fix for issue 1221. However, need to double check which it's the best way to handle special characters

  time to process

  1. Convert the initial image that is sent to the server as grayscale
  2. Add some debug logs on the applet to determine which step is taking
     a long time. As suspected, it is on the network, esp. using http.
  3. Fix a bug in the server side. Turns out we are not incrementing the
     timestamps in constant interval like we do with the voice. Not doing so,
     doesn't allow the Flash Player to drop frames when packets arrive late.

  send the blocks to the server, and how long it takes for the server to receive all the blocks.

   disconnecting when the connection hiccups

   the screen caltured to other users

Do not process for Matterhorn  if webcam, audio, or desktop are not avai...