haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
jiti-meet/react/features/base/dialog/components/styles.js

22 lines
491 B
JavaScript
Raw Normal View History

[RN] Power to Dialog * Implement disabling buttons (like Web had the ability). * Use consistent colors (e.g. for the buttons) like the rest of the app (e.g. WelcomePage). * Enable AbstractDialog to await a thenable from onSubmit and Dialog to render a LoadingIndicator in place of the OK/submit button text.
2017-09-22 20:09:15 +00:00
import { ColorPalette, createStyleSheet } from '../../styles';
/**
[RN] Fix documentation comments * Javadoc introduced @code as a replacement of <code> and <tt> which is better aligned with other javadoc tags such as @link. Use it in the Java source code. If we switch to Kotlin, then we'll definitely use Markdown. * There are more uses of @code in the JavaScript source code than <tt> so use @code for the sake of consistency. Eventually, I'd rather we switch to Markdown because it's easier on my eyes. * Xcode is plain confused by @code and @link. The Internet says that Xcode supports the backquote character to denote the beginning and end of a string of characters which should be formatted for display as code but it doesn't work for me. <tt> is not rendered at all. So use the backquote which is rendered itself. Hopefully, if we switch to Markdown, then it'll be common between JavaScript and Objective-C source code.
2017-10-01 06:35:19 +00:00
* The React {@code Component} styles of the feature base/dialog.
[RN] Power to Dialog * Implement disabling buttons (like Web had the ability). * Use consistent colors (e.g. for the buttons) like the rest of the app (e.g. WelcomePage). * Enable AbstractDialog to await a thenable from onSubmit and Dialog to render a LoadingIndicator in place of the OK/submit button text.
2017-09-22 20:09:15 +00:00
*/
export default createStyleSheet({
/**
[RN] Fix documentation comments * Javadoc introduced @code as a replacement of <code> and <tt> which is better aligned with other javadoc tags such as @link. Use it in the Java source code. If we switch to Kotlin, then we'll definitely use Markdown. * There are more uses of @code in the JavaScript source code than <tt> so use @code for the sake of consistency. Eventually, I'd rather we switch to Markdown because it's easier on my eyes. * Xcode is plain confused by @code and @link. The Internet says that Xcode supports the backquote character to denote the beginning and end of a string of characters which should be formatted for display as code but it doesn't work for me. <tt> is not rendered at all. So use the backquote which is rendered itself. Hopefully, if we switch to Markdown, then it'll be common between JavaScript and Objective-C source code.
2017-10-01 06:35:19 +00:00
* The style of the {@code Text} in a {@code Dialog} button.
[RN] Power to Dialog * Implement disabling buttons (like Web had the ability). * Use consistent colors (e.g. for the buttons) like the rest of the app (e.g. WelcomePage). * Enable AbstractDialog to await a thenable from onSubmit and Dialog to render a LoadingIndicator in place of the OK/submit button text.
2017-09-22 20:09:15 +00:00
*/
buttonText: {
color: ColorPalette.blue
},
/**
[RN] Fix documentation comments * Javadoc introduced @code as a replacement of <code> and <tt> which is better aligned with other javadoc tags such as @link. Use it in the Java source code. If we switch to Kotlin, then we'll definitely use Markdown. * There are more uses of @code in the JavaScript source code than <tt> so use @code for the sake of consistency. Eventually, I'd rather we switch to Markdown because it's easier on my eyes. * Xcode is plain confused by @code and @link. The Internet says that Xcode supports the backquote character to denote the beginning and end of a string of characters which should be formatted for display as code but it doesn't work for me. <tt> is not rendered at all. So use the backquote which is rendered itself. Hopefully, if we switch to Markdown, then it'll be common between JavaScript and Objective-C source code.
2017-10-01 06:35:19 +00:00
* The style of the {@code Text} in a {@code Dialog} button which is
[RN] Power to Dialog * Implement disabling buttons (like Web had the ability). * Use consistent colors (e.g. for the buttons) like the rest of the app (e.g. WelcomePage). * Enable AbstractDialog to await a thenable from onSubmit and Dialog to render a LoadingIndicator in place of the OK/submit button text.
2017-09-22 20:09:15 +00:00
* disabled.
*/
disabledButtonText: {
color: ColorPalette.darkGrey
}
});