MMM-Carousel; Two of the Same Module?

sdetweil

@JeffreyDaro i don’t know carousel very well, but it uses module names as class names… you could give another class for an instance with the classes:“someodd_string”,
attribute on the module, and then use THAT string in the carousel config…

I mostly use MMM-Pages, and i have documented another way to use it with the classes attribute, see the doc in my fork for the second method
https://github.com/sdetweil/MMM-pages

i think my ‘page1’,‘page2’ … approach will work the same with carousel…

JeffreyDaro

@sdetweil, thank you…I will give that a try.

KristjanESPERANTO

@JeffreyDaro That’s possible with MMM-Carousel. Look for carouselId in the README file :-)

JeffreyDaro

@KristjanESPERANTO Thank you for responding. I started working on the carouselID’s but I am struggling a bit to get that to work.

I was experimenting with both classes and carouselID:

{
            module: "MMM-Carousel",
            position: "bottom_bar", // Required to draw in position
            config: {
                mode: "slides",
                ignoreModules: ["MMM-GooglePhotos"],
                transitionInterval: 40000,
                slideTransitionSpeed: 3000,
                slides: {
                    main: ["clock", "weather"],
                    "slide2": ["clock", "weather", "compliments"],
                    "slide3": ["clock", "MMM-NFL"],
                    "slide4": [{ name: "calendar", carouselId: "cal1", classes:"cal1" }, "MMM-NFL"],
                    "slide5": [{ name: "calendar", carouselId: "cal2", classes: "cal2" }, "weather"]
                }
            }
        },

And as an example, my first calendar on the screen…

{
            module: "calendar",
            carouselId: "cal1",
            classes: "cal1",

And my second…

{
            module: "calendar",
            carouselId: "cal2",
            classes: "cal2",

KristjanESPERANTO

@JeffreyDaro The carouselId has to be in the config part. Like this:

{
      module: "calendar",
      position: "top_right",
      config: {
      	carouselId: "cal1",
      	...
      }
    },
    {
      module: "calendar",
      position: "top_right",
      config: {
      	carouselId: "cal2",
      	...
      }
    },

JeffreyDaro

@KristjanESPERANTO,

Thank you! That was the issue. My eye did not catch that in the documentation. I appreciate your time and your patience.

JD.

dathbe

Is there any functional difference between MMM-Pages and MMM-Carousel? I’m using Carousel, but just stumbled across Pages and am wondering if the grass is greener on that side…

sdetweil

@dathbe roughly the same . the buttons are a separate modules

and because it uses classes , the duplicates are easier

sdetweil

@dathbe I like the flexibility of pages, you can use the module classes: property
outside the module config for multiple instances of the same module
(and use the same value in custom.css selectors)

I updated the doc on how to use a fixed page name structure

“page1”,
“page2”,
“page3”

and use those values in the classes: of the modules you want to group together

I always had trouble remembering, is THIS module on page 2 or 3?
have to go back and look at the config(using module names)
and then back down, lose my place, repeat

now the module itself lists the page its on…
no id’s, no weird settings,

my forks of pages, Carousel and ModulesGroupsRotation all provide a property to have different display times for different pages.

and the page name can be anything

Mom, Dad, joe, finance, power mgmt, … so it helps you organize the data (me at least)

dathbe

@sdetweil I like the idea of scheduling display times for pages.

Most of the rest of this it seems like I can do with Carousel–including giving the pages sensible names, and labeling certain modules to correspond with those pages–if, perhaps, in a bit more clunky way.