Ticket to track low-complexity / "cosmetic" follow-up tasks on the browser extension not covered by the original implementation ticket #1
Implement "Show all" functionality
a) show all current browser tabs in the Browser to Canvas tab (to easily close already open and synced tabs)
b) show all current canvas tabs in the Canvas to Browser tab (to manage tabs stored in Canvas even when they are already open in the browser)
Add shift+click-select functionality(or a tickbox) to open only selected tabs in C2B / close or remove only selected tabs in B2C, this implies having additional buttons in the extension popup besides "Open All" and "Sync All" (or dynamically switch the button label to "Open Selected" and "Sync Selected" + "Remove Selected" and "Delete Selected" in the C2B tab
Add "pin tab" functionality to the browser to canvas pane so that switching context when autoupdate tabs is set won't automatically close a pinned tab (you may have some tabs that you want to keep cross-context)
~Add either a tab or a windows border color to all tabs of a context if a context workspace color is set (there is a example extension in the ff ext repo doing just this but maybe there are better options available)~
Summary for the "Settings" menu update
Lets keep the settings as simple as possible
1) We don't need that accordion there, feel free to remove it
2) We don't need any filtering based on browser because we'll have tags, should be more than enough. I am internally indexing what app data is coming from anyway(you are adding the browser name to meta - this we should keep)
3) Pinned tabs are not setting-depended, a user can pin any tab that's currently open in the browser. A pinned tab would not get opened, closed nor synced automatically (lets say, a youtube lecture/music player you want to keep even if switching contexts)
Settings menu
Browser identity
Tag tabs from this browser: string
If set, all insert ops would additionally have featureArray['data/abstraction/tab', 'custom/tag/foo' ]
Sync only tagged tabs: boolIf False, always fetch all tabs from the whole context(as we do currently), maybe show a small tag sticker for tabs that are tagged for our browser if a browser tag is set; if True, call getDocuments with ['data/abstraction/tab', 'custom/tag/foo' ] which will only return tagged tabs (this feature will be great!)
Context sync settings
Automatically open tabs on context change: bool
Handle existing tabs on context change:
Close
Save and Close
Keep
Connection settings
Protocol: string
Host: string
Port: number
Auth token: string (Password field for the user token)
Pin browser to Canvas session: string (Defaults to "default")
Internally, you always call session:create, followed by session:context:get, you can just take whatever is listed there, will handle edge cases on the backend
Ticket to track low-complexity / "cosmetic" follow-up tasks on the browser extension not covered by the original implementation ticket #1
Implement "Show all" functionality
Add shift+click-select functionality(or a tickbox) to open only selected tabs in C2B / close or remove only selected tabs in B2C, this implies having additional buttons in the extension popup besides "Open All" and "Sync All" (or dynamically switch the button label to "Open Selected" and "Sync Selected" + "Remove Selected" and "Delete Selected" in the C2B tab
Add "pin tab" functionality to the browser to canvas pane so that switching context when autoupdate tabs is set won't automatically close a pinned tab (you may have some tabs that you want to keep cross-context)
~Add either a tab or a windows border color to all tabs of a context if a context workspace color is set (there is a example extension in the ff ext repo doing just this but maybe there are better options available)~
Summary for the "Settings" menu update
Lets keep the settings as simple as possible
1) We don't need that accordion there, feel free to remove it 2) We don't need any filtering based on browser because we'll have tags, should be more than enough. I am internally indexing what app data is coming from anyway(you are adding the browser name to meta - this we should keep) 3) Pinned tabs are not setting-depended, a user can pin any tab that's currently open in the browser. A pinned tab would not get opened, closed nor synced automatically (lets say, a youtube lecture/music player you want to keep even if switching contexts)
Settings menu
Browser identity
Context sync settings
Connection settings