Manage editor lifecycle and multi-view attachments for Pulp plugin adapters.
npx skills add https://github.com/danielraffel/pulp --skill view-bridge
Please help me install this Agent Skill. Skill: view-bridge Source: https://github.com/danielraffel/pulp/tree/main/.agents/skills/view-bridge Command: npx skills add https://github.com/danielraffel/pulp --skill view-bridge
This document captures the lifecycle invariants, ownership rules, and adapter responsibilities required to correctly open, attach, resize, and close editor views for Pulp plugins so hosts and plugins avoid resource leaks, duplicated processors, and dangling pointers.
Open the ViewBridge documentation and implement the open then notify_attached then resize then close protocol when overriding Processor::create_view or building a new adapter.
High-intent search queries and answers about installing and using this skill.
To manage the plugin editor lifecycle safely, implement the open then notify_attached protocol before resizing and closing views. This two-step process guarantees balanced on_view_opened and on_view_closed calls, preventing resource leaks and duplicated processors across format adapters.
The two-step open and notify_attached protocol requires adapters to call open() followed by notify_attached() when creating plugin UI views. This sequence ensures balanced lifecycle callbacks and safe attachment of secondary views before any resizing or closing operations occur.
To safely transfer ownership of a secondary view, use the release_view function to hand the view to container widgets. The caller must keep the view alive until bridge.close() is invoked, preventing dangling pointers during the plugin editor lifecycle.
Yes, the Pulp view bridge supports AU v2, AU v3, CLAP, VST3, and Standalone format adapters. It provides per-format attach points, common pitfall guidance, and test references for implementing create_view, release_view, notify_attached, resize, and close functions.
Duplicated processors occur when the plugin editor lifecycle protocol is unbalanced. Adapters must follow the open then notify_attached sequence and use release_view for safe ownership transfer, ensuring remote views and inspectors attach without duplicating processor instances.
Yes, you can attach inspectors and remote views using the Pulp view bridge lifecycle. It describes view roles, the Phase 4 remote-view protocol, and associated tests to ensure secondary and remote views attach correctly while maintaining lifecycle invariants.
Generous-CorpCoordinate editor lifecycle and view attachment protocols for Pulp audio plugins.
Generous-CorpConfigure and validate ARA SDK integration within Pulp audio plugins.
wecode-aiOutput Markdown links using attachment:// and wegent:// protocols for attachments and Wegent pages.
Generous-CorpIntegrate WebView-based UI panels into the Pulp framework with native bridge communication.
