jiti-meet/react/features/overlay
Lyubo Marinov a9bdde193d Approach consistent filmstrip naming
We seemed to be using the names "film strip" and "filmstrip" (and,
consequently, their source code-conscious forms such as film-strip,
FilmStrip, etc.) In order to comply with our coding style which requires
a consistent one name for a given abstraction, choose one name and
rename the uses of the other name.

Wikipedia has a definition of a "filmstrip", I couldn't find a "film
strip". I guess our abstraction can be seen as what's described there.
When I google "film strip", I get results about "filmstrip" at the top.
That's why I chose "filmstrip".

Certain uses of "film strip" such as interfaceConfig.filmStripOnly and
in the external API I left untouched in an attempt to preserve
compatibility.

I wasn't sure whether CSS was tangled in compatibility so I made a
choice and renamed there was well.
2017-04-10 12:59:44 -05:00
..
components Approach consistent filmstrip naming 2017-04-10 12:59:44 -05:00
actionTypes.js Comply w/ coding style 2017-02-18 21:57:38 -06:00
actions.js Comply w/ coding style 2017-02-18 21:57:38 -06:00
functions.js ref(overlays): Replace the abstract class for overlays with overlay frame component 2017-03-24 13:16:14 -05:00
index.js Comply w/ coding style 2017-02-18 21:57:38 -06:00
reducer.js Prevent undefined JitsiMeetJS 2017-02-27 21:35:34 -06:00