Doni/TermRemoteCtl
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: neutralize task 1 scaffolds

Browse Source
This commit is contained in:
sladro 2026-03-27 10:41:05 +08:00
parent 1096c15b82
commit 147a950c61
6 changed files with 55 additions and 137 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -15,4 +15,5 @@ TermRemoteCtl is a personal remote coding controller for one Windows workstation
## Initial Setup
1. Run flutter create apps/mobile_app --platforms=android,ios --project-name term_remote_ctl
2. Run dotnet new sln -n TermRemoteCtl.Agent -o apps/windows_agent
3. Follow the implementation plan in docs/superpowers/plans/2026-03-27-mobile-windows-terminal-controller.md
3. Verify the generated workspace with `flutter --version` and `dotnet --version`
4. Begin implementation in `apps/mobile_app` and `apps/windows_agent` using the checked-in workspace files and protocol notes

23
apps/mobile_app/README.md
View File

@ -1,16 +1,15 @@
# term_remote_ctl
# TermRemoteCtl Mobile App
A new Flutter project.
This directory contains the Flutter client for TermRemoteCtl.
## Getting Started
## Current State
- Minimal bootstrap shell only
- No remote control workflows implemented yet
This project is a starting point for a Flutter application.
## Local Development
1. Run `C:\tools\flutter\bin\flutter.bat pub get`
2. Run `C:\tools\flutter\bin\flutter.bat test`
3. Run `C:\tools\flutter\bin\flutter.bat run`
A few resources to get you started if this is your first Flutter project:
- [Lab: Write your first Flutter app](https://docs.flutter.dev/get-started/codelab)
- [Cookbook: Useful Flutter samples](https://docs.flutter.dev/cookbook)
For help getting started with Flutter development, view the
[online documentation](https://docs.flutter.dev/), which offers tutorials,
samples, guidance on mobile development, and a full API reference.
## Purpose
This app will eventually provide the mobile control surface for the Windows agent, but at this stage it only verifies that the Flutter workspace is wired correctly.

129
apps/mobile_app/lib/main.dart
View File

@ -1,122 +1,55 @@
import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
runApp(const TermRemoteCtlApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
class TermRemoteCtlApp extends StatelessWidget {
const TermRemoteCtlApp({super.key});
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
debugShowCheckedModeBanner: false,
title: 'TermRemoteCtl',
theme: ThemeData(
// This is the theme of your application.
//
// TRY THIS: Try running your application with "flutter run". You'll see
// the application has a purple toolbar. Then, without quitting the app,
// try changing the seedColor in the colorScheme below to Colors.green
// and then invoke "hot reload" (save your changes or press the "hot
// reload" button in a Flutter-supported IDE, or press "r" if you used
// the command line to start the app).
//
// Notice that the counter didn't reset back to zero; the application
// state is not lost during the reload. To reset the state, use hot
// restart instead.
//
// This works for code too, not just values: Most code changes can be
// tested with just a hot reload.
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
colorScheme: ColorScheme.fromSeed(seedColor: Colors.teal),
),
home: const MyHomePage(title: 'Flutter Demo Home Page'),
home: const BootstrapShell(),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
// This widget is the home page of your application. It is stateful, meaning
// that it has a State object (defined below) that contains fields that affect
// how it looks.
// This class is the configuration for the state. It holds the values (in this
// case the title) provided by the parent (in this case the App widget) and
// used by the build method of the State. Fields in a Widget subclass are
// always marked "final".
final String title;
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
int _counter = 0;
void _incrementCounter() {
setState(() {
// This call to setState tells the Flutter framework that something has
// changed in this State, which causes it to rerun the build method below
// so that the display can reflect the updated values. If we changed
// _counter without calling setState(), then the build method would not be
// called again, and so nothing would appear to happen.
_counter++;
});
}
class BootstrapShell extends StatelessWidget {
const BootstrapShell({super.key});
@override
Widget build(BuildContext context) {
// This method is rerun every time setState is called, for instance as done
// by the _incrementCounter method above.
//
// The Flutter framework has been optimized to make rerunning build methods
// fast, so that you can just rebuild anything that needs updating rather
// than having to individually change instances of widgets.
return Scaffold(
appBar: AppBar(
// TRY THIS: Try changing the color here to a specific color (to
// Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
// change color while the other colors stay the same.
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
// Here we take the value from the MyHomePage object that was created by
// the App.build method, and use it to set our appbar title.
title: Text(widget.title),
),
body: Center(
// Center is a layout widget. It takes a single child and positions it
// in the middle of the parent.
child: Column(
// Column is also a layout widget. It takes a list of children and
// arranges them vertically. By default, it sizes itself to fit its
// children horizontally, and tries to be as tall as its parent.
//
// Column has various properties to control how it sizes itself and
// how it positions its children. Here we use mainAxisAlignment to
// center the children vertically; the main axis here is the vertical
// axis because Columns are vertical (the cross axis would be
// horizontal).
//
// TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
// action in the IDE, or press "p" in the console), to see the
// wireframe for each widget.
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
const Text('You have pushed the button this many times:'),
Text(
'$_counter',
style: Theme.of(context).textTheme.headlineMedium,
return const Scaffold(
body: SafeArea(
child: Center(
child: Padding(
padding: EdgeInsets.all(24),
child: Column(
mainAxisSize: MainAxisSize.min,
children: <Widget>[
Icon(Icons.computer, size: 48),
SizedBox(height: 16),
Text(
'TermRemoteCtl',
textAlign: TextAlign.center,
),
SizedBox(height: 8),
Text(
'Bootstrap shell ready for the mobile client.',
textAlign: TextAlign.center,
),
],
),
],
),
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: const Icon(Icons.add),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}

28
apps/mobile_app/test/widget_test.dart
View File

@ -1,30 +1,18 @@
// This is a basic Flutter widget test.
//
// To perform an interaction with a widget in your test, use the WidgetTester
// utility in the flutter_test package. For example, you can send tap and scroll
// gestures. You can also use WidgetTester to find child widgets in the widget
// tree, read text, and verify that the values of widget properties are correct.
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:term_remote_ctl/main.dart';
void main() {
testWidgets('Counter increments smoke test', (WidgetTester tester) async {
// Build our app and trigger a frame.
await tester.pumpWidget(const MyApp());
// Verify that our counter starts at 0.
expect(find.text('0'), findsOneWidget);
expect(find.text('1'), findsNothing);
// Tap the '+' icon and trigger a frame.
await tester.tap(find.byIcon(Icons.add));
testWidgets('shows the TermRemoteCtl bootstrap shell', (tester) async {
await tester.pumpWidget(const TermRemoteCtlApp());
await tester.pump();
// Verify that our counter has incremented.
expect(find.text('0'), findsNothing);
expect(find.text('1'), findsOneWidget);
expect(find.text('TermRemoteCtl'), findsOneWidget);
expect(
find.text('Bootstrap shell ready for the mobile client.'),
findsOneWidget,
);
expect(find.byIcon(Icons.computer), findsOneWidget);
});
}

2
apps/windows_agent/src/TermRemoteCtl.Agent/Program.cs
View File

@ -1,6 +1,4 @@
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
app.MapGet("/", () => "Hello World!");
app.Run();

7
apps/windows_agent/tests/TermRemoteCtl.Agent.IntegrationTests/UnitTest1.cs
View File

@ -2,9 +2,8 @@ namespace TermRemoteCtl.Agent.IntegrationTests;
public class UnitTest1
{
[Fact]
public void Test1()
[Fact(Skip = "Placeholder until integration scenarios are defined.")]
public void PlaceholderTest()
{
}
}
}