haskal/jiti-meet - GitLain - Git with a cup of Lain

Author	SHA1	Message	Date
Bettenbuk Zoltan	2b4ace75ae	[RN] Add connection indicator	2019-04-16 17:33:23 +02:00
Bettenbuk Zoltan	4e78502c9e	Generalize indicators	2019-04-01 21:03:36 +02:00
Bettenbuk Zoltan	e65918564b	[RN] Add UI for raised hand feature	2019-04-01 21:03:36 +02:00
Saúl Ibarra Corretgé	2b91745af1	[RN] Fix dominant speaker and moderator indicators They are part of the Jitsi font now, there is no need to load them from FontAwesome.	2018-12-03 11:27:12 +01:00
Lyubo Marinov	3aff4967f1	Keep buttons in their associated features Contributing all buttons in one place goes against the designs that we set out at the beginning of the project's rewrite and that multiple of us have been following since then.	2018-05-15 14:12:38 -05:00
Lyubo Marinov	ca94563c51	[RN] Coding style The files styles.js are used (pretty much) on React Native only and each of them exports 1 name. Export it as default to cut down on source code.	2017-06-10 18:07:51 -05:00
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