SRL Archive - Suggestions

Byproduct of this thread: http://villavu.com/forum/showthread.php?t=62494

Okay here are 4 versions of my ideas, they may or may not be possible. 2 full size, 2 slimline.

Added features:
-Changelog box -> Of course shows the change log of the latest reversion
-Rollback -> Roll back to a specific reversions (IMO is would be VERY useful)

Also in the mind concept with the rollback drop down, the change log box would then change to the change log of the selected reversion.


What do you think? :)

Oh yeah, and I cleaned up the title bar.

Yes I know they are a bit messy, i threw them together really quickly in paint so not everything is lined up as well as it could be :p

Number 4, WITH an little down pointing arrow button which will reveal the change log.
Love it, perfect.

I'd like #4 as well, but instead of showing the rollback button it may be better to have an expanded options button to show rollback and changelog. (and you could have it remember whether the user has it simple or expanded).

Oo absolutely! I remember reading something Wizzup said about it being a huge pain to have change logs though.

I like the on with the change log box and roll back option.

The change log hopefully wouldnt be TOO hard. We could always get it to read from a webfile with anchors to different sections.

From: Hobbit
The change log hopefully wouldnt be TOO hard. We could always get it to read from a webfile with anchors to different sections.

Whatever works. I agree obviously. I suggested something like that here.

Remember that upload simply uses snapshots from the last srl/ref/msi. It DOES NOT call git or subversion or whatever. The ``revision numbers'' are also meaningless. For MSI, they are the number of commits + a static number since Coh3n did the switch to git without importing from svn. For srl / ref they are the amount of commits to git. BUT git doesn't work with versions so there's no real way to relate a commit to a number.

The auto updater was made for convenience, mainly for leechers. If you want to do real developing you should really just use git (or subversion, if it's a svn repos)… I suppose the changelog can be added, but rollback isn't really possible unless you start using git hashes instead of numbers, and even that is not easy on it's own, let alone creating the git commits for each users.

Rollback is possible, but really not worth the effort. Why would you want to rollback?

I support Hobbit's idea, but in respect to the include updaters, it would mean Wizzup would have to mirror *all* of the repos information. It could probably be done through a redirect to github though too per tag (since github already stores the tarballs).

Perhaps all this would take would be a webscript checking for new tags, then it could get the log information (there's git python hooks available) then create a nice output to have a script parse for the changelog information. Store it all in a directory with the name of the tag. Then, redirect those who try to get the tarball to the github link, then the change log information would also be present in that folder.

Again.. all just ideas. :) No real information pertaining to implementation here.

I like 1 if we cant have roll-back and 2 if we can.

they look very nice, good work :)