How about using the marvelous drag and drop interface the .module API to bring ANY type of node into a new order? Because currently, changing the weight of articels is quite a tedious task.

A generic (play)list_node.module would let me tick on in admin/setting any content type I might want to rearrange. The output could tie into views and/or import/export.

Does this make sense? Can't contribute (as not a coder), but might be able to sponsor (at least a bit).

Comments

hubrt’s picture

hubrt commented
Title: generic playlist_node.module » add on: generic playlist_node.module

would be a nice example module for the playlist.module API, too. As audio_playlist is pretty complex.

zirafa’s picture

zirafa commented

I would be interested in working this in if there is enough interest/sponsorship. Perhaps this could help modularize things more - I've been thinking that audio_playlist is waaaayyy too big as it is...

Maybe something like:

playlist.module (handles raw database/queries)
generic_playlist.module (handles any node type(s) you choose)
audio_playlist.module (handles audio nodes only)