Understanding architecture of „raising hand“ feature && development / extending set of feedback icons in addition to the „hand“

[Tobias Welz]

Hallo Community,

 

we consider to contribute to the development of the BBB System on github with the following aspect, but we have no idea where to start, maybe the community can help us:

 

Evaluations on our BBB-teaching-events  figured out that there is a strong demand for more feedback icons during a bbb session – in addition to „raising hand“.

Because teachers are unable to look at the faces of students in aggregation in a conference environment, they would highly recommend the existence of icons for expressing „yes“, „no“, „smiling“, „lack of understanding“ …

Students and teachers confirmed that these icons would highly reduce the distance between participants, increase the social quality and enable more effective communication.

 

We hope to find a solution before BBB 1.1++, so we try to get an overview what to do. Our idea is to understand how the „raising hand“ feature works and extend the set of icons next to the „hand“. Normally it is necessary to display only one feedback icon at once, and this would go along with the current user interface template. Instead of only switching the „hand“ on and off, we would give the user the possibility to choose between a set of icons. Other participants should see the given feedback icon next to the participants name at the same position as the “hand”.

 

So our first questions are:

-          Do you think this is a good idea and worth to contribute to?

-          How does the „raise hand“ feature work?

-          Which server-side apps are involved?

-          Which files and functions are included in the source code on the client-side / server-side?

Hopefully to find a starting point

Regards, Tobias

[Chad Pilkey]

I would suggest taking a look at what Mconf has created. They have made some modifications to the BBB client and server, one of which is additional status icons. You can see their demo here, http://mconf.org/ and the source code can be found here, https://github.com/mconf/bigbluebutton/tree/mconf-live0.6.4. Your best bet would be to find the changes you want and either attribute where they came from or take inspiration from their implementation.

[Felipe Cecagno]

Hi Tobias,

You can check this branch: https://github.com/mconf/bigbluebutton/tree/090-expanded-status

It's the additional status feature isolated from the other things we've implemented on top of BigBlueButton (not the final 0.9.0-release), so you can merge it easily with BigBlueButton if you want.

Regards,

--

   Felipe Cecagno

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.
Visit this group at http://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Tobias Welz]

Wow Felipe,

thats exactly what we are thinking about. Amazing what you have already done in the mconf-project.

We will try to merge these changes into 0.9.1 and give feedback here.

Let's hope that this feature finds its way into the supported release of the BBB Team :)

Thank you so much - Tobias