我目前正在尝试使用新的Flutter Web Beta构建Web应用程序。
要能够拥有历史记录，处理浏览器的前进和后退按钮，并能够处理用户输入到URL中的内容，需要使用新的Navigator 2.0 API（至少从我理解的角度如此）。
目前只有很少的资源可以使用，基于这些资源，我正在尝试构建我的Navigator。
我使用的资源：
- (我的主要来源) '学习Flutter的新导航和路由系统' by John Ryan
- 一个相似的项目 (by orestesgaolin)，但带有页面管理器和更复杂的功能
- Flutter公开分享的文档，介绍了新的Navigator
我已经成功实现了Back和Forward按钮以及历史记录的功能。但是，我无法处理页面切换（在Navigator()中）。在John的示例中，他在Navigator Widget的'page: '数组中管理了不同的站点（在routeDelegater中）。这对我来说似乎很奇怪，但我尝试过这样做，它并没有真正起作用（见下面的代码）。
在“page: []”中，我首先尝试使用布尔值触发器（如show404），但那并不是很干净，所以我的下一个尝试是按以下方式获取当前页面（在数组中）：
if(_currentPage.name == 'pages[0]') pageBuilds[0]
这样做有点效果，因为我随后能够输入段落 /matchit/0 ，正确的页面加载了，但由于某种原因，'/'路由不再起作用，我遇到了错误。
Navigator.onGenerateRoute was null, but the route named "/" was referenced
我尝试使用 'ongenerateRoute'，但是报了一大堆错误。可能是因为我还很新，所以我可能做错了什么。但是在我看来，这似乎不是正确的方法。这就是我目前所卡住的地方。我不知道接下来该尝试什么，希望你们中的一些人可以帮助我。
我的路由委托如下所示（我也会在代码中包含我的注释，也许可以帮助你们中的一些人了解Navigator 2.0正在发生什么）：
/**
* The RouteDelegate defines application specific behavious of how the router
* learns about changes in the application state and how it responds to them.
* It listens to the RouteInformation Parser and the app state and builds the Navigator with
* the current list of pages (immutable object used to set navigator's history stack).
*/
//ChangeNotifier for the listeners as they are handled there
//The popRoute is handled by 'PopNavigatorRouterDelegateMixin'
class RoutesDelegater extends RouterDelegate<RoutePath>
with ChangeNotifier, PopNavigatorRouterDelegateMixin<RoutePath> {
//This is the state of the navigator widget (in build method)
GlobalKey<NavigatorState> get navigatorKey => GlobalKey<NavigatorState>();
//RoutesDelegater() : navigatorKey = GlobalKey<NavigatorState>();
MyPage _currentPage;
bool show404 = false; //checks if we show the 404 page
List<MyPage> pages = [
MyPage('ProjektListe'),
MyPage('StudiListe'),
MyPage('PRView'),
];
List<Page> pageBuilds = [
MaterialPage(key: ValueKey('Unknown'), child: UnknownScreen()),
MaterialPage(key: ValueKey('Homepage'), child: MyFirstHomepage()),
MaterialPage(key: ValueKey('OtherScreen'), child: OtherScreen()),
];
//currentConfiguration detects changes in the route information
//It helps complete the browser history and (IMPORTANT) makes the browser back and forward buttons work
RoutePath get currentConfiguration {
if (show404) {
return RoutePath.unknown();
}
if (_currentPage == null) return RoutePath.home();
//if not 404 or homepage it is some other page
return RoutePath.details(pages.indexOf(_currentPage));
}
@override
Widget build(BuildContext context) {
return Navigator(
key: navigatorKey,
pages: //List.of(pageBuilds),
[
//pageBuilds[1],
if (show404)
pageBuilds[0]
else if (_currentPage != null)
pageBuilds[1]
],
onPopPage: (route, result) {
if (!route.didPop(result)) {
return false;
}
_currentPage = null;
show404 = false;
//we are using Changenotifier
notifyListeners();
return true;
});
}
void _handleTapped(MyPage page) {
_currentPage = page;
notifyListeners();
}
@override
Future<void> setNewRoutePath(RoutePath path) async {
//Handle the unknown path
if (path.isUnknown) {
show404 = true;
_currentPage = null;
return;
}
if (path.isDetailPage) {
//Check if Path id is valid
if (path.id.isNegative || path.id > pages.length - 1) {
show404 = true;
return;
}
_currentPage = pages[path.id];
} else {
//homepage will be shown
_currentPage = null;
}
show404 = false;
}
}
我的RoutingInformationParser如下所示：
/*
* The RouteInformationParser takes the RouteInformation from RouteInformationProvider and
* parses it into a user-defined data type.
*/
class MyRoutesInformationParser extends RouteInformationParser<RoutePath> {
@override
Future<RoutePath> parseRouteInformation(
RouteInformation routeInformation) async {
//routeInformation is an object we get from the uri
final uri = Uri.parse(routeInformation.location);
// Handle '/' (Home Path)
//Path segments are the segments seperated by /, if we don't have any we are on Home
if (uri.pathSegments.length == 0) {
return RoutePath.home();
}
//We have 2, as we have matchit/...
if (uri.pathSegments.length == 2) {
//If there is no 'matchit' in the first path segment the path is unknown
if (uri.pathSegments.first != 'matchit') return RoutePath.unknown();
//If we now have the correct first segment we can now handle the rest of the segment
final remaining = uri.pathSegments.elementAt(1);
final id = int.tryParse(remaining);
//if it fails we return the unknown path
if (id == null) return RoutePath.unknown();
return RoutePath.details(id);
}
//Handling the unknown Path, e.g. user just typed anything in uri
return RoutePath.unknown();
}
//THIS IS IMPORTANT: Here we restore the web history
@override
RouteInformation restoreRouteInformation(RoutePath path) {
//Here we set the routeInformation which is used above, e.g. /404 for unknown page
if (path.isUnknown) {
return RouteInformation(location: '/404');
}
if (path.isHomePage) {
return RouteInformation(location: '/');
}
//Any other page is handled here via /matchit/... <= the id of the path
if (path.isDetailPage) {
return RouteInformation(location: '/matchit/${path.id}');
}
//If none of the paths are hit
return null;
}
}
我们还有用于路由信息的 Data-type：
class RoutePath{
final int id;
final bool isUnknown;
RoutePath.home()
: id = null,
isUnknown = false;
//Details means here that it is any other side than Home or unknown
RoutePath.details(this.id) : isUnknown = false;
RoutePath.unknown()
: id = null,
isUnknown = true;
//check if is on HomePage or other page, then either == null or != null
//not needed for isInknown, as when unknown then = true as set above
bool get isHomePage => id == null;
bool get isDetailPage => id != null;
}
最后是我的主页（Homepage()），在那里初始化了 InformationParser 和 Delegater：
class Homepage extends StatefulWidget {
@override
State<StatefulWidget> createState() => _HomepageState();
}
class _HomepageState extends State<Homepage> {
//initialize the RouteDelegater and Information Parser to be unsed further down
RoutesDelegater _routesDelegater = RoutesDelegater();
MyRoutesInformationParser _myRoutesInformationParser =
MyRoutesInformationParser();
/*
* Relevant routing information for this build method:
* We need to use the MaterialApp.router else we can't use routerDelegate and routeInformationParser.
* Then we define the delegate and Information Parser (they are initiated above)
*/
@override
Widget build(BuildContext context) {
return MaterialApp.router(
title: 'MatchIT',
routerDelegate: _routesDelegater,
routeInformationParser: _myRoutesInformationParser,
theme: ThemeData(primarySwatch: Colors.blue),
debugShowCheckedModeBanner: false);
}
}
提前感谢您！