Demo Chronicles Skip to this page's content
Terms Of Use Updated: Mar 13, 2010 Revision 3.0.3
Welcome, Guest
Sign In Register
Current Visitors: 5 [ Members: 1, Guests: 4 ]Unique Visitors This Month: 359Registered Members: 5Find us on Twitter!Find us on FaceBook!Link to the RSS feed.
Go to the Proximal Studios project page.
View information about this site.Watch Demo Scene productionsWork with your friends to build demo productions.Enter your demo production into the Demo Challenge
Getting StartedWin32OpenGLDirect XLinks
Features
User H.U.D.
Theme: "The Spinning Cube"
Date: Feb 1 - Mar 31
Registration: Open to everyone
Description: produce a single effect and bore your audience with it. [more]


Title: Fireworks
Artist: Brian Wade
Challenge Date: July 2000
OS: Windows
Download: Fireworks.zip


A communal gathering location for demo sceners
[ Pouet ]
The main repository of executable productions released at demo parties
[ Scene ]
Viewable movie versions of the demo productions located at scene.org
[ DSTV ]
Getting Started - Setting Up An IDE
<< Main IndexOverview - What is an IDE? Choosing an IDE >>
Video Accompaniment | Audio Accompaniment

Listen to an audio version of this page: audio (full page).
Watch a video demonstrating concepts in this article: video
Getting Started: The IDE
The following article introduces a number of integrated development environments (IDE). IDEs covered by this article include Microsoft's Visual Studio, Dev C++, and Code::Blocks for the Windows operating system as well as Code::Blocks for Linux. The article also describes how to compile a simple project in each of these environments.
Now, because program instructions can stretch on for pages and can become hard for the programmer to follow, a program will often be spread over a number of uniquely named files. Large projects might have upwards of 50 files and this can become hard to manage. The IDE helps to organize these files by categorizing them according to type and presenting them to the user in alphabetical order. Furthermore, a catalogue of the files is stored in a project file which preserves the organization of the entire project and allows a programmer to continue his or her work by just opening it. In this way the IDE frees the programmer from the tedious task of locating and organizing his files.
As well, since the IDE is coupled with a compiler, the task of sending the finished program off to be converted into .OBJ files and then linked into an executable is greatly simplified. An IDE also organizes and makes accessible various configuration options that affect how the final executable is created. Good examples are the Debug and Release configurations. When the IDE directs the compiler to create an executable with the Debug configuration, the resulting file contains additional information that aids in the debugging process. It should be noted here that the compiler is not part of the IDE but rather, it is called by the IDE. This means that an IDE can be associated with an array of compilers. The IDE is also useful for keeping track of all the files that make up a program and how they are interrelated.
The real power of the IDE arises from its ability to aid a programmer in tracking down errors. When the compiler discovers an error in the code, the IDE is able to take the programmer right to the file and line where the first error occurred. If the programmer is using a DOS console, he has to read where the error is indicated to be and then open up the appropriate file and search for the offending line. An IDE bypasses this tedium by receiving any errors sent out by the compiler and directs the programmer to the offending line in the specific file with a 'click'. The entire process of software development is made much more comfortable by an IDE.
<< Main Index Choosing an IDE >>

Last updated: Mar 12, 2010
Author: godvalve
Back to common navigation links
© 2001-2010 Proximal Studios. All rights reserved.