Closed GoogleCodeExporter closed 9 years ago
Original comment by leonardo...@gmail.com
on 16 May 2011 at 7:02
We decided not to use "bigbluebutton://" as default when the client is on a
mobile devise. We still use HTTP because the user might want to open the
session in his browser (if he has a flash).
The "bigbluebutton://" links are now provided in a separate page (a dialog),
that shows the link and also a QR code image that can be scanned by the mobile
application to join the conference.
The feature was implemented in bigbluebutton_rails and still needs improvements
(see Issue #95).
Original comment by leonardo...@gmail.com
on 20 May 2011 at 6:45
Original issue reported on code.google.com by
leonardo...@gmail.com
on 12 May 2011 at 12:23