5.20.0

Author: Drawner

CHANGELOG.md

@@ -1,4 +1,19 @@
 
+## 5.20.0
+March 31, 2025
+error_handler.dart
+- Flag when an error handler is explicitly passed into the app, _passedErrorHandler
+- Calls error handler when an unhandled error occurs in the root isolate.
+  _platformOnError = PlatformDispatcher.instance.onError;
+- Call to error handler in try-catch construct
+app_statex.dart - New functions to catch Asynchronous errors
+- Future<bool> onCatchAsyncError(Object error) async => await rootState?.catchAsyncError(error) ?? false;
+- Future<bool> catchAsyncError(Object error)
+- Future<bool> Function(Object error)? inCatchAsyncError
+- Deprecated onErrorHandler(). Use onError() instead.
+app_statefulWidget.dart:
+- future.catchError( calls catchAsyncError()
+
 ## 5.19.0
 March 17, 2025
 - Folder, test, moved to example/lib allowing testing on the Web

README.md

@@ -45,59 +45,4 @@ Free articles on Fluttery Framework:
 [A Fluttery Digest](https://dev.to/andrious/a-fluttery-digest-2kb8)
 
 As great as Flutter is, you will not create a ‘production-worthy’ app using Flutter right out of the box.
-When building a Flutter app, it’s expected to be one codebase that runs on an Android phone,
-an iOS phone, on Windows, on Linux, and or on the Web---and to do so seamlessly.
-It is to display the appropriate design interface (Material, Cupertino, etc.) depending on the platform it’s running on,
-it is to have a responsive interface that displays its information correctly no matter the screen size of the device or platform,
-and it is to fail gracefully if and when it encounters an error.
-Flutter right out of the box does not have these capabilities.
-Until now.
-
-When I first started working with Flutter,
-I began keeping modular bits of code from past projects that generally accelerated the development process.
-I would use these again and again in future apps---building up a toolkit as we developers often do.
-Libraries of tried and tested bits of software that I can later put together to reliably supply a particular function or feature.
-Over time, I turned to the Flutter community for such libraries, and again,
-if I didn’t find one I liked, I wrote my own:
-<ul>
-   <li id="prefs"><a href="https://pub.dev/packages/prefs">Prefs</a></li>
-   <li id="state"><a href="https://pub.dev/packages/state_set">State Set</a></li>
-   <li id="db"><a href="https://pub.dev/packages/dbutils">DBUtils</a></li>
-   <li id="l10n"><a href="https://pub.dev/packages/l10n_translator">l10n Translator</a></li>
-   <li id="remote"><a href="https://pub.dev/packages/remote_config">Remote Config</a></li>
-   <li id="extend"><a href="https://pub.dartlang.org/packages/state_extended">StateX</a></li> 
-</ul>
-
-The Fluttery Framework uses packages you will likely need in your own apps.
-It's a collection of software that's proven to be effective solutions to those capabilities required time and time again by a typical real-world app.
-It’s an amalgamation of what's great about Flutter and what the Flutter community has contributed over the last years.
-As the years went by, I found packages that made my life easier and so they too were incorporated into the Fluttery Framework:
-
-- [connectivity_plus]( https://pub.dartlang.org/packages/connectivity_plus)
-- [device_info_plus]( https://pub.dev/packages/device_info_plus)
-- [flutter_localizations]( https://pub.dev/packages/flutter_localization)
-- [go_router]( https://pub.dev/packages/go_router) (but not before [discovering]( https://github.com/flutter/flutter/issues/123570#issuecomment-1588610299) how to fix it)
-- [http](https://pub.dev/packages/http)
-- [package_info_plus](https://pub.dev/packages/package_info_plus)
-- [path_provider](https://pub.dev/packages/path_provider)
-- [sizer](https://pub.dev/packages/sizer)
-- [state_extended](https://pub.dev/packages/state_extended)
-- [timezone](https://pub.dev/packages/timezone)
-- [universal_io](https://pub.dev/packages/universal_io)
-- [universal_platform](https://pub.dev/packages/universal_platform)
-- [url_launcher](https://pub.dartlang.org/packages/url_launcher)
-- [url_strategy](https://pub.dev/packages/url_strategy)
-- [uuid](https://pub.dartlang.org/packages/uuid)
-
-I was careful to choose only packages that fulfill the general requirements of a typical app.
-After all, this is to serve as a ‘general framework’ for all my apps no matter how diverse each is.
-Of course, for your specific app with its specific needs,
-you then will add additional packages or write your own.
-You supply the specific code; the Fluttery Framework supplies the rest.
-
-Such a framework is to offer a structured approach to making a production-worthy app.
-For we Flutter developers in particular, a ready means to access a State object’s **setState**() function is of interest.
-With that, Fluttery own unique contribution to this package is the concept of a ‘State Object Controller.’
-The use of controllers are nothing new to Flutter. It uses controllers in a number of its widgets.
-It would encourage a separation of an app’s interface from its event handling and business rules promoting a clean architecture.
-Unlike other options out there, it works with Flutter; not on top of it as a separate approach.
+Until now.

example/android/app/src/main/AndroidManifest.xml

@@ -1,4 +1,5 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android">
+<!--    <uses-feature android:glEsVersion="0x00010001" android:required="true" />-->
     <application
         android:label="fluttery_framework_example"
         android:name="${applicationName}"

example/lib/main.dart

@@ -1,6 +1,4 @@
 //
 import '/src/view.dart';
 
-void main() => runApp(
-      FlutteryExampleApp(),
-    );
+void main() => runApp(FlutteryExampleApp());