Who uses this tool to save their various versions of Storyline files. My department would like to use this as we are currently in the middle of updating and re-creating courses. I am unfamiliar with this tool and wanted to know if anyone else uses it?
Thank you. Its new to me also, and I am reading about its a place to house code, but I also heard you can store your Captivate and Storyline files in this area.
We initially used it but it becomes unwieldy (its designed for code). In my experience it is better to use a business cloud account like egnyte (which I used and like), dropbox (currently using, egnyte is better), or box. They deal with bigger files easier, which svn doesn't. (use the business versions)
We use Tortoise SVN for Storyline projects. It's true that all the text comparisons and so on are not usable (the tool is designed for code as you said), but the most important features for us are to be able to track who did what and when and the possibility to version projects and be able to reverse to an older version if needed.
SVN is great. We used it about ten years back in production for large teams. The tech folks got along well with SVN. Some of the less technical didn't like it very well and it didn't (at the time) play very well with Office documents. I don't remember the issues we had with Word documents but it seemed to mangle stuff from time to time.
One of the great things about SVN is the options you have for integration with other tools. We used Trac for project and defect tracking. Worked really well. We also used ActiveCollab for project management and collaboration / comms. This also worked pretty well and offers an integration with SVN and GIT.
The biggest drawback to technical tools that require a process to commit files (and enforce comments) is the value of the tool decreases with inconsistent use. In our case, folks were entering nonsense into comments (ASDFSDFA, for example) just to get the commits in and some just couldn't figure out how to make it work (or would forget to commit) which caused version issues. If one team member doesn't use the tool well, it can cause problems for the rest of the team.
Overall, SVN or GIT are fantastic if you have a significant code-base. For proprietary bundled source like Storyline and MS Office Docs, you might have a better time with a shared folder sync application like Dropbox, Egnyte, or OwnCloud. No commits required or complex branch logic to maintain.
6 Replies
Hi Helena,
I haven't heard of it before but hopefully someone in the community will be able to chime in!
Thank you. Its new to me also, and I am reading about its a place to house code, but I also heard you can store your Captivate and Storyline files in this area.
We initially used it but it becomes unwieldy (its designed for code). In my experience it is better to use a business cloud account like egnyte (which I used and like), dropbox (currently using, egnyte is better), or box. They deal with bigger files easier, which svn doesn't. (use the business versions)
Ok its very strange and yes its design for code but I guess we will see. Thanks
We use Tortoise SVN for Storyline projects.
It's true that all the text comparisons and so on are not usable (the tool is designed for code as you said), but the most important features for us are to be able to track who did what and when and the possibility to version projects and be able to reverse to an older version if needed.
SVN is great. We used it about ten years back in production for large teams. The tech folks got along well with SVN. Some of the less technical didn't like it very well and it didn't (at the time) play very well with Office documents. I don't remember the issues we had with Word documents but it seemed to mangle stuff from time to time.
One of the great things about SVN is the options you have for integration with other tools. We used Trac for project and defect tracking. Worked really well. We also used ActiveCollab for project management and collaboration / comms. This also worked pretty well and offers an integration with SVN and GIT.
The biggest drawback to technical tools that require a process to commit files (and enforce comments) is the value of the tool decreases with inconsistent use. In our case, folks were entering nonsense into comments (ASDFSDFA, for example) just to get the commits in and some just couldn't figure out how to make it work (or would forget to commit) which caused version issues. If one team member doesn't use the tool well, it can cause problems for the rest of the team.
Overall, SVN or GIT are fantastic if you have a significant code-base. For proprietary bundled source like Storyline and MS Office Docs, you might have a better time with a shared folder sync application like Dropbox, Egnyte, or OwnCloud. No commits required or complex branch logic to maintain.
This discussion is closed. You can start a new discussion or contact Articulate Support.