Slim 是一個 Flutter 套件,提供必要的應用基礎架構,包括本地化支援、UI 訊息管理、狀態管理工具、有用的延伸功能以及 REST API 結合。設計用以簡化常見的開發任務,為建立可擴展且可維護的應用程式提供一致性的基礎。此套件強調簡單性與可重用性,減少專案中的樣板程式碼。透過其模組化結構,開發者可僅採用所需的元件。對於希望標準化應用架構並加速開發的團隊特別有用。
適用情境
本地化應用內容
管理UI訊息
簡化狀態管理
新增 REST API 客戶端
建立可重複使用的 UI 延伸
標準化應用架構
主要特色
內建本地化支援
UI 消息系統
狀態管理助手
REST API 結合
有用的 Dart 擴展
模組化設計
適合對象
Flutter 初學者
基於團隊的應用程式開發
大規模 Flutter 應用
快速原型設計
需要本地化的應用
頻繁進行 API 互動的專案
使用建議
有限的平台特定功能
無內建主題
需要手動設定複雜狀態
不適合高度專業化的使用者介面需求
依賴外部相依性以實現完整功能
高級用法的文件可能很少
原始 README
以下為關聯原始碼儲存庫的 README 原文快照,最新內容請造訪原始碼儲存庫。
slim - app essentials
slim was written to give some app essentials and capabilities that are common for most apps.
slim makes it easier to set up app infrastructure so you can start working on your screens and logic.
Localizations
UI Messages
State Management
AppLifecycleState Events
Useful Extensions
Rest Api
Configurations
Easy app level configuration that gives 'ready to use' localization and UI messages.
App class constructor
This is the place to set your supported locales and if you want also set your own SlimLocaleLoader
The default SlimLocaleLoader will load you locale files from - assets/locales/ so make sure you created folder and files matching your supported locales
and add it to pubspec.yaml file.
MaterialApp builder
Add the SlimMaterialAppBuilder.builder to it. If you have additional builders just chain them.
SlimMaterialAppBuilder.builder gives you the UI messages caps.
MaterialApp localizationsDelegates
Set to SlimLocalizations.delegates
That will support all delegates needed including the SlimLocalizations.slimLocaleLoader delegate.
MaterialApp supportedLocales
Set to SlimLocalizations.supportedLocales you configured in App class constructor.
The following example will load simple json locale configurations from - assets/locales/en.json
import'package:slim/slim.dart';
classMyAppextendsStatelessWidget{
MyApp(){
SlimLocalizations.supportedLocales = [Locale('en', 'US')];
/// If you want to customize you locale loader just create class that extends SlimLocaleLoader and change:////// SlimLocalizations.slimLocaleLoader= YouCustomLocalLoader();
}
@overrideWidgetbuild(BuildContext context) =>
MaterialApp(
builder: SlimMaterialAppBuilder.builder,
title: 'Flutter Demo',
theme: ThemeData(
primarySwatch: Colors.blue,
visualDensity: VisualDensity.adaptivePlatformDensity,
),
home: MyHomePage("First Screen"),
localizationsDelegates: SlimLocalizations.delegates,
supportedLocales: SlimLocalizations.supportedLocales,
);
}
Localization
UI direction
The confgurations above will make your UI ltr/rtl automatically according to os locale.
You can use BuildContext extension method to get your locale text direction context.textDirection
Translation
If you didn't provide any custom SlimLocaleLoader , Your localization would be configured with a default one. The default SlimLocaleLoader expects locale files to be in - assets/locales/ folder with name convention of your locale. for example - assets/locales/en.json.
The default locale file format is a single level json that holds you translation. You can extends SlimLocaleLoader to your own.
{"welcome":"translation of 'welcome' key"}
Access to translation of a key gained by BuildContext extension method called translate.
UI Messages caps are available via BuildContext extension methods. Since SlimController accessed by SlimBuilder has an access to current context, these caps are also available inside it. That will be explained in the State Management section below.
You can display overlay with your own widget, text message and a snackbar.
For text overlay and snackbar you can set the background color and text style.
For overlay of text or widget you can specify if dismissible.
State Management
slim provides state management based on InhertiedNotifier and ChangeNotifier classes.
The concept is that you keep an object at the top of the tree or sub tree of children that might access it.
The state object can be a widget state object, data object, business object or whatever you want it to be.
You can even use it for passing parameters between screens, so it can be a String, int or even an enum.
This is the one of the powerful concepts of slim state management - it can be any state and not limited for a widget state.
Before you go over below examples, excluding the case of parameter passing between screens, the most recommended state object is the SlimController and recommended way to access it is via SlimBuilder widget.
By using the SlimController from one side and SlimBuilder on the other, you get the best of three worlds:
Widget state control - you can make the wrapped widget to rebuild by calling updateUI method.
Since SlimController based on ChangeNotifier it will cause all widgets that referenced it to rebuild.
That is great but considered to be a ChangeNotifier disadvantage in case you only want to rebuild the current widget. For that you can pass the current flag and decide when you want to globaly or localy update the UI.
updateUI({bool current = false})
Global & Local shared objects/values - you can make any object/values shared between your app screens.
Global - put your object/value at the top of your app tree by wrapping the material app widget.
Local - put your object/value at the top of a sub tree. That way you can share objects for a local tree or pass
parameters between screens.
Separate & not disconnected business logic - The SlimController accessed by SlimBuilder allows you to separate the business from UI but gives access to current context. That gives you that ability to combine navigation flows and use the UI messages inside your business class.
SlimController
abstract class that can be used for state management or logic, inherits from ChangeNotifier and gives you widget rebuild options: T slim<slim>() - access to ancestor slims
updateUI({bool current = false}) - will refresh the state of all / current widgets that reference it (current update flag workd only if you access it via [SlimBuilder] widget). closeKeyBoard() - close keyboard by requesting focuse
The SlimController has context propery to access the current context so you can use context extensions from inside a business login class interacting with UI: showOverlay - display overlay text message showWidget - display overlay widget showSnackBar - display snackbar with given text clearOverlay - clears overlays forceClearOverlay - clears overlays even if not dismissible
For overlay message and snackbar you can set background color, text style, overlay color and overlay opacity.
For overlay message and widget you can set dismissible flag.
SlimAppStateController
abstract class that inherits from SlimController and recieves AppLifecycleState events. the events change recieves only if the SlimAppStateController
is accessed in the current app's screen. SlimAppStateController force to override its void onAppStateChanged(AppLifecycleState state) method.
SlimAppStateController must be access via SlimBuilder, SlimController access via SlimBuilder is optional but recommended
Putting Slims in the tree
For the following example we will use a simple Counter class:
classCounterextendsSlimController{
int value=0;
inc(){
value++;
}
}
@overrideWidgetbuild(BuildContext context){
returnSlimBuilder<Counter>(
[instance: optional local instance of Counterif you dont want to pre put it on tree]
builder:(counter){
...
return someWidget;
}
);
}
Simple Access - without updateUI(current:true) support
@overrideWidgetbuild(BuildContext context){
final counter = Slim.of<Counter>(context);
...
return someWidget;
}
@overrideWidgetbuild(BuildContext context){
final counter = context.slim<Counter>();
...
return someWidget;
}
Useful Extensions
slim provides some useful extension methods for several classes (some of them mentioned previously).
The full extension methods list is:
BuildContext bool hasOverlay - true if any overlay currently displayed void clearOverlay() - clears current overlay message if dismissible void forceClearOverlay() - clears current overlay message even if not dismissible void showWidget(Widget widget, {bool dismissible = true})
T slim<T>() - access a state object of type T double width - media query width double height - media query height NavigatorState navigator - navigator state void pop<T>({T result}) - navigator pop Future<T> push<T>(Route<T> route) - navigator push Future<T> pushReplacement<T>(Route<T> route) - navigator pushReplacement void popTop() - navigator pop till can't pop anymore String translate(String key,[String group]) - locale translation of key TextDirection textDirection - current locale text direction void closeKeyboard() - request focuse
Widget Future<T> push<T>(BuildContext context) - navigator push Future<T> pushReplacement<T>(BuildContext context) - navigator pushReplacement Future<T> pushTop<T>(BuildContext context) - push at navigators most top
int Duration get seconds - get in seconds Duration get hours - get in hours Duration get days - get in days Duration get minutes - get in minutes Duration get milliseconds - get in milliseconds Duration get microseconds - get in microseconds DateTime get nowMinutesInterval - get current time with minutes round up to interval
RestApi
SlimApi is an abstract class that gives you rest (get, delete, post, put) methods for fast service writing.
The SlimApi class constructor gets the server url, and its methods gets the service url and some additional data. SlimApi class has a createHeaders method that can be overriden. SlimApi methods wrapped in try/catch clause and returns SlimResponse object.
/// Extends slim SlimController classclassLoginControllerextendsSlimController{
badLogin(User user) async {
/// Access login service via slimfinal loginService = slim<LoginService>();
/// Using context access to display loading indicatorshowWidget(CircularProgressIndicator(), dismissible:false);
final result = await loginService.login(user);
/// Using context access to clear loading indicatorforceClearOverlay();
/// Checking slim RestApiResult for successif (result.success)
/// Using slim widget extension method to replace current screen to Home widgetHome().pushReplacement(context);
else/// Using context access to show a snackbar and locale translationshowSnackBar(context.translate("badcreds"), backgroundColor: Colors.red);
}
goodLogin(User user) async {
/// Access login service via slimfinal loginService = slim<LoginService>();
/// Close keyboardcloseKeyboard();
/// Using context access to display loading indicatorshowWidget(CircularProgressIndicator(), dismissible:false);
await loginService.login(user);
//Using context access to clear loading indicatorforceClearOverlay();
/// Using slim widget extension method to replace current screen to Home widgetHome().pushReplacement(context);
}
}
App Configurations
classMyAppextendsStatelessWidget{
@overrideWidgetbuild(BuildContext context) {
return [
/// Putting single instance of Userat the top of the treeSlimer<User>(User()),
/// Putting single instance of LoginService at the top of the treeSlimer<LoginService>(LoginService()),
/// Putting single instance of LoginController at the top of the treeSlimer<LoginBloc>(LoginController()),
].slim(
child: MaterialApp(
/// Configure material app builder for slim UI messages support
builder: SlimMaterialAppBuilder.builder,
title: 'Flutter Demo',
theme: ThemeData(
primarySwatch: Colors.blue,
visualDensity: VisualDensity.adaptivePlatformDensity,
),
home: Login(),
/// Configure slim localizations delegates
localizationsDelegates: SlimLocalizations.delegates,
/// Configure slim localizations supported locales
supportedLocales: SlimLocalizations.supportedLocales..addAll([Locale('en', 'US')]),
),
);
}
}