``
your code
``
void main() {
ui.platformViewRegistry.registerViewFactory(
'hello-world-html',
(int viewId) => IFrameElement()..src = 'https://www.sample-videos.com/video123/mp4/720/big_buck_bunny_720p_20mb.mp4'
);
runApp(Directionality(
textDirection: TextDirection.ltr,
child: HtmlView(viewType: 'hello-world-html'),
));
}
http://localhost:8080/post?id=1234
in the Flutter code I will be able to take that ID argument in the post
endpoint
flutter config --enable-web
now, do anyone know any available online doc talking about the best pratice to manage a flutter project for both mobile and web? It seems I still need to have two different versions of pubspec.yaml
and remove all the packages which are not supported by the web. so any best practise? Maybe I just move all the common packages out to be a single lib package. So end up three dart packages. one for common class, one for mobile and one for web. Is this a good design? Thanks a lot.
pubspec.yaml
. I didn’t find the right procedure to do it. Flutter team hides this deeply. After following the right procedure, it turns out it has to be a completely diffrerent project/package due to flutter create —web .
did something I am unsure. So, the question still applies. Should I create three projects (packages)? One for common, one for mobile and one for web? Is this best practise? I haven’t tried it if that way will work or not.
RawKeyboardListener(
focusNode: FocusNode(),
onKey: (event) {
if (event.runtimeType == RawKeyDownEvent && (event.logicalKey.keyId == 54)) {
print("ENTER Key pressed");
//Do something
}
},
child: TextFormField()),
path
param to page widget and do manual rewrite in initState:window.history.replaceState(null, widget.title, widget.path);
window.history.replaceState(null, widget.title, '/#'+widget.path);