Closed (fixed)
Project:
Panels
Version:
7.x-3.x-dev
Component:
Plugins - layouts
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Aug 2010 at 23:47 UTC
Updated:
2 Dec 2011 at 21:10 UTC
Like many other innovations originating in Panels, layouts are potentially applicable elsewhere. I've been looking at how Context could support Panels layouts, #888298: Support Panels-style layouts.
Thoughts about whether it makes sense to pull layouts into ctools (or elsewhere)?
Comments
Comment #1
merlinofchaos commentedOnce you've got layouts in CTools you've not left Panels much to do. =)
Seriously though, I think changing the owning module of the layouts would be a bit of a strain on people updating, since it would require changing the ctools_plugin_directory function (or .info code) for any one currently providing layouts. The only value is that it would let some modules use the layouts without having Panels, but CTools itself wouldn't actually do much with layouts, and I suspect that means we'd have to slip more and more support code over to the CTools side.
So I'm probably not likely to do this.
Comment #2
sdboyer commentedThis could be 'faked'. Sorta. It'd be a little ugly, but since the namespacing for module owner and plugin type is separate, Context could just implement a plugin type called 'layouts' that works in exactly the same way as the Panels ones, and...well, it'd be nasty, but it could just work. So no real dependency.
Comment #3
nedjoYep. Mainly I'm thinking we should try to standardize on a layout plugin API. Currently we have Panels, Context, Composite Layouts, and possibly others each defining layout plugins that themes and/or modules can provide. They're all basically similar (a template, region names, css and js files...) and there's not a lot to be gained by module and theme developers having to supply various different plugin formats for the same thing. Panels is the most used and known and so seems the most likely starting point.
Comment #4
davidburnswasn't there supposed to be a subscribe link for individual issues?
subscribe +1
Comment #5
itserich commentedsubscribe
Comment #6
Letharion commentedSince there hasn't been any discussion for a full year, I'm just gonna close this one. Feel free to re-open if you have something new to add.