Repository navigation
geolocator_watchos: upstream's example, the Baseflow demo - #29
Merged
Merged
Conversation
The example was a hand-written demo, though the README called it the upstream Baseflow demo "ported verbatim". AUTHORING.md §3 asks for upstream's own example, so it is now geolocator's example app, ported with `flutter-watchos plugin port --include-example` (#24). Its code is unchanged; two listed watchOS deviations: - example/pubspec.yaml adds url_launcher_watchos, so the template's links open on the watch. - The runner's Info.plist sets FlutterWatchOSContentScale to 0.6. The demo is laid out for a phone and overflowed a 46 mm watch screen by 106 pixels; the scale fits it without touching the Dart code. The package's LICENSE is Baseflow's MIT licence, which covers the demo. geolocator ships no integration test. On the watchOS 27.0 Simulator, built with flutter.inspector.structuredErrors=false so framework errors reach the log (spec 0006 criterion 8a), the example starts with no exception in its first 15 seconds and no overflow, and reports the location service enabled. 0.2.0 is not published yet (#16), so this joins its CHANGELOG entry.
The permission prompt and live updates were verified on a physical Apple Watch with 0.1.x; 0.2.0 has run only on the Simulator so far (#16). The README is published with 0.2.0, so it says so.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #24.
Example. Our example was a hand-written demo, though the README called it the upstream Baseflow demo "ported verbatim". It is now
geolocator's own example app, ported withflutter-watchos plugin port --include-example. Its code is unchanged, with two listed watchOS deviations (both in the README's new Example section):example/pubspec.yamladdsurl_launcher_watchos, so the template's links open on the watch.Info.plistsetsFlutterWatchOSContentScaleto 0.6. The demo is laid out for a phone and overflowed a 46 mm watch screen by 106 pixels; the scale fits it without touching the Dart code. network_info_plus does the same.The package's
LICENSEis Baseflow's MIT licence, which covers the demo. geolocator ships no integration test.Verified on the watchOS 27.0 Simulator. The build uses
--dart-define=flutter.inspector.structuredErrors=false, so framework errors reach the log (spec 0006 criterion 8a). Before the scale, that check reported the overflow.Unit tests (26) and
flutter analyze lib testare clean. The repo's version, example-constraint, README-snippet, word and format checks pass.0.2.0 is not published yet (#16), so the change joins its CHANGELOG entry under a new "Example" heading.