Seeking advice on suitable module
Posted: Fri Jan 02, 2015 6:48 am
I'm looking for some advice on a suitable module to satisfy the following requirements: Essentially what I am trying to create is the ability for someone to add slides and layers for a Layer-Based Slider.
-Each slide would have it's own set of field definitions.
(eg. bg image, link, speed, transition, bgpositoin, bgfit, etc.)
-Each layer would have it's own set of field definitions.
(eg. start, end, easing, x-pos, y-pos, etc.)
-Each layer could be a child of any slide
I have already implemented something like this using ListIt2 and ListIt2 Xlink to link an LI2 instance of Slides and an LI2 instance of Layers, but I'm not that thrilled with the solution.
My other thought was to just build a hierarchy of pages to act as slides, with child pages acting as layers. A slide page would use a specific template containing content blocks acting as field definitions, and a layer page would use a different template containing content blocks acting as the field definitions pertaining to layers. This would be better than the LI2 solution, but I would rather use a module than the core page functionality if at all possible.
I also looked at the cataloger module which I believe is perfectly suited to this purpose, except there are quite a few bugs with it, and it hasn't been updated in a while.
Any other suggestions?
-Each slide would have it's own set of field definitions.
(eg. bg image, link, speed, transition, bgpositoin, bgfit, etc.)
-Each layer would have it's own set of field definitions.
(eg. start, end, easing, x-pos, y-pos, etc.)
-Each layer could be a child of any slide
I have already implemented something like this using ListIt2 and ListIt2 Xlink to link an LI2 instance of Slides and an LI2 instance of Layers, but I'm not that thrilled with the solution.
My other thought was to just build a hierarchy of pages to act as slides, with child pages acting as layers. A slide page would use a specific template containing content blocks acting as field definitions, and a layer page would use a different template containing content blocks acting as the field definitions pertaining to layers. This would be better than the LI2 solution, but I would rather use a module than the core page functionality if at all possible.
I also looked at the cataloger module which I believe is perfectly suited to this purpose, except there are quite a few bugs with it, and it hasn't been updated in a while.
Any other suggestions?