Hey Sam,

as promised right after the "Panels API" at the Drupalcon 2008 Szeged, here my suggestion as an issue:

Defining and building a common, reusable mechanism for modules such as Panels and Views to enable to configuration "code" developed by building Panels/Views via the UI to be managed in an SVN/CVS software-dev environment and to be integrated into a staging/deployment process properly.
This could be for example achieved by "synchronising" the panels (or viewS) config code with a version stored on disk (auto-export /-import?!) or by chosing to store it to the disk from the beginning on.
Such a mechanism can/should be commonly available as some kind of smallest-common-denominator API for use by many "coding through config" modules such as Panels and Views (and others) and would thereby help drupal to get more enterprise ready.

i know this is far down your priority list and needs syncing with the needs of other big module maintainers, but should be kept on the long range radar and may possibly get more acute some day... so starting now to thinking about the proper way to do that ("in the back of your heads") and/or addressing this issues with heavy-duty-users for getting their opinion could pay off later ...

cheers,

daniel

Comments

merlinofchaos’s picture

merlinofchaos commented

I'm not entirely sure what we could do more generically than we do now. I suppose Panels and Views could put their heads together and create a generic import/export mechanism because there is a lot of common code, and by doing that other modules could do it. The panels_export module could then work with any module that utilized this library.

But each module would still have to define its own import/exports.

As you said, not a high priority, but could be an interesting project for someone.

tannerjfco’s picture

tannerjfco commented

I think this would be very helpful for anyone using SVN to manage their projects. The macro module works well for keeping track of any changes made in configuration, but it doesn't work with views or panels (in fact it breaks if you make a panels change). Something like this would make it easy to fill that gap that macro can't fill right now (though getting macro to work with them would be great!)

drewish’s picture

drewish commented

Subscribing. I think views exporting allows this to work very well. I haven't had similar luck with panels though. The exporting seems to be one of the unfinished parts of the code.

merlinofchaos’s picture

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

Panels 2 is no longer available and is unsupported. Marking all Panels 2 issues won't fix.