NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev, #1161 most downloaded on pub.dev
A Flutter package to use and make beautiful Material design based themes.
Latest stable
9.0.0
Last release 2 months ago
15 Sep 2026
Ships unpredictably
gaps range from 8 days to 10 months
Nearly every release is documented
notes for 46 of 46 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
66 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Impact: The impact of this style breaking change is only visible on the Material 2 type BottomNavigationBar in dark mode. When using the M3 mode, its…
Mar 18, 2023
This is the final beta v7 release before stable v7. There will be no new features or API changes in the FlexColorScheme package from this version to stable version 7.0.0. The only changes to stable will be potential bug fixes, typo corrections, API doc comment improvements and adding more tests.
The companion app Themes Playground, may get label improvements plus spelling and grammar corrections. Layouts in it may also be modified and improved as needed. It will not get any new features, but it may of course receive bug fixes.
The Themes Playground app built for this beta release is unfortunately not a SKIA renderer build, it is using the HTML renderer. This makes it less performant than the app would otherwise be. Additionally, scaled content, like the Themes Simulator panel in the Playground, is also fuzzier than it would be with the SKIA renderer. Due to an issue in Flutter stable (3.7.7), builds made with the SKIA renderer performs very poorly and crashes quite quickly. For more information see Flutter issue #122189. Hopefully, before the stable v7.0.0 release, a fix will be available. If not, a new build using the same package version will be made later and released when a fix is available.
FIX
Fixed bug in legacy theme secondary and tertiary color swapping when using seed generated ColorScheme. In dark mode, combining legacy swapping and seed generation did not swap secondary and tertiary colors for schemes where it should do so. This is now fixed. If seed generation was not used, the swapping worked correctly in dark mode. In light mode it worked correctly also when seed generated schemes were used. The swapLegacyOnMaterial3 feature was introduced in version 6.1.0, it has had this bug for this case since it was introduced.
Fixed bug where FlexSubThemes.drawerTheme was using BorderRadiusDirectional.horizontal with end radius instead of start radius as its endShape. This bug was introduced by version 7.0.0-dev.1 and has not been in any stable version.
The FlexThemeModeOptionButton now correctly displays its hoverColor, previously it was obscured by the colored boxes inside it.
The systemNavigationBarDividerColor issue #100027 in Flutter that in FCS v5 forced removing support for divider on the system navigation bar in Android, that was available via FlexColorScheme.themedSystemNavigationBar has been fixed. The issue could no longer be observed on Android versions 8 to 13 on Flutter 3.7.7 stable. The divider has been enabled again, and its test setting is also available in the Themes Playground app again. The extra SystemUiOverlayStyle call used as a work-around, for the same issue to fix an issue with Android 11, has also been removed, since the workaround was no longer needed.
Fixed a bug where when passing in a custom textTheme or primaryTextTheme, instead of defining text theme via fontFamily, that FCS tinted text feature, via subThemesData.blendTextTheme, was not being correctly applied to the custom text themes. This is now fixed. If subThemesData.blendTextTheme is not being used, then the used Typography, either via subThemesData.useTextTheme, or by using a custom FlexColorScheme.typography override, always gets correct brightness for both textTheme and primaryTextTheme, regardless of brightness on passed in text themes. They also get the used Typography appropriate opacities on their text styles. In practice, this means that M2 style 2018 typography has opacity on some text styles, while M3 style 2021 typography, is fully opaque for all text styles.
NEW
Add: drawerIndicatorOpacity to FlexSubThemesData.
It controls the indicatorOpacity property in the FlexSubThemes.navigationDrawerTheme used to customize the opacity of used color on the NavigationDrawer indicator.
Add: segmentedButtonUnselectedForegroundSchemeColor to FlexSubThemesData.
It controls the unselectedForegroundSchemeColor property in the new FlexSubThemes.segmentedButtonTheme used to customize the SegmentedButton.
Add: usedColors value 7.
In FlexColorScheme and FlexThemeData light/dark constructors, the usedColors now accepts value 7. When used, the primary, secondary and tertiary colors in the used input scheme, are used as defined, but primaryContainer, secondaryContainer and tertiaryContainer are computed. This is FlexColorScheme's own more Material2 version of seed generation of the container colors by using their main colors as input colors.
Add: bottomAppBarTheme, menuBarTheme and menuButtonTheme to FlexSubThemes.
Add: inputDecoratorPrefixIconSchemeColor, drawerWidth, drawerIndicatorWidth, drawerIndicatorRadius, drawerIndicatorSchemeColor, navigationBarIndicatorRadius, navigationRailIndicatorRadius, menuBarRadius, menuBarElevation, menuBarShadowColor, snackBarActionSchemeColor and bottomAppBarSchemeColor to FlexSubThemesData.
Add: menuRadius, menuElevation, menuOpacity, menuSchemeColor and dropdownMenuTextStyle to FlexSubThemesData.
Add: drawerSelectedItemSchemeColor, drawerUnselectedItemSchemeColor, tabBarIndicatorSize, and tabBarDividerColor to FlexSubThemesData.
Add: Static helper function onSchemeColor to FlexSubThemes.
Add: To FlexThemeModeOptionButton added properties semanticLabel, focusColor and setFocusOnTap. If setFocusOnTap is set to true, the button will request focus when it is tapped. Display of previously not shown hover and focus effects where fixed, they now correctly use hoverColor and the new focusColor.
Add: Property snackBarRadius to FlexSubThemesData, it controls the border radius via FlexSubThemes.snackBarTheme by using its radius property.
Add: Properties tabBarUnselectedItemSchemeColor, tabBarUnselectedItemOpacity, tabBarIndicatorWeight and tabBarIndicatorTopRadius to FlexSubThemesData.
Add: New configuration class FlexAdaptive used to configure on which platforms adaptive theming features are used. Including 100% unit test coverage for the new class.
Add: Four new FlexSubThemesData properties that uses the FlexAdaptive configuration class, to configure the features adaptiveRemoveElevationTint, adaptiveElevationShadowsBack, adaptiveAppBarScrollUnderOff and adaptiveRadius. The adaptiveRadius controls if the defaultRadiusAdaptive is used as value for effective global border radius instead of defaultRadius.
Add: Seven new FlexSubThemesData properties menuBarBackgroundSchemeColor, menuPadding, menuItemBackgroundSchemeColor, menuItemForegroundSchemeColor, menuIndicatorBackgroundSchemeColor, menuIndicatorForegroundSchemeColor and menuIndicatorRadius.
Add: Boolean property useInputDecoratorThemeInDialogs to FlexSubThemesData. Used to control if the application's themed input decoration is used or not, on time picker dialog theme text input fields. If not used, the time picker dialog uses null as input to its input decorator, in order to get the Flutter time picker default style. This toggle will also be used on date picker when/if it gets supported.
CHANGE
Style breaking: FlexSubThemes.blendTextTheme defaults to false.
In FCS before version 7, the default for blendTextTheme in FlexSubThemes was true, and blended text themes were used by default. Going forward if you want it, and also if you had not defined earlier and do not want to break your apps past style, set blendTextTheme to true.
Style breaking: Card elevation default 1 dp.
The Card opinionated sub-theme now defaults to null elevation, resulting in same default of 1 dp elevation as Flutter SDK in both M2 and M3 mode. Previously, FCS defaulted to elevation 0 dp on Cards when opting in on sub-themes.
Style breaking: ColorScheme.outline and ColorScheme.outlineVariant.
The FCS built-in computed none seeded values for ColorScheme.outline and ColorScheme.outlineVariant were modified. The new values are more in line with what you get with the M3 default seed algorithm, but plain grey-scale variants of them without any primary color blend. Technically light mode color for outline was changed from 30% lighten of light mode onBackground color to 45%, and outlineVariant from 60% lighten of onBackground to 75%. Likewise for the dark mode, but with darkening of the onBackground with the same percentage changes. The new values match the M3 design intent better.
Style breaking: lightSurfaceVariant and darkSurfaceVariant.
FCS v7 introduces FlexColor.lightSurfaceVariant and FlexColor.darkSurfaceVariant colors that are used when making none-seeded ColorSchemes. The colors are plain not tinted light and greys, matching the grey level of the tinted versions you get with seed-generated M3 colors. The colors are used as defaults for light and dark surfaceVariant color in none-seeded versions of generated FlexColorScheme color schemes. In previous versions surfaceVariant was just white and black in light and dark theme mode. To be able to better match the M3 color system, without using seed generation, this surface color should not be just white or black. The new surfaceVariant corrects this past design to improve compatibility with the M3 color system when not using seed generated color schemes.
Style breaking: NavigationBar
Changed the default NavigationBar height from 62 dp to 80 dp. The 80 dp height is also the M3 spec default height for a Material 3 NavigationBar in Flutter. This makes the FCS default NavigationBar theme less opinionated compared to M3 spec. The FCS default background color is now using surfaceVariant in M2 mode, and defaults in M3 to its spec surface with elevation tint. The FCS M2 surfaceVariant default makes it look a bit more like the M3 mode surface with elevation tint. Especially if you use a seed-generated ColorScheme or FCS surface blends. This makes the FCS difference in style between M2 and M3 mode less than before. Since M2 does not support surface tint, it cannot match it exactly.
NavigationBar from M3 default value of 80 dp, the ink level moves up or down with same amount as the deviation from the default 80 dp height. See issue report and illustration here FCS #114 as well as in Flutter SDK issue #117420. The issue is caused by a regression in Flutter 3.7.0 and 3.7.1. It does not exist in Flutter 3.3 and earlier. It is also fixed in the current master channel via PR 117473. This fix has now been cherry-picked (CP) via # 119553. This fix landed in Flutter hot-fix 3.7.2. To avoid the bug, upgrade to Flutter 3.7.2 or later.Style breaking: All component themes have null properties in M3 mode.
When enabling Material 3 and not enabling FCS sub-themes, and if no direct properties in FlexColorScheme raw constructor, or its light and dark factories are set in a way that requires creating a sub-theme to deliver the result, FlexColorScheme no longer creates any component sub-themes with none-null properties in Material 3 mode. In previous versions, it did so in a few cases. This is no longer required to deliver a nice starting point M3 theme, thanks to M3 now being almost fully supported in Flutter 3.7. When using FlexColorScheme with useMaterial3 set to true and its other properties at default values, and not enabling sub-themes, all component sub-themes will have null by default properties in FCS, just like in plain ThemeData. When using Material 2, FlexColorScheme as before even when not enabling sub-themes, still creates core component themes listed under core default in the documentation. This is done for FCS legacy reasons, and to be able to deliver the default slightly opinionated M2 style it had before component sub-themes were a part of its offering.
Impact: The impact of this style breaking change is only visible on the Material 2 type BottomNavigationBar in dark mode. When using the M3 mode, its dark mode icons have changed to the Flutter default style. When you opt in on FCS sub-themes in the M3 mode, it gets the same icon color as before, like it still gets in the M2 FCS style, with or without sub-themes enabled. Since the BottomNavigationBar is a Material 2 component, this should be less relevant in the M3 mode. With component themes on, it looks as before.
Note: Later when theme.scaffoldBackgroundColor and maybe also some other colors in current ThemeData are deprecated, FlexColorscheme will need to set those colors in their own sub-theme, also in M3 mode to be able to continue to deliver e.g. surface blends that impacts the scaffold background color separately from ColorScheme colors. Currently, it does this via theme.scaffoldBackgroundColor without using a component theme.
Style breaking: The SnackBar action button defaults to inversePrimary.
The SnackBar theming got property snackBarActionSchemeColor in FlexSubThemes. It defaults to M3 default inversePrimary. Earlier FCS used its foreground color with alpha 0xDD for the action button text color. Flutter's M2 defaults are poor designs and not very usable, but new Flutter M3 defaults are fine. As before, FCS uses a custom default style to fix M2 when using sub-themes. The M3 mode default is also opinionated, to make it match M3 defaults, set FlexSubThemes.snackBarBackgroundSchemeColor to SchemeColor.inverseSurface. By default, it uses the same style as its opinionated M2 style, which is onSurface alpha blended with primary and opacity, both alpha blend and opacity are different in light and dark theme mode. This was kept as the default also in M3 mode, so it can be used as an option there as well. If you want the pure M3 style, select inverseSurface instead. This part of the style is same as before so not style breaking, only SnackBar action button got a new default text color, that can be themed to any ColorScheme based color.
Style breaking: Tinted TextTheme was made less obviously tinted. M3-seeded ColorSchemes brings color tint to themes, if then also using tinted text, via the optional tinted TextTheme, is becomes too much. It is now more subtle and more usable also with seeded ColorSchemes. The changes are:
Style breaking: FlexColorSchemes own algorithm to compute light and dark theme container colors from their main colors, was modified to align better with expectation by the M3 color system. The changes are:
Style breaking: The border radius on ToolTip, PopupMenuButton, DropDownMenu and Menu no longer follow the global override for defaultRadius. These items should generally not be themed together with a large general radius override. They can still be modified individually.
API default value breaking: The unselectedIsColored parameters in FlexSubThemes functions switchTheme, checkboxTheme and radioTheme was changed to be nullable and to default to false if not defined. Previously, they were not nullable and defaulted to true. If you have not used these FlexSubThemes functions directly, typically they are not used directly, then this change has no impact on resulting themes, since FlexSubThemedata.unselectedToggleIsColored defaulted to false earlier as well, and set these sub-theme values to false by default, or true when so defined.
Label value breaking: The FlexColor.materialBaselineName name string was changed from 'M3 baseline' to 'Material 3 purple'.
Label value breaking: The FlexColor.materialBaselineDescription description string was changed from 'Material guide 3 baseline based theme' to 'Material 3 guide and default purple theme'.
Style breaking: The boolean FlexSubThemesData.interactionEffects now correctly control if color-tinted interaction effects for hover, focus, highlight, pressed and splash are used. The setting affects both M2 and M3 mode, and all in FCS covered component themes, to the extent that the Flutter SDK supports changing their interaction effects. All components have new tinted interaction effects, that are used when setting this property to true. When it is false, all components use Flutter SDK default grey styles.
Style breaking: In Material 2 mode the InputDecorator's border radius default value was changed from 16 to 10, to be less rounded by default.
Style breaking: The boolean FlexSubThemesData.tintedDisabledControls now correctly control if color-tinted disabled widgets are used. The setting affects both M2 and M3 mode, and all in FCS covered component themes, to the extent that the Flutter SDK supports changing their disabled color. All components have new tinted disabled styles, that are used when setting this property to true. When it is false, all components use Flutter SDK default disabled grey styles.
Style breaking: The ToggleButtons theme has a slightly changed style in both M2 and M3 mode. It now also correctly reacts to FlexSubThemesData.interactionEffects and FlexSubThemesData.tintedDisabledControls. The slight change of past theme was needed to support this.
Minor style breaking: The FlexColorScheme TimePicker dialog style in M3 mode was changed. It is now styled closer to the Material 3 specification. It is also closer to correct M3 style than Flutter is in version 3.7. When Flutter fully supports TimePicker M3 theming in the stable channel, FCS will use its native styling as its default too.
API breaking: In FlexSubThemes the floatingActionButtonTheme and timePickerTheme now require the colorScheme, previously it was optional in both. Unless you have used FlexSubThemes.floatingActionButtonTheme or FlexSubThemes.timePickerTheme directly as helpers to make custom component themes with them, and not as typically used via FlexSubThemesData, you will not notice this breaking API change.
API default value breaking: The FlexSubThemesData property useTextTheme, is now nullable and defaults to null. Previously it was not nullable and defaulted to false. As before, this boolean toggle determines if the Material 3 TextTheme and Typography is used.
Typography.material2021.ThemeData.useMaterial3 is true, then useTextTheme defaults to true and Typography.material2021 is used.ThemeData.useMaterial3 is false, then useTextTheme defaults to false, and Typography.material2018 is used.Typography.material2021 in Material 2 mode, and for using Typography.material2018 in Material 3 mode.ThemeData.useMaterial3 is false and sub themes are not used, the default typography is Typography.material2018. Note that if FlexColorScheme is not used at all, and your ThemeData has ThemeData.useMaterial3 set to false, then Flutter defaults to using obsolete Typography.material2014. In such a case, consider defining your typography manually to Typography.material2018 or why not even Typography.material2021.typography for FlexColorScheme or FlexThemeData, the useTextTheme property has no impact on used typography at all.The SegmentedButton unselected button foreground color defaults to the correct M3 spec color onSurface. This is a change from 7.0.0-dev.2, but not considered style breaking, since it has not existed in previous stable versions. Flutter 3.7.3 and earlier versions, via a spec deviation bug defaults to using primary color. See issue #119733 for more information. Using the new segmentedButtonUnselectedForegroundSchemeColor we can also define it to use the primary color, that Flutter in version 3.7 uses as default. This selection actually looks quite nice. Some might say it looks better than the M3 specification, but that is why easy theming configurations are there, so you can change it to fit your design preferences.
In FlexSubThemes the filledButtonTheme property baseSchemecolor was renamed to backgroundSchemeColor. This is a change from 7.0.0-dev.2, but not considered breaking since it has not existed in any previous stable versions.
Remove: The ListTileThemeData workaround added in version 7.0.0-dev.2 was removed from core defaults. The issue https://github.com/flutter/flutter/issues/117700 never landed in Flutter 3.7 and its workaround is not needed. Extra setting of property value of tileColor: Colors.transparent in ListTiles used in elevated popupmenus were also removed from the Playground app. In previous dev releases, they were used to hide the issue in M3 mode in the app, when FCS was not used.
Remove: The creation of IconTheme and primaryIconTheme when opting in on sub themes, was removed. Previously, their colors were set to be equal to the color of same typography color as
used on TextTheme nad PrimaryTextTheme, by style TitleLarge. This is no longer needed and also got in the way of getting the undefined default behavior for IconTheme in some widgets. Like new IconButtonThemeData in master channel.
THEMES PLAYGROUND
The Themes Playground is example number 5 in the package repository, originally included as the last step in a "how to use FlexColorScheme" training tutorial. Since its humble introduction it has grown into a notable and quite extensive application of its own, and is too extensive to serve as a very helpful tutorial step anymore. Despite having many advanced and useful features as a companion application to the FlexColorScheme package, it is architecturally identical to steps and examples 3 and 4 in the tutorial.
The application has an architecture that is a bit too simplistic to be extended to offer all features users are asking for. There is a plan to refactor it and make it into a proper stand-alone application developed in its own repo. This is potentially the last major release of the Themes Playground in its current form, and as being included with the FlexColorScheme package as "just an example" of how to use the package to build a dynamically themed app, which is how it started. It will still remain in minor and fix versions of v7, but will likely be removed in a future v8 version of the FlexColorScheme package.
As a tutorial and example app, the Themes Playground has never had any functional guarantees or even any tests at all of its own. This is still the case. The FlexColorScheme package has and always aims for 100% test coverage in its stable releases.
Despite Themes Playground not having any formal guarantees, it is extensively used and user tested during development of FlexColorScheme releases. In addition to being a very useful tool to configure and experiment with different themes for Flutter apps, and to quickly copy needed API configuration to get the same theme in your app. It is also an excellent tool to use during development of the FlexColorScheme package. It is used to visually see and verify that all features in the package actually do what is expected of them. The changes to the Themes Playground app are also generally already quite thoroughly tracked, going back many releases. Changes to version v7.0.0-dev.3, from v7.0.0-dev.2 are listed below.
usedColors value 7 to the "Theme Colors" panel. It is presented more logically in the UI than a number, to make it more understandable.NavigationBar icon and label colors. API already existed in FCS.NavigationRail icon and label colors. API already existed in FCS.ExpansionTile and ExpansionPanelList to panel ListTile and Widget Showcase.NavigationDrawer to panel NavigationDrawer.NavigationDrawer to panel Navigation Drawer.NavigationBar to panel Navigation Bar.NavigationRail to panel Navigation Rail.SnackBar action button to panel BottomSheet, Snack Banner. The UI also got better testing feature of both fixed and floating SnackBar and correct defaults info for different settings and modes.TabBar in M3 to panel TabBar. Unfortunately, the feature does not work due to a bug in Flutter. The issue has been fixed in the master channel via [PR #119690](https://github.com/flutter/flutter/pull/119690, but is not available in latest stable (3.7.7).TabBar to panel TabBar.NavigationDrawer to panel Navigation Drawer.FocusTraversalGroup:s and by letting important UI controls get focus on tap. This was done to make keyboard usage of the Playground easier. Its semantics were also improved, by adding the scheme names in the color selector to semantics.defaultRadiusAdaptive and adaptiveRadius to panel Component themes. They are used to define to make a platform adaptive override to the global border radius override value.menuBarBackgroundSchemeColor, menuItemBackgroundSchemeColor, menuItemForegroundSchemeColor, menuIndicatorBackgroundSchemeColor, menuIndicatorForegroundSchemeColor, menuIndicatorRadius and for menuPadding properties via start, end, top, bottom values to panel Menus and codegen for same props.AlertDialog, TimePicker and DatePicker dialogs to panel Dialogs and Widget showcase.TODO BEFORE FCS STABLE 7.0.0 RELEASE
FlexSubThemes with all its new component themes is only 73% tested now, all other package files have 100% test coverage.TODO AFTER FCS STABLE 7.0.0 RELEASE
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Updated to require minimum Flutter stable 3.7.0, compared to 7.0.0-dev.1 that required beta 3.7.0-1.4.pre.
Jan 25, 2023
CHANGE
FIX
redM3 faulty dark mode colors.THEMES PLAYGROUND
SegmentedButton.PopupMenuButton.Badge, so it gets featured as well.TODO BEFORE FCS STABLE 7.0 RELEASE
MUST DO: Review and do actionable TODOs in the code.
MUST DO: Review and fix test coverage. Test new colors too.
MUST DO: Review and test all tutorial examples.
MUST DO: Add important changes to docs.flexcolorscheme.com:
After release, more updates to FlexColorScheme docs:
MAYBE: Make tinted disabled controls apply consistently to all controls when applied.
MAYBE: Make tinted interaction effect apply consistently to all controls. New M3 widgets need to define it in their own sub-themes to get them, they don't use the hover, focus, highlight color from ThemeData for their defaults.
Postponed TODOs, that were planned for FCS stable 7.0, but moved forward to 7.1 or later.
This keeps the in Flutter SDK to be deprecated ThemeData.dividerColor always same as actually used effective Divider color. Thus, if an app uses Theme…
Jan 23, 2023
This major release does not contain any breaking API changes. However, the major version is bumped because some past styles and defaults, when opting in on Material 3, have been slightly tuned to better align with new Material 3 widgets and design, included in the Flutter 3.8/4.0 (?) release. The new features are also significant.
NEW
Added 12 new Material 3 color schemes: redM3,pinkM3, purpleM3, indigoM3, blueM3, cyanM3, tealM3, greenM3, limeM3, yellowM3, orangeM3 and deepOrangeM3 for a total of 52 built-in light and dark theme pairs. These schemes work well in Material 3 with or without seed generation. But using FCS advanced and flexible key color-based seed generation is recommended when using Material 3. You can always lock e.g. primary and tertiary color to custom brand color values you used as keys.
Added support for new ColorScheme colors scrim and outlineVariant.
Added support for fontFamilyFallback and package so that a copyWith on FlexColorScheme generated ThemeData is not needed to use them.
Added support for Material 3 buttons FilledButton and FilledButton.tonal.
FlexSubThemes.filledButtonTheme that is controlled via FlexSubThemesData properties filledButtonRadius, filledButtonSchemeColor and filledButtonTextStyle.FilledButton it was noticed that variant FilledButton.tonal cannot be themed separately, see issue: https://github.com/flutter/flutter/issues/115827.Added option to keep using the M2 style Divider in M3. The in M3 used primary color tinted outlineVariant does not fit on any color. The M2 style based on black or white with opacity does. It is also less prominent than the M3 style and may be preferred. Set FlexSubThemesData property useM2StyleDividerInM3 to true to use the M2 style in M3. Defaults to false.
ThemeData.dividerColor to ThemeData.colorScheme.outlineVariant when ThemeData.useMaterial3 is true. This keeps the in Flutter SDK to be deprecated ThemeData.dividerColor always same as actually used effective Divider color. Thus, if an app uses Theme.of(context).dividerColor while it still exists, to set a color to it, and expects it be the same color as effective Divider color, it will be so in FCS, regardless of if M2 or M3 is being used. This is not the case in Flutter SDK by default, see issue https://github.com/flutter/flutter/issues/117755 for more information.Added elevation to FlexSubThemes.timePickerTheme, and make it use the dialog shared FlexSubThemesData.dialogElevation setting. This property does not yet exist in Flutter beta 3.7.0-1.4.pre. It is thus unsure if it will land in next stable Flutter, if it does not it will be commented and removed for the next FCS release as well.
Added boolean tintedDisabledControls to FlexSubThemesData. If set to true, disabled widgets will get a hint of their active main color when disabled. In future minor versions, this will also apply to components that use own themed settings for disabled color, not only to the ones where disabled color controlled by ThemeData.disabledColor. Previously tinted disabled color for ThemeData.disabledColor was included and defined when FlexSubThemesData.interactionEffects was set to true. It is now instead controlled by this separate tinted disabled-controls setting. Defaults to true, for an FCS opinionated default. This matches past default when it was included in FlexSubThemesData.interactionEffects.
Added boolean inputDecoratorFocusedHasBorder to FlexSubThemesData. Default to true. If set to false, there is no border on the InputDecorator, typically used by text fields, when the input decorator is focused. It controls the new parameter focusedHasBorder in FlexSubThemes.inputDecorationTheme.
Added SchemeColor value inputDecoratorBorderSchemeColor to FlexSubThemesData. It is used to define and customize the border color of InputDecorator on e.g. TextField. It controls the new parameter borderSchemeColor in FlexSubThemes.inputDecorationTheme.
Added appBarTheme and tabBarTheme to FlexSubThemes.
Added Material 3 styling to TabBar when M3 is used. Use FlexTabBarStyle.flutterDefault to get the SDK default colors in M3 mode. TabBar may get more configuration options in the next FCS version.
Added double value appBarScrolledUnderElevation to FlexSubThemesData. It is used to define and customize the themed scrolled under elevation of the AppBar. It controls the new parameter scrolledUnderElevation in FlexSubThemes.appBarTheme.
Added SchemeColor value toggleButtonsUnselectedSchemeColor and toggleButtonsBorderSchemeColor to FlexSubThemesData. They are used to define and customize the themed unselected button and border color of ToggleButtons. They control the new parameters unselectedSchemeColor and borderSchemeColor in FlexSubThemes.toggleButtonsTheme.
Added SchemeColor value sliderIndicatorSchemeColor, and enum FlexSliderIndicatorType value sliderValueIndicatorType, plus enum ShowValueIndicator value sliderShowValueIndicator to FlexSubThemesData. They control the new parameters valueIndicatorColor, valueIndicatorType and showValueIndicator in FlexSubThemes.sliderTheme.
Added SchemeColor value drawerBackgroundSchemeColor and double values drawerRadius, drawerElevation to FlexSubThemesData. They control the new parameters backgroundSchemeColor, radius and elevation in new sub-theme FlexSubThemes.drawerTheme.
Added menuTheme to FlexSubThemes, it provides styling for elevation, radius and background color with optional opacity for the new Mw components MenuAnchor, MenuBar and DropDownMenu. The same FlexSubThemesData that are used for PopupMenuButton are used to control this theme. Those are popupMenuRadius, popupMenuElevation, popupMenuSchemeColor, and popupMenuOpacity.
Added timePickerElementRadius to FlexSubThemesData that can be used to control elementRadius in FlexSubThemes.timePickerTheme, it changes the themed border radius of the time input entry elements.
Added segmentedButtonRadius, segmentedButtonSchemeColor, segmentedButtonUnselectedSchemeColor, segmentedButtonBorderSchemeColor and segmentedButtonBorderWidth to FlexSubThemesData they control the equivalent properties in the new FlexSubThemes.segmentedButtonTheme used to customize the SegmentedButton.
CHANGE
Style change on tinted disabled components when opting in on tintedDisabledControls. It is visually breaking, but subtle. Disable opacity alpha and alpha blend constants where tuned, kDisabledAlphaBlend from 0xAA (67%) to 0xCC (80%) and kDisabledBackgroundAlpha from 0x31 (19%) to 0x26 (15%). The new tinted disable colors look better. They are close in style to default grey ones, with a subtle primary tint, while still being more legible than in previous versions. Opting in on tinted disabled components is still not yet available on all components. It is more available in M2 mode. In upcoming minor releases, tinted disabled components will be made available on all themed components and consistently applied in both M2 and M3 mode. More visual tuning of this feature may be required in later releases.
Removed in version 6.1.0 included manual M3 elevation tint for BottomSheet and PopupMenuButton, in Flutter 3.7.0, the tint is included automatically as it should be and we no longer need the workaround.
The ListTileThemeData was added to core defaults. It sets ListTileThemeData.tileColor to Colors.transparent if ThemeData.useMaterial3 is true. This is done to avoid issue: https://github.com/flutter/flutter/issues/117700. This extra M3 core default theme fix will be removed as soon as the issue is fixed.
Changed FlexColorScheme.bottomAppBarElevation to be nullable. In M2 mode if is null, it follows defined appBarElevation as before. In M3, it is kept null in order to default to M3's default elevation of 3, so that BottomAppBar get elevation tint by default. In M3 mode a minor spec deviation was noted in Flutter SDK and reported here https://github.com/flutter/flutter/issues/118150.
Changed FlexColorScheme default BottomAppBar color to be colorScheme.surface, same as Flutter default. Previously FlexColorScheme used colorScheme.background color as an opinionated default. The change is minor, and in many designs the color values are the same.
The Material buttons ElevatedButton, OutlinedButton and TextButon, now only create custom sub-theme properties in Material 3 mode when using none default (none null) values. Previously, they created sub-themes for some properties corresponding to the default values. This task now falls back to the role of default widget behaviour, as it should. Effective styles are unchanged.
Previously existing "native" Material 3 color schemes, materialBaseline, verdunHemlock and dellGenoa were changed to use Material 3 error colors, also in Material 2 mode and when not using seed colors.
When making seed generated ColorScheme with a custom surfaceTint color. This tint color is now also used as seed-key for the neutral and neutral variant tonal palettes. Flutter SDK can only use
primary color as seed-key for the neutral colors. This limitation in Flutter makes using a custom surfaceTint in seeded ColorSchemes less usable with often unappealing results. This happens because the custom tint color then differs from the slight primary tint that is hard coded into Flutter's seeded neutral colors used for surfaces and backgrounds, and the colors may clash. In FlexColorScheme the custom tint color is automatically also used to slightly tint the neutral colors used for surfaces and backgrounds in the seed-generated ColorScheme. The same color is then also used as ColorScheme.surfaceTint color. This makes the custom elevation tint color match the custom seed-tinted surface and background colors. This feature is enabled by the FlexSeedScheme package starting from version 1.2.0-dev.1. When using a custom surfaceTint color, the same color is also used as the surface alpha blend color, when using SurfaceMode and blendLevel to adjust surface color with or without using seed generated ColorScheme. Ensuring that neutral seed tint, elevation and surface blend color always match, as they should.
Changed, or one could call it fixed SnackBarTheme action and close icon colors. They are now also themed automatically to fit on selected SnackBar color.
The boolean FlexSubThemesData.interactionEffects no longer modifies ThemeData.disabledColor. This part of the control is now instead controlled separately by FlexSubThemesData.tintedDisabledControls.
The InputDecorationTheme, can now be configured to match Material 3 for critical styles if so desired. It uses a few opinionated values that give it a slightly different style by default. It can be configured to match M3 defaults if so desired. FCS does one opinionated adjustment to error border and suffix icon. It keeps them error colored on unfocused-hovered error state, instead of onErrorContainer. The M3 default looks odd. This FCS change is considered an opinionated M3 style fix in FCS. The M3 default of setting unfocused hovered error floating label also to onErrorContainer, is also keeping FCS own past style error.withAlpha(0xA7), which looks more refined. There is no way to set these settings back to the M3 default style within FCS. You can of course as always adjust them and anything with copyWith on produced ThemeData if needed.
Added M3 slider support with correct DropSliderValueIndicatorShape in M3 mode.
Added theming for TimePicker that corrects Flutter SDK issue https://github.com/flutter/flutter/issues/118657 when using FCS component sub-themes.
Made tabBarStyle in FlexColorScheme, FlexColorScheme.light, FlexColorScheme.dark, FlexThemeData.light and FlexThemeData.dark nullable and null by default. In M2 mode tabBarStyle defaults to FlexTabBarStyle.forAppBar as before. However, in M3 mode, if not defined, it defaults to FlexTabBarStyle.flutterDefault, producing a style matching M3 default TabBar.
THEMES PLAYGROUND
NEW
BottomSheet independently.Typography workaround in Playground app. Workaround was used before due to issue https://github.com/flutter/flutter/issues/103864 that is now fixed in Flutter by https://github.com/flutter/flutter/pull/110870.ColorScheme, when FCS is not in use.FilledButton and FilledButton.tonal, see issue: https://github.com/flutter/flutter/issues/115827 for info on current theming limitations in the SDK for these new buttons.useM2StyleDividerInM3 to panel Component Themes with name "Use Material 2 styled Divider in Material 3". Playground defaults this setting to ON (true), but default in API is false. Rationale for keeping it on in the Playground when using component sub-themes; it just looks better than M3:s new default (opinionated). When using M3 and FCS component themes, for a true M3 styled Divider, turn OFF the setting.SegmentedButton in panel Selection Buttons and to Widget Showcase.SegementedButton to control its colors, border radius and width.Drawer and NavigationDrawer in the new Drawer panel and to the Widget Showcase. Also added controls to theme color, border radius and elevation of the Drawer. The border radius follows the global border radius setting if it is used.BottomAppBar in panel AppBar and also to the Widget Showcase.BottomAppBar elevation setting to Playground in panel AppBar.DropdownMenu in panel Text Field, Menu and to Widget Showcase.MenuBar in panel Menu and to Widget Showcase.MenuAnchor in panel Menu and to Widget Showcase.PopuMenuButton not also control the menu style of DropdownMenu, MenuBar and MenuAnchor.TextField has a border to panel Text Field.TextField to panel Text Field.TextField background color to panel Text Field.TextField settings to match M3 default style.AppBar to panel AppBar.ToggleButtons to panel Toggle Buttons.RangeSlider in panel Slider and to Widget Showcase.Slider value indicator color, visibility and value indicator type.FIX
tileColor in M3, until a fix for https://github.com/flutter/flutter/issues/117700 lands via https://github.com/flutter/flutter/pull/117965. By doing this the ListTiles in the app will look OK also when FlexColorScheme theming is not used, even if issue #117965 might still be in effect. May not need this work around in V7.0 release if the issue does not land in new Flutter stable after 3.3. follow-up.Material in Flutter release.TODO BEFORE STABLE 7.0 RELEASE
The next stable version of Flutter after version 3.3 must be released before FlexColorScheme 7.0 can be released.
Postponed TODOs, that were planned for FCS stable 7.0, but moved forward to 7.1 or later.
Fix for issue #106 bottomSheetModalBackgroundColor not correctly set. Thanks mcssym for the fix PR #107.
Dec 26, 2022
FIX
Themes Playground (Example 5): Fixed scroll issue in page view mode on Web builds. Only examples related, no package impact.
Nov 22, 2022
FIX
Style breaking: Changed component themes thinBorderWidth to default to 1.0. It was 1.5 before. This is a style breaking change from previous thin outl…
Nov 20, 2022
FlexColorScheme version 6.1.0 contains many new features, more component sub-themes and configurable properties. It improves seed-generated color scheme capabilities by adding more pre-configured seed generation configurations and color contrast accessibility options.
A criticism of Material 3's color system and seed-generated color schemes, is that using colored contrasting colors may be less accessible. FlexColorScheme offers a way to enable in-app modification of its seed-generated color schemes, any seed generation configuration can optionally return results with plain white and black contrasting on colors. This can be applied separately for main on colors and on surfaces.
The Themes Playground application, has been updated to include most of the new features. It has been improved to make it easier to discover some of its previously existing features, like using custom colors in the Playground to define your own theme.
NEW
FlexAppBarStyle that is used by property appBarStyle got a new value scaffoldBackground that enables this. This is useful for matching the AppBar color exactly to the Scaffold background color, when Scaffold background uses different surface blends than the theme's ColorScheme surface or background colors.materialTapTargetSize and pageTransitionsTheme to FlexColorScheme and FlexThemeData. They are only convenience properties to avoid having to use a copyWith on FlexColorScheme produced ThemeData, to define them.swapLegacyOnMaterial3 in FlexColorScheme.light/dark and FlexThemeData.light/dark allows for better automatic adjustment of built-in scheme colors to the Material 3 color-system. It applies to color schemes that were originally designed for Material 2, when using the Material 3 mode with or without seed-generated ColorSchemes.
swapLegacyOnMaterial3 to true, will when useMaterial3 is true, swap the built-in scheme colors secondary and tertiary and also their container colors.secondary and tertiary colors in Material 3 color system.FlexSchemeColor has a new boolean meta-data property called swapOnMaterial3, that has been defined to be true, if the FlexSchemeColor it defines, benefits design compliance wise from swapping its secondary and tertiary colors when using Material 3.swapLegacyOnMaterial3 is false by default, but it is recommended to always set it to true. The flag has no impact when using Material 2.swapLegacyOnMaterial3 flag can also be toggled in the Themes Playground, it is on by default there.FlexSchemeColor, it is done before any other built-in scheme modifier properties, including swapColor and usedColors.FloatingActionButton can now be set to always be circular, also in Material 3 and without assigning a high-radius setting. If you always want a circular FAB, and stadium on extended FAB, then set fabAlwaysCircular in FlexSubThemesData to true, and FAB stays circular regardless of if you use M2 or M3, or how you modify the global default border radius. You could get this effect before too by setting a very high themed radius on the FAB, but this is more convenient.FlexSubThemesData properties:
Slider theme can now be adjusted via FlexSubThemesData properties sliderBaseSchemeColor, sliderValueTinted and sliderTrackHeight.chipSelectedSchemeColor was added as themed background color, it is used by Chips that are selectable. The chipDeleteIconSchemeColor can be used to theme the "Delete" icon color on Chips. While adding these features, some Flutter M3 Chip spec and theming issues were found, see issue #115364 for more information.switchThumbSchemeColor property, to control the thumb color separately. A switch custom color theme was prepared for M3 Switch, which is not yet available in Flutter 3.3.Tooltip theme now has FlexSubThemesData properties tooltipRadius, tooltipWaitDuration, tooltipShowDuration, tooltipSchemeColor and tooltipSchemeColor.bottomSheetBackgroundColor and bottomSheetModalBackgroundColor can be used to theme the background color of the BottomSheet.navigationBarElevation to adjust the themed elevation of NavigationBar.popupMenuElevation and popupMenuSchemeColor to further quick theme the PopupMenuButton.outlinedButtonBorderWidth, outlinedButtonPressedBorderWidth, toggleButtonsBorderWidth, inputDecoratorBorderWidth and inputDecoratorFocusedBorderWidth define the themed outline border thickness in different states of their respective components. These properties use previously existing properties thinBorderWidth and thickBorderWidth as their defaults. Resulting in that, the new properties are API backwards compatible, and they have shared global default settings. The new part is that you can now define themed outline border thickness separately for these components.elevatedButtonTextStyle, outlinedButtonTextStyle and textButtonTextStyle were added to be able to theme TextStyle on ElevatedButton, OutlinedButton, TextButton. These are convenience properties to allow different text styles on buttons without having to use copyWith on the overall ThemeData and its button component themes to modify the text styles, often sizes.
ThemeData and its button themes. The current version does not include adjusting them in the Themes Playground. Adding all possible usage of them is currently not in the scope of the Playground app. However, button font size changes may be added later as a usage example of these properties. These properties are using the tricky MaterialStateProperty, that have so far been avoided in this flattened simplified theming. It was used for the benefit of offering the text styles as ThemeData pass along properties. Modifying the ButtonStyle theme using copyWith, is a bit more involved than for other sub themes, with these properties you can customize the button text style using FlexSubThemesData properties instead. If you need to modify the FlexColorScheme created buttons themes even further for some not included properties, an example of how to do that can be found here.CHANGE
FlexTones, the FlexTones.oneHue and FlexTones.vividBackground.FlexSubThemesData all component controlling properties except booleans, are now nullable and null by default. FlexColorScheme made sub themes still default to same values as before when assigning a default FlexSubThemesData() to FlexColorScheme.subThemesData. The properties are nullable to enable using different defaults in FlexColorScheme made sub-themes for Material 2 and Material 3 modes.thinBorderWidth to default to 1.0. It was 1.5 before. This is a style breaking change from previous thin outline style in FlexColorScheme.
thinBorderWidth to 1.5, to get the same result as previous default theme.Chip style is slightly modified from previous versions. The new opinionated FCS default style is more distinct than before and more aligned with styling borrowed from the Material 3 mode Chip design. The deleteIconnColor now defaults to onSurface instead of primary and it can be defined to be any color scheme based color. The Chips revised style, look better than before. Using Material 3 and with it themed Chips is also fully supported, also customizing color on selected state of selectable Chips is available. Color-tinted chips are also available as before. Be aware though that Material 3 theming in the current 3.3 version of Flutter has some limitations. If you assign a custom color to selected chips, the disabled state of Chips can no longer conform, to M3 spec of disabled selected Chips.
FilterChip and InputeChip, there is simple not enough theme properties in ChipTheme to support this. Due to this limitation, we recommend only using Chip theme designs that work with dark text in light mode, and light text in dark mode.BottomSheet background color now defaults to theme's ColorScheme surface color, in both M2 and M3 mode. Previously it defaulted to the Material's default color theme.canvasColor, that typically equals ColorScheme background. The new default follows upcoming Material 3 default for BottomSheet. The style change is minor, in most designs the color values are the same. If needed you can put it back to theme background color with: final ThemeData themeLight = FlexThemeData.light(
subThemesData: const FlexSubThemesData(
bottomSheetBackgroundColor: SchemeColor.background,
bottomSheetModalBackgroundColor: SchemeColor.background,
),
);
FIX
BottomSheet gets a manually applied elevation tint to keep it distinguishable from the background. This temporary fix works despite Material tint elevation being broken in Flutter 3.3 and earlier, when useMaterial3 is true.PopupMenuButton.BottomSheet and PopupMenuButton, already exist in the Flutter master channel, they will probably land in next new stable release after Flutter 3.3.BottomSheet and PopupMenuButton when opting in on Material 3. Since shadow elevations are still not working for them in M3, it is not perfect, but much better.Material elevation issue #107190 in M3 mode. As a result we get no elevation tint or any shadow on such Material using widgets in M3 mode.Material, also if the components and their themes do not land. In combination with the here made M3 manual elevation tint fix, they would in such a case get the correct M3 default background elevation tint behaviour and shadow.THEMES PLAYGROUND
On Theme colors panel:
swapLegacyOnMaterial3 setting.Updated and shortened the Introduction. Probably nobody reads it, or the package docs with Playground guides, but at least it is there.
The Seeded ColorScheme panel:
FlexSchemeColor, that gets used as key colors for the Material 3 seeded ColorScheme generation, when it is turned on.
On Surface blends:
ToggleButtons control, as before, only shows popular options.Other new controllable properties and features:
scaffoldBackground color as its themed background color. This is useful for matching the AppBar color exactly to the Scaffold background color, when Scaffold background uses different surface blends than the theme's ColorScheme surface or background colors.BottomSheet.NavigationBar.PopupMenuButton.ToggleButtons border width.OutlineButtons border widths.InputDecorator border widths.Dialog elevation.Slider via base color, track height and base color tinted value indicator.Tooltip via scheme color, radius, opacity, show duration and wait duration.Switch thumb color via scheme color selection.User interface changes:
AppBarStyle, SchemeColor selection and SurfaceStyle. Their style follow ToggleButtons height and border radius.ToggleButtons controls in a ListTile can now for convenience be toggled in sequence by just tapping on the ListTile it is used in.Slider widget is now presented in the Widget Showcase panel. Basic theming options are now available. The Slider theme is already excellent out of the box. When you need more radical changes to it, those typically go beyond the scope of FCS and require extending the Slider widget.PageView is fine when swiping, where it remains, but it was a tad annoying when clicking on the panel page selector.Slider.adaptive to Slider.
SwitchListTileAdaptive to just SwitchListTile.
SwitchListTileAdaptive iOS switch on iOS on macOS. However, the app presents Material theming, and the new Material 3 Switch will land in Flutter stable soon. The new Material 3 Switch is even nicer than the Cupertino Switch, and we want to see it in the app when it lands. We will thus use the Material Switch in the Themes Playground app on all of its own controls on all platforms going forward.SwitchListTileAdaptive is kept in use on examples 2 to 4. As an example of how to make and use a theme following platform adaptive ListTileSwitch. In the SwitchListTileAdaptive doc comments it is mentioned that the plain SwitchListTile.adaptive is not theme color following on iOS/macOS platforms, nor can it be themed to be so. You have to make a custom wrapper like SwitchListTileAdaptive.FIX Themes Playground
A null check was fixed by sososdk in FlexColorScheme.light when using custom scheme PR #90. Issue did not exist in FlexColorScheme.dark.
Sep 21, 2022
FIX
A null check was fixed by sososdk in FlexColorScheme.light when using custom scheme PR #90. Issue did not exist in FlexColorScheme.dark.
Cam16 from Material Color Utilities was exported by accident by FlexColorScheme in version 6.0.0 via its FlexSeedScheme package export. This export was removed. Cam16 was not exported before moving features to FlexSeedScheme and should not have been now either. FlexSeedScheme does however export it as before, it is used by the FlexColorPicker.
In FlexSeedScheme, FlexTones contains a minor breaking change to make the API cleaner. The FlexTones.light and FlexTones.dark no longer produce the co…
Aug 31, 2022
Due to a number of known and below documented Flutter SDK issues when using useMaterial3 set to
true, we cannot yet recommend using the option in production. Use it only if you are willing to
accept the still incomplete Material 3 implementation in Flutter and the issues. If you
keep useMaterial3 set to false, and use FCS opinionated component themes, you can create a
theme that is visually fairly similar to M3, but still using M2 ThemeData mode to avoid many
issues.
BREAKING
This FlexColorScheme version no longer directly depends on package Material Color Utilities package, which is also used by Flutter SDK. Instead, it uses package
FlexSeedScheme that depends on it. As a part of this change classes FlexTones, FlexTonalPalette and FlexCorePalette where moved into the package FlexSeedScheme. FlexColorScheme still exports these classes. If you were using them directly before, you can still do so without adding the FlexSeedScheme package.
In FlexSeedScheme, FlexTones contains a minor breaking change to make the API cleaner. The FlexTones.light and FlexTones.dark no longer produce the config for the Material 3 tone and chroma setup. They no longer lock the chroma values to the default values for M3, but use null in their configs for their chroma values. Resulting in that chroma from key colors will be used, as long as they are over set minimum values. These named constructors then provide a cleaner starting API for defining additional configurations, by not forcing null to be passed to use chroma value in key colors. To get the Material 3 configuration, use the factory FlexTones.material instead of FlexTones.light and FlexTones.light. It as before produces the correct Material 3 configuration, by defining secondaryChroma: 16 and tertiaryChroma: 24 using FlexTones.light and FlexTones.dark to return the correct Material 3 matching FlexTones configuration as before. This change was introduced to prepare for extracting FlexTones and FlexSeedScheme to their own package that will provide a fromFlexSeeds extension on ColorScheme. It is unlikely to impact any normal usage of FlexColorScheme, but it is still a breaking change.
In FlexSeedScheme FlexCorePalette.fromSeeds properties secondaryChroma and tertiaryChroma now default to null instead of previous M3 palette default generating values 16 and 24 respectively. Set them to values 16 and 24 to create same tonal palettes as Material Color Utilities CorePalette and previous versions of FlexCorePalette.
To allow for greater flexibility and addition of tonal palette tones 5 (custom for FCS) and 98 (Google Material 3 Web theme builder app includes tone 98 to, but not Flutter SDK), FlexCorePalette no longer extends CorePalette, it is a modified re-implementation.
In FlexSeedScheme the FlexTonalPalette method asList and constructor fromList, now include the values of the error color in produced asList, and as required values in fromList.
NEW
In FlexSeedScheme, added customization possibility of error tonal palette to the default FlexTonalPalette constructor.
In FlexSeedScheme, added two new FlexTones:
FlexTones.ultraContrast with even more contrast that highContrast.FlexTones.jolly for a seeded ColorScheme with more poppy and jolly seed colors.In FlexSeedScheme, added SeedColorScheme.fromSeeds(...) that can be used to create a seeded ColorScheme using multiple seed colors and FlexTones configuration.
In FlexSeedScheme, added FlexTonalPalette a re-implementation of Material Color Utilities TonalPalette, with addition of tonal palette tones 5 and 98. The tone 98 also exists in the Web Material Theme Builder app, but not in Flutter or Material Color Utilities package. Tone 5 is custom addition for FlexTones and FlexColorScheme.
Added appBarCenterTitle property to FlexSubThemesData configuration. It works the same way as centerTitle in AppBar and its theme. The property is not available in the Themes Playground app, only via the API. We recommend keeping it null to use platform
adaptive default behavior, but offer it as convenience property for those that like to use same centering style regardless of used platform.
Added two new properties to FlexSubThemes.elevatedButtonTheme.
useMaterial3, defaults to false.onBaseSchemeColor, defaults to null SchemeColor?.When useMaterial3 is false, the elevatedButtonTheme.baseSchemeColor is used as background color as before, and the new property elevatedButtonTheme.onBaseSchemeColor is used as foreground color. However, when useMaterial3 is true, their foreground and background color roles are reversed, and baseSchemeColor becomes its foreground color and the onBaseSchemeColor its background color.
Added elevatedButtonSecondarySchemeColor property of type SchemeColor? to FlexSubThemesData. Use it to control secondary color of the ElevatedButton in its sub-themes. FCS applies this color to FlexSubThemes.elevatedButtonTheme.onBaseSchemeColor. If useMaterial3 is false, it is the foreground color. If useMaterial3 is true, it is the background color. Material 3 and 2 have a completely different default elevated button styles. The Material 2 elevated button is color wise, like the M3 filled button, but with elevation.
Added two new properties to FlexSubThemes.outlinedButtonTheme.
useMaterial3, defaults to false.outlineSchemeColor, defaults to null SchemeColor?.
When useMaterial3 is false, the outlineSchemeColor defaults to baseSchemeColor.
When useMaterial3 is true, the outlineSchemeColor defaults to SchemeColor.outline.REMOVED EARLIER DEPRECATED MEMBERS
As a chore and clean up all previously deprecated members have been removed from version 6.0.0. It no longer has any self deprecated members. This removes a lot legacy backwards compatibility with deprecated members from versions 2, 3 and 4, and even one from version 5.1.0. Removed all earlier self deprecated members as follows:
inputDecorationRadius, bottomNavigationBarSchemeColor, navigationBarIsStyled, navigationBarTextSchemeColor, navigationBarMutedUnselectedText, navigationBarIconSchemeColor, navigationBarHighlightSchemeColor.primaryVariant, secondaryVariant, useSubThemes. Removed static FlexColorScheme.m3TextTheme deprecated in 5.1.0 and static FlexColorScheme.themedSystemNavigationBar in version 2 its deprecated parameter nullContextBackground.primaryVariant, secondaryVariant, useSubThemes.primaryVariant, secondaryVariant.primaryVariant, secondaryVariant.kDarkenSecondaryVariant, kDarkenSecondaryVariantFromSecondary, kDarkenPrimaryVariant.baseSchemeColor.textSchemeColor, unselectedTextSchemeColor, mutedUnselectedText, iconSchemeColor, highlightSchemeColor.STYLE CHANGE - BREAKING
FlexSubThemesData.fabUseShape opinionated component theme style default was changed from true to false, this breaks previous default style. The opinionated style change was done to use a style that by default matches M3 style when ThemeData.useMaterial3 is true. The new default style is also a way to work around issue #107946, where it is shown that you cannot create a theme that replicates the default roundings in M3 of the FAB.
Style migration: If you had kept FlexSubThemesData.fabUseShape unspecified and relied on default value in a previous version, you must set it to true to get the same result as before. Breaking style changes like this, in the opinionated opt in component sub-themes are unfortunate. However, required as FlexColorScheme continues to evolve with Flutter SDK to support Material 3 theming, while offering its own opinionated tweaks on some M3 default styles as well.STYLE CHANGE - MINOR
The M3 color utilities package material_color_utilities from the Material team, that Flutter SDK depends on and FCS also uses, introduced a minor breaking change going from version 0.1.4 to 0.1.5. Some colors in the tonal palettes no longer give exactly the same color values as before. This changes the results for some colors when you create a ColorScheme.fromSeed or FCS does it internally with its extended version SeedColorScheme.fromSeeds. The new algorithm changes for example all the default M3 error colors slightly. The changes in the color values are minor, and not visually noticeable to the eye. Values are however slightly different, and this release uses the new value for FCS M3 error colors. Tests were also updated to use the new values. The change did break FCS color value tests, and should be per its own policy be considered a major breaking change. However, since the Material 3 design and material_color_utilities calls this change minor, then so does FCS.
The opt-in opinionated tinted text themes were made less aggressive on the tint, and received a bit of opacity for styles that in 2014/2018/2021 styles have opacity. The custom styles uses significantly less opacity since they already also get alpha blended tint color applied. Combining it with same level of opacity would make them too low contrast.
Style fix, the main text theme uses surfaceTint color instead of primary when tinted text theme is enabled. By default surfaceTint equals primary, but if theme surfaceTint is set to use a custom color, the for surface tinted textTheme is now also based on it, to fit the custom tinted surfaces. The primary text theme, that fits on primary color, still uses primary color as its tint color.
The FlexAppBarStyle property was made nullable. It now defaults to null in all constructors. When it is null and useMaterial3 is false, the app bar will use style FlexAppBarStyle.primary in light mode as default, like before and FlexAppBarStyle.material in dark mode. However, if useMaterial3 is true, then it will use FlexAppBarStyle.surface in both light and dark mode, to match the un-themed defaults of Material 3 design AppBar.
Updated ElevatedButton to support useMaterial3 defaults concerning its switched foreground and background color roles. It now also uses stadium border instead of 20dp, M3 size, padding and elevation defaults, when useMaterial3 is opted in on.
Updated OutlinedButton to support useMaterial3 defaults concerning its outline color default. It now also uses stadium border instead of 20dp, M3 size and padding, when useMaterial3 is opted in on.
Updated TextButton to support useMaterial3 defaults concerning its use of stadium border instead of 20dp radius, as well M3 size and padding, when useMaterial3 is opted in on.
Changed opinionated dialog sub-theme defaults to match M3 defaults. Elevation set to 6, was 10 and actionsPadding defaults to EdgeInsets.only(left: 24.0, right: 24.0, bottom: 24.0), it did not have a custom default before. These are new defaults for the opinionated dialog sub-theme for both M2 and M3.
Updated Chip sub-theme when opting in on useMaterial3. When true it now uses upcoming M3 styled Chips instead of its own opinionated custom style, also when the opinionated component sub-themes are enabled. To get the same opinionated coloring as before, but on the M3 styled chips when using M3, set component sub-themes data subThemesData: const FlexSubThemesData(chipSchemeColor: SchemeColor.primary). This feature will only work with intended design in stable channel after feature and PR "Migrate Chips to Material 3" lands in stable channel. Currently, it is only available in Flutter master 3.1.0-x.
Updated InputDecoration default sub-theme when opting in on useMaterial3. When true it now results in a more upcoming M3 styled TextField style by default, instead of its own more opinionated custom style, also when the opinionated component sub-themes are enabled. It still uses a touch a lot of its own style in M3 mode, because TextField's real M3 design is not yet available in Flutter 3.3. TextField FCS opinionated style, combined with M3 real defaults, will need more work on M3 styles after "Migrate TextField to Material 3" lands in stable channel. The M3 alignment of FCS InputDecoration planned adjustments are:
CHANGE
FlexSubThemes.buttonTheme, as long as Flutter SDK has not deprecated it, neither will FCS.FlexColor colors. They are not used actively by any built-in schemes. However, in line with past statement. The old M2 color names and values will not be removed. Feel free to use to them, if so desired.toggleableActiveColor when PR Deprecate toggleableActiveColor #97972 lands, while retaining the previous FCS defaults for Switch, CheckBox and Radio widgets, when not opting in on component sub-themes. The created SwitchThemeData, CheckboxThemeData and CheckboxThemeData can no longer be null, when not opting in on sub-themes like before. To support the previous nicely theme colored
toggles in light and dark themes, that were set by defining the right scheme color for toggleableActiveColor in M2 and M3 theme modes, sub-themes for them that replicates the color styles must now be created also when not opting in on sub-themes. This update includes the necessary change to do so. This will be reflected in updates to the core defaults documentation. For a migration guide concerning toggleableActiveColor see Flutter breaking-changes.toggleableActiveColor FCS still defines its appropriate color value for ThemeData.EXAMPLES
Themes Playground: New feature, the used code highlight colors were added as colors in a CodeTheme class ThemeExtension to ThemeData. To demonstrate how one can use theme extensions directly with FlexColorScheme as well, in this case to add custom semantic colors for the code view's code keyword highlighter. Additionally, a fancy Material 3 feature was added, color harmonization of custom colors. The process is described in M3 guide under custom colors. The M3 library MaterialColorUtilities has the Blend function needed to perform the color harmonization, as described here and the Dart color Blend function is here.
Themes Playground: Updated the default AppBar style, it uses a dropdown menu that can also select 'null' choice and use default M2 and M3 theming as defaults via it. The AppBar panel now also displays an AppBar Widget of its own, so one does not have to look at the actual AppBar to see the style. It also has widgets below it used to demonstrate the opacity setting.
Themes Playground: Code gen and control enable/disable for onColor blends updated to lock controls with no impact when using seeded color scheme. Code is also not generated for onColor blend settings that has no impact when using seeded color schemes.
Themes Playground: Features and code gen for additional Elevated.button individual foreground and background colors.
Themes Playground: Features and code gen for additional Outlined.button separate outline color.
Themes Playground: To the component panel added support to customize outline border thickness for OutlinedButton, ToggleButtons and TextField's InputDecorator.
Themes Playground: Added features and UI for new Flutter SDK ColorScheme colors outlineVariant and scrim.
DOCS
Removed duplicated section of 5.1.0 changelog entry with date July 5, 2022.
Harmonized the changelog style and its past history. The new style and how it looks will be tested with a dev release to ensure it works well on pub.
KNOWN FLUTTER SDK ISSUES IMPACTING THEMING
The issues below in the Flutter SDK itself, are known to impact FlexColorScheme and Flutter theming in general. The issues are typically caused by incomplete Material 3 implementation in Flutter.
The M3 Chip themes available in Flutter master 3.1.0-0.0.pre.2216 at the time of writing, do as noted here PR 107166 comment, not yet M3 theme plain vanilla Chip when using Material 3. This might be fixed in an additional PR later in the SDK. This proposal tracks the potential implementation of this #109470.
#107946 Cannot theme Shape and IconSize differently for different sized FloatingActionButtons. One of the drivers behind the breaking FAB style defaults for the opinionated FAB theme in FCS, was this issue.
#108539 Cannot theme shape independently for SnackBar with different behavior. This is the reason why FCS does not yet offer a custom shape in its opinionated SnackBar theme. To replicate the un-themed behavior with slightly different border radius values, one must make custom wrapper widgets for SnackBar.
The Flutter SDK M3 useMaterial3 flag set to true continues to have a number of challenges in addition to the above ones. We as before still have the issues below in Flutter stable 3.0.5 and also at least in Flutter master 3.1.0-0.0.pre.2216 and earlier:
#107190 Elevation issue with Material widget, when opting in on useMaterial3 causes widespread elevation issues. Concerning the reported elevation issue for dialogs included in the linked report, it was observed as fixed for them in master, but later the PR fixing it was reverted. Then it was relanded and then the reland reverted, see Issue #107423, PR #108718, PR #109170 and PR 109172. Even after it lands it won't solve all the mentioned incompleteness caused M3 elevation issues, only Dialogs. Popup in particular will remain troublesome.
#103864 Dynamically changing Typography in ThemeData generates an error
#107305 Regression: AppBarTheme properties iconTheme and actionsIconTheme ignored on master channel when useMaterial3 is true. This was not in stable Flutter channel stable 3.0.5. This issue was fixed via PR #108332 and could no longer be observed in master, 3.1.0-0.0.pre.2108 or later versions. The fix did however not make it into Flutter stable 3.3.0 and now exists there. The issue must be re-opened or a new one submitted.
This issue discussed in SliverAppBar.medium and large PR #103962, now exists in stable channel. There is no open issue for it yet.
Aug 31, 2022
Due to a number of known and below documented Flutter SDK issues when using useMaterial3 set to
true, we cannot yet recommend using the option in production. Use it only if you are willing to
accept the still incomplete Material-3 implementation in Flutter and the issues. If you
keep useMaterial3 set to false, and use FCS opinionated component themes, you can create a
theme that is visually fairly similar to Material-3, but still using Material-2 ThemeData mode to avoid many
issues.
BREAKING
This FlexColorScheme version no longer directly depends on the
Material Color Utilities package, which
is also used by Flutter SDK. Instead, it uses package
FlexSeedScheme that depends on it.
As a part of this change classes FlexTones, FlexTonalPalette and FlexCorePalette where
moved into the package FlexSeedScheme. FlexColorScheme still exports these classes. If you
were using them directly before, you can still do so without adding the FlexSeedScheme package.
In FlexSeedScheme, FlexTones contains a minor breaking change to make the API cleaner.
The FlexTones.light and FlexTones.dark no longer produce the config for the Material-3 tone
and chroma setup. They no longer lock the chroma values to the default values for Material-3, but use
null in their configs for their chroma values. Resulting in that chroma from key colors will be
used, as long as they are over set minimum values.
These named constructors then provide a cleaner starting API for
defining additional configurations, by not forcing null to be passed to use chroma value in
key colors. To get the Material-3 configuration, use the factory FlexTones.material instead of
FlexTones.light and FlexTones.light. It as before produces the correct Material-3
configuration, by defining secondaryChroma: 16 and tertiaryChroma: 24 using FlexTones.light
and FlexTones.dark to return the correct Material-3 matching FlexTones configuration as
before. This change was introduced to prepare for extracting FlexTones and FlexSeedScheme to
their own package that will provide a fromFlexSeeds extension on ColorScheme. It is unlikely
to impact any normal usage of FlexColorScheme, but it is still a breaking change.
In FlexSeedScheme FlexCorePalette.fromSeeds properties secondaryChroma and
tertiaryChroma now default to null instead of previous Material-3 palette default generating values
16 and 24 respectively. Set them to 16 and 24 to create same tonal palettes as
Material Color Utilities CorePalette and previous versions of FlexCorePalette.
To allow for greater flexibility, and addition of tonal palette tones 5 (custom for FCS) and 98
(Google Material-3, Web theme builder app includes tone 98 to, but not Flutter SDK),
FlexCorePalette no longer extends CorePalette, it is a modified re-implementation.
In FlexSeedScheme the FlexTonalPalette method asList and constructor fromList, now
include the values of the error color in produced asList, and as required values in fromList.
NEW
In FlexSeedScheme, added customization possibility of error tonal palette to the default
FlexTonalPalette constructor.
In FlexSeedScheme, added two new FlexTones:
FlexTones.ultraContrast with even more contrast that highContrast.FlexTones.jolly for a seeded ColorScheme with more poppy and jolly seed colors.In FlexSeedScheme, added SeedColorScheme.fromSeeds(...) that can be used to create a
seeded ColorScheme using multiple seed colors and FlexTones configuration.
In FlexSeedScheme, added FlexTonalPalette a re-implementation of Material Color Utilities
TonalPalette, with addition of tonal palette tones 5 and 98. Tone 98 also exists in the
Web Material Theme Builder app, but not in
Flutter or Material Color Utilities package.
Tone 5 is custom addition for FlexTones and FlexColorScheme.
Added appBarCenterTitle property to FlexSubThemesData configuration. It works the
same way as centerTitle in AppBar and its theme. The property is not available in the
Themes Playground app, only via the API. We recommend keeping it null to use platform
adaptive default behavior, but offer it as a convenience property for those that like to use the
same centering style, regardless of the used platform.
Added two new properties to FlexSubThemes.elevatedButtonTheme.
useMaterial3, defaults to false.onBaseSchemeColor, defaults to null SchemeColor?.When useMaterial3 is false, the elevatedButtonTheme.baseSchemeColor is used as background
color as before, and the new property elevatedButtonTheme.onBaseSchemeColor is used as
foreground color. However, when useMaterial3 is true, their foreground and background
color roles are reversed, and baseSchemeColor becomes its foreground color and the
onBaseSchemeColor its background color.
Added elevatedButtonSecondarySchemeColor property of type SchemeColor? to
FlexSubThemesData. Use it to control secondary color of the ElevatedButton in its
component themes. FCS applies this color to FlexSubThemes.elevatedButtonTheme.onBaseSchemeColor.
If useMaterial3 is false, it is the foreground color. If useMaterial3 is true, it is the
background color. Material-3, and 2, have completely different elevated button styles.
The Material-2 elevated button is color wise, like the Material-3-filled button, but with elevation.
Added two new properties to FlexSubThemes.outlinedButtonTheme.
useMaterial3, defaults to false.outlineSchemeColor, defaults to null SchemeColor?.
When useMaterial3 is false, the outlineSchemeColor defaults to baseSchemeColor.
When useMaterial3 is true, the outlineSchemeColor defaults to SchemeColor.outline.REMOVED EARLIER DEPRECATED MEMBERS
As a chore and cleanup, all previously deprecated members have been removed from version 6.0.0. It no longer has any self-deprecated members. This removes legacy backwards compatibility with deprecated members from versions 2, 3 and 4, and even one from version 5.1.0. Removed all earlier self-deprecated members as follows:
inputDecorationRadius, bottomNavigationBarSchemeColor,
navigationBarIsStyled, navigationBarTextSchemeColor, navigationBarMutedUnselectedText,
navigationBarIconSchemeColor, navigationBarHighlightSchemeColor.primaryVariant, secondaryVariant, useSubThemes. Removed static FlexColorScheme.m3TextTheme
deprecated in 5.1.0 and static FlexColorScheme.themedSystemNavigationBar in version
2 its deprecated parameter nullContextBackground.primaryVariant, secondaryVariant, useSubThemes.primaryVariant, secondaryVariant.primaryVariant, secondaryVariant.kDarkenSecondaryVariant, kDarkenSecondaryVariantFromSecondary, kDarkenPrimaryVariant.baseSchemeColor.textSchemeColor, unselectedTextSchemeColor, mutedUnselectedText, iconSchemeColor,
highlightSchemeColor.STYLE CHANGE — BREAKING
FlexSubThemesData.fabUseShape opinionated component theme style default was changed from true
to false, this breaks previous default style. The opinionated style change was done
to use a style that by default matches Material-3 style when ThemeData.useMaterial3 is true.
The new default style is also a way to work around issue
#107946, where it is shown that you cannot
create a theme that replicates the default border radius in Material-3 of the FAB.
Style migration: If you had kept FlexSubThemesData.fabUseShape unspecified and relied on
default value in a previous version, you must set it to true to get the same result as before.
Breaking style changes like this, in the opinionated opt-in component themes are unfortunate.
They are, however, required as FlexColorScheme continues to evolve with Flutter SDK to support Material-3
theming, while offering its own opinionated tweaks on some Material-3 default styles as well.STYLE CHANGE — MINOR
The Material-3 color utilities package material_color_utilities from the Material team, that Flutter SDK
depends on and FCS also uses, introduced a minor breaking change going from version 0.1.4 to
0.1.5. Some colors in the tonal palettes no longer give exactly the same color values as before.
This changes the results for some colors when you create a ColorScheme.fromSeed or FCS does
it internally with its extended version SeedColorScheme.fromSeeds. The new algorithm changes
all the default Material-3 error colors slightly. The changes in the color values are minor,
and not visually noticeable to the eye. Values are still slightly different, and this release
uses the new value for FCS Material-3 error colors. Tests were also updated to use the new values.
The change did break FCS color value tests, and should per its own policy be considered a
major breaking change. However, since the Material-3 design and material_color_utilities
call this change minor, then so does FCS.
The opt-in opinionated tinted text themes were made less aggressive on the tint and received a bit of opacity for styles that in 2014/2018/2021 styles have opacity. The custom styles use significantly less opacity since they already also get alpha-blended tint color applied. Combining it with the same level of opacity would make them too low contrast.
Style fix, the main text theme uses surfaceTint color instead of primary when tinted text
theme is enabled. By default surfaceTint equals primary, but if theme surfaceTint is set
to use a custom color, the for surface tinted textTheme is now also based on it, to fit the
custom-tinted surfaces. The primary text theme, that fits on primary color, still
uses primary color as its tint color.
The FlexAppBarStyle property was made nullable. It now defaults to null in all constructors.
When it is null and useMaterial3 is false, the app bar will use style FlexAppBarStyle.primary
in light mode as default, like before and FlexAppBarStyle.material in dark mode. However, if
useMaterial3 is true, then it will use FlexAppBarStyle.surface in both light and dark mode,
to match the un-themed defaults of Material-3 design AppBar.
Updated ElevatedButton to support useMaterial3 defaults concerning its switched foreground and
background color roles. It now also uses a stadium border instead of 20 dp, Material-3 size, padding and
elevation defaults, when useMaterial3 is opted in on.
Updated OutlinedButton to support useMaterial3 defaults concerning its outline color default.
It now also uses a stadium border instead of 20 dp, Material-3 size and padding, when useMaterial3 is
opted in on.
Updated TextButton to support useMaterial3 defaults concerning its use of a stadium border
instead of 20 dp radius, as well Material-3 size and padding, when useMaterial3 is opted in on.
Changed opinionated dialog component theme defaults to match Material-3 defaults. Elevation set to 6, was
10 and actionsPadding defaults to EdgeInsets.only(left: 24.0, right: 24.0, bottom: 24.0), it
did not have a custom default before. These are new defaults for the opinionated dialog component theme
for both Material-2 and Material-3.
Updated Chip component theme when opting in on useMaterial3. When useMaterial3 is true, it
now uses upcoming
Material-3-styled Chips instead of its own opinionated custom style, also when the opinionated
component themes are enabled. To get the same opinionated coloring as before, but on the Material-3 styled
chips when using Material-3, set component themes data
subThemesData: const FlexSubThemesData(chipSchemeColor: SchemeColor.primary).
This feature will only work with intended design in the stable channel, after the feature and PR
"Migrate Chips to Material-3", lands in the stable
channel. Currently, it is only available in Flutter master 3.1.0-x.
Updated InputDecoration default component theme when opting in on useMaterial3. When true it
now results in a more upcoming Material-3 styled TextField style by default, instead of its own more
opinionated custom style, also when the opinionated component themes are enabled.
It still uses a touch a lot of its own style in Material-3 mode, because TextField's real Material-3 design is
not yet available in Flutter 3.3. TextField FCS opinionated style, combined with Material-3 real defaults,
will need more work on Material-3 styles after
"Migrate TextField to Material-3" lands in
the stable channel.
The Material-3 alignment of FCS InputDecoration planned adjustments are:
CHANGE
FlexSubThemes.buttonTheme, as long as Flutter
SDK has not deprecated it, neither will FCS.FlexColor colors.
They are not used actively by any built-in schemes. However, in line with past practice,
the old Material-2 color names and values will not be removed. Feel free to use them, if so desired.toggleableActiveColor when PR
Deprecate toggleableActiveColor #97972 lands,
while retaining the previous FCS defaults for Switch, CheckBox and Radio widgets, when
not opting in on component themes. The created SwitchThemeData, CheckboxThemeData and
CheckboxThemeData can no longer be null, when not opting in on component themes like before.
To support the previous theme colored
toggles in light and dark themes, that were set by defining the right scheme color for
toggleableActiveColor in Material-2 and Material-3 theme modes, component themes for them that replicates the color
styles must now be created also when not opting in on component themes. This update includes the
necessary change to do so. This will be reflected in updates to the core default documentation.
For a migration guide concerning toggleableActiveColor see
Flutter breaking-changes.toggleableActiveColor FCS still
defines its appropriate color value for ThemeData.EXAMPLES
Themes Playground: New feature, the used code highlight colors were added as colors in
a CodeTheme class ThemeExtension to ThemeData. To demonstrate how one can use theme
extensions directly with FlexColorScheme as well, in this case to add custom semantic colors
for the code view's code keyword highlighter. Additionally, a fancy Material-3 feature was added,
color harmonization of custom colors. The process is described in the Material-3 guide under
custom colors.
The Material-3 library MaterialColorUtilities has
the Blend function needed to perform the color harmonization, as described
here and the Dart color
Blend function is here.
Themes Playground: Updated the default AppBar style, it uses a dropdown menu that can also select 'null' choice and use default Material-2 and Material-3 theming as defaults via it. The AppBar panel now also displays an AppBar Widget of its own, so one does not have to look at the actual AppBar to see the style. It also has widgets below it used to demonstrate the opacity setting.
Themes Playground: Code gen and control enable/disable for onColor blends updated to lock controls with no impact when using seeded color schemes. Code is also not generated for onColor blend settings that have no impact when using seeded color schemes.
Themes Playground: Features and code gen for additional Elevated.button individual foreground
and background colors.
Themes Playground: Features and code gen for additional Outlined.button separate outline
color.
Themes Playground: To the component panel added support to customize outline border
thickness for OutlinedButton, ToggleButtons and TextField's InputDecorator.
Themes Playground: Added features and UI for new Flutter SDK ColorScheme colors
outlineVariant and scrim.
DOCS
Removed the duplicated section of 5.1.0 changelog entry with date July 5, 2022.
Harmonized the changelog style and its history. The new style and how it looks will be tested with a dev release to ensure it works well on pub.
KNOWN FLUTTER SDK ISSUES IMPACTING THEMING
The issues below in the Flutter SDK itself, are known to impact FlexColorScheme and Flutter theming in general. The issues are typically caused by incomplete Material-3 implementation in Flutter.
The Material-3 Chip themes available in Flutter master 3.1.0-0.0.pre.2216 at the time of writing,
do as noted here
PR #107166 comment,
not yet Material-3 theme plain vanilla Chip when using Material-3. This might be fixed in an
additional PR later in the SDK. This proposal tracks the potential implementation of this
#109470.
#107946 Cannot theme Shape and IconSize differently for different sized FloatingActionButtons. One of the drivers behind the breaking FAB style defaults for the opinionated FAB theme in FCS was this issue.
#108539 Cannot theme shape independently
for SnackBar with different behavior. This is the reason why FCS does not yet offer a
custom shape in its opinionated SnackBar theme. To replicate the un-themed behavior with
slightly different border radius values, one must make custom wrapper widgets for SnackBar.
The Flutter SDK Material-3 useMaterial3 flag set to true continues to have a number of challenges in
addition to the above ones. We as before still have the issues below in Flutter stable 3.0.5 and
also at least in Flutter master 3.1.0-0.0.pre.2216 and earlier:
#107190 Elevation issue with Material widget, when opting in on useMaterial3 causes widespread elevation issues. Concerning the reported elevation issue for dialogs included in the linked report, it was observed as fixed for them in master, but later the PR fixing it was reverted. After that, it was relanded, then the reland reverted, see Issue #107423, PR #108718, PR #109170 and PR 109172. Even after it eventually lands in stable, it will not solve all the mentioned incompleteness caused Material-3 elevation issues. It will only do so for Dialogs. Popup in particular will remain troublesome.
#103864 Dynamically changing Typography
in ThemeData generates an error
#107305 Regression: AppBarTheme properties iconTheme and actionsIconTheme are ignored in the master channel when useMaterial3 is true. This was not in stable Flutter channel stable 3.0.5. This issue was fixed via PR #108332 and could no longer be observed in master, 3.1.0-0.0.pre.2108 or later versions. The fix did however not make it into Flutter stable 3.3.0 and now exists there. The issue must be re-opened or a new one submitted.
This issue discussed in SliverAppBar.medium and large PR #103962, now exists in the stable channel. There is no open issue for it yet.
In FlexSeedScheme, FlexTones contains a minor breaking change to make the API cleaner. The FlexTones.light and FlexTones.dark no longer produce the co…
Aug 28, 2022
This dev release is for Flutter beta 3.3.0-0.5.pre, it will be released when next Flutter stable version after 3.0 comes out, presumably version 3.3.
If you experiment with this dev release and want to use the Theme Playground, then please use the version 6 beta build, here. The doc site does not yet contain any information about version 6, it will be added after its stable release.
Due to a number of known and below documented Flutter SDK issues when using useMaterial3 set to true, we cannot yet recommend using the option in production. Use it only if you are willing to accept the still incomplete Material 3 implementation in Flutter and the issues. If you keep useMaterial3 set to false, and use FCS opinionated component themes, you can create a theme that is visually fairly similar to M3, but still using M2 ThemeData mode to avoid many issues.
BREAKING
This FlexColorScheme version no longer directly depends on package Material Color Utilities package, which is also used by Flutter SDK. Instead, it uses package
FlexSeedScheme that depends on it. As a part of this change classes FlexTones, FlexTonalPalette and FlexCorePalette where moved into the package FlexSeedScheme. FlexColorScheme still exports these classes. If you were using them directly before, you can still do so without adding the FlexSeedScheme package.
In FlexSeedScheme, FlexTones contains a minor breaking change to make the API cleaner. The FlexTones.light and FlexTones.dark no longer produce the config for the Material 3 tone and chroma setup. They no longer lock the chroma values to the default values for M3, but use null in their configs for their chroma values. Resulting in that chroma from key colors will be used, as long as they are over set minimum values. These named constructors then provide a cleaner starting API for defining additional configurations, by not forcing null to be passed to use chroma value in key colors. To get the Material 3 configuration, use the factory FlexTones.material instead of FlexTones.light and FlexTones.light. It as before produces the correct Material 3 configuration, by defining secondaryChroma: 16 and tertiaryChroma: 24 using FlexTones.light and FlexTones.dark to return the correct Material 3 matching FlexTones configuration as before. This change was introduced to prepare for extracting FlexTones and FlexSeedScheme to their own package that will provide a fromFlexSeeds extension on ColorScheme. It is unlikely to impact any normal usage of FlexColorScheme, but it is still a breaking change.
In FlexSeedScheme FlexCorePalette.fromSeeds properties secondaryChroma and tertiaryChroma now default to null instead of previous M3 palette default generating values 16 and 24 respectively. Set them to values 16 and 24 to create same tonal palettes as Material Color Utilities CorePalette and previous versions of FlexCorePalette.
To allow for greater flexibility and addition of tonal palette tones 5 (custom for FCS) and 98 (Google Material 3 Web theme builder app includes tone 98 to, but not Flutter SDK), FlexCorePalette no longer extends CorePalette, it is a modified re-implementation.
In FlexSeedScheme the FlexTonalPalette method asList and constructor fromList, now include the values of the error color in produced asList, and as required values in fromList.
NEW
In FlexSeedScheme, added customization possibility of error tonal palette to the default FlexTonalPalette constructor.
In FlexSeedScheme, added two new FlexTones:
FlexTones.ultraContrast with even more contrast that highContrast.FlexTones.jolly for a seeded ColorScheme with more poppy and jolly seed colors.In FlexSeedScheme, added SeedColorScheme.fromSeeds(...) that can be used to create a seeded ColorScheme using multiple seed colors and FlexTones configuration.
In FlexSeedScheme, added FlexTonalPalette a re-implementation of Material Color Utilities TonalPalette, with addition of tonal palette tones 5 and 98. The tone 98 also exists in the Web Material Theme Builder app, but not in Flutter or Material Color Utilities package. Tone 5 is custom addition for FlexTones and FlexColorScheme.
Added appBarCenterTitle property to FlexSubThemesData configuration. It works the same way as centerTitle in AppBar and its theme. The property is not available in the Themes Playground app, only via the API. We recommend keeping it null to use platform
adaptive default behavior, but offer it as convenience property for those that like to use same centering style regardless of used platform.
Added two new properties to FlexSubThemes.elevatedButtonTheme.
useMaterial3, defaults to false.onBaseSchemeColor, defaults to null SchemeColor?.When useMaterial3 is false, the elevatedButtonTheme.baseSchemeColor is used as background color as before, and the new property elevatedButtonTheme.onBaseSchemeColor is used as foreground color. However, when useMaterial3 is true, their foreground and background color roles are reversed, and baseSchemeColor becomes its foreground color and the onBaseSchemeColor its background color.
Added elevatedButtonSecondarySchemeColor property of type SchemeColor? to FlexSubThemesData. Use it to control secondary color of the ElevatedButton in its sub-themes. FCS applies this color to FlexSubThemes.elevatedButtonTheme.onBaseSchemeColor. If useMaterial3 is false, it is the foreground color. If useMaterial3 is true, it is the background color. Material 3 and 2 have a completely different default elevated button styles. The Material 2 elevated button is color wise, like the M3 filled button, but with elevation.
Added two new properties to FlexSubThemes.outlinedButtonTheme.
useMaterial3, defaults to false.outlineSchemeColor, defaults to null SchemeColor?.
When useMaterial3 is false, the outlineSchemeColor defaults to baseSchemeColor.
When useMaterial3 is true, the outlineSchemeColor defaults to SchemeColor.outline.REMOVED EARLIER DEPRECATED MEMBERS
As a chore and clean up all previously deprecated members have been removed from version 6.0.0. It no longer has any self deprecated members. This removes a lot legacy backwards compatibility with deprecated members from versions 2, 3 and 4, and even one from version 5.1.0. Removed all earlier self deprecated members as follows:
inputDecorationRadius, bottomNavigationBarSchemeColor, navigationBarIsStyled, navigationBarTextSchemeColor, navigationBarMutedUnselectedText, navigationBarIconSchemeColor, navigationBarHighlightSchemeColor.primaryVariant, secondaryVariant, useSubThemes. Removed static FlexColorScheme.m3TextTheme deprecated in 5.1.0 and static FlexColorScheme.themedSystemNavigationBar in version 2 its deprecated parameter nullContextBackground.primaryVariant, secondaryVariant, useSubThemes.primaryVariant, secondaryVariant.primaryVariant, secondaryVariant.kDarkenSecondaryVariant, kDarkenSecondaryVariantFromSecondary, kDarkenPrimaryVariant.baseSchemeColor.textSchemeColor, unselectedTextSchemeColor, mutedUnselectedText, iconSchemeColor, highlightSchemeColor.STYLE CHANGE - BREAKING
FlexSubThemesData.fabUseShape opinionated component theme style default was changed from true to false, this breaks previous default style. The opinionated style change was done to use a style that by default matches M3 style when ThemeData.useMaterial3 is true. The new default style is also a way to work around issue #107946, where it is shown that you cannot create a theme that replicates the default roundings in M3 of the FAB.
Style migration: If you had kept FlexSubThemesData.fabUseShape unspecified and relied on default value in a previous version, you must set it to true to get the same result as before. Breaking style changes like this, in the opinionated opt in component sub-themes are unfortunate. However, required as FlexColorScheme continues to evolve with Flutter SDK to support Material 3 theming, while offering its own opinionated tweaks on some M3 default styles as well.STYLE CHANGE - MINOR
The M3 color utilities package material_color_utilities from the Material team, that Flutter SDK depends on and FCS also uses, introduced a minor breaking change going from version 0.1.4 to 0.1.5. Some colors in the tonal palettes no longer give exactly the same color values as before. This changes the results for some colors when you create a ColorScheme.fromSeed or FCS does it internally with its extended version SeedColorScheme.fromSeeds. The new algorithm changes for example all the default M3 error colors slightly. The changes in the color values are minor, and not visually noticeable to the eye. Values are however slightly different, and this release uses the new value for FCS M3 error colors. Tests were also updated to use the new values. The change did break FCS color value tests, and should be per its own policy be considered a major breaking change. However, since the Material 3 design and material_color_utilities calls this change minor, then so does FCS.
The opt-in opinionated tinted text themes were made less aggressive on the tint, and received a bit of opacity for styles that in 2014/2018/2021 styles have opacity. The custom styles uses significantly less opacity since they already also get alpha blended tint color applied. Combining it with same level of opacity would make them too low contrast.
Style fix, the main text theme uses surfaceTint color instead of primary when tinted text theme is enabled. By default surfaceTint equals primary, but if theme surfaceTint is set to use a custom color, the for surface tinted textTheme is now also based on it, to fit the custom tinted surfaces. The primary text theme, that fits on primary color, still uses primary color as its tint color.
The FlexAppBarStyle property was made nullable. It now defaults to null in all constructors. When it is null and useMaterial3 is false, the app bar will use style FlexAppBarStyle.primary in light mode as default, like before and FlexAppBarStyle.material in dark mode. However, if useMaterial3 is true, then it will use FlexAppBarStyle.surface in both light and dark mode, to match the un-themed defaults of Material 3 design AppBar.
Updated ElevatedButton to support useMaterial3 defaults concerning its switched foreground and background color roles. It now also uses stadium border instead of 20dp, M3 size, padding and elevation defaults, when useMaterial3 is opted in on.
Updated OutlinedButton to support useMaterial3 defaults concerning its outline color default. It now also uses stadium border instead of 20dp, M3 size and padding, when useMaterial3 is opted in on.
Updated TextButton to support useMaterial3 defaults concerning its use of stadium border instead of 20dp radius, as well M3 size and padding, when useMaterial3 is opted in on.
Changed opinionated dialog sub-theme defaults to match M3 defaults. Elevation set to 6, was 10 and actionsPadding defaults to EdgeInsets.only(left: 24.0, right: 24.0, bottom: 24.0), it did not have a custom default before. These are new defaults for the opinionated dialog sub-theme for both M2 and M3.
Updated Chip sub-theme when opting in on useMaterial3. When true it now uses upcoming M3 styled Chips instead of its own opinionated custom style, also when the opinionated component sub-themes are enabled. To get the same opinionated coloring as before, but on the M3 styled chips when using M3, set component sub-themes data subThemesData: const FlexSubThemesData(chipSchemeColor: SchemeColor.primary). This feature will only work with intended design in stable channel after feature and PR "Migrate Chips to Material 3" lands in stable channel. Currently, it is only available in Flutter master 3.1.0-x.
Updated InputDecoration default sub-theme when opting in on useMaterial3. When true it now results in a more upcoming M3 styled TextField style by default, instead of its own more opinionated custom style, also when the opinionated component sub-themes are enabled. It still uses a touch a lot of its own style in M3 mode, because TextField's real M3 design is not yet available in Flutter 3.3. TextField FCS opinionated style, combined with M3 real defaults, will need more work on M3 styles after "Migrate TextField to Material 3" lands in stable channel. The M3 alignment of FCS InputDecoration planned adjustments are:
CHANGE
FlexSubThemes.buttonTheme, as long as Flutter SDK has not deprecated it, neither will FCS.FlexColor colors. They are not used actively by any built-in schemes. However, in line with past statement. The old M2 color names and values will not be removed. Feel free to use to them, if so desired.toggleableActiveColor when PR Deprecate toggleableActiveColor #97972 lands, while retaining the previous FCS defaults for Switch, CheckBox and Radio widgets, when not opting in on component sub-themes. The created SwitchThemeData, CheckboxThemeData and CheckboxThemeData can no longer be null, when not opting in on sub-themes like before. To support the previous nicely theme colored
toggles in light and dark themes, that were set by defining the right scheme color for toggleableActiveColor in M2 and M3 theme modes, sub-themes for them that replicates the color styles must now be created also when not opting in on sub-themes. This update includes the necessary change to do so. This will be reflected in updates to the core defaults documentation. For a migration guide concerning toggleableActiveColor see Flutter breaking-changes.toggleableActiveColor FCS still defines its appropriate color value for ThemeData.EXAMPLES
Themes Playground: New feature, the used code highlight colors were added as colors in a CodeTheme class ThemeExtension to ThemeData. To demonstrate how one can use theme extensions directly with FlexColorScheme as well, in this case to add custom semantic colors for the code view's code keyword highlighter. Additionally, a fancy Material 3 feature was added, color harmonization of custom colors. The process is described in M3 guide under custom colors. The M3 library MaterialColorUtilities has the Blend function needed to perform the color harmonization, as described here and the Dart color Blend function is here.
Themes Playground: Updated the default AppBar style, it uses a dropdown menu that can also select 'null' choice and use default M2 and M3 theming as defaults via it. The AppBar panel now also displays an AppBar Widget of its own, so one does not have to look at the actual AppBar to see the style. It also has widgets below it used to demonstrate the opacity setting.
Themes Playground: Code gen and control enable/disable for onColor blends updated to lock controls with no impact when using seeded color scheme. Code is also not generated for onColor blend settings that has no impact when using seeded color schemes.
Themes Playground: Features and code gen for additional Elevated.button individual foreground and background colors.
Themes Playground: Features and code gen for additional Outlined.button separate outline color.
Themes Playground: To the component panel added support to customize outline border thickness for OutlinedButton, ToggleButtons and TextField's InputDecorator.
Themes Playground: Added features and UI for new Flutter SDK ColorScheme colors outlineVariant and scrim.
DOCS
Removed duplicated section of 5.1.0 changelog entry with date July 5, 2022.
Harmonized the changelog style and its past history. The new style and how it looks will be tested with a dev release to ensure it works well on pub.
KNOWN FLUTTER SDK ISSUES IMPACTING THEMING
The issues below in the Flutter SDK itself, are known to impact FlexColorScheme and Flutter theming in general. The issues are typically caused by incomplete Material 3 implementation in Flutter.
The M3 Chip themes available in Flutter master 3.1.0-0.0.pre.2216 at the time of writing, do as noted here PR 107166 comment, not yet M3 theme plain vanilla Chip when using Material 3. This might be fixed in an additional PR later in the SDK. This proposal tracks the potential implementation of this #109470.
#107946 Cannot theme Shape and IconSize differently for different sized FloatingActionButtons. One of the drivers behind the breaking FAB style defaults for the opinionated FAB theme in FCS, was this issue.
#108539 Cannot theme shape independently for SnackBar with different behavior. This is the reason why FCS does not yet offer a custom shape in its opinionated SnackBar theme. To replicate the un-themed behavior with slightly different border radius values, one must make custom wrapper widgets for SnackBar.
The Flutter SDK M3 useMaterial3 flag set to true continues to have a number of challenges in addition to the above ones. We as before still have the issues below in Flutter stable 3.0.5 and also at least in Flutter master 3.1.0-0.0.pre.2216 and earlier:
#107190 Elevation issue with Material widget, when opting in on useMaterial3 causes widespread elevation issues. Concerning the reported elevation issue for dialogs included in the linked report, it was observed as fixed for them in master, but later the PR fixing it was reverted. Then it was relanded and then the reland reverted, see Issue #107423, PR #108718, PR #109170 and PR 109172. Even after it lands it won't solve all the mentioned incompleteness caused M3 elevation issues, only Dialogs. Popup in particular will remain troublesome.
#103864 Dynamically changing Typography in ThemeData generates an error
FIXED #107305 Regression: AppBarTheme properties iconTheme and actionsIconTheme ignored on master channel when useMaterial3 is true. This is not in stable Flutter channel stable 3.0.5, but if you used master channel it was something to be aware of, as it exists in Flutter master 3.1.0-0.0.pre.2033 and many earlier master 3.1.0-x versions. This issue was fixed via PR #108332 and can no longer be observed in master, 3.1.0-0.0.pre.2108 or later versions.
Deprecated: FlexColorScheme.m3TextTheme. The custom M3 text theme is no longer needed after Flutter 3.0.0 release that includes the new M3 Typography…
NEW
Added full support for in Flutter 3.0.0 new ColorScheme.surfaceTint color. It is set to ColorScheme.primary color by default, as Flutter and Material 3 does. If a custom surfaceTint color is provided, it is also used as the blend color, instead of primary color, for
FlexColorScheme's surface blend feature.
Added API for using Flutter 3.0.0 theme extensions directly via FlexColorScheme API. It was added as a convenience feature in order to avoid having to add theme extensions with a copyWith on FlexColorScheme produced ThemeData. With the FlexColorScheme.extensions and FlexThemeData.extensions properties you can add custom theme extensions directly.
DEPRECATED
Deprecated: FlexColorScheme.m3TextTheme. The custom M3 text theme is no longer needed after Flutter 3.0.0 release that includes the new M3 Typography in addition to its earlier released TextTheme. You can opt in on using the new M3 style TextTheme as before by setting FlexColorScheme.subThemesData.useTextTheme to true or by setting FlexColorScheme.useMaterial3 to true. Using either does however come with known issue #103864, where dynamically switching Typography, e.g. from 2014 or 2018, to M3 2021 Typography, triggers the mentioned assert in issue
#103864. This issue has always existed in Flutter SDK ThemeData when dynamically changing between different Typography. Before FlexColorScheme avoided triggering this issue by only using Typography 2018, also when
opting in on M3 TextTheme, that before used 2018 based Typography to make a custom M3 like TextTheme. Avoiding this issue is no longer possible when opting in on M3, that now correctly uses its own and different Typography from M2. This exposes this issue if you dynamically change ThemeData from one to another Typography. To avoid this Flutter SDK issue, use the same Typography for all your themes in your app and don't dynamically switch theme between ThemeData objects that uses different Typography in your application. The use cases for doing this are few, but it is still a Flutter SDK limitation to be aware about.
Deprecated: FlexSubThemes.buttonTheme that creates an opinionated ButtonThemeData. The ButtonThemeData is marked as obsolete in Flutter SDK, but not yet deprecated in Flutter version 3.0.0. FlexColorscheme now marks it as deprecated. It will be removed in a future FlexColorScheme release when Flutter SDK deprecates ButtonThemeData.
M3 STYLE FIXES AND CHANGES
FAB M3 defaults change: Floating Action Button background color, will when opting in on ThemeData.useMaterail3, use color theme.colorScheme.primaryContainer, otherwise theme.colorScheme.secondary is used.
Input Decorator default change: The TextField and its InputDecorator border radius default value was changed from 20dp to 16 dp when using opinionated component themes. If opting in on Material 3, the default value for M3 design is used, which is only 4 dp. See specification https://m3.material.io/components/text-fields/specs. Flutter 3.0.x does not yet implement the new M3 TextField style, but via this change when opting in on M3, FlexColorScheme offers an early approximation of it.
NavigationBar M3 defaults change: Default colors of NavigationBar when opting in on useMaterial3 and not using opinionated component themes will now match M3 default colors. The background color will follow M3 style also by default when component themes are enabled and useMaterial3 is true. This style is difficult to replicate with a single color otherwise. The difference is subtle for FCS surface tinted background colors. You can still set it to background color to replicate past FCS default color when sub-themes were enabled. For other properties, if opinionated component themes are not used, FCS will use default M3 theme styles on NavigationBar when useMaterial3 is true. If opting in on opinionated component themes, FCS uses its own custom opinionated default style. Which can be modified to be the same as default M3 style too, just as before. The change also includes a default font size change for FCS opinionated styled navigation bar, from 11dp to 12dp. This change was done to harmonize it with its M3 style.
NavigationRail M3 defaults change: Default colors of NavigationRail when opting in on useMaterial3 and not using opinionated component themes will now match M3 default colors. If opinionated component themes are not used, FCS will use default M3 theme styles on NavigationRail when useMaterial3 is true. If opting in on opinionated component themes, FCS uses its own custom opinionated default style. Which can be modified to be the same as default M3 style too, just as before. The change also includes a default font size change for FCS opinionated styled rail, from 14dp to 12dp. This change was done to harmonize it with its M3 style.
Toggleable M3 style change: Default color of toggles (Switch, CheckBox and Radio) are now using primary color as default themed color when opting in on opinionated component themes or setting ThemeData.useMaterail3 to true. The Switch, CheckBox and Radio themes then use a style that match the M3 color design intent. In it, switches and toggles are mostly primary color based. In M3 color design, the secondary color is a poor choice for switches and toggles, and it is therefore not used as their default color. It does not look nice with M3 based ColorSchemes, created e.g. using M3 color seeding. If you use a custom M3 color design, where secondary color is still prominent, you can of course still use it.
Fixed lint: "Avoid using private types in public APIs". See tweet discussion about why and when you might run into this lint being triggered by older Stateful Widgets. The lint warning was addressed in the package and examples.
EXAMPLE UPDATES
Added a Theme Extensions example to the default example app, i.e. the "Hot Reload Playground".
Themes Playground: Updated the default style info labels for Switch, CheckBox and Radio.
Themes Playground: To the top row theme selector, where the FlexColorScheme and component themes switches are, added the "Use Material 3" toggle. Previously this toggle was only available on the introduction panel. The availability in the header makes it easy to toggle it ON and OFF at any time, to see what impact it has on widgets.
Themes Playground: Updated the default style info labels for the NavigationBar. The logic to display default color labels in different config modes (M2/M3/FCS/FCS+M2/FCS+M3) is quite involved, please report any issues.
Themes Playground: Updated the default style info labels for the NavigationRail. The logic to display default color labels in different config modes (M2/M3/FCS/FCS+M2/FCS+M3) is quite involved, please report any issues.
Themes Playground: Due to issue #107190, the Playground previous default to use Material 3 was changed to false.
Added support in Themes Playground to customize the surfaceTint color. It controls both the elevation color used for elevated Material surfaces in M3. Plus for FlexColorScheme it is also used as the surface blend color. By default, the surfaceTint color equals ColorScheme.primary color. Generally there are not many good design reasons to change the color, but it is now possible to do so. A good graphical designer can use it to create subtle difference from the standard surface elevation color branding effects. Used poorly, it mostly creates not so appealing visual and coloring results.
KNOWN FLUTTER SDK ISSUES
The issues below in the Flutter SDK itself, are known to impact FlexColorScheme and Flutter theming in general.
Switching Typography dynamically in Flutter SDK ThemeData is broken, see issue #103864 for more information. If it is done and the error ignored, an app doing so eventually become unstable.
The Themes Playground app contains a workaround to avoid issue #103864. The workaround is done by always using 2021 Typography, but simulating 2018 Typography. This is done by using a custom TextTheme that looks like 2018 Typography is used when using M2 theme mode. The Playground App actually always stays in 2021 Typography, but looks
like it switches it. Which it does by applying a custom TextTheme in 2021 Typography, that looks like 2018 Typography is used. All other examples also avoid the issue by only using the M3 2021 Typography and not even mimicking a switch between M2 and M3 Typography. The above workaround is needed because the Playground app has toggles that switches Typography frequently, without the workaround it will eventually crash. With this workaround it never switches Typography, it just looks like it does, but app stays in 2021 Typography all the time. The by Themes Playground generated ThemeData config will use the actual real effective Typography. This is also fine, since an app using the theme will likely never switch used Typography. However, if it does, it will face the same issue the Playground app did. The issue is a Flutter SDK issue that FlexColorScheme cannot fix. Most likely 99% of apps will never run into this issue.
In Flutter SDK 3.0.x, when opting in on useMaterial3:true, the Material widget and other SDK widgets built on it, gets no elevation when only the elevation property is defined. It is required to also define shadowColor and/or surfaceTintColor to get any elevation effect. When using the Material widget itself this is easy to address. However, widgets like Drawer, PopupMenuButton, BottomNavigationBar, NavigationRail, Dialog, AlertDialog, TimePickerDialog, DatePickerDialog, MaterialBanner and BottomSheet do not expose these Material properties and cannot be elevated.
The issue is reported and tracked here #107190 and also mentioned in the FlexColorScheme repo here #54. There are no good workarounds for using elevation on these widgets when useMaterial3 is true. The options are to not use M3, if such elevations are important to your app design. One working fix is to wrap those widgets in a theme where useMaterial3 is false, then te rest of your app can still use it. This is however a rather tedious workaround fix. Due to current SDK Material elevation issues when useMaterial3 is true, it is recommended to not use it yet.
This regression in master channel impacts AppBar icon colors when using Material 3 #107305. It has not yet landed in stable channel Flutter 3.0.4, but if you use master channel it is something to be aware of.
July 8, 2022
NEW
Added full support for in Flutter 3.0.0 new ColorScheme.surfaceTint color. It is set to ColorScheme.primary color by default, as Flutter and Material-3 does. If a custom surfaceTint color is provided, it is also used as the blend color, instead of primary color, for FlexColorScheme's surface blend feature.
Added API for using Flutter 3.0.0 theme extensions directly via FlexColorScheme API. It was added as a convenience feature to avoid having to add theme extensions with a copyWith on FlexColorScheme produced ThemeData. With the FlexColorScheme.extensions and FlexThemeData.extensions properties you can add custom theme extensions directly.
DEPRECATED
Deprecated: FlexColorScheme.m3TextTheme. The custom Material-3 text theme is no longer required after Flutter 3.0.0 release that includes the new Material-3 Typography in addition to its earlier released TextTheme. You can opt in on using the new Material-3 style TextTheme as before by setting FlexColorScheme.subThemesData.useTextTheme to true or by setting FlexColorScheme.useMaterial3 to true. Using either does however, come with known issue #103864, where dynamically switching Typography, e.g., from 2014 or 2018, to Material-3 2021 Typography triggers mentioned assert in issue #103864. This issue has always existed in Flutter SDK ThemeData when dynamically changing between different Typography. Before FlexColorScheme avoided triggering this issue by only using Typography 2018, also when opting in on Material-3 TextTheme, that before used 2018 based Typography to make a custom Material-3 like TextTheme. Avoiding this issue is no longer possible when opting in on Material-3, that now correctly uses its own and different Typography from Material-2. This exposes this issue if you dynamically change ThemeData from one to another Typography. To avoid this Flutter SDK issue, use the same Typography for all your themes in your app and do not dynamically switch theme between ThemeData objects that use different Typography in your application. The use cases for doing this are few, but it is still a Flutter SDK limitation to be aware of.
Deprecated: FlexSubThemes.buttonTheme that creates an opinionated ButtonThemeData. The ButtonThemeData is marked as obsolete in Flutter SDK but not yet deprecated in Flutter 3.0.0. FlexColorscheme now marks it as deprecated. It will be removed in a future FlexColorScheme release when Flutter SDK deprecates ButtonThemeData.
Material-3 STYLE FIXES AND CHANGES
FAB Material-3 defaults change: Floating Action Button background color, will when opting in on ThemeData.useMaterial3, use color theme.colorScheme.primaryContainer, otherwise theme.colorScheme.secondary is used.
Input Decorator default change: The TextField and its InputDecorator border radius
default value was changed from 20 dp to 16 dp when using opinionated component themes.
If opting in on Material-3, the default value for Material-3 design is used, which is only 4 dp.
See specification https://m3.material.io/components/text-fields/specs.
Flutter 3.0.x does not yet implement the new Material-3 TextField style, but via this change when
opting in on Material-3, FlexColorScheme offers an early approximation of it.
NavigationBar Material-3 defaults change: Default colors of NavigationBar when opting in on
useMaterial3 and not using opinionated component themes will now match Material-3 default colors. The background color will follow Material-3 style also by default when component themes are enabled and useMaterial3 is true. This style is difficult to replicate with a single color otherwise. The difference is subtle for FCS surface tinted background colors. You can still set it to background color to replicate past FCS default color when component themes were enabled. For other properties, if opinionated component themes are not used, FCS will use default Material-3 theme styles on NavigationBar when useMaterial3 is true. If opting in on opinionated component themes, FCS uses its own custom and opinionated default style. It can be modified to be the same as the default Material-3 style too, just as before. The change also includes a default font size change for FCS opinionated styled navigation bar, from 11 dp to 12 dp. This change was done to harmonize it with its Material-3 style.
NavigationRail Material-3 defaults change: Default colors of NavigationRail when opting in on
useMaterial3 and not using opinionated component themes will now match Material-3 default colors. If opinionated component themes are not used, FCS will use default Material-3 theme styles on NavigationRail when useMaterial3 is true. If opting in on opinionated component themes, FCS uses its own custom and opinionated default style. It can be modified to be the same as the default Material-3 style too, just as before. The change also includes a default font size change for FCS opinionated styled rail, from 14 dp to 12 dp. This change was done to harmonize it with its Material-3 style.
Toggleable Material-3 style change: Default color of toggles (Switch, CheckBox and Radio) are now using primary color as the default theme color when opting in on opinionated component themes or setting ThemeData.useMaterial3 to true. The Switch, CheckBox and Radio themes then use a style that matches the Material-3 color design intent. In it, switches and toggles are mostly primary color. In Material-3 color design, the secondary color is a poor choice for switches and toggles, and it is therefore not used as their default color. It does not look nice with Material-3-based ColorSchemes, created e.g., using Material-3 color seeding. If you use a custom Material-3 color design, where secondary color is still prominent, you can, of course, still use it.
Fixed lint: "Avoid using private types in public APIs". See tweet discussion about why and when you might run into this lint being triggered by older Stateful Widgets. The lint warning was addressed in the package and examples.
EXAMPLES
Added a Theme Extensions example to the default example app Hot Reload Playground.
Themes Playground: Updated the default style info labels for Switch, Checkbox, and Radio.
Themes Playground: To the top row theme selector, where the FlexColorScheme and component themes switches are, added the "Use Material-3" toggle. Previously, this toggle was only available on the introduction panel. The availability in the header makes it easy to toggle it ON and OFF at any time, to see what impact it has on widgets.
Themes Playground: Updated the default style info labels for the NavigationBar. The logic to display default color labels in different config modes (Material-2/Material-3/FCS/FCS+Material-2/FCS+Material-3) is quite involved, please report any issues.
Themes Playground: Updated the default style info labels for the NavigationRail. The logic to display default color labels in different config modes (Material-2/Material-3/FCS/FCS+Material-2/FCS+Material-3) is quite involved, please report any issues.
Themes Playground: Due to issue #107190, the Playground previous default to use Material-3 was changed to false.
Themes Playground: Added support to customize the surfaceTint color. It controls both the elevation color used for elevated Material surfaces in Material-3. Plus for FlexColorScheme it is also used as the surface blend color. By default, the surfaceTint color equals ColorScheme.primary color. Generally, there are few good design reasons to change the color, but it is now possible to do so. A good graphical designer can use it to create subtle difference from the standard surface elevation color branding effects. Used poorly, it mostly creates not so appealing visual and coloring results.
KNOWN FLUTTER SDK ISSUES
The issues below in the Flutter SDK itself, are known to impact FlexColorScheme and Flutter theming in general.
Switching Typography dynamically in Flutter SDK ThemeData is broken, see
issue #103864 for more information.
If it is done and the error is ignored, an app doing so eventually becomes unstable.
The Themes Playground app contains a workaround to avoid issue #103864. The workaround is done by always using the 2021 Typography, and simulate 2018 Typography. This is done by using a custom TextTheme that looks like the 2018 Typography, when selecting it. The Playground App actually always stays in 2021 Typography, but it looks like it switches it. Which it does by applying a custom TextTheme to its 2021 Typography, that looks like 2018 Typography is used. All other examples avoid the issue by only using the Material-3 2021 Typography and not even mimicking a switch between Material-2 and Material-3 Typography.
The above workaround is required because the Themes Playground app has toggles that can switch Typography, without the workaround it will eventually crash. With this work-around it never switches Typography, it just looks like it does, but app stays in 2021 Typography all the time. The by Themes Playground generated ThemeData config will use the actual real effective Typography. This is also fine, since an app using the theme will likely never switch used Typography. However, if it does, it will face the same issue as the Playground app did. The issue is a Flutter SDK issue that FlexColorScheme cannot fix. Most likely, 99% of apps will never run into this issue.
In Flutter stable 3.0.x, when opting in on useMaterial3:true, the Material widget and other SDK widgets built on it, gets no elevation when only the elevation property is defined. It is required to also define shadowColor and/or surfaceTintColor to get any elevation effect. When using the Material widget itself this is easy to address. However, widgets like Drawer, PopupMenuButton, BottomNavigationBar, NavigationRail, Dialog, AlertDialog, TimePickerDialog, DatePickerDialog, MaterialBanner and BottomSheet do not expose these Material properties and cannot be elevated.
The issue is reported and tracked here #107190 and also mentioned in the FlexColorScheme repo here
#54. There are no good workarounds for using elevation on these widgets when useMaterial3 is true. The options are to not use Material-3 if such elevations are important to your app design. One working fix is to wrap those widgets in a theme where useMaterial3 is false, then the rest of your app can still use it. This is, however, a rather tedious workaround. Due to current Flutter SDK Material elevation issues when useMaterial3 is true, it is recommended to not use it until this issue is fixed.
This regression in master channel impacts AppBar icon colors when using Material-3 #107305. It has not yet landed in stable channel Flutter stable 3.0.5, but if you use the master channel, it is something to be aware of.
For the custom and temporary m3TextTheme: Fixed the Typography letterSpacing for bodyLarge to match corrected M3 spec that had wrong specification on
FIX
April 29, 2022
FIX
m3TextTheme: Fixed the Typography letterSpacing for bodyLarge to match corrected Material-3 spec that had wrong specification on the Material-3 website 0.15 -> 0.5. See Flutter SDK issue #102121.FlexColorScheme version 5 is style wise a big breaking change since all the built-in produced ColorSchemes the themes use have been revised to follow…
The full journey from version 4.2.0 to stable 5.0.0 includes the steps in change logs for development versions 5.0.0-dev.3, -dev.2 and -dev.1. Please refer to them for all details. This changelog contains a summary of breaking and other critical changes from version 4.2.0.
FlexColorScheme version 5 is style wise a big breaking change since all the built-in produced ColorSchemes the themes use have been revised to follow the new Flutter 2.10.0 Material 3 based ColorScheme. The color changes to the built-in schemes have been kept minimal compared to previous styles.
Mostly new color values were added to provide support for all the new colors in the Flutter Material 3 ColorScheme update, that landed in Flutter 2.10.0. The new colors are style aligned with past styles as far possible, while also keeping them inline with the Material 3 ColorScheme design intent.
As ColorScheme.primaryVariant and secondaryVariant have been deprecated in Flutter 2.10 SDK, so have they in FlexColorScheme. All past color constants for all color values and helper classes with the name "variant" in them, have been self deprecated in FlexColorScheme. The variant color values still exists, if you have used any of them directly, they still work. The old built-in variant color values will remain available at least until version 6.0, maybe even 7.0 if so requested by users.
Breaking
Requires at least Flutter 2.10.0.
ColorScheme do not exist in any stable version of Flutter before version 2.10.surfaceStyle removed.
surfaceStyle, including all its implementing classes, enums, helpers and tests have been removed.surfaceStyle in FlexColorScheme.light and FlexSchemeData.light.surfaceStyle in FlexColorScheme.dark and FlexSchemeData.dark.FlexSurface, that only surfaceStyle was using.FlexSchemeSurfaceColors.from that was used to create surface using the surfaceStyle. The factory FlexSchemeSurfaceColors.blend replaced it in version 4.0.0 already, when using surfaceMode and blendLevel.surfaceMode and blendLevel instead, it has more blend styles and finer granularity than the removed surfaceStyle.theme: FlexThemeData.light(
scheme: FlexScheme.flutterDash,
surfaceMode: FlexSurfaceMode.highScaffoldLowSurface,
blendLevel: 20,
),
FlexSubThemesData.navigationBarIsStyled removed.
navigationBarIsStyled in FlexSubThemesData has been removed. If you have used it, it has a broader more general replacement called FlexSubThemesData.useFlutterDefaults.useFlutterDefaults instead, or set styles manually using individual properties to desired styles matching Flutter defaults un-themed component designs.FlexColorScheme.useSubThemes no function
useSubThemes. This property has no function after 4.2.0 stable and 5.0.0-dev.1. Previously setting this property to true activated the default set and configuration of the optional opinionated component sub-themes, even if you did not pass any FlexSubThemesData() configuration data to subThemesData. Before when useSubThemes was true and no subThemesData defined, it created one internally using the default constructor FlexSubThemesData() and used it. It also ignored any defined and to subThemesData assigned one, if the flag was set to false.FlexSubThemesData() to FlexColorScheme.subThemesData.keyColors with FlexKeyColors and tones with FlexTones.FlexColorScheme.useSubThemes to true and not specified any subThemesData properties, you must now add the default constructor. Likewise, if you had set FlexColorScheme.useSubThemes to false, and had a FlexColorScheme.subThemesData defined, you must remove it disable using it. If you need to toggle it ON and OFF, use a bool to enabled/disable it, then pass in the FlexSubThemesData when enabled, and null when not using it.Breaking and deprecated due to Flutter SDK change in 2.10.0 stable release.
primaryVariant and secondaryVariant
primaryVariant and secondaryVariant in FlexColorScheme are deprecated and can no longer be used to set colors values that result in any color values in Flutter SDK deprecated same named ColorScheme color properties.ColorScheme deprecated properties primaryVariant and secondaryVariant will always get their Flutter SDK default values,
regardless of what input you give to them in FlexColorScheme. Flutter sets its deprecated primaryVariant equal to primary and secondaryVariant equal to secondary.primaryContainer, secondaryContainer, tertiary or tertiaryContainer color, as replacement colors in your custom widgets. The right choice depends on your color design.FlexColorScheme setup made for a version before version 5.0, with version 5.0, and, if you have used custom color schemes where you defined theFlexColorScheme properties primaryVariant and secondaryVariant or defined and used them via custom FlexSchemeColors, in the colors property in FlexColorScheme. Then, in those cases the variant color properties will function as fallback input for color properties primaryContainer and secondaryContainer respectively, unless own color values for these properties are provided.FlexColorScheme instead. Then migrate away from using Flutter SDK ColorScheme colors primaryVariant and secondaryVariant anywhere in your application. Instead, use any of its new ColorScheme color properties as fitting with your design. This is something you have to do after Flutter 2.10, even if you are not using FlexColorScheme. Sure, not immediately, but eventually when the Flutter SDK ColorScheme colors primaryVariant and secondaryVariant are removed after a year or so.Change and breaking past style.
The custom "internal" and temporary m3TextTheme was changed. It is style breaking with 4.2.0 and 5.0.0-dev.1 & 2. It breaks past used style when opting in on component themes and its optional custom m3TextTheme enabled. The updated custom implementation of it now follows the implementation used in Flutter master channel, apart from this issue, where it for now implements the value used in the M3 Web guide. The changes in styles otherwise concern the addition of the font geometry height, which the previous custom implementation did not have. The usage of the custom m3TextTheme should be considered internal and temporary. It will be changed to use the actual Flutter implementation once PR #97829 lands in Flutter stable channel. The custom m3TextTheme will then be deprecated.
The computed colors for ThemeData colors primaryColorLight, primaryColorDark and secondaryHeaderColor were changed.
It is style breaking with 4.2.0 and 5.0.0-dev.1 & 2. The change breaks past used styles on these rarely used colors. These ThemeData colors are also on a deprecation path and will likely receive some new none MaterialColor dependent color defaults when that change happens. The new ColorScheme.primary computed colors for these rarely used colors are better balanced than before, and work well regardless of used ColorScheme.primary shade and tint.
The color definition value for FlexColor.espressoLightPrimary color was changed. This is style breaking with 4.2.0 and 5.0.0-dev.1 & 2. The new color for FlexColor.espressoLightPrimary breaks past used color for this color constant. The color was changed from 0xFF220804 to 0xFF452F2B. Past color was too dark brown, almost black to be very usable in a UI. It was very black coffee like, but not very practical in a UI, it was too close to black. Since version 5 is anyway a major style breaking with the introduction of the new Material 3 ColorScheme, the opportunity to improve this color value used in the built-in theme espresso theme was used.
Beware
SchemeColor values and order, potentially breaking. The enum SchemeColor has new values and past values are in a new order. The order was changed to accommodate all the new color values, and to keep them in the same order as their corresponding color properties in Flutter Material 3 ColorScheme color values. The change of order is potentially breaking, but highly unlikely to break anything in major ways in normal usage.The custom m3TextTheme will then be deprecated.
Test release to verify builds and minor changes before stable release.
The package documentation has now moved too its own site at docs.flexcolorscheme.com.
It is a major update and rewrite of previous documentation. It also contains general Flutter theming guidance. One chapter is still work in progress. When it is completed, the stable v5.0.0 will be released.
m3TextTheme revised.m3TextTheme enabled. The updated custom implementation of it now follows the implementation used in Flutter master channel, apart from this issue, where it for now implements the value used in the M3 Web guide.m3TextTheme should be considered internal and temporary, it will be changed to use the actual Flutter implementation once PR #97829 lands in Flutter stable channel. The custom m3TextTheme will then be deprecated.ThemeData colors primaryColorLight, primaryColorDark and secondaryHeaderColor were changed.Style breaking with 4.2.0 and 5.0.0-dev.1 & 2, breaks past used styles on the rarely used colors primaryColorLight, primaryColorDark and secondaryHeaderColor.
These ThemeData colors are on a deprecation path and will likely receive some new none MaterialColor dependent color defaults when that change happens. The new ColorScheme.primary computed colors for these rarely used colors are better balanced than before, and work well regardless of used ColorScheme.primary shade and tint.
FlexColor.espressoLightPrimary color was changed.Style breaking with 4.2.0 and 5.0.0-dev.1 & 2: New color for FlexColor.espressoLightPrimary breaks past used color for this color constant.
The color was changed from 0xFF220804 to 0xFF452F2B. Past color was too dark brown, almost black to be very usable in a UI. It was very black coffee like, but not very practical in a UI, it was too close to black. Since version 5 is anyway a major style breaking with the introduction of the new Material 3 ColorScheme, the opportunity to improve this color value used in the built-in theme espresso theme was used.
Completed in version 4.0.0 planned, for version 5.0.0, removal of deprecated property surfaceStyle, including all its implementing classes, enums and…
BREAKING
Completed in version 4.0.0 planned, for version 5.0.0, removal of
deprecated property surfaceStyle, including all its implementing classes,
enums and helpers:
surfaceStyle in FlexColorScheme.light.surfaceStyle in FlexColorScheme.dark.FlexSurface, that surfaceStyle where.FlexSchemeSurfaceColors.from that was used to create
surface using the FlexSurface. The factory FlexSchemeSurfaceColors.blend
replaced in version 4.0.0 already when using surfaceMode and blendLevel.Deprecated property useSubThemes. This property has no function after
4.2.0 stable and 5.0.0-dev.1. FlexColorScheme opinionated component sub-themes
are now created by adding a default constructor FlexSubThemesData() or one with
some custom property values set, to subThemesData. This creates sub-themes
using the FlexColorScheme opinionated sub-themes. Removing this property makes the
API more consistent. It now follows the same design that is used for keyColors
with FlexKeyColors and tones with FlexTones.
Setting the property useSubThemes will not cause an error, it just has no effect.
You can safely remove it. The property useSubThemes will be removed in release 6.0.0.
The property navigationBarIsStyled in FlexSubThemesData was removed in
v5.0.0-dev.1 as no longer needed. It is now kind of back with a new broader
replacement called FlexSubThemesData.useFlutterDefaults.
The in dev.1 version tested API-style to
set various SchemeColor properties to null, to get SDK default for them was not
nice. The FlexSubThemesData should default to its own preferred
and recommended harmonized defaults when not defined. It is better to offer a
toggle that can be set, to when possible/offer an opt-out from some bigger style
differences from SDK defaults. This can be useful if one wants to create
custom component themes and wish to start from less opinionated ones.
The new useFlutterDefaults is false by default, and the sub-themes undefined
null values result in its own harmonized and recommended settings. By setting
it to true a bit messier and un-harmonized Flutter default are back. Currently,
this impacts different styles and colors on BottomNavigationBar, NavigationBar,
and NavigationRail. See API docs for details regarding
defaults with this flag on and off.
The FlexSubThemesData property popupMenuRadius and the radius in
corresponding static sub-theme helper FlexSubThemes.popupMenuTheme,
now defaults to 4.
In versions before v5.0.0-dev.2 it defaulted to 10. The M3 spec for it
was not available when it was chosen originally. It was assumed to have
higher border radius like rest of designs. However, the spec has it
defined here now, and it
is 4. Since border radius default values are stated in FlexColorScheme
sub-theme design goals to follow the M3 design specs, it was updated to
match the spec. A bit higher rounding, may actually fit better with
the very round M3 design, try 8 or 10. It is very simple to change bach with
the API.
FIX
Pub.dev analysis does not like document references to deprecated Flutter
properties. Changed the primaryVariant and secondaryVariant references
in document comments to primaryVariant and secondaryVariant. Nor does it
like when you use tests to deprecated Flutter SDK members, removed them too,
they were not needed either after some redesign of a few tests.
Fixed. When using sub-themes and selecting a ColorScheme based color, as
color for the AppBar, instead of using abbBarStyle in light and dark
factories, the appBarOpacity was not applied to the selected color. The
priority of effective AppBar color was also revised to follow the norm,
which from lowest to highest is:
abbBarStyle in light/dark factories and ThemeData extensions, which
selects the used color from active scheme or colors, in the same
factories or extensions.appBarBackgroundSchemeColor in FlexSubThemesData when used.appBarBackground in FlexColorScheme.CHANGE
Changed the priority in FlexColorScheme when using direct input color
properties, colorScheme input and using key color seeded ColorScheme
generation. The new order is that input colorScheme is in this rare use case
always overridden by the seed generate ColorScheme. This allows us
to use a colorScheme as input to seed generation, where this color
scheme could already have been externally seeded generated, but that we want
to modify by using custom FlexTones or surface blends in FleColorScheme.
The direct properties overrides the seeded color scheme as before, unless it
is primary, secondary, tertiary or their container colors. In that case
the keyColors, "keep" property determines if those colors are kept or not.
The FlexSubThemesData property inputDecorationRadius was deprecated and
renamed to inputDecoratorRadius, to harmonize the other
InputDecoration property names in FlexSubThemesData.
The old name will be removed in release 6.0.0.
Deprecated and renamed navigationBarHighlightSchemeColor to
navigationBarIndicatorSchemeColor in FlexSubThemesData, to
harmonize the naming standard. Likewise, the parameter highlightSchemeColor
ìn FlexSubThemes.navigationBarTheme was deprecated and replaced by
indicatorSchemeColor. The old names will be removed in release 6.0.0.
In 5.0.0-dev.1, the renamed properties were deprecated and broken with 4.2.0.
They are still deprecated, but now fallback via the old properties. They
are no longer breaking. This concerns FlexSubThemesData properties:
bottomNavigationBarSchemeColor -> bottomNavigationBarSelectedLabelSchemeColornavigationBarTextSchemeColor -> navigationBarSelectedLabelSchemeColornavigationBarMutedUnselectedText -> navigationBarMutedUnselectedLabelnavigationBarIconSchemeColor -> navigationBarSelectedIconSchemeColorAnd FlexSubThemes.navigationBarTheme properties:
textSchemeColor -> selectedLabelSchemeColorunselectedTextSchemeColor -> unselectedLabelSchemeColoriconSchemeColor -> selectedIconSchemeColormutedUnselectedText -> mutedUnselectedLabelAnd FlexSubThemes.bottomNavigationBarTheme properties:
baseSchemeColor -> selectedLabelSchemeColorThe old property names will be removed in release 6.0.0.
NEW
Added SchemeColor based theming of SnackBar background color via
snackBarBackgroundSchemeColor in FlexSubThemesData and support for it
in FlexSubThemes.
Changed the color values for FlexColor.materialLightSecondaryContainer and
FlexColor.materialLightSecondaryContainerHc. These color properties
do not have any specification in Material 2 spec. Updated the colors values
that had been made up for dev.1 release to better match the design intent
of those colors for the new Material 3 ColorScheme.
Added inputDecoratorUnfocusedBorderIsColored to FlexSubThemesData and
support for it in FlexSubThemes via unfocusedBorderIsColored. Previously
an unfocused or hovered border/underline always had a hint of selected
base color. Setting this to false, leaves it at the grey defaults used by
Flutter defaults.
Added navigationBarIndicatorOpacity and navigationRailIndicatorOpacity
to FlexSubThemesData, to expose their already existing properties in
corresponding sub-themes used by FlexColorScheme.
DEMO APPS
TESTS
Despite being a very big release, with many new features, actual breaking changes are very few and mostly concerns in version 4 deprecated members and…
Version 5 is a big refactor with deprecation of previous variant based
color names in favor of container ones that were added to updated M3
based ColorScheme in Flutter 2.10.0. The same additions and changes are now
also introduced in FlexColorScheme. Despite being a very big release, with
many new features, actual breaking changes are very few and mostly concerns
in version 4 deprecated members and of course requiring minimum Flutter
2.10.0 to work.
The WIP updates now includes the version of the key color seeded M3 ColorScheme
usage intended for the final design. The feature supports seeding by not only
using a single primary key color, but also using separate key colors for
secondary and tertiary colors. The Flutter SDK ColorScheme.fromSeed only
support using a single color as seed. The primary, secondary and tertiary
color are used as key color seeds, when seeding is used, and by default all
three color are used as key for their respective tonal palette used by
the generated ColorScheme. Using secondary and teritary colors can each
optionally be turned OFF. If both are, the result is same as when using
ColorScheme.fromSeed, with the primary color as seed key color.
When using a key seed color generated ColorScheme, it may sometimes, e.g. for
branding purposes, be useful to lock a certain color in the resulting
ColorScheme to the actual key color value used for primary, secondary
and tertiary. FlexColorScheme includes scheme appropriate colors for
each of these color properties, as well
their containers. You can for each property define which ones you want to keep
as defined by these input colors, in the seed generated ColorScheme. You
can of course use this feature with custom input colors as well.
The bundled example 5, the Themes Playground is now fully up to date with all the new features. Its updated code generation still needs results verification.
There are also now in Flutter master channel more actual M3 impacts and ThemeData color property deprecations commits landed in Flutter master channel that I reviewed and prepared for in advance when possible.
Much work on tests, and readme documentation updates remain, but API docs are up-to-date. And this book long change log should help. There are only a few breaking changes, and most of them are rarely used properties, so migration should be relatively easy, despite the long list of changes and new features.
BREAKING
Requires at least Flutter stable 2.10.0.This release uses new M3 ColorScheme
properties that are not included before Flutter version 2.10.0, as well
as the ThemeData flag useMaterial3.
Removed parameter surfaceStyle from FlexThemeData
extensions FlexThemeData.light and FlexThemeData.dark that uses
in version 4.2.0 already deprecated property surfaceStyle in FlexColorScheme
class. The same deprecated property surfaceStyle in FlexColorScheme class
is still available in 5.0.0-dev.1. In the stable release 5.0.0 it might
be removed as well. They were all scheduled for deprecation in version 5.0.0,
but keeping it around a bit longer in the main class in 5.0.0-dev releases
to prolong backwards API compatibility during development. Maybe I will keep
it in the release too, many tests need to be rewritten when they are removed.
The enum SchemeColor has new values and past values are in a
new order. The order was changed to accommodate new color values and to
keep them in the same order as their corresponding color properties
in M3 ColorScheme. The change of order is potentially breaking, but unlikely
to break anything in major ways, other than possibly local storage of selected
enum values. In the bundled samples you might for example see wrong color
selections loaded from local storage, just reset or select correct value
to fix it.
To get more harmonized setup on opt-in sub themes for NavigationBar,
BottomNavigationBar and NaivgationRail a few properties in
FlexSubThemesData and FlexSubThemes had to be modified and broken.
Impact is estimated to be low for most users.
The following properties were renamed in FlexSubThemesData:
navigationBarTextSchemeColor -> navigationBarSelectedLabelSchemeColornavigationBarMutedUnselectedText -> navigationBarMutedUnselectedLabelnavigationBarIconSchemeColor -> navigationBarSelectedIconSchemeColorbottomNavigationBarSchemeColor -> bottomNavigationBarSelectedLabelSchemeColorIn FlexThemeData the property navigationBarIsStyled was removed. It is
no longer needed. The same end result it enabled can be achieved by
by setting all NavigationBar related properties in FlexSubThemesData that
have a none null default value to null.
The following parameters were renamed in FlexSubThemes.navigationBarTheme:
textSchemeColor -> selectedLabelSchemeColorunselectedTextSchemeColor -> unselectedLabelSchemeColoriconSchemeColor -> selectedIconSchemeColormutedUnselectedText -> mutedUnselectedLabelThe following parameter wa renamed in FlexSubThemes.bottomNavigationBarTheme:
baseSchemeColor -> selectedLabelSchemeColorNEW
Added useMaterial3 to all theme constructors and factories. This is
the same flag as in ThemeData, it does not have any major impact on
default themed widgets in Flutter 2.10.x. Opting in on opinionated
sub-themes, will however as before give opinionated component sub-themes that
result in Material 3 like styles. Similar look will become default widget
design in later Flutter SDK versions when using the flag useMaterial3 is
set to true.
Added new properties onPrimaryContainer, onSecondaryContainer,
tertiary, tertiaryContainer, onTertiary and onTertiaryContainer to
the un-namedFlexColorScheme constructor and factories
FlexColorScheme.light and FlexColorScheme.dark, as well as to extension
FlexThemeData to extensions FlexThemeData.light and FlexThemeData.dark
on ThemeData.
In FlexColor added new color properties for all color values to cover the
new "Container" color properties in Flutter 2.10 new M3 ColorScheme.
For every built-in FlexColor, there are now also these new color properties:
primaryContainersecondaryContainertertiarytertiaryContainerThe previous color values maps as follows:
tertiary = old secondaryVariant color value, that is deprecated
for each color value.primaryVariant, is just deprecated for each color value.The "variant" colors are still available as deprecated properties, and will
remain available until version 6.0.0. The old color properties and their values
still work as inputs, and they produce same equivalent ColorScheme results
as before. This is done by the values still being assigned as fallback value
in custom schemes so that new:
primaryContainer, if not assigned, falls back via old primaryVariant.secondaryContainer, if not assigned, falls back via old secondaryVariant.When it comes to the new built-in scheme designs, the color used on past:
secondaryVariant was a reasonable fit for new M3 tertiary color property
and was used as its value.secondaryContainer and
tertiaryContainer, had to get new built-in color values that fit with
the M3 design intent for those color properties. This while considering the
value secondary already had, and the value tertiary got by being
assigned the color value of past secondaryVariant.primaryContainer also needed a new color value. The
past primaryVariant is not the correct design fit for how the color
value is intended to be used in M3 Color design.Container color properties
are new features in this release, so they are considered "new" even
if their color value might have been recycled from previous properties
in some cases. Some Container color values may still be fine-tuned
before final 5.0.0 release, but it is unlikely.In class FlexSchemeColor added new color properties
primaryContainer and secondaryContainer they replace
deprecated properties primaryVariantand secondaryVariant. The old
properties still work and are
used as fallback to the new ones when the new ones are not provided.
The previous properties are still available as deprecated, and will remain
available until version 6.0.0, or until they are removed from the Flutter
stable channel, whichever comes first. The properties for built-in schemes
were assigned to their new corresponding FlexColorvalues.
In class FlexSchemeColor added new color definitions from FlexColor
for FlexSchemeColor.tertiary and FlexSchemeColor.tertiaryContainer.
In class FlexSchemeColor the FlexSchemeColor.secondaryContainer
and FlexSchemeColor.tertiaryContainer should be brighter versions of their
none container parent light mode and darker in dark mode. They receive
such color values via new corresponding FlexColorvalues.
In factory FlexSchemeColor.from added optional and nullable parameter
brightness. If not assigned, the factory works as before, producing a
complete FlexSchemeColor from just one or more color property inputs,
by producing a toned complete FlexSchemeColor suitable for a light or
dark M2 design based theme. If brightness is given value Brightness.light
it produces a FlexSchemeColor from just one or more color property inputs
suitable for a M3 light theme mode theme. If brightness is dark, for
a dark mode intended M3 scheme. When brightess is defined the factory
also sets defaults for error and errorContainer colors, if they
were not passed in. The error color is based on the Material 2 guide color
and errorContaier is a FlexColorScheme definition as it has no M2 value.
Seed based new M3 error colors are used when using key based seeded M3
ColorScheme. An option to also use M3 based error colors when not using
seeded ColorScheme, may be added in a future version.
Factory FlexSchemeColor.effective got the same nullable and optional
brightness property as FlexSchemeColor.from, with same functionality,
producing the same kind of M3 tone mapped colors when reducing amount of
used colors, and also providing error color defaults.
The FlexSchemeColor.effective factory otherwise works as before considering
color swapping and effective input colors reduction. Producing same results
via usedColors input limiter as if provided FlexSchemeColor would have
been created with FlexSchemeColor.from limited to same colors as implied
by usedColors parameter in the FlexSchemeColor.effective factory.
To the method FlexSchemeColor.toDark(), that computes a dark theme mode
appropriate FlexSchemeColor set from colors designed for light
theme mode, added the optional positional bool parameter swapColors.
It is false by default to not break past behavior.
It is used to swap the "main" and its Container color properties. So that
primary <> primarycontainer, secondary<> secondarycontainer and
tertiary<> tertiaryContainer in the input light theme mode designed
FlexSchemeColor are swapped before producing the output FlexSchemeColor
suitable for a dark theme mode. This is useful if the input
FlexSchemeColor is designed for a light M3 based ColorScheme. If it is
then, to get a correct M3 designed output and via whiteBlend value
desaturated colors, the main and container values of the light mode colors
should be swapped in the result. In light mode, M3 main is darker than
container, but in M3 dark mode it should be the other way around so that
main is lighter and container is darker. By swapping the colors and then
desaturating them with an adjustable white alpha blend, we can achieve
this design goal as well, when computed dark theme mode colors from a set
of provided light theme mode input colors.
Added additional opinionated component sub-themes for:
SwitchThemeData via FlexSubThemes.switchTheme.CheckboxTHemeData via FlexSubThemes.checkboxTheme.Radio via FlexSubThemes.radioTheme.NavigationRailThemeData via FlexSubThemes.navigationRailTheme.There are many quick and easy configuration parameters added
to FlexSubThemesData. There following built in widgets now have quick and
easy custom theming option via sub-themes opt-in.
TextButtonElevatedButtonOutlinedButtonButtonThemeDataToggleButtonsSwitchCheckboxRadioInputDecorationFloatingActionButtonChipCardPopupMenuButtonDialogTimePickerDialogSnackBarTooltipBottomSheetBottomNavigationBarNavigationBarNavigationRailAdded additional ColorScheme color selection options to component
sub-themes configuration class FlexSubThemesData. The feature
introduced in version 4.2.0 is now also supported by sub-themes for:
FloatingActionButton, via FlexSubThemesData.fabSchemeColor.TextButton, via FlexSubThemesData.textButtonColor.ElevatedButton, via FlexSubThemesData.elevatedButtonColor.OutlinedButton, via FlexSubThemesData.outlinedButtonColor.MaterialButton, via FlexSubThemesData.materialButtonColor.ToggleButtons, via FlexSubThemesData.toggleButtonsColor.Switch via FlexSubThemes.switchTheme.Checkbox via FlexSubThemes.checkboxTheme.Radio via FlexSubThemes.radioTheme.NavigationRail via FlexSubThemes.navigationRailTheme.DialogTheme and TimePickerThemeData
via FlexSubThemesData.dialogBackgroundColor. If used this property
overrides color property dialogBackground in all FlexColorScheme
constructors, factories and theme data extensions.AppBar background color, via the AppBar sub-theme definition is built into
the FlexColorScheme.toTheme method (legacy).
May migrate its implementation to own FlexSubThemes sub-theme later.TabBar for indicator and item color. The TabBar sub-theme definition
is currently built into the FlexColorScheme.toTheme method (legacy).
May migrate its implementation to own FlexSubThemes sub-theme later.Added a FlexKeyColors configuration class that can be used with
the FlexColorScheme.keyColors to enable and configure Material 3 based
key color based tonal palettes' generation that are then used to define
the ColorScheme. The tonal palettes are generated using existing
built-in or custom colors, as key colors for generating palettes.
The method matches the ColorScheme.fromSeed Flutter SDK
feature if you only use primary color as input. However, it also offers more
configuration and flexibility on how to use key colors as seed colors. It
does so without the need to go to lower API levels to produce custom tonal
palettes and use them manually in the ColorScheme definition. The
implementation makes it easy to use use a combination of key seeded colors and
fixed colors, in any combination, to produce the color scheme.
This makes using seeded colors an option for supplementary colors while e.g.
primary color is locked to a given brand or design color value, but
other colors in the ColorScheme are less critical, and it is more important
that they match the tone of the over all theme.
Added bool property useMaterial3ErrorColors to FlexColorScheme.light and
FlexColorScheme.dark. Set to true, to use the new Material 3 error colors,
instead of past Material2 based ones, which are still default. When using key
color seed generated [ColorScheme]s always use the Material 3 based error
colors.
Added custom tone configuration for seeded ColorScheme. M3 color design
has it own fixed defaults for which tone from the relevant TonalPalette
is used as input on each color property in the light and corresponding dark
ColorScheme. By configuring and passing in a FlexTones to tones in
FlexColorScheme.light and FlexColorScheme.dark it is possible
to control which color tone from the relevant TonalPalette is used for
each color property in generated ColorScheme.
Obviously making poor selections produces bad results, but there are some
tuning that works very well for different needs, e.g. primary could
be assigned a one step lower value in light mode, to produce seeded color
schemes that are more vivid or saturated.
The Material 3 based seeded ColorScheme also locks down the chroma level of
seed color for secondary colors to 16 and to 24 for tertiary colors, and keeps
it at min 48 for primary color. The FlexTones configuration makes it
possible to change these restrictions. You can then get more vivid tonal
palettes also for secondary and tertiary TonalPalettes. FlexTones has a
FlexTones.light and FlexTones.dark constructor that have default values
that gives the same result as using the hard coded ColorScheme.fromSeed
tone mapping and chroma limit behavior on TonalPalette. These constructors
are also convenient to use when making custom FlexTones setups. To show
how, it comes with four built in examples. They take a Brightness value
as input, and return FlexTones configs with different design goals suitable
for dark or light mode brightness themes. There is FlexTones.material, it is
an alternative Brightness input based API for FlexTones.light and
FlexTones.dark to get the default Material 3 design guide config.
In a similar fashion there are 3 alternative configurations.
FlexTones.soft, for even softer and more earthy tones than
M3 defaults, that are pretty soft and pastel like to begin with.FlexTones.vivid.FlexTones.highContrast.It is easy to make your own configs with the API. The setup of the these built-in examples shows how.
Added new alpha blend control blendOnLevel value for onColors to class
FlexSubThemesData. It is used to produce onColors for main colors that
can be adjusted and be more in-line with M3 seed color usage design by tuning
their blend level. Before, this was turned on via blendOnColors toggle
that will remain, but has a slightly modified new function.
The blendOnLevel introduces a new blend level value for onColor that is not
tied to used blend level on surfaces.
Defined matching color values for new FlexSchemeColor.secondaryContainer
and FlexSchemeColor.tertiaryContainer for all existing built-in
color schemes. This was surprisingly tedious task.
New color schemes: Added four new built-in color schemes. Total number of color schemes is now 40 matched light and dark pairs.
FlexScheme.flutterDash for easy access to it.FlexScheme.materialBaseline for easy access to it.FlexScheme.verdunHemlock for easy access to it.FlexScheme.dellGenoa for easy access to it.CHANGE
Added all the new ColorScheme M3 color properties to SchemeColor
enum and its static functions schemeColor and schemeColorPair.
Deprecated the enum values primaryVariant and secondaryVariant. These
deprecated enum values are still available, but return correct replacement M3
color values from the in Flutter 2.10.0 updated ColorScheme when using
functions schemeColor and schemeColorPair.
To class FlexColorScheme default constructor, light and
dark factories, added properties primaryContainer and
secondaryContainer. They replace deprecated properties primaryVariant
secondaryVariant. The old properties still work and are used as fallback to
the new ones, if the new ones are not provided.
The previous properties are still available as deprecated, and will remain
available until version 6.0.0.
In extension FlexThemeData to extensions FlexThemeData.light
and FlexThemeData.dark added properties primaryContainer and
secondaryContainer. They replace deprecated properties primaryVariant
secondaryVariant. The old properties still work and are used as fallback to
the new ones, if the new ones are not provided.
The previous properties are still available as deprecated, and will remain
available until version 6.0.0.
The opt-in, custom M3 TextTheme is now defined using the
new actual M3 TextStyle names available in Flutter 2.10.0. The change is
none breaking thanks to underlying implementation in Flutter SDK 2.10.0.
It now also includes the new styles headlineMedium and labelMedium that do
not directly map to any previous M2 text styles. Flutter SDK automatically
maps the new TextTheme and its TextStyles to corresponding M2 text style
names, so they work and can be used as before. This opt-in TextTheme includes
the new M3 typography (text size and letter spacing), for what presumably will
become EnglishLike2021 as Typography when it is included in Flutter.
This typography (font geometry) is not yet available in Flutter 2.10.0 and
was not even in master at the time when when Flutter 2.10.0 was released.
FlexColorScheme has included a EnglishLike2021 geometry since version
4.0.0, now it also uses the correct TextStyle names since they became
available in Flutter 2.10.0. The actual EnglishLike2021 will arrive in
the Flutter stable release after 2.10.x. The current custom version of it
will be removed then.
The feature of blendOnColors has changed design wise slightly, it is now
used as a toggle to indicate that on colors for the main colors,
that is onPrimary, onSecondary, onTertiary and onError should also receive
an alpha bland of its color pair, of strength blendOnLevel/2 when
blendOnColors is true. If blendOnColors is false, they use white or
black contrast color as appropriate for their main color pair. The
blending of onColor only occurs when their main color is not using seed
based ColorScheme based color value.
The darkIsTrueBlack option in FlexColorScheme.dark that makes and keeps
scaffold background fully black, now makes other blended surfaces 5% darker
instead of 8%, scaffold remains black.
The lightIsWhite option in FlexColorScheme.light that makes and keeps
scaffold background fully white, now makes other blended surfaces 5% lighter
instead of 8%, scaffold remains white.
The built-in description for FlexScheme.material was changed to
"Default Material 2 color theme, used in the design guide" from
"Default Material color theme, used in the design guide", to make it clear
it came from the M2 guide.
The built-in description for FlexScheme.materialHc was changed to
"High contrast Material 2 design guide theme" from
"High contrast Material design guide theme", to make it clear it came
from the M2 guide.
The order of the colors, in the rarely outside FlexColorScheme
used demo apps, theme presentation/switch button FlexThemeModeSwitch was
changed for better placement of new color primaryContainer and tertiary.
The Colors primaryVariant and secondaryVariant were removed from it
since the colors are deprecated in Flutter SDK. The change was from:
| Before | Before |
|---|---|
| Primary | Primary variant |
| Secondary | Secondary variant |
to:
| After | After |
|---|---|
| Primary | Secondary |
| Primary container | Tertiary |
FIXED
When using FlexSubThemesData.inputDecoratorSchemeColor the floating label
did not change to the selected ColorScheme based SchemeColor. Now it does,
it also keeps the correct error color behavior. Tricky bugger to define this
one by the way.
FIX TO MATCH M2 SPEC and STYLE BREAKING: In all previous versions
of FlexColorScheme, the Flutter
ThemeData.estimateBrightnessForColor was used to calculate if black or white
on color should be used on the error colors. In dark mode for the default
error FlexColor.materialDarkError and the high contrast dark mode error
color FlexColor.materialDarkErrorHc, this resulted in correctly computed
contrast color value white being used on them. Regardless of this the
Material 2 guide specifies and Flutter SDK uses the on color for these
colors as black. These two cases were added as special considerations
to return black color for these two particular cases, even if the Flutter
contrast color computation says it should be white, but M2 spec is black.
KNOWN ISSUES
FlexColorScheme.themedSystemNavigationBar. The
divider feature is disabled until the issue has been resolved. There is
also a temporary workaround implemented that attempts to keep system icon
brightness getting the wrong brightness on Android 11, it may not always
work.EXAMPLES and Themes Playground
Update examples 1...4
RaisedButton, OutlineButton and FlatButton in ALL the examples.
They are going away in next stable release of Flutter after 2.10.x, as
per this notice #98537.Update default example app, the Hot Reload Playground.
Major update for "example 5" the Themes Playground to include support for all the new features. Updates listed below:
ColorScheme.usedColors, it is an old
API in FlexColorScheme, it has just never been featured much.useMaterial3 toggle.FlexTones. Made some useful setups as preconfigured FlexTones, and the
playground uses demo. Now comes with FlexTones.material for the default
Material 3 design guide config, and FlexTones.soft, FlexTones.vivid,
FlexTones.vividSurfaces and FlexTones.highContrast as built-in
preconfigured options. It is easy to make own configs with the API.TonalPalette and sliders to adjust chroma. this could later be used to
create a custom FlexTones config and get it as part of setup code too.TESTS TODO
SchemeColor properties.FlexTones.FlexKeyColors.FlexCorePalette.FlexSubThemes.useMaterial3 property.FlexSubThemes and its config data
in FlexSubThemesData.primaryVariant and secondaryVariant properties.March 14, 2022
Version 5.0.0-dev.1 is a big refactor, with deprecation of previous variant based color names in favor of container ones that were added to updated Material-3 based ColorScheme in Flutter 2.10.0. The same additions and changes are now also introduced in FlexColorScheme. Despite being a big release, with many new features, actual breaking changes are very few and mostly concerns in version 4 deprecated members and, of course, requiring minimum Flutter 2.10.0 to work.
Deprecated: The property surfaceStyle has been deprecated. In version 4.0.0 it was already recommended to use, the then introduced more powerful surfa…
New: Updated required Dart SDK to minimum 2.15 that Flutter 2.8.0 uses.
To use this release at least Flutter 2.8.0 is required.
New: Added support for opinionated sub-theme for the new Material 3 based
NavigationBar. Flutter version 2.8.0 is the first stable version that
includes the new Material 3 design based NavigationBar.
Deprecated: The property surfaceStyle has been deprecated. In
version 4.0.0 it was already recommended to use, the then introduced more
powerful surface branding properties surfaceMode and blendLevel instead.
The surfaceStyle property is still available and works as before, but you
now get a deprecation warning if it is used. The property and all its related features
will be completely removed in version 5.0.
New: Custom FlexColorScheme based themes can now also be defined by
alternatively passing in a ColorScheme object to the colorScheme
property in default the constructor, as well as in FlexColorScheme.light and
FlexColorScheme.dark factories. When used it overrides the scheme and
colors properties in the factories. Same color property in any constructor
that exist as direct property in the constructors, still have the highest
priority and will also override corresponding color properties in passed in
colorScheme. The capability to make custom FlexColorScheme based themes from
standard Flutter color schemes is useful if you already have a predefined
elaborate ColorScheme definition. You can now use it directly and still
use FlexColorScheme for its surface color branding and easy sub-theming.
This capability will also be very useful when Material 3 based ColorScheme
in Flutter SDK arrives in the stable channel. With Material 3, color schemes
may be created using new Material 3 design based color tools, e.g. from
seed color(s) or using dynamic colors extracted from system wallpaper colors.
With this feature it will then be able to feed those colors directly into
FlexColorScheme, and use them as colors to create your ThemeData.
Changed: All properties in all FlexColorScheme constructors are now
optional. The change is none breaking, and uses Material 2 based
design guide example theme light and dark as defaults for undefined values.
New: Added a ColorScheme color selection option to selected opinionated
sub-themes configuration class FlexSubThemesData. The sub-themes that
support changing their ColorScheme based
used theme color selection, have one or more properties called
nnnSchemeColor where nnn describes the color feature that can be set
to an alternative ColorScheme based color and not just its pre-defined
ColorScheme based color property.
The color selector is a SchemeColor enum property value that is used to
select the enum value that corresponds to same named color
property value in theme.colorScheme. This SchemeColor color quick
selection option has been added to:
TextField via FlexSubThemes.inputDecorationTheme to select a
base color for the border and fill color.TabBar sub-theming to select its indicator color, when you want it to be a
different color than the color of the TabBar icon and text, which are
controlled via FlexTabBarStyle in the FlexColorScheme.tabBarStyle
property as before. It gives you an easy option to override the indicator
color with any of the theme's colorScheme colors.BottomNavigationBar via FlexSubThemes.bottomNavigationBar to set the
preferred color of the icon and label text in the Material 2 based
BottomNavigationBar, as well as used container background color.NavigationBar in FlexSubThemes.navigationBarTheme to set the
preferred ColorScheme color of the text, icon in the Material 3 based
NavigationBar, as well as the pill shaped highlight color separately that
surrounds the selected icon and its container background color.ChipThemeData from FlexSubThemes.chipTheme to change the used
ColorScheme based base color of Chips.The SchemeColor properties for the above sub-themes have a default selection
that results in same ColorScheme color values being used as they had
before. The additional configuration options are none breaking. The enum
properties to modify the used ColorScheme color can be defined in the
configuration class FlexSubThemesData using its new properties:
inputDecoratorSchemeColorchipSchemeColortabBarIndicatorSchemeColorbottomNavigationBarUsedColorbottomNavigationBarSchemeColorbottomNavigationBarBackgroundSchemeColornavigationBarIconSchemeColornavigationBarTextSchemeColornavigationBarHighlightSchemeColornavigationBarBackgroundSchemeColorUsage examples of the above new configuration possibilities have been added to the default example, the so-called developers hot reload playground.
The ColorScheme color selection in SchemeColor includes all colors in
ColorScheme supported by Flutter 2.8. You may want to avoid using the
primaryVariant and secondaryVariant colors if you want to avoid later
migrations. These variant colors are being deprecated in Flutter SDK,
see #93427.
A later FlexColorScheme version will add support for the new Material 3
colors in ColorScheme when they land in the stable channel.
This quick selection of ColorScheme based colors as none standard themed
colors of widget sub-themes, may be extended to a few more sub-themes in
future versions. At least if it is seen as a practical and quick way to
customize widget sub-theme colors within the constraints of colors in
the theme.colorScheme.
As before you can still apply your own total custom sub-themes to the
ThemeData created with FlexColorScheme by using copyWith.
FlexColorScheme is a way to easily make fancy and color wise consistent and
balanced ThemeData objects using convenience shortcut properties and
methods. It does not prevent you from further modifying and tuning the
produced ThemeData with standard Flutter SDK features.
Removed: The uses-material-design: true line from library
pubspec.yaml file was removed. It is not needed since Material icon
features are not used by this package.
Example 5 - Themes Playground
Example theme - Copy Playground Theme
Documentation: Reviewed and corrected many API docs. The API docs are very thorough and complete. They usually cover any question you might have and more. Added a brief "API Intro and Guide" chapter to the readme.
Tests: Added tests to cover the new features, now total 1123 tests.
Documentation: Fixed a broken link in the readme that pub.dev analyser found.
November 20, 2021
FIX DOCS
Fix: The defaultRadius in FlexSubThemesData now defaults to null so all sub-themes border radius will default to M3 default border radius per widget.
Fix: The defaultRadius in FlexSubThemesData now defaults to null
so all sub-themes border radius will default to M3 default border
radius per widget. The const default value it had was a remnant from early
dev phase when widgets all defaulted to single shared radius and not M3
defaults per widget type. If you explicitly passed in null, you did also in
previous version get the M3 defaults. Older tests did that, now they expect
same result when no value is assigned, as it should have been.
Examples: Updated and tuned the examples. Example 5 "Themes Playground" now includes capability to define custom color schemes starting from built-in ones. It can also generate the FlexColorScheme setup code needed for any defined viewed theme setup. You can copy/paste a theme's Flutter Dart code, from the Themes Playground to your app and use it as its theme. This is a very quick and convenient way to try a theme you made and see in the Themes Playground in your own app.
Opt in opinionated sub themes minor style changes:
SnackBarThemeData when
using opt in opinionated sub themes.caption got a bit
of opacity. M2 designed widgets like ListTile, depend on it for
making more muted subtitles by default for ListTile via the heading level
opacity on caption text style. The opacity on it is lower though, to
retain a bit more contrast on blended surfaces, while still adhering to
the style intent.
Minor details on the opinionated sub themes may still be tuned and changed slightly as a part of improving them and their appeal. For the text theme coloring future version may expose parameter(s) that can be used to adjust the color tint effect on text theme when colored text theme is enabled.
Major updates to readme doc, and typo corrections.
Tests:
defaultRadius issue.November 20, 2021
FIX
defaultRadius in FlexSubThemesData now defaults to null,
component themes border radius will then default to Material-3 default border
radius per widget. The const default value it had before was a remnant from early
dev phase when widgets all defaulted to single shared radius and not Material-3
defaults per widget type. If you explicitly passed in null, you did also in
previous versions get the Material-3 defaults. Older tests did that, but now they expect
the same result when no value is assigned, as it should have been.CHANGE
Opt in opinionated component themes minor style changes:
Added missing themed background color for SnackBarThemeData when
using opt in opinionated component themes.
Tuned the colored text theme on the component themes that are applied when
using the optional colored text themes. The text styles now better match
the regular none-colored style,
and they are a bit more subtle. Text style caption got a bit
of opacity. Material-2 designed widgets like ListTile, depend on it for
making more muted subtitles by default for ListTile via the heading level
opacity on caption text style. The opacity on it is lower though, to
retain a bit more contrast on blended surfaces, while still adhering to
the style intent.
Major updates to readme doc, and typo corrections.
EXAMPLES
TESTS
defaultRadius issue.The surface color blend style surfaceStyle is still default, and not yet deprecated, but may be so in later versions. It is not really needed anymore,…
The new V4 docs are still a bit lacking and will be improved in docs updates later.
The breaking case is a minor difference in produced style for true black mode. Version 4.0.0 is still fully API compatible with version 3. Version 4.0.0 does however contain so many new features, that it in itself warrants a new major release bump.
Breaking: In dark mode, the darkIsTrueBlack now makes surface color
8% darker instead of 6%. This change was needed to support overlay color
in dark mode when using darkIsTrueBlack when using the new surfaceMode
property. For more information see Flutter SDK
issue 90353.
Fix/Breaking: From the color scheme English descriptions the sentence end "." was removed from all description strings. If and when you want one, you can add it as needed.
New: Added a more flexible and powerful alpha blending feature for
surface and background colors. The new properties in the FlexColorScheme
factories light and dark are surfaceMode, of type enum FlexSurfaceMode
and integer blendLevel. Consider using them instead of previous
surfaceStyle.
The surface color blend style surfaceStyle is still default, and not yet
deprecated, but may be so in later versions. It is not really needed anymore,
but there was no major reason to break things by removing it either.
New: Major new feature; easy sub-theming of Flutter SDK UI widgets.
FlexColorScheme.useSubThemes to true, it is false by default.FlexSubThemesData class, passed to
FlexColorScheme.subThemesData.FlexSubThemesData class provides parameters for easy adjustment
of corner radius in Widgets that use ShapeBorder or decorations, that
support changing the Widget's corner radius. With the sub themes enabled, you
can easily create a theme with a consistent corner radius on built-in
Flutter SDK UI widgets.ToggleButtons
to match the standard buttons regarding size and design as far as possible.ButtonThemeData that as far as possible match the same style.New: Added FlexThemeData static extension on ThemeData.
FlexThemeData.light and FlexThemeData.dark, instead of using
FlexColorScheme.light().toTheme and FlexColorScheme.dark().toTheme.toTheme method is still available and works as before. It will not
be deprecated. It is needed when making elaborate custom sub themes beyond
what is offered when using FlexColorScheme based opt-in sub themes. When
you make custom sub themes yourself, you often need access to
the ColorScheme that is defined in current FlexColorScheme() instance.
You can get it with FlexColorScheme().toScheme. Then use this
this standard ColorScheme or any of its colors, in your custom sub theme
definitions, that you then add with copyWith to your FlexColorScheme based
theme, like FlexColorScheme().toTheme.copyWith(..."your sub themes and other ThemeData over-rides here").New: Added textTheme and primaryTextTheme properties to
FlexColorScheme to enable easy setup of custom TextThemes, without the
need to add a custom TextTheme via a copyWith, plus merge with the
default text theme.
New: Added FlexColorScheme.dialogBackground as a background surface
color that can be controlled and themed separately.
New: Added appBarOpacity to FlexColorScheme.light() and dark().
With it, you can apply themed opacity to the AppBar background color to
the selected FlexAppBarStyle it is using.
New: On the FlexColorScheme factories light and dark, exposed
the Color properties primary, primaryVariant, secondary,
sedondaryVariant, appBarBackground, dialogBackground and error.
They all default to null, but if provided they can be used as override values
to factory behaviors defined by scheme, colors, appBarStyle,
surfaceMode and surfaceStyle that
otherwise via the factories define the colors for these properties. If a value
for one of the new direct color properties is used with the factory, it always
has precedence over other properties that assign or compute colors for it.
New: Exposed boolean property applyElevationOverlayColor. It has the same
function as the same property in ThemeData. It applies a semi-transparent
overlay color on Material surfaces to indicate elevation for dark themes.
In FlexColorScheme it defaults to true. In Flutter ThemeData.from it
also default to true, but in ThemeData it defaults to false.
The property is just available for convenience, so you can avoid a copyWith
if you wish to turn it off. It is not necessarily needed or even desired when
using strong alpha blends on surfaces in dark mode, to use an elevation
overlay color.
New: All FlexSchemeData objects in FlexColor are exposed as static
const objects, making them easy to pick and reuse as const objects
individually in custom color scheme lists, or as input to the colors
property. Previously only the individual color value definitions were exposed.
New: Added convenience extension .blendAlpha() on Color
in FlexColorExtensions.
New: The FlexThemeModeSwitch got a bool property hasTitle, if set
to false it removes the title entirely.
New: The FlexThemeModeSwitch got a buttonOrder property using enum
FlexThemeModeButtonOrder that you can use to define the order of its
light, system and dark theme mode buttons, in all possible combinations.
New: Added edgeToEdge support to
FlexColorScheme.themedSystemNavigationBar. This brings the previously
experimental support for transparent system navigation bar in Android
into the supported fold in FlexColorScheme. Its functionality
requires min Android SDK level 29, but other than that it works without
Android setup shenanigans. No added APIs, the API for it already existed
in previous version of FlexColorScheme, using it did however require
special Android build configuration setup, this is no longer required.
Change: The FlexColor.schemesList is now a const for improved
efficiency.
New color schemes: Added four new built-in color schemes. Total number of color schemes is now 36 matched light and dark pairs.
FlexScheme.blueWhale for easy access to it.
This theme is final and selected for inclusion as a new one.FlexScheme.sanJuanBlue for easy access to it.FlexScheme.rosewood for easy access to it.FlexScheme.blumineBlue for easy access to it.Documentation:
FlexThemeData extension syntax to create the
ThemeData and surfaceMode to define the alpha blended surfaces.Tests:
November 13, 2021
The breaking case is a minor difference in produced style for true black mode. Version 4.0.0 is still fully API compatible with version 3. Version 4.0.0 does, however, contain so many new features that it in itself warrants a new major release bump.
BREAKING
In dark mode, the darkIsTrueBlack now makes surface color
8% darker instead of 6%. This change was required to support overlay color
in dark mode when using darkIsTrueBlack when using the new surfaceMode
property. For more information, see Flutter SDK
issue 90353.
From all the color scheme English descriptions, the sentence ending period was removed from all description strings. If and when you want one, you can add it as needed.
NEW
Added a more flexible and powerful alpha blending feature for
surface and background colors. The new properties in the FlexColorScheme
factories light and dark are surfaceMode, of type enum FlexSurfaceMode
and integer blendLevel. Consider using them instead of previous
surfaceStyle.
The surface color blend style surfaceStyle is still default, and not yet
deprecated, but may be so in version 5. It is not required anymore,
but there was no major reason to break things by removing it either.
Major new feature, easy sub-theming of Flutter SDK UI widgets.
FlexColorScheme.useSubThemes to true, it is false by default.FlexSubThemesData class, passed to
FlexColorScheme.subThemesData.FlexSubThemesData class provides parameters for easy adjustment
of corner radius in Widgets that use ShapeBorder or decorations, that
support changing the Widget's corner radius. With the component themes enabled, you
can create a theme with a consistent corner radius on built-in
Flutter SDK UI widgets.ToggleButtons
to match the standard buttons regarding size and design as far as possible.ButtonThemeData that as far as possible match the same style.Added FlexThemeData static extension on ThemeData.
FlexThemeData.light and FlexThemeData.dark, instead of using
FlexColorScheme.light().toTheme and FlexColorScheme.dark().toTheme.toTheme method is still available and works as before. It will not
be deprecated. It is required when making elaborate custom component themes beyond
what is offered when using FlexColorScheme based opt-in component themes. When
you make custom component themes yourself, you often need access to
the ColorScheme that is defined in current FlexColorScheme() instance.
You can get it with FlexColorScheme().toScheme. Then use this
standard ColorScheme or any of its colors, in your custom component theme
definitions, that you then add with copyWith to your FlexColorScheme based
theme, like FlexColorScheme().toTheme.copyWith(..."your sub themes and other ThemeData over-rides here").Added textTheme and primaryTextTheme properties to
FlexColorScheme to enable easy setup of custom TextThemes, without the
need to add a custom TextTheme via a copyWith, plus merge with the
default text theme.
Added FlexColorScheme.dialogBackground as a background surface
color that can be controlled and themed separately.
Added appBarOpacity to FlexColorScheme.light() and dark().
With it, you can apply themed opacity to the AppBar background color to
the selected FlexAppBarStyle it is using.
On the FlexColorScheme factories light and dark, exposed
the Color properties primary, primaryVariant, secondary,
secondaryVariant, appBarBackground, dialogBackground and error.
They all default to null, but if provided they can be used as override values
to factory behaviors defined by scheme, colors, appBarStyle,
surfaceMode and surfaceStyle that
otherwise via the factories define the colors for these properties. If a value
for one of the new direct color properties is used with the factory, it always
has precedence over other properties that assign or compute colors for it.
Exposed boolean property applyElevationOverlayColor. It has the same
function as the same property in ThemeData. It applies a semi-transparent
overlay color on Material surfaces to indicate elevation for dark themes.
In FlexColorScheme it defaults to true. In Flutter ThemeData.from it
also default to true, but in ThemeData it defaults to false.
The property is just available for convenience, so you can avoid a copyWith
if you wish to turn it off. It is not required or even desired when
using strong alpha blends on surfaces in dark mode, to use an elevation
overlay color.
All FlexSchemeData objects in FlexColor are exposed as static
const objects, making them easy to pick and reuse as const objects
individually in custom color scheme lists, or as input to the colors
property. Previously, only the individual color value definitions were exposed.
Added convenience extension .blendAlpha() on Color
in FlexColorExtensions.
The FlexThemeModeSwitch got a bool property hasTitle, if set
to false it removes the title entirely.
The FlexThemeModeSwitch got a buttonOrder property using enum
FlexThemeModeButtonOrder that you can use to define the order of its
light, system and dark theme mode buttons, in all possible combinations.
Added edgeToEdge support to
FlexColorScheme.themedSystemNavigationBar. This brings the previously
experimental support for transparent system navigation bar in Android
into the supported fold in FlexColorScheme. Its functionality
requires min Android SDK level 29, but other than that, it works without
Android setup shenanigans. No added APIs, the API for it already existed
in the previous version of FlexColorScheme, using it did, however, require
special Android build configuration setup. This is no longer required.
New color schemes: Added four new built-in color schemes. The total number of color schemes is now 36 matched light and dark theme pairs.
FlexScheme.blueWhale for easy access to it. This theme is final and selected for inclusion as a new one.FlexScheme.sanJuanBlue for easy access to it.FlexScheme.rosewood for easy access to it.FlexScheme.blumineBlue for easy access to it.CHANGE
FlexColor.schemesList is now a const for improved efficiency.DOCS
FlexThemeData extension syntax to create the ThemeData and surfaceMode to define the alpha blended surfaces.TESTS
The surface color blend style surfaceStyle is still default, and not yet deprecated, but may be so in later versions. It is not really needed anymore,…
The breaking case refer to a minor difference in produced style for true black mode. Version 4.0.0 is still fully API compatible with version 3. Major version was bumped due to the small change in produced output in some rare usage options. Version 4.0.0 does however contain so many new features, that it in itself warrants a new major release bump.
Breaking: In dark mode, the darkIsTrueBlack now makes surface color
8% darker instead of 6%. This change was needed to support overlay color
in dark mode when using darkIsTrueBlack when using the new surfaceMode
property. For more information see Flutter SDK
issue 90353.
Fix/Breaking: From the color scheme English descriptions the sentence end "." was removed from all description strings. If and when you want one, you can add it as needed.
New: Added a more flexible and powerful alpha blending feature for
surface and background colors. The new properties in the FlexColorScheme
factories light and dark are surfaceMode, of type enum FlexSurfaceMode
and integer blendLevel. Consider using them instead of previous
surfaceStyle.
The surface color blend style surfaceStyle is still default, and not yet
deprecated, but may be so in later versions. It is not really needed anymore,
but there was no major reason to break things by removing it either.
New: Major new feature; easy sub-theming of Flutter SDK UI widgets.
FlexColorScheme.useSubThemes to true, it is false by default.FlexSubThemesData class, passed to
FlexColorScheme.subThemesData.FlexSubThemesData class provides parameters for easy adjustment
of corner radius in Widgets that use ShapeBorder or decorations, that
support changing the Widget's corner radius. With the sub themes enabled, you
can easily create a theme with a consistent corner radius on built-in
Flutter SDK UI widgets.ToggleButtons
to match the standard buttons regarding size and design as far as possible.ButtonThemeData that as far as possible match the same style.New: Added FlexThemeData static extension on ThemeData.
FlexThemeData.light and FlexThemeData.dark, instead of using
FlexColorScheme.light().toTheme and FlexColorScheme.dark().toTheme.toTheme method is still available and works as before. It will not
be deprecated. It is needed when making elaborate custom sub themes beyond
what is offered when using FlexColorScheme based opt-in sub themes. When
you make custom sub themes yourself, you often need access to
the ColorScheme that is defined in current FlexColorScheme() instance.
You can get it with FlexColorScheme().toScheme. Then use this
this standard ColorScheme or any of its colors, in your custom sub theme
definitions, that you then add with copyWith to your FlexColorScheme based
theme, like FlexColorScheme().toTheme.copyWith(..."your sub themes and other ThemeData over-rides here").New: Added textTheme and primaryTextTheme properties to
FlexColorScheme to enable easy setup of custom TextThemes, without the
need to add a custom TextTheme via a copyWith, plus merge with the
default text theme.
New: Added FlexColorScheme.dialogBackground as a background surface
color that can be controlled and themed separately.
New: Added appBarOpacity to FlexColorScheme.light() and dark().
With it, you can apply themed opacity to the AppBar background color to
the selected FlexAppBarStyle it is using.
New: On the FlexColorScheme factories light and dark, exposed
the Color properties primary, primaryVariant, secondary,
sedondaryVariant, appBarBackground, dialogBackground and error.
They all default to null, but if provided they can be used as override values
to factory behaviors defined by scheme, colors, appBarStyle,
surfaceMode and surfaceStyle that
otherwise via the factories define the colors for these properties. If a value
for one of the new direct color properties is used with the factory, it always
has precedence over other properties that assign or compute colors for it.
New: Exposed boolean property applyElevationOverlayColor. It has the same
function as the same property in ThemeData. It applies a semi-transparent
overlay color on Material surfaces to indicate elevation for dark themes.
In FlexColorScheme it defaults to true. In Flutter ThemeData.from it
also default to true, but in ThemeData it defaults to false.
The property is just available for convenience, so you can avoid a copyWith
if you wish to turn it off. It is not necessarily needed or even desired when
using strong alpha blends on surfaces in dark mode, to use an elevation
overlay color.
New: All FlexSchemeData objects in FlexColor are exposed as static
const objects, making them easy to pick and reuse as const objects
individually in custom color scheme lists, or as input to the colors
property. Previously only the individual color value definitions were exposed.
New: Added convenience extension .blendAlpha() on Color
in FlexColorExtensions.
New: The FlexThemeModeSwitch got a bool property hasTitle, if set
to false it removes the title entirely.
New: The FlexThemeModeSwitch got a buttonOrder property using enum
FlexThemeModeButtonOrder that you can use to define the order of its
light, system and dark theme mode buttons, in all possible combinations.
New: Added edgeToEdge support to
FlexColorScheme.themedSystemNavigationBar. This brings the previously
experimental support for transparent system navigation bar in Android
into the supported fold in FlexColorScheme. Its functionality
requires min Android SDK level 29, but other than that it works without
Android setup shenanigans. No added APIs, the API for it already existed
in previous version of FlexColorScheme, using it did however require
special Android build configuration setup, this is no longer required.
Change: The FlexColor.schemesList is now a const for improved
efficiency.
New color schemes: Added four new built-in color schemes. Total number of color schemes is now 36 matched light and dark pairs.
FlexScheme.blueWhale for easy access to it.
This theme is final and selected for inclusion as a new one.FlexScheme.sanJuanBlue for easy access to it.FlexScheme.rosewood for easy access to it.FlexScheme.blumineBlue for easy access to it.Documentation:
FlexThemeData extension syntax to create the
ThemeData and surfaceMode to define the alpha blended surfaces.TODO Documentation:
TODO Tests:
Fix: The internal order of swapping primary and secondary colors and reducing used colors in static function FlexSchemeColor.effective(FlexSchemeColor
FlexSchemeColor.effective(FlexSchemeColor colors, int usedColors, {bool swapColors = false}) matters for the intended result when
used together in the same call. The function now swaps primary and secondary colors,
before reducing the used colors.Its usage does however no longer have impact on produced themes, this is a potential breaking change. The probability that you might have used it as a…
Breaking: The color accentColor is being deprecated in Flutter SDK ThemeData starting
from version v2.3.0-0.1.pre.
Usage of accentColor in FlexColorScheme is removed to support this
transition. The property is deprecated in FlexColorScheme, but is still present. Its
usage does however no longer have impact on produced themes, this is a potential breaking change.
The probability that you might have used it as a property in your
FlexColorScheme based theme is low. It was set before to primary color
in FlexColorScheme, as a way to make the highlight color of outlines and underlines on
text field boxes primary colored in dark theme mode, and not secondary/accent colored as they used
to bve in Flutter's default dark theme mode. The old accentColor was
not used for anything else in themes anymore when using FlexColorScheme.
The property is now going away totally
in Flutter SDK. The default ThemeData in Flutter SDK in dark mode now creates a
theme for outline and underline indicators on input fields that are based on primary color,
just like FlexColorScheme does and already did before. Flutter SDK no longer uses
accentColor for it. The resulting default dark mode style on text fields thus now remain
unchanged in FlexColorScheme even with this definition removed. If you
had used accentColor in FlexColorScheme as a short-cut to define a different text field
outline or underline highlight color in dark theme mode than primary color, then you will need to
recreate it via text field decoration theming.
New: The FlexColorScheme.dark and FlexColorScheme.light factories have a new
property called swapColors. If true, this will swap primary and primaryVariant
colors with their secondary counter-parts.
This flag can be set to true if you want to make a theme where your primary and secondary colors are swapped compared to their definition. It is useful if you want to quickly swap primary and secondary colors when using the pre-defined color schemes or with computed dark schemes from light schemes. It doubles the variation possibilities of themes based on the pre-defined color schemes.
If you are explicitly defining all you light or dark scheme colors, you can of course define them in desired order. This feature will still swap whatever colors you defined for primary and secondary when set to true. You can thus also use this feature as an easy end-user modifiable theme option, if you like to offer the capability to toggle the primary and secondary theme colors the other way around.
New: The static function FlexSchemeColor.effective(FlexSchemeColor colors, int usedColors, {bool swapColors = false}) is used to implement the above
swapColors feature. It also exposes the logic behind the FlexColorScheme
dark and light theme usedColors property. This static method is helpful if
you need to compute effective built-in theme colors externally to FlexColorScheme
to present the active theme, based on these settings. This is used by example 5
to change the colors on the theme mode switch when the swap color settings
is toggled. The usedColors property is not shown in any bundled
example, but it can be used the same way.
New color schemes: Added four new built-in color schemes.
FlexScheme.bahamaBlue for easy access to it.FlexScheme.mallardGreen for easy access to it.FlexScheme.espresso for easy access to it.FlexScheme.outerSpace for easy access to it.Inspired by MaterialYou at GoogleIO 2021, I recently hooked up FlexColorScheme with an algorithm that extracts prominent colors from images. Then fed these colors to FlexColorScheme to make themes from them. The above new color schemes in release 3.0.0 came from these image based theme experiments. You can see examples of FlexColorScheme making color schemes and themes from images in my Tweets about it. This was a first quick test of the idea, later I added some more features to it, here and here. This quick test shows that FlexColorScheme is very versatile.
Tests: Added tests for the new features and removed test related to accentColor. Total 736 tests, coverage 99.76%.
Change: Made the VoidCallback onSelect in FlexThemeModeOptionButton nullable. The optional callback allows for the button to be used e.g. as a trailin
onSelect in FlexThemeModeOptionButton nullable.
The optional callback allows for the button to be used e.g. as a trailing
widget in a ListTile. Keep it null to not have any callback, nor hover or Ink of its own, and use
the select event of the parent instead. When it is used as standalone button you
normally want to use this callback, but not if you want the parent to handle it, that use case was
not allowed with previous version.Fix: Toggling FlexColorScheme(transparentStatusBar) from true to false, did not restore the Android default status bar scrim, unless the app was compl
FlexColorScheme(transparentStatusBar) from true to false, did not restore the
Android default status bar scrim, unless the app was completely rebuilt. This has been fixed.FlexColorScheme.themedSystemNavigationBar(useDivider) in an AnnotatedRegion, toggling
useDivider from true to false, did not remove the system navigation bar divider again, unless the
app was completely rebuilt. This has been fixed, see API docs for more info.FlexColorScheme.themedSystemNavigationBar for styling the system navigation bar got a
new convenience property systemNavBarStyle that takes a FlexSystemNavBarStyle enum with values:
system: For default white system nav bar in light theme and black in dark theme mode.surface: The system navigation bar will be the same color as active theme colorScheme.surface color.
If your FlexColorScheme definition is set to use primary branded surface and background colors, the
same primary color blend that the surface color has received will be used.background: The system navigation bar will be the same color as active theme colorScheme.background color.
If your FlexColorScheme definition is set to use primary branded surface and background colors, the
same primary color blend that the background color has received will be used.scaffoldBackground: The system navigation bar will be the same color as active theme scaffoldBackground color.
If your FlexColorScheme definition is set to use primary branded surface and background colors, the
same primary color blend that the scaffoldBackground color has received will be used.transparent: An experimental feature. The goal is to make the system navigation bar fully transparent,
showing the background, while navigation buttons float over the background. This feature only works if it is
also configured in the Android embedder and on SDK 30 or higher.
More information in this example: https://github.com/rydmike/sysnavbarFirst stable release of FlexColorScheme with sound null safety.
FlexColorScheme.themedSystemNavigationBar has been
revised to be disabled by default. To use a divider on the top of the system navigation bar on Android,
you have to enabled it manually. This is more in line with expected default behavior.March 15, 2021 * Changes
March 15, 2021
February 4, 2021 * Changes
February 4, 2021
Added four new built-in color schemes.
Added four new built-in color schemes.
FlexScheme.barossa for easy access to it.FlexScheme.shark for easy access to it.FlexScheme.bigStone for easy access to it.FlexScheme.damask for easy access to it.Improved Semantics for the ThemeMode Widget buttons.
Improved FlexThemeModeSwitch widget tests, makes and checks for system mode changes.
More tests, totally 723 tests, codecov is now > 99.5%.
Added GitHub actions to automate build and to publish the examples on the Web on a new release.
Minor changes to the examples. Modified to not need the late keyword when they are converted
to null safe versions.
Documentation:
Added more tests, now 689 tests. All color values used are now also tested, any modification to them is considered a breaking change. A bit more tests…
scheme to FlexColorScheme factories light and dark. This a shortcut for using the built-in color schemes. The colors property can still be used as before. The .light and .dark factories no longer have any required properties. If scheme is not provided it defaults to FlexScheme.material and if both scheme and colors are provided, the scheme provided via colors prevail.scheme property, as in theme: FlexColorScheme.light(scheme: FlexScheme.mandyRed).toTheme.opacity property in FlexColorScheme.themedSystemNavigationBar.scheme property when using built-in schemes.Marked FlexSchemeSurfaceColors.themeSurface as deprecated in favor of the correctly named FlexSchemeSurfaceColors.surfaceStyle version. The older them…
FlexSchemeSurfaceColors.themeSurface as deprecated in favor of the correctly named
FlexSchemeSurfaceColors.surfaceStyle version. The older themeSurface will be removed when
null safe Version 2.0.0 is officially released as the main version.Diagnosticable mixin to classes FlexSchemeOnColors, FlexSchemeSurfaceColors and FlexColorScheme,
that all also received proper identity overrides and copyWith methods.Added four new built-in color schemes.
Added four new built-in color schemes.
FlexScheme.amber for easy access to it.FlexScheme.vesuviusBurn for easy access to it.FlexScheme.deepPurple for easy access to it.FlexScheme.ebonyClay for easy access to it.Added a style option for the tab bar. The FlexColorScheme created tab bar theme now defaults to a
TabBarTheme that fits its created AppBarTheme, also works via the factory app bar style options. There is also
an optional style that makes the tab bar theme suitable for surface and background colors. This was the
default style before. The change to this default style is a fix to make the default TabBarTheme one that
fits on app bar's instead, which is expected default behavior in Flutter and Material design.
The style is set via the FlexColorScheme property tabBarStyle using enum values FlexTabBarStyle.forAppBar
(default) and FlexTabBarStyle.forBackground.
The themed AppBar and BottomAppBar elevations still default to 0. However, and for convenience, the themed values
can now both be modified directly via the FlexColorScheme properties appBarElevation and bottomAppBarElevation,
without need to change these frequently modified values with an extra copyWith to get them re-themed as desired.
When using the recommended FlexColorScheme.light and FlexColorScheme.dark factories, appBarElevation
defaults to '0', if not defined and bottomAppBarElevation defaults to appBarElevation, if not defined.
When using the default constructor (the factories are recommended), they both default to '0'.
Example updates
Updated example 5 to include UI that can be used to vary the computed dark themes white blend percentage level. This was added to better demonstrate t
toDark feature.defaultError fix/modifier that enables the built-in schemes to use the Material design guide's default dark
error color when using the toDark method to compute a dark scheme from a light scheme, that already defines a light
scheme error color. The toDark method can be used without the defaultError scheme modifier as well, but then the
dark error color also change with the other computed dark scheme colors when using the "Compute dark theme" feature
and the level adjustment. This is not necessarily the desired behavior. The fix enables the alternative more often
desired behavior and ensures that the dark error color just uses the default value. For custom schemes that do not
specify a custom error color for their light scheme and thus default to the Material Guide's standard error color,
the fix is not needed. Example 5 demonstrates the use case of defaultError as well.Added API to make a matching dark scheme from a light scheme. See FlexSchemeColor.toDark.
false, to exclude the system setting based theme mode option.FlexColorScheme.comfortablePlatformDensity as their visualDensity
setting. The Flutter default compact mode for desktop and web goes a bit overboard in its compactness. This
optional setting presents an alternative where comfortable density is used on desktops and Web, while devices keep
their standard visual density. Just omit the setting if you prefer Flutter's super compact Web and Desktop widgets.toDark method. Example 4 also includes a sub-page that can be opened to see the same theme on a new page.toDark option, so it can be
toggled and compared to the hand-tuned versions. The same custom color scheme as in example 4 are also included.
Example 5 also has the same sub-page as example 4. Example 5 now also show how to solve the issue that the system
navigation bar does not get color scheme and theme mode appropriate system navigation bar style in Android as we
change the color scheme and theme mode. This is done with an AnnotatedRegion and the new helper
method FlexColorScheme.themedSystemNavigationBar.Documentation layout updates and typo corrections.
December 21, 2020
DOCS
Removed legacy usage of deprecated ThemeData properties textSelectionColor, cursorColor and textSelectionHandleColor. They are no longer needed even f…
First development pre-release on pub.dev.
December 17, 2020
3.24k
likes
160
points
139k
downloads
Documentation
API reference
rydmike.com
A Flutter package to use and make beautiful Material design based themes.
Homepage
Repository (GitHub)
View/report issues
Contributing
#theme #colorscheme #material3 #color #materialdesign
BSD-3-Clause ( license )
cupertino_ui , flex_seed_scheme , flutter , material_ui , meta
Packages that depend on flex_color_scheme
3.24k
likes
160
points
139k
downloads
Documentation
API reference
rydmike.com
A Flutter package to use and make beautiful Material design based themes.
Homepage
Repository (GitHub)
View/report issues
Contributing
#theme #colorscheme #material3 #color #materialdesign
BSD-3-Clause ( license )
cupertino_ui , flex_seed_scheme , flutter , material_ui , meta
Packages that depend on flex_color_scheme
Back
One column per quarter.