I very much like the simplicity of this module compared to the panels module. I also recognize that there may be many advantages of using custom region layouts. However, why not just use (or make it possible to use) the regions defined in the theme? It would be like the normal block configuration page but per node.

I would be willing to contribute code, if you could somehow lead me in the right direction.

Marcus

Comments

marcushenningsen’s picture

marcushenningsen commented

Sorry, the last line should have been more like: I'd like to contribute code if you are interested, and I was hoping you could lead me in the right direction.

=)
Marcus

bengtan’s picture

bengtan commented

Hi,

> However, why not just use (or make it possible to use) the regions defined in the theme?

Interesting idea. When I first thought up the idea of Composite Layout, I just never thought about it this way.

I think it's worth exploring and it'll be nice to have, but I'm not sure whether it's doable. There will be a number of practical difficulties and issues to work through.

1) The theme would have to explicitly support Composite Layout by having enough regions defined so that users have flexibility to choose between 2 and 3 column layouts (not to mention any arbitrary custom layouts the users may have created themselves).

2) I'm not sure if there is a clean way to code this.

3) Block (and region) configuration tends to be global or per-theme, while Composite Layout configures per node. This needs to be reconciled somehow.

These are the ones I can think of at the moment. If you'd like to pursue this idea, I'd be happy to provide discussion and feedback. I'm just not quite certain it's feasible at the moment.

Alternatively, perhaps you want a completely new module 'Regions by node' that configures regions on a per-node basis. It could use the same techniques as Composite Layout, without necessarily being part of Composite Layout. And later we could merge the two into one (if feasible).

bengtan’s picture

bengtan commented
Title: Theme regions instead » Composite Layout should configure regions instead

Changing title to be more accurate.

marcushenningsen’s picture

marcushenningsen commented

Hi bengtan,

thanks for the comments. Unfortunately, I'm not a very skilled programmer, but I would love to dig into this.

If Composite Layout (or perhaps a new module) just used the regions defined in the theme, I don't see how the theme has to support Composite Layout. The module should just "ask" the theme which regions exist and then provide the same drag and drop layout as for the block administration, i.e. all available regions stacked vertically. You would then loose the nice layout where you actually see which regions is left and which is right, because that would then be controlled by the theme's css.

I don't see it should be a problem that blocks would be defined per node. In fact, you can do this already by configuring a block on the block administration on the fieldset "Page specific visibility settings". However, configuring this on the page would make much more sense for users.

I'm a bug fan of the Context module as well, and blocks defined there don't conflict with blocks defined by the normal block administration and vica versa. Hence, it should be doable to have a third module add to this.

I'll try to take a look at it and report back with my findings. I have little hope, though, that I'll get far without help.

Marcus

bengtan’s picture

bengtan commented

Hi Marcus,

> but I would love to dig into this.

No problem. Everyone starts somewhere, so let's just see where this leads.

The more I think about this, the more I think you're looking for a new module altogether (or at least, a totally new feature which may or may not necessarily be part of Composite Layout) to configure the allocation of blocks to theme-defined regions on a per-node basis. Let's call this feature RLN (Regions Layout by Node). Whether it becomes a separate module or not, we shall see.

I'm not sure whether RLN is technically possible, but past experience would suggest there's a good chance it is. We won't know until someone examines it deeply.

I don't think RLN should replace the existing CL (Composite Layout) functionality, because it would be a step backwards in most cases ie. for non-CL-aware themes, you'd lose the existing 2 and 3 column layouts.

> I'm a big fan of the Context module as well

I'm not familiar with the Context module, but maybe it's worth seeing how it does things inside.

bengtan’s picture

bengtan commented
Status: Active » Closed (won't fix)

Expiring this issue as it is old and uncertain whether it is still applicable.