[Digital Jedi]

Originally Posted by Paul M

I really want to avoid any more significant changes to vb.org code, its already complicated enough, and with one eye on eventually upgrading, its not helpful to add more complication.

JFYI, Ive been thinking about an idea based on a system we already have. At the moment you can define a modification as being an add-on to another, so it becomes like a child, and when you view the main mod, its add-ons (children) are displayed. This system is not perfect as the child mod does not list its parent (due to the way it works).

What id like when I have the time is to re-do that system so it works both ways (a parent mod lists its children, a child mod lists it parent), and also try and use the same (or similar) system to link different (major) vb versions of the same modification - so if you viewed the 3.8 version of a mod, it would list the 3.6, 3.7 and 4.0 versions as well as any add-ons.

It might even be possible to then send an e-mail when a new (higher version) link is added. So if you add a new link to your 3.8 mod, for the 4.0 release, it sends out a notification, but if you add a link to an older version (like 3.7), no notification is sent.

Anyway, just something ive been thinking about for a while, no idea if / when I will have time to actually do it.

You know, I've been meaning to suggest that.

Hey! Can we opt out of getting any posts that ask if a vB 4 version is ready/in the works/a general timeline on when it will be done? Just sayin'... >_>