Hello, for some weird purpose, I would be able to create compositions using composite, without attaching it to a node.

It would be the same paradigm that layouts. As you can create and expose layouts with your custom modules, I would like to be able to create and expose default compositions -I.E. filled with already set blocks/data (references) to some regions- and save it in order to prepopulate node forms later.

Is it doable? I'm ready to write a loooot of code if needed; If this feature seems interesting to you, let's talk about the right paradigm how to implement it.

I would like that compositions are totally separated from node, they had their own id until a user attach it to a node. I would like that these compositions being exportable (with any kind of optional features module integration, preferably without using ctools).

Each composition would be clonable, disable-able, override-able.

Also, if this module could have an OOP oriented API, or a better separation between code parts, would be great for other's modules integration, with CRUD operations for all "types", by types, I mean: "layouts", "references" and "compositions" (links between a layout, its regions, and a set of references).

Comments

bengtan’s picture

bengtan commented

Hi,

There is already a 'Composite Layout Sets' functionality which overlaps somewhat with what you have suggested. If you visit the Zones tab of a Composite-enabled node, have a look at the 'Layout sets' options under Tasks.

Admittedly, the UI for this isn't the best ... because when I wrote it, I didn't want to include yet another handful of administration/configuration pages.

Maybe have a look at this feature and see how it informs what you are trying to do?

On a general note, I'm open to suggestions about improving or adding new features although I may not have much time to do it. Each 'feature request' would be considered on its own merits.

pounard’s picture

pounard
Primary language French
commented

Yep, may be I'm asking too much. In fact I did put a whole bunch of ideas here to find it back and do "atomic indenpendent feature requests" later.

A layout builder/saver/exporter would be the really first one I need, and this could easily be a separate module; But I really need your module to have stable API in order to do this.

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.