corteza: Add support for Compose page block tabs [PlanID:2023.3/8/2.6]

Integrators can configure Tabs block on Compose page. This is accomplished by linking existing record page blocks of any other type. Each linked block represents one tab in the tab block.

The implementation is based on Bootstrap’s tabs.

• Prepare mockups that demonstrate this feature @darh

---

• Page can have multiple tab blocks
• For now, nested tabs are not allowed (block tab with a block tab)
• Tabs are configured right of the “General” tab in the block configuration
• Integrator can use pre-existing blocks (show warning where there are no blocks available)
• New blocks can be added via tab block
• Integrator can change the order of tabs by reordering linked blocks
• Page block rendering logic must be corrected to omit linked blocks when rendering a page
• [When tab block is deleted, page blocks should render those blocks again.
• Blocks can be duplicated via tab block’s configurator
  • Checkboxes are shown
  • Duplicate button should not be disabled once a box is checked
  • Tab should be duplicated and block should be duplicated for all checked boxes
• Implement bootstrap’s properties for <b-tabs>: align, fill, justified, small, pulls, vertical
• By default, 1st tab is active
• When changed, the active tab must be preserved after refresh (store it in URL)
• Linked’s block title is used as a tab title

Phase 2 Requirements

• Each block should have a temp ID and tabbed option in their meta and Switch to using blockID once blocks have been saved
• Making a tab is broken, this should be fixed.
• Tabs should be rendered visually in tabBase
• Edit is broken. This should be fixed.
• Add new block feature is broken, this should be fixed.
• Each Block should have a ‘General’ toggle switch for tabbing blocks
• When a Tab Block is deleted, tabbed blocks should be deleted and should appear on page
• Actual blocks should not be saved in each tab
• Until a Tab block is added to the page, the add button should be disabled
• Deleting a tabbed block out of a tab should not alter the page-rendering logic only when you delete a tab block itself
• Tabbing a block should flip its tabbed switch automatically
• remove tab tracking
• Blocks should not be saved in options
• Change tab interface structure
• remove tabbed options from all blocks
• Remove blockIndex from Tabs block
• Truncate via css alone
• Remove tabbed option from all blocks and use just meta
• Cancelling should undo changes in configurator including adding a block or making a tab or tabbing blocks
• When adding a block in a tab, the tabs option should be disabled in the block selector
• Cross-check method names
• Fix Apply issues in libjs
• Add delete to each block’s configurator except tabs
• Deleting a tabbed block should remove it from any Tabs block
• Update from TempIDs when the page is saved
• Eliminate the tabs mixins
• Refactor the UpdateBlocks method
• Take care of Tabs duplication edge-case
• TempID setting logic should be on the class level
• Refactor Selection disabling logic
• Add a comment to block deleting logic.
• Manually untabbing blocks should remove it from everywhere it is tabbed
• PageBlock Class should have a method to reset tabs for copying and cloning