Share service
Create or retrieve this service with page.share(**properties). Ruflet reuses the registered service unless you supply a different id.
Example
status = text(value: "Ready to share")
page.add(status)
page.share_text(
"Try Ruflet: https://ruflet.dev",
title: "Ruflet",
subject: "Ruby apps for every screen",
on_result: ->(result, error) {
page.update(status, value: error ? error.to_s : "Share result: #{result}")
}
)
Page accessor
page.share(**props)
Properties
data— Arbitrary value you can attach to the control and read back in handlers.key— Stable identity used to preserve state across rebuilds.
Page convenience methods
Use these one-shot Page calls when you do not need to keep the service object:
page.share_text(text = ..., title: ..., subject: ..., preview_thumbnail: ..., share_position_origin: ..., download_fallback_enabled: ..., mail_to_fallback_enabled: ..., excluded_cupertino_activities: ..., timeout: ..., on_result: ...)page.share_uri(uri = ..., share_position_origin: ..., excluded_cupertino_activities: ..., timeout: ..., on_result: ...)page.share_files(files = ..., text: ..., title: ..., subject: ..., preview_thumbnail: ..., share_position_origin: ..., download_fallback_enabled: ..., mail_to_fallback_enabled: ..., excluded_cupertino_activities: ..., timeout: ..., on_result: ...)
Result and error handling
Client calls are asynchronous. When a method accepts on_result:, handle both callback values: |result, error|. Availability and returned data can vary by platform.
Common service API
The service also supports the common Ruflet control API: attach_handler(event_name, handler), children, emit(event_name, event), has_handler?(event_name), id, merge_props(values = ...), on(event_name, &block), props, runtime_page, runtime_page=, to_patch, type, wire_id, wire_id=.
Use the named methods above for application code; common control methods mainly support event registration, updates, and runtime integration.
Wire reference
- Service helper:
share - Wire type:
share