Workspaces

Hi Sergii,

There is no such features as of yet. I'll add this to our TODO list.

Just to be sure, you'd like the sessions in the broadcast channel to be remembered and re-added to it when you open them back?

Best regards,

Hi Xavier,

yes, application remembers the state and recreates using some kind of profile or workspace item.

Things to remember - open sessions, position of these sessions(split screen, new tab, etc) and broadcast input toggles

Thanks!

Hi Sergii,

The opened sessions should already be remembered. When you quit RDM leaving sessions open, the next time you start RDM should prompt you if you want to relaunch those session.

Remembering broadcast status shouldn't be too much work, but remembering position might require a bit more time. I'll add this in the TODO list though.

Best regards,

Cool, thanks!

Hi Sergii,

I have some more questions for you, if it would not bother you.

I've been looking into implementing this and while I was doing this I came across some interrogation.

How I started to go about, I was going to remember (in a file) for each data source when the broadcasting was enabled on a session (and for which session) and that, until the user disable it manually. So if it was checked on, each successive time the session would have been open, the broadcasting would be turned on.

But re-reading your message, I realize that would be quite limited (and quite difficult to implement for the split position of sessions thereafter). How I see it now, you'd like to have a way to remember "templates" (let's call it so for now) containing the currently opened sessions, their position and their broadcasting state. A bit like our Playlist entry works, though this only launch a collection of sessions, nothing about their placement or broadcasting state.

This second feature would be a bit more complicated for the broadcasting, but a lot less complicated for the placement of sessions (split + undocked view) and would offer a better versatility since it would offer you the possibility of multiple "templates" for different purposes.

In the end, you're the user. Which of those better fits your workflow?

Best regards,

Hi Xavier,

Sorry for the late response,

What if we do not remember current state and have a wizard for a new "workspace"

maybe it is too much to ask, but that's how I see it:

- Each "workspace" is a separate window.

- In workspace settings there are sessions and a checkbox if this session participates in broadcasting

- Positioning should be simple - either every session is a separate tab, or all the sessions on the same screen. In this case application arranges windows automatically, just make tiles that fit into the window

What is gives us: all workspaces are independent and isolated. Also they could be run simultaneously, so multiple workspaces support.

Does it make sense? Let me know if you need more info on that. Thanks

Hi Sergii,

This is interesting. Though to create a new "workspace", I though more about a Save new "workspace" menu item that would take currently opened sessions of selected window, their split state, their size and broadcasting status. When "launching" a workspace, it would launch all sessions and place them accordingly. I think this could make it a bit more versatile than just a wizard, while I could still add a wizard too.

I could look into implementing split screen for the undocked (external) windows. Which would allow an embedded and external mode for the "workspace", in both case organizing sessions in a split-able container, either in the Main Window or in a new undocked window.

What do you think?

Best regards,

Cool, makes sense. Thanks!

BTW, I can participate in any beta testing if there is any?

Nice, thanks