Read without ads and support Scribd by becoming a Scribd Premium Reader.
See Premium Plans
 
Version Control your FlashDevelopment with SubVersion
a Step by Step How To Guide
DATE:
1/3/2006 13:26 a1/p1
AUTHOR:
Ivan Todorov
VERSION:
2.1.0
Last Revised by:
Ivan Todorov
Document Purpose:
The purpose of this document is to provide general overview of version control concepts, implementation guidelines, best practices and a step by step guide onhow to get up and running in no time with SubVersion.
 
Amazingly, I’m finding that not too many Flash developers have embraced version controlas common practice during (Flash) production. Some people rely on questionable namingconventions which may result in file names such as “finalReallyFinal3_final5_IT3.fla”. Eventhough most developers topically understand version control and know they should use it,for one reason or another they have avoided implementing it in their daily work. For me itwas the frustration with finding a cost effective solution that would allow me to not onlyversion tiny .as files, but would allow me to add big FLAs, while not bloating the storagerequirements with every update (many version control servers have limits that are only afew hundred megabytes).Whether you are a freelancer working from home, or manage a large agency with multipleflash developers, you should really consider adopting this practice, disciplining yourself (aswell as your team) to implement it on every project. Once you’ve completed a few, you’llfind that versioning your projects is invaluable.In this article I cover the basics and provide a step by step guide on how to get things upand running quickly. I touch on common questions, problems, best practices, and things towatch out for, as well as two deployment scenarios: a large organization such as aninteractive agency and a smaller (individual) scale deployment for freelancers.Before I dive into the details, I’d like to mention thatPeter Elst’s presentation on AS 2.0Best Practicesprompted me to release this guide, which is based on our (BLITZ’s) internalversion control setup, handling 20-40 concurrent jobs with a team of 50 (some remote overVPN) and storage requirements of 500GB. Please note that I don’t recommend you throw allprojects assets into a version control repository. Things like gigabytes of client assets orlarge uncompressed video should not be added into the repository. I highly suggest youread theGuidelines for Project Directory Structure and Naming Conventions.While this article references a Windows deployment, the software supports most popularOSs. I recommend you read it from start to finish first and then go back to follow the steps.Let’s begin. Download the articles here:BLITZ_VersionControlWithSubVersion.docBLITZ_VersionControlWithSubVersion.pdf 
INITIAL HERE
↑
Page©2005 BLITZ Agency2
 
What You Need to Download
Steps on installation will follow shortly after.1.
S ubVersion Server (SVN)
This is the program/process that enables you to connect to your project repository (aspecial folder containing database files describing changes made over time perproject). Normally you will install this on your file server (in a networkedenvironment) or on you workstation. The download/installer is available for prettymuch any major operating systems.Cost: $0.002.
SVN Service Wrapper
(for Windows only)If you’d like for SubVersion to auto-start every time windows boots up (useful whendeployed on a file server, where most network users don’t have access to launchsoftware on that server directly)Cost: $0.003.
SVN Client:
TortoiseSVNfor Windows or similarOptionally (but highly recommended) download aGUI client, such asTortoiseSVNfor Windows. SubVersion Server is managed by a command line interface, therefore apretty GUI makes things much easier, more intuitive, and will likely save you a lot of typing. You install this on your workstation, and optionally on your file server(installing the client on the file server allows for an easy new repository creation bythe administrator). This install will require a re-boot on Windows.Cost: $0.004.
SubVersion Book
(In-depth Documentation)This is the complete electronic documentation that has everything else you may everneed down to the finest detail, with the exception of an easy step by step guide.Cost: $0.00
Total Cost: $0.00
– yes it is all free
.
INITIAL HERE
↑
Page©2005 BLITZ Agency3
Search
Search History:
Searching...
Result 00 of 00
00 results for result for
  • p.
    • Notes
    Load more