Page Manager is awesome! :-)
It has demonstrated that a lot of what the Panels eco-system does in Drupal 7 will work in Drupal 8, and even moved several of those ideas into Drupal 8 core.
However, it now contains some code that doesn't conceptually belong in Page Manager, either because:
It makes sense that this code is in Page Manager today, because CTools (the proper home for the code in question) didn't exist in Drupal 8 until very, very recently. But now that CTools, Panels and Layout Plugin are starting to come together, it's high time to move everything into it's right place!
We had a meeting on Google Hangouts to discuss this - here are the notes: https://docs.google.com/document/d/18nEhyVZdZwvQjAXz6YhRDyzl1zf3ZvATppS2...
This meta issue will track the issues to add the code to CTools, the follow-ups to refactor in Page Manager, as well as follow-ups in Panels and Layout Plugin to take advantage of the new code. I'm going to create all the CTools issues up-front, but I won't create all the Page Manager follow-ups until they become necessary (otherwise, I'd be creating an unreasonably large number of issues at once :-)).
#2511556: Add BlockVariantInterface (and Trait), and BlockPluginCollection from Page Manager
#2568741: Add EntityView block from Page Manager
#2511558: Add Drupal\page_manager\Plugin\VariantCollection from Page Manager
#2511560: Add Drupal\page_manager\Plugin\VariantAwareInterface and VariantCollection from Page Manager
#2511566: Add an abstract version of Drupal\page_manager\Plugin\DisplayVariant\BlockDisplayVariant from Page Manager
#2511570: Remove Drupal\page_manager\Plugin\PageAwareVariantInterface
#2511574: Refactor after non-controversial code (issue #2511556) is moved to CTools
#2511596: Switch from EventSubscribers to core-style ContextProviders
We will need to add follow-ups as the CTools issues get fixed!
#2511576: Remove dependency on Page Manager
#2511582: Extend BlockDisplayVariant rather than copying code from Page Manager
Comments
Comment #1
dsnopekCreated all the CTools issues and added them to the issue summary.
Comment #2
dsnopekCreated a couple of the Page Manager issues and added them to the issue summary.
Comment #3
dsnopekCreated all the Panels issues and added them to the issue summary.
Comment #4
dsnopekCreated the (probably only) follow-up issue for Layout Plugin and added it to the issue summary. It should now only be Page Manager that will need more follow-ups later on - I think the Panels and Layout Plugin issues are all listed.
Comment #5
dsnopekMinor fixes in issue summary for type-o's and clarity.
Comment #6
dsnopekAdded one more Page Manager issue: #2511596: Switch from EventSubscribers to core-style ContextProviders
Comment #7
Anonymous (not verified) commentedFor me personally I need the simplest possible solution for "managing pages" where I can jsut create a page via UI, choose layout for it an put blocks in it. Having to additionally install CTools for me is totally unwanted.
If this gets done will the Page Manager be able to perform this simple task without CTools? I don't like modules to rely on anoter modules, especially if they have broad code base.
Comment #8
tim.plunkett@ivanjaros sorry, but you just described the functionality of page_manager + panels + ctools.
Comment #9
dsnopek@ivanjaros: We're treating CTools like an incubator for core, ie. things that should probably be in Drupal core but we weren't able to get them there for 8.0.0. We're hoping that we'll be able to continually move things from CTools to core in point relases like 8.1.0, 8.2.0 and so on. So, while CTools will be a necessary dependency for now, we hope that won't be the case forever. :-)
Comment #10
rlmumfordUpdated for split of #2511556: Add BlockVariantInterface (and Trait), and BlockPluginCollection from Page Manager
Comment #11
japerryGet it saved
Comment #12
dsnopek#2511568: Create "context stack" service where available contexts can be registered turned out not to be a dependency of any of these issues, so I'm removing it from this meta (it's still worth doing, though)
Comment #13
dsnopekI'm going to close this. It's done enough that we can just worry about the remaining open issues -- this meta isn't needed to track theme anymore.