General version control dicussions

I’ve made something similar with svn, but now I’ve changed my mind.
If I ever start a project with the need of versioning and localization (l10n) I’d definately use Monotone http://monotone.ca/
The advantage is that is saves everything in one or more database files, it is so much better, but I think you can inform yourself about it on its homepage.

I would use extra tables for each language to enable localization, so everybody who authors a page can choose (dropdown etc.) the language then the localizion (ie.: en-us->Texas).
The versioning part is way more complex.
First, every change on pages can be automated by schedule and/or commited manually when needed by RPC to the monotone database (not a (my)sql db, but maybe possible ).
Usually this is very hard to code yourself, but thanks to [remote/or not] (PHP)XML-RPC, which is even built in(!) since PHP 5.2 it can be accomplished much easier.

@rthrash this is the way I go around the servers who don’t support my sweet monotone. Sounds simple, for experienced PHP developers, but scary for beginners. Hey but they know at least howto even if they can’t do it itself. This is why people like you are online =)

After the commit you can visit any page you like, and say, hey I need version xyz click the checkout revision button and the magic happens.
Monotone DB gets read by PHP and and returns your revision.


Yea, again all this is so much effort, okay you’ll benefit of it, but can’t you make it easier boiii?
Yes we can, even visually more attracting, and foolsafe ;-)

Have you heard about SIMILE & Exhibit Project [timeline, maps, tables, etc..]?
No? OMG!
hurry and read this: http://simile.mit.edu/ & this http://simile.mit.edu/exhibit/

This is my idea: Simile can track changes and display them in a timeline (so much more eyecatching than any other thing), so you can post in intervalls or manually changes to it.
What else do I need to explain?
I don’t want to go into more detail, got to sleep now

Timeline reminds me on Minority Report, where is my transparent touchscreen? heheeh

Quote from: Xsss4hell at May 14, 2007, 05:14 PM

I’ve made something similar with svn, but now I’ve changed my mind.
If I ever start a project with the need of versioning and localization (l10n) I’d definately use Monotone http://monotone.ca/
The advantage is that is saves everything in one or more database files, it is so much better, but I think you can inform yourself about it on its homepage.

I looked at Monotone but didn’t see a way of maintaining version control when a site is split between a database and individual files. Maybe I didn’t look long enough.

You’re certainly right that those of us used to version control are uneasy without it. Especially when dealing with a product with a version number <1.0 no matter how fabulous it is (and it is!). I use QVCS for my C++ work but I still feel nostalgic for Polytech’s PVCS.

Bob

Oh, I didn’t look into commercial VCS-Systems. But I doubt they support scheduled or event based (My)SQL export, but I maybe wrong =)


Look at this
http://www.innovartis.co.uk/Automated_Database_Change_Management_Whitepaper.htm#_Toc76374597
It just decribing the technique and not the product of that company. maybe interesting.

Have a look at this, it is an automated technique for SVN:
http://www.codeproject.com/cs/database/ScriptDB4Svn.asp

Hey there are lotta DB versioning tools out there ie. reddot, but they are all commercial and not PHP nor another weblanguage.
They are all windows executables, so not doing their job crossplatform.

however, I just pointed to a possible way of how to create a monotons db vcs system.
Maybe this helps you with monotone
http://monotone.ca/docs/Migrating-and-Dumping.html
monotone can output it’s db as sql, hehe =))

Monotone Wiki

I split this topic from the original, which is focused on how MODx will handle versioning in the product without any reliance on external version control systems.

Cheers

uhhm sorry I didn’t get it..
Is this the topic, or is this the part which got split from the topic.

Quote from: Xsss4hell at May 19, 2007, 06:55 PM

uhhm sorry I didn’t get it..
Is this the topic, or is this the part which got split from the topic.

This is the topic split from the original because this is slightly off-topic, and does not discuss version control in terms of how MODx will manage versions of content internally.