• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Death-A-Lot

Maintaining a code library

6 posts in this topic

I'm learning c++ I thought that if I have a peice of code that I made or found and I think it may be useful at a later date how do I keep them?

What I mean by keep them is how do I maintain my own code library in order to keep them organised?

Is it a folder on my drive?
Is it a document with them all in?

What's your way?
0

Share this post


Link to post
Share on other sites

What you're looking for is a topic called "Revision Control."  At the moment, your best solution is to try Git.

 

http://git-scm.com/

 

The simplest thing to do is to setup a repo and put it on Google drive or drop box or something.  That way you can access the code from home, school, on vacation, and you have an offsite backup.  Of course putting your stuff online caries some risk of someone else stealing your code, but if you're just learning to code, that's not a concern.

 

I wish I had know about revision control when I was in school.  One of the great things these systems do is keep track of changes and let you undo mistakes.  This would have saved me countless hours in school when I broke something and couldn't get it working again.

 

Work through the manual, and just learn the command line.  There are only a few commands that you'll use on a daily basis anyway.

 

http://git-scm.com/book/en/Getting-Started

 

For example, all I ever use is:

 

git checkout -b new-branch 

git add --all

git commit -am 'commit message'

git stash

git stash pop

git merge --no-ff branch

git branch -d to-delete

 

And that list is for a company with tons of software.  You won't event need all that!

2

Share this post


Link to post
Share on other sites

I think that Mercurial should be mentioned too. You can read all about it here.

 

Both work on the same principle, but Mercurial (or simply hg) is considered more newbie friendly then Git. It has simpler interface with fewer options that "do the right thing".

0

Share this post


Link to post
Share on other sites

I think the op meant how to organise it's files. Keeping them all in the same folder is usually a good idea, unless you have a very large number of classes, then separating them in folder would make more sense.

0

Share this post


Link to post
Share on other sites

Best way to organize the code is based on how easy it is for you to access...I don't know how to make you more efficient.

0

Share this post


Link to post
Share on other sites
All good and I will look into them.

What I am referring too is this. ......

Lets say in the future I write a snippet of code that calculates all even numbers up too n. By some miracle ive got it working on a few lines of code. Now I can forget ive done that once Ive finished that. Or I can store it somewhere for potential future use.
0

Share this post


Link to post
Share on other sites

All good and I will look into them.

What I am referring too is this. ......

Lets say in the future I write a snippet of code that calculates all even numbers up too n. By some miracle ive got it working on a few lines of code. Now I can forget ive done that once Ive finished that. Or I can store it somewhere for potential future use.

 

 

Manage it as you go along.  I use JsFiddle for my JavaScript functions that I write, just look for somewhere to put your stuff and then think no further of it.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0