A wp-native approach would mean f.e. a sliders custom post type with 1-3 postmeta entries (for itself, slides and elements) with values saved in an array. A many post type approach would even make slides and elements reusable between different sliders. I’m proposing this mainly because having to deal with additional tables in an multisite-setup is a big plugin-drawback. In my opinion additional tables are only justified in cases where the data relationship is to complex to be saved in a native manner and/or for obvious gains in query performance. I think none of this is the case here so, why not? I write the ajax, you the post type/ backward compatibility part? =)
A wp-native approach would mean f.e. a sliders custom post type with 1-3 postmeta entries (for itself, slides and elements) with values saved in an array. A many post type approach would even make slides and elements reusable between different sliders. I’m proposing this mainly because having to deal with additional tables in an multisite-setup is a big plugin-drawback. In my opinion additional tables are only justified in cases where the data relationship is to complex to be saved in a native manner and/or for obvious gains in query performance. I think none of this is the case here so, why not? I write the ajax, you the post type/ backward compatibility part? =)