Yes, happy for this to be added.

I've had a brief look at Niri's IPC and it looks like it's missing events, which would make this tricky. Without those, Ironbar would have to constantly poll Niri to find the focused workspace, as it won't be notified of changes. I might be missing something though.

Assuming that can be resolved, the rest shouldn't be too hard, especially since Niri provides rust types for its IPC. Effectively entries would need to be added to the compositor client code to spawn a Niri client here and a new client would need to be written which implements the WorkspaceClient trait

Lines 142 to 148 in 6a06fa5

    
           pub trait WorkspaceClient: Debug + Send + Sync { 
        
               /// Requests the workspace with this name is focused. 
        
               fn focus(&self, name: String) -> Result<()>; 
        
               /// Creates a new to workspace event receiver. 
        
               fn subscribe_workspace_change(&self) -> broadcast::Receiver<WorkspaceUpdate>; 
        
           }

	pub trait WorkspaceClient: Debug + Send + Sync {
	/// Requests the workspace with this name is focused.
	fn focus(&self, name: String) -> Result<()>;

	/// Creates a new to workspace event receiver.
	fn subscribe_workspace_change(&self) -> broadcast::Receiver<WorkspaceUpdate>;
	}

Support Niri out of the box #650

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions