Owen/control docs p5

[OwenMcDonnell]

Description

SearchBar, Slider and Row example tests and images.

Add tap_at method to flet Tester class.

Summary by Sourcery

Add new test infrastructure and documentation imagery for Row, Slider, and SearchBar controls while extending tester capabilities for coordinate-based taps.

New Features:

• Introduce a tap_at helper on the Python tester API and underlying Flutter tester service to simulate taps at specific screen offsets.
• Add integration tests and golden image generation for Row and SearchBar examples, including animated spacing and wrapping scenarios.

Enhancements:

• Update Row, Slider, and SearchBar documentation to reference new golden images and include simple inline code examples.
• Adjust example scripts for Row and SearchBar to be directly runnable via main guards and align type hints with returned control lists.

Documentation:

• Refresh Row, Slider, and SearchBar control docs to use centralized golden test images, updated captions, and resized imagery for clarity.

Tests:

• Create new integration tests for core Row and material SearchBar examples, exercising layout behaviors and generating screenshots and GIFs for documentation.
• Update Slider integration tests to use coordinate-based taps for event handling screenshots.

[sourcery-ai]

We've reviewed this pull request using the Sourcery rules engine

[cloudflare-workers-and-pages]

Deploying flet-docs with    Cloudflare Pages

Latest commit:	65a4a3c
Status:	✅  Deploy successful!
Preview URL:	https://7e8c401b.flet-docs.pages.dev
Branch Preview URL:	https://owen-control-docs-p5.flet-docs.pages.dev

View logs

[FeodorFitsner]

We have ft.Offset type which can be passed to method args "as is".

[FeodorFitsner]

I think scroll prop can be removed from this example, for brevity :)

[FeodorFitsner]

Use parseOffset() function to parse received Offset object.

[FeodorFitsner]

Remove this debug statement.

[FeodorFitsner]

I'd do just:

var offset = parseOffset(args["offset"]);
if (offset == null) {
  throw Exception("Offset is required.");
}

[ndonkoHenri]

Update docstring, since we now have only one prop.

[ndonkoHenri]

Suggested change

	ft.Row(
	controls=[
	ft.Card(
	shape=ft.ContinuousRectangleBorder(radius=10),
	content=ft.Container(
	padding=5,
	border_radius=ft.BorderRadius.all(5),
	bgcolor=ft.Colors.AMBER_100,
	content=ft.Text(f"Control {i}"),
	),
	)
	for i in range(1, 6)
	],
	),
	ft.Row(
	controls=[
	ft.Card(
	shape=ft.ContinuousRectangleBorder(radius=10),
	content=ft.Container(
	padding=5,
	border_radius=ft.BorderRadius.all(5),
	bgcolor=ft.Colors.AMBER_100,
	content=ft.Text(f"Control {i}"),
	),
	)
	for i in range(1, 6)
	],
	)

[ndonkoHenri]

Suggested change

	var offsetObj = args["offset"];
	var offset = parseOffset(offsetObj);
	if (offset == null) {
	throw Exception("Offset not found: $offsetObj, $offset");
	}
	await control.backend.tester!.tapAt(offset);
	var offset = parseOffset(args["offset"]);
	if (offset != null) {
	await control.backend.tester!.tapAt(offset);
	}

[ndonkoHenri]

Suggested change

	```python
	ft.SearchBar(bar_hint_text="Search...")
	```
	Example:
	```python
	ft.SearchBar(bar_hint_text="Search...")
	```

[OwenMcDonnell]

Are you suggesting this for every small code snippet at the top of a control's doc?
I think with small non-runnable example snippets it's unnecessary to label them as "examples"