Write a new, or at least rewrite the Subversion class to allow for more actions to be done.
[quote=jacmoe]I hope the Subversion class will be implementing an abstract class. Would make it easier to write implementations for Git and Mercurial.[/quote]
Good idea.
There's a bug when adding and editing repositories, instead of "Project" field description i get "[repository_project_description]" and when I edit the repository and I have more then one project even if the repository is for the second project the first project is selected.
I got it to work, it's a little simple now, maybe you could make it more like websvn, check it out ;) http://demo.websvn.info/listing.php
By the time I've actually finished the source browser, it will have multiple revision browsing and file viewing.
Oh also there's "[location]" for location's field name.
Sorry for reopening this ticket again, but I don't want to add new ticket for small suggestion. I think that the "Message" should be truncated to something around 100 characters cause when a message is long it's displayed in multiple lines and looks ugly.
I think it would be nice to have directories first and then files instead of absolute alphabetical list like it is now. ;)
I hope the Subversion class will be implementing an abstract class. Would make it easier to write implementations for Git and Mercurial. When you decide on an interface, I'd like to help writing a SCM plugin for Mercurial.
Take a look at InDefero, they have such a system in place.