silverstripe-issues
commented
11 years ago comment by: @chillu (ischommer) created at: 2012-05-09
Started working on this as a followup on completing http://open.silverstripe.org/ticket/7261 . Basic idea is to use a TabSet through LeftAndMain->ContentTabs(), extend the core Tab class with setLink(), custom template support, and configurable attributes - as we need all three for the lazy loading tabs. We already have a CMSTabSet.ss template which just renders the tab nav menu, not the content (which is taken care of by LeftAndMain_EditForm.ss). Depending on how much markup changes we can accommodate easily, we might need a second template extending TabSet.ss.
tractorcow
created by: @sminnee (sminnee) assigned to: @chillu (ischommer) created at: 2012-05-03 original ticket: http://open.silverstripe.org/ticket/7268
Right now the top level tabs in the CMS (Content, Settings, History) are hardcoded.
We should have an API for adding new ones. Note that, right now, the Content and Settings tabs are coming from different field lists, and that's fine. There should just be some kind of overridable method on SiteTree that returns a list of the tabs, and their corresponding Ajax URLs.
Ideally, creating a simple new tab would only require defining a field list method, and not a complete Ajax action.
Marking as a critical enhancement as it will be awkward if this isn't available in 3.0 and people start hacking their own solutions.