Dartvel on devices: windows, widgets, kiosks and desktop

Linux binds the most today and iOS the fewest. A test checks that every binding a target claims has a handler behind it, and on Android an emulator job checks it again.

// One surface on every target. A feature the platform does not have answers
// that it is unavailable, and does not throw, so a call site does not need
// to know which platform it is on.
Future<void> shareReceipt(String orderId) async {
  await DV.Haptics.lightVibrate();
  await DV.Share.shareText('Order $orderId is on its way.');
}

// A widget, with the annotation on it. The same functional widget every
// other piece of Dartvel UI is: the input is private, and the generated
// NextShiftWidget is what the home screen and the route reach.
@DVHomeWidget(title: 'Next shift')
@DVFunctionalWidget()
Widget _nextShiftWidget(BuildContext context) => const DVBox.list(<Widget>[
      DVText('Next shift'),
      DVText('Thursday, 07:00'),
    ]);

// What the home screen shows, pushed from anywhere in the app.
Future<void> refreshShift(String when) =>
    DVHomeWidgets.publish('next-shift', when);

System key combinations that leave the app are blocked on Linux, Windows and macOS, as far as each OS lets an app, and by lock task mode on Android. Accessibility keys still work.

DV.Platform.window.open opens a page in its own window on Linux, once: opening it again focuses the one that is open. A second launch of the app hands its arguments to the first.

A window opens on the display you ask for, such as DVDisplayHint.secondary for a projector, and window.setFullscreen(true, on: ...) fills that display. If that display is not connected, the call is refused and the current screen stays as it is.

// Idempotent by route: opening a route a window already shows returns that
// window instead of a second copy of it.
// The route is the generated target, never a string: moving the page moves
// this with it, and a route that no longer exists is a compile error rather
// than a window onto nothing.
Future<DVWindow> openCart() => DV.Platform.window.open(DVRoutes.cart);

On a foldable the first pane sits on one side of the fold and the second on the other, with nothing in the hinge. With no fold they sit side by side on a tablet and stack on a phone.

// The fold is a rectangle the page is told about, so a layout can keep
// content out from under the hinge without guessing at a breakpoint.
Widget shiftBoard(BuildContext context) {
  final List<DVFold> folds = context.screen.folds;
  final bool split = folds.any((DVFold fold) => fold.occludes);
  return DVBox.list(<Widget>[
    const DVText('Today'),
    if (!split) const DVText('Tomorrow'),
  ]);
}

// Trays, menus and shortcuts are the same DV.Platform surface, so a desktop
// build asks for them and a phone build answers that it has none.
Future<void> installDesktopChrome() async {
  await DV.Platform.tray.show(
    icon: DVAsset.tray,
    tooltip: 'Oakline',
    menu: const <DVTrayMenuItem>[
      DVTrayMenuItem.header('Oakline'),
      DVTrayMenuItem.separator(),
      DVTrayMenuItem(id: 'cart', label: 'Open the cart'),
      DVTrayMenuItem(id: 'sounds', label: 'Order sounds', checked: true),
    ],
    onSelected: (String id) => DV.Platform.window.open(DVRoutes.cart),
  );
  // The same icon, changed in place: no flicker, no second icon.
  await DV.Platform.tray.update(tooltip: 'Oakline: 2 orders waiting');
  await DV.Platform.shortcuts.register(
    const DVGlobalShortcut(id: 'cart', accelerator: 'Ctrl+Shift+O'),
    onPressed: () => DV.Platform.window.open(DVRoutes.cart),
  );
}

Every native feature on this page reaches the device through DV.Platform. See the platform page for the full member list, binding status per platform, and planned capabilities.

GETTING STARTED

APP

DATA

BACKEND

OPERATIONS

SHIPPING

REFERENCE

Devices and desktop

Call native features through DV.Platform

Put a widget on the home screen

Lock a screen to your app

Open more windows and tabs

Lay out around the fold on a foldable

Trays, menus, shortcuts and drag and drop