Your mileage may varies, I used Angular Dart 6 Alpha for production without any issue for a year until it is finally released this month. So far only build a simple website with Flutter for web to see how its layout, navigation and responsive etc works. Feels more like building a mobile app than a typical web app. For me, it is good enough. I would suggest to take it for a spin. If you plan to have charts, see if those libraries are available or can be integrated.
@dukefirehawk: https://pub.dev/packages/shelf_router is similar, and there is also a code generator that creates the boilerplate based on annotations.
I see that https://angulardart.dev/ have documentation about v. 5.3, where person who never used before angularDart (and Angular) could find documentation and some tutorials about Angular Dart 6 for start learn it?
most updates were inner stuff so I think there is a high probability that you can use the current documentation to learn
According to
https://github.com/dart-lang/angular_components/blob/master/angular_components/pubspec.yaml…name: angular_components
version: 1.0.2-dev
description: >
The official Material Design components for AngularDart. Used at Google in
production apps.
repository: https://github.com/dart-lang/angular_components
environment:
sdk: '>=2.8.1 <3.0.0'
dependencies:
angular: ^6.0.0
angular_forms: ^3.0.0
async: ^2.1.0
build: ^1.0.0
build_config: ^0.4.0
built_collection: ^4.0.0
collection: ^1.14.10
fixnum: ^0.10.7
intl: ^0.16.0
js: ^0.6.1
logging: ^0.11.2
meta: ^1.0.4
observable: ^0.22.2
protobuf: ^1.0.0
quiver: ^2.0.0
sass_builder: ^2.0.2
dev_dependencies:
path: ^1.6.1
pedantic: ^1.8.0
test: ^1.0.0
Took me only one google, second hit. I’m tempted to paste the Google instructions here too. :)
This is what I use for Angular Dart 6 project
name: my-app
description: A web app that uses AngularDart Components
version: 2.0.0
environment:
sdk: ">=2.2.0 <3.0.0"
dependencies:
angular: ^6.0.0
angular_components: ^1.0.1
angular_router: ^2.0.0
angular_forms: ^3.0.0
firebase: ^7.3.0
dev_dependencies:
angular_test: ^3.0.0
build_runner: ^1.10.2
build_test: ^1.2.2
build_web_compilers: ^2.12.0-dev.3
#build_web_compilers: ^2.12.2
test: ^1.15.4
sass_builder: ^2.1.3
I was once concerned with Angular, but now that flutter_web is here, not so much.
Very simple case is, the tabular form of data that we are displaying using CSS flex and grid usually overflows horizontally and vertically on the browser and using
SingleChildScrollViewwon't be apt. I mean, going by their statement in their docs: If the viewport is expected to usually contain content beyond the dimensions of the screen, then SingleChildScrollView would be very expensive.
Agree. As I understand flutter and its rendering model its going to be really challenging to make flutter web work well. Take the apps listed on the angular page - Google Ads, Google AdSense, Google Fiber, Google Play Console. I don't expect these to be re-implemented in flutter.
I get that google doesn't want to invest in supporting angular externally. Makes sense. That doesn't mean flutter is the answer.
Also for experienced teams angular dart works well.
Here's structure of my code
router.dart
static final nonAuth = <RouteDefinition>[login];
static final authenticated = <RouteDefinition>[users, plansIndex, usersEdit, dashboard];app_component.dart
<div *ngIf="!isSignedIn">
<router-outlet [routes]="Routes.nonAuth"></router-outlet>
</div>
<div *ngIf="isSignedIn">
<div id="main-wrapper">
<app-header [user]="user"></app-header>
<app-sidebar [user]="user"></app-sidebar>
<div class="page-wrapper">
<div class="container-fluid">
<router-outlet [routes]="Routes.authenticated"></router-outlet>
<app-right-sidebar></app-right-sidebar>
</div>
</div>
<footer class="footer">
© 2020 COpyright
</footer>
</div>
</div>
So, whether I call
router.navigate('anypath') it just does nothing
Instead, if I put all routes into single array of <RouteDefinition> it works just fine
I should be publishing everything tomorrow @/all