* webcam: add showVideoSourceDropdown
* webcam: update video device list when adding/removing a video device
* webcam: cleaner changes
* delete extraneous file
* webcam: store sources data in state
* webcam: regather sources after getting access
* webcam: put the source selector next to the buttons
* webcam: put the video source selection on its own row in mobile view
* website: show webcam video source dropdown
* enable webcam features in dev example
* facingMode takes precedence over deviceId, and not needed when specific device is selected
fixes issue where on mobile (iOS) the device selection was ignored due to facingMode being set to 'user'
* Remove “video source” copy, style select, deal with iOS zoom-in issue
Co-authored-by: Tsy-Jon Lau <tlau@parsys.com>
Co-authored-by: Artur Paikin <artur@arturpaikin.com>
The existing word describing drag n drop, while technically correct, is a bit weird when seen on a website.
This commit changes it into a more proper word.
The editor is unusable if you're importing stylesheets individually and leave this one out. In line with the documentation of other plugins, I added a note to import the relevant CSS file.
* Explicitly add moment timezone as a dependency and fix timezones for queries and displaying data to be based on user zoom timezone setting
* wip
* Remove async/await to match other providers, add comment to explain to/from conversion from local time to UTC
* Update comment, rename meetingInfo to plural to indicate multiple are retrieved
Unfortunately I can't figure out how to make the dependencies and
versions work out well here.
Instead, this uses a custom slide transition component. It is much more
simple than preact-css-transition-group, which supports animating groups
of components. The `<Slide />` component:
- can only support one element, that either exists or does not exist
- requires that the child element takes a `className` property, that it
passes onto its root element
- only uses `setTimeout()` for when the transition finishes
(in preact-css-transition-group, the `transitionend` event is used,
which is more _accurate_ but less _reliable_)
- hardcodes the transition duration
- hardcodes the transition name
This makes it much more limited. Hopefully the reduced complexity is
worth it.
If we have other transitions in the future, we can copy-paste this
component.
* Fix zoom provider date pagination so that it retrieves the correct start of the next month.
* Add comments to why we are checking dates and try to make initialization of date ranges more readable
* docs: document Companion 2.0 related changes
* docs: migrating from companion v1 to v2
* docs: correct node version range for companion 2.0
* website[docs]: update minimum node.js requirement for companion
