Fornecedor de tema fácil de usar e personalizável. Este widget pode ser usado para fornecer facilmente um controlador de tema em toda a árvore de widgets.
Orientação gerada a partir de informações públicas. Apenas para referência.
O Theme Provider é um pacote leve e personalizável que simplifica a gestão de temas em aplicativos Flutter. Permite compartilhar facilmente um controlador de tema em toda a árvore de widgets, suportando alternância suave entre modo claro e escuro. Com configuração mínima, os desenvolvedores podem definir e aplicar temas globalmente, tornando-o ideal para aplicativos que exigem temas dinâmicos. O pacote se integra perfeitamente ao sistema de compilação do Flutter e oferece suporte a todas as principais plataformas.
Casos de uso
Alternância dinâmica de temas
Implementação de modo claro e escuro
Gerenciamento de tema global
Criação de tema personalizado
Temas multiplataforma
Principais recursos
Compartilhamento fácil de controlador de tema
Suporta modos claro e escuro
Altamente personalizável
Mínimo boilerplate
Compatibilidade multiplataforma
Indicado para
Aplicativos que precisam de persistência de tema
Desenvolvedores procurando temas simples
Projetos com múltiplos temas
aplicações com foco em UI
Iniciantes do Flutter aprendendo temas
Considerações
Requer gerenciamento manual do estado do tema
Predefinições de tema embutidas limitadas
Nenhuma persistência automática de tema fora da caixa
Depende da lógica de tema definida pelo usuário
Não otimizado para hierarquias de tema complexas
README original
Snapshot do README original do repositório-fonte vinculado. Consulte o repositório para o conteúdo mais recente.
theme_provider
Easy to use, customizable Theme Provider. This provides app color schemes throughout the app and automatically rebuilds the UI dynamically.
You can also persist your color theme as well. Easily store and retrieve user preference without hassle.
This package also provides you with several widgets that can help you to easily add theme switching abilities.
Additionally you can pass option classes to store and provide data which should be associated with the current theme.
You may also provide additional themes using the themes parameter. Here you have to provide a theme id string and theme data value. (Make sure to provide unique theme ids)
classMyAppextendsStatelessWidget{
@overrideWidgetbuild(BuildContext context) {
returnThemeProvider(
themes: [
AppTheme.light(), // This is standard light theme (id is default_light_theme)AppTheme.dark(), // This is standard dark theme (id is default_dark_theme)AppTheme(
id: "custom_theme", // Id(or name) of the theme(Has to be unique)
description: "My Custom Theme", // Description of theme
data: ThemeData( // Real theme data
primaryColor: Colors.black,
accentColor: Colors.red,
),
),
],
child: ThemeConsumer(
child: Builder(
builder: (themeContext) => MaterialApp(
theme: ThemeProvider.themeOf(themeContext).data,
title: 'Material App',
home: HomePage(),
),
),
),
);
}
}
Changing and accessing the current theme
You can use the theme id strings to change the current theme of the app.
If you provide the theme consumer on MaterialApp then you don't have to provide ThemeConsumer on routes. However that would disable the ability to use multiple theme controllers. Also a visible flickr may occur at the start of app when the saved theme is loaded.
This approach is much easier to integrate and works well with all other material components such as SearchDelegates and DialogBoxes without wrapping with ThemeConsumers.
Wrapping each route independently with ThemeProvider
However you could also wrap each route and dialog in ThemeConsumer instead of wrapping the whole material app.
This will give a more granular control and will not cause a visual flikr.
However, some integrations(eg: SearchDelegates) might not be trivial.
If you want to change the StatusBarColor when the theme changes, you can provide a onThemeChanged callback to the ThemeProvider.
Passing Additional Options
This can also be used to pass additional data associated with the theme. Use options to pass additional data that should be associated with the theme.
eg: If font color on a specific button changes according to the current theme, create a class to encapsulate the value.
Options classes must implement or extend AppThemeOptions.
defaultThemeId will always be used to determine the initial theme. (If not provided the first theme you specify will be the default app theme.)
But you can manually load the previous(saved) theme by using:
Or to load a theme/do some task at theme controller initialization use onInitCallback.
This will get called on the start.
For example, snippet below will load the previously saved theme from the disk. (if previosuly saved.)
ThemeProvider(
defaultThemeId: "theme_1",
themes: [
AppTheme.light(id: "theme_1"),
AppTheme.light(id: "theme_2"),
AppTheme.light(id: "theme_3"),
],
saveThemesOnChange: true,
onInitCallback: (controller, previouslySavedThemeFuture) async {
// Do some other task here if you need toString savedTheme = await previouslySavedThemeFuture;
if (savedTheme != null) {
controller.setTheme(savedTheme);
}
},
// ...
)
⚡ Dynamically Adding/Removing Themes
Themes can be dynamically added/removed via addTheme and removeTheme. Whether a theme id exists or not can be checked via hasTheme.
A theme can only be added if it is not added previously. Similarly, a theme can only be removed if it is previously added.
So the membership must be checked before adding/removing themes. (Whether a theme exists or not is decided via its theme id)
Note that the active theme cannot be removed.
🔌 Checking system theme when loading initial theme
You can do this by simply checking for the system theme in onInitCallback callback. Following is an example usage.
In the following snippet, the theme will be set to the previously saved theme.
If there is no previously saved theme, it is set to light/dark depending on system theme.
You can use any kind of logic here to change the initialization callback.
Dynamically listening to theme changes is not yet available. The theme check is only possible on app start.
import'package:flutter/scheduler.dart';
ThemeProvider(
saveThemesOnChange: true, // Auto save any theme change we do
loadThemeOnInit: false, // Do not load the saved theme(use onInitCallback callback)
onInitCallback: (controller, previouslySavedThemeFuture) async {
String savedTheme = await previouslySavedThemeFuture;
if (savedTheme != null) {
// If previous theme saved, use saved theme
controller.setTheme(savedTheme);
} else {
// If previous theme not found, use platform defaultBrightness platformBrightness =
SchedulerBinding.instance.window.platformBrightness;
if (platformBrightness == Brightness.dark) {
controller.setTheme('dark');
} else {
controller.setTheme('light');
}
// Forget the saved theme(which were saved just now by previous lines)
controller.forgetSavedTheme();
}
},
themes: <AppTheme>[
AppTheme.light(id: 'light'),
AppTheme.dark(id: 'dark'),
],
child: ThemeConsumer(
child: Builder(
builder: (themeContext) => MaterialApp(
theme: ThemeProvider.themeOf(themeContext).data,
title: 'Material App',
home: HomePage(),
),
),
),
);
🎁 Additional Widgets
Theme Cycle Widget
IconButton to be added to AppBar to cycle to next theme.