Files
Terminal.Gui/Examples/FluentExample/Program.cs
Copilot e199063a31 Introduce IRunnable interface architecture with Fluent API (Phase 1) (#4405)
* Initial plan

* Add IRunnable interface, Runnable base class, and RunnableSessionToken

Co-authored-by: tig <585482+tig@users.noreply.github.com>

* Add comprehensive parallelizable unit tests for IRunnable

Co-authored-by: tig <585482+tig@users.noreply.github.com>

* Add 41 more unit tests for comprehensive IRunnable coverage

- Added ApplicationRunnableIntegrationTests with 29 integration tests covering Begin/End/Run lifecycle
- Added RunnableEdgeCasesTests with 24 edge case and error condition tests
- Tests cover event propagation, cancellation scenarios, nested runnables, result handling
- Fixed App property not being set in Begin() method
- Total test count increased from 23 to 64 tests for IRunnable functionality

Co-authored-by: tig <585482+tig@users.noreply.github.com>

* Fix parallel test failures in CI/CD

- Fixed IsModal property to check RunnableSessionStack instead of just TopRunnable
- Added "fake" driver parameter to Application.Init() in integration tests
- Fixed Begin() to capture old IsModal value before pushing to stack
- Moved App property assignment before stack operations to ensure proper state
- Skipped 2 tests that use Run() with main loop (not suitable for parallel tests)
- All 11,654 parallelizable tests now pass (4 skipped)

Co-authored-by: tig <585482+tig@users.noreply.github.com>

* Refactor Application with IRunnable and session management

Modernized `Application` and `ApplicationImpl` by introducing `IRunnable` and `RunnableSessionToken` for improved session management. Deprecated legacy methods and added `Obsolete` attributes to indicate their removal. Simplified method bodies using expression-bodied members and null-coalescing assignments.

Enhanced lifecycle management in `ApplicationImpl` by removing redundant code and improving `SessionStack` iteration. Introduced `IToplevelTransitionManager` to handle top-level state changes.

Updated `Runnable<TResult>` to implement `IRunnable<TResult>` with lifecycle event handling for `IsRunning` and `IsModal` states. Improved result management during lifecycle transitions.

Removed legacy classes like `SessionToken` and consolidated their functionality into the new constructs. Updated and expanded the test suite to cover `IRunnable` lifecycle events, `RunnableSessionToken` behavior, and integration with `Application`.

Performed code cleanup, improved readability, and updated documentation with detailed remarks and examples. Added new unit tests for edge cases and lifecycle behavior.

* Implement fluent API for Init/Run/Shutdown with automatic disposal

- Changed Init() to return IApplication for fluent chaining
- Changed Run<TRunnable>() to return IApplication (breaking change from TRunnable)
- Changed Shutdown() to return object? (extracts and returns result from last Run<T>())
- Added FrameworkOwnedRunnable property to track runnable created by Run<T>()
- Shutdown() automatically disposes framework-owned runnables
- Created FluentExample demonstrating: Application.Create().Init().Run<ColorPickerView>().Shutdown()
- Disposal semantics: framework creates → framework disposes; caller creates → caller disposes

Co-authored-by: tig <585482+tig@users.noreply.github.com>

* New Example: Demonstrates new Fluent API using ColorPicker

Conditional compilation (`#if POST_4148`) to support both a new Fluent API and a traditional approach for running `ColorPickerView`. The Fluent API simplifies the application lifecycle with method chaining and automatic disposal, while the traditional approach retains explicit lifecycle management.

Refactor `ColorPickerView` to support both approaches:
- Add an `instructions` label for user guidance.
- Replace `_okButton` and `_cancelButton` with local `Button` instances.
- Use a new `ColorPicker` with enhanced styling options.

Add a warning log for WIP issue (#4148) in `ApplicationImpl.Run.cs` to highlight limitations with non-`Toplevel` views as runnables.

Update `Terminal.sln` to include the new `FluentExample` project with appropriate build configurations.

Improve code readability with verbatim string literals and better alignment/indentation.

* Introduce `RunnableWrapper` for making any View runnable

Added the `RunnableWrapper<TView, TResult>` pattern to enable any
`View` to be run as a blocking session with typed results, without
requiring inheritance from `Runnable<TResult>` or implementation
of `IRunnable<TResult>`.

- Added `RunnableWrapperExample` project to demonstrate usage.
- Introduced `ApplicationRunnableExtensions` and `ViewRunnableExtensions`
  for clean, type-safe APIs to run views with or without result extraction.
- Updated `CodeSharingStrategy.md` to document reduced duplication
  using `#if POST_4148` directives.
- Added `RunnableWrapper.md` with detailed documentation and examples.
- Created runnable examples in `Program.cs` showcasing various use cases.
- Improved maintainability by reducing code duplication by 86% and
  increasing shared code by 264%.
- Gated all new functionality behind the `POST_4148` feature flag
  for backward compatibility.

* Simplified `#if POST_4148` usage to reduce duplication and improve clarity. Refactored `RunnableWrapper` to use a parameterless constructor with `required` properties, ensuring type safety and better lifecycle management. Updated `AllViewsView` with new commands, improved generic handling, and enhanced logging.

Refactored `ApplicationRunnableExtensions` and `ViewRunnableExtensions` for cleaner initialization and event handling. Enhanced `TestsAllViews` to handle required properties and constraints dynamically. Updated documentation to reflect new designs and provide clearer examples.

Improved overall code readability, consistency, and maintainability while leveraging modern C# features.

* Update docfx documentation for IRunnable architecture

- Updated View.md with comprehensive IRunnable section
  - Interface-based architecture explanation
  - Fluent API patterns and examples
  - Disposal semantics ("whoever creates it, owns it")
  - Result extraction patterns
  - Lifecycle properties and CWP-compliant events
  - Marked legacy Modal Views section for clarity

- Updated application.md with IRunnable deep dive
  - Key features and benefits
  - Fluent API patterns with method chaining
  - Disposal semantics table
  - Creating runnable views with examples
  - Lifecycle properties and events
  - RunnableSessionStack management
  - Updated IApplication interface documentation

- Updated runnable-architecture-proposal.md
  - Marked Phase 1 as COMPLETE 
  - Updated status to "Phase 1 Complete - Phase 2 In Progress"
  - Documented all implemented features
  - Added bonus features (fluent API, automatic disposal)
  - Included migration examples

All documentation is now clear, concise, and complete relative to Phase 1 implementation.

Co-authored-by: tig <585482+tig@users.noreply.github.com>

---------

Co-authored-by: Tig <tig@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: tig <585482+tig@users.noreply.github.com>
2025-11-21 16:01:16 -07:00

144 lines
3.8 KiB
C#

// Fluent API example demonstrating IRunnable with automatic disposal and result extraction
using Terminal.Gui.App;
using Terminal.Gui.Drawing;
using Terminal.Gui.ViewBase;
using Terminal.Gui.Views;
#if POST_4148
// Run the application with fluent API - automatically creates, runs, and disposes the runnable
// Display the result
if (Application.Create ()
.Init ()
.Run<ColorPickerView> ()
.Shutdown () is Color { } result)
{
Console.WriteLine (@$"Selected Color: {(Color?)result}");
}
else
{
Console.WriteLine (@"No color selected");
}
#else
// Run using traditional approach
IApplication app = Application.Create ();
app.Init ();
var colorPicker = new ColorPickerView ();
app.Run (colorPicker);
Color? resultColor = colorPicker.Result;
colorPicker.Dispose ();
app.Shutdown ();
if (resultColor is { } result)
{
Console.WriteLine (@$"Selected Color: {(Color?)result}");
}
else
{
Console.WriteLine (@"No color selected");
}
#endif
#if POST_4148
/// <summary>
/// A runnable view that allows the user to select a color.
/// Demonstrates IRunnable<TResult> pattern with automatic disposal.
/// </summary>
public class ColorPickerView : Runnable<Color?>
{
#else
/// <summary>
/// A runnable view that allows the user to select a color.
/// Uses the traditional approach without automatic disposal/Fluent API.
/// </summary>
public class ColorPickerView : Toplevel
{
public Color? Result { get; set; }
#endif
public ColorPickerView ()
{
Title = "Select a Color (Esc to quit)";
BorderStyle = LineStyle.Single;
Height = Dim.Auto ();
Width = Dim.Auto ();
// Add instructions
var instructions = new Label
{
Text = "Use arrow keys to select a color, Enter to accept",
X = Pos.Center (),
Y = 0
};
// Create color picker
ColorPicker colorPicker = new ()
{
X = Pos.Center (),
Y = Pos.Bottom (instructions),
Style = new ColorPickerStyle ()
{
ShowColorName = true,
ShowTextFields = true
}
};
colorPicker.ApplyStyleChanges ();
// Create OK button
Button okButton = new ()
{
Title = "_OK",
X = Pos.Align (Alignment.Center),
Y = Pos.AnchorEnd (),
IsDefault = true
};
okButton.Accepting += (s, e) =>
{
// Extract result before stopping
Result = colorPicker.SelectedColor;
RequestStop ();
e.Handled = true;
};
// Create Cancel button
Button cancelButton = new ()
{
Title = "_Cancel",
X = Pos.Align (Alignment.Center),
Y = Pos.AnchorEnd ()
};
cancelButton.Accepting += (s, e) =>
{
// Don't set result - leave as null
RequestStop ();
e.Handled = true;
};
// Add views
Add (instructions, colorPicker, okButton, cancelButton);
}
#if POST_4148
protected override bool OnIsRunningChanging (bool oldIsRunning, bool newIsRunning)
{
// Alternative place to extract result before stopping
// This is called before the view is removed from the stack
if (!newIsRunning && Result is null)
{
// User pressed Esc - could extract current selection here
// Result = _colorPicker.SelectedColor;
}
return base.OnIsRunningChanging (oldIsRunning, newIsRunning);
}
#endif
}