Whilst this is probably a silly thing for a person who wouldnt know javascript if it jumped up and bit him, and only knows a tiny bit more about php and CSS, I think that including display mode within a snippet serves to complicate it and potentially add future compatability problems.
Although I’ve yet to try MaxiGallery 0.5 with the new templating features (i fear they look way too complex for me) I think that using templates to define how a gallery is displayed, via javascript toys or otherwise, makes MaxiGallery more modular, which would allow the snippet to grow more fluidly (providing the opportunity for community developed display modes for example). Although I’m a new, it is far less daunting to develop small segments than having to investigate a key snippets core code.
Equally however, I realise that part of MaxiGallerys charm is in its abilty to make use of such funky display modes - and again, as a non-programming, non-designing new person(!) - this holds great appeal, it would be great if the code that currently exists to govern display could be exploded out into such "templates"
From a personal point of view I’m very keen on seeing the functional side of MaxiGallery expanded so if moving to a template orientated system could take some of the burden off doze i think thats a positive move.
Steve
BTW the Slideshow script mentioned is very cool!