21
edits
Changes
→OS Key-Codes
* #define ''' F11_KEY''' 280
* #define ''' F12_KEY''' 281
== Obsolete Stuff ==
=== SVN ===
<p>[[Development and submission steps using SVN - OOP344 20121]] This is a quick way to get everyone familiar with SVN in a brain friendly manner without the need to sift through pages of unnecessary documentation.</p>
<p>
[http://lmgtfy.com/?q=what+is+svn What is SVN?] Subversion or SVN is a control system where it allows you to properly organize and manage files and directories and the changes to them over time. SVN allows you to recover older versions of your data, or examine the history of how your data changed. In this regard, many people think of a version control system as a sort of “time machine”. [http://svnbook.red-bean.com/en/1.4/svn.intro.whatis.html]
</p>
=== SVN Clients ===
* [[Tortoise in 5]] - This page is dedicated to those poor souls that have to use SVN but don't have time to read through chapter upon chapter about it just to be able to participate in assignment 2.
* [[RabbitVCS]] - RabbitVCS is a Linux alternative to TortoiseSVN. This page will help describe how to install and use RabbitVCS.
* [http://rapidsvn.tigris.org/ RapidSVN] - Another SVN client for Linux - a very simple and straight-forward SVN client.
* [http://www.lachoseinteractive.net/en/community/subversion/svnx/features/?sid=337041a90a9f11841f9f77fda5224723 svnX] - A very competent SVN client for Mac OS X.
=== SVN Hosts ===
<p>The best way to learn SVN is to experiment it, we programmers, love to explore. Though Seneca already provides us SVN hosting, there are other free SVN hosting out there that you can use and experiment around (since you might not want to mess around with your team's account if you don't know what you're doing). One of the best SVN hosts out there is probably [http://code.google.com/hosting/ Google Code Hosting] because it has many cool features such as web presentation of [http://code.google.com/p/rainulf/source/browse/trunk/core.php syntax highlighted sources], [http://code.google.com/p/rainulf/source/diff?path=/trunk/core.php&format=side&r=4&old_path=/trunk/core.php&old=3 diff], [http://code.google.com/p/rainulf/w/list wiki] and more (which you can do also within a client program) of sources and it does show what SVNs are truly for: ease.</p>
<p>Here's a few SVN hosts:</p>
* Google Code Hosting - create account [http://code.google.com/hosting/createProject here]
* [http://sourceforge.net/ SourceForge]
* [https://www.bountysource.com/ Bounty Source]
* And [http://lmgtfy.com/?q=svn+hosts more], ranging from free to paid hosting.
NOTE: Seneca already provides us SVN hosting (SVN login and pass), all of our work academic work should be all there.
=== Doing a task in SVN ===
Below is a quick guide to follow to complete a task under SVN.
1. Create subdirectories in "branches" under your Seneca email ID. This is your ROOT.
Repo
|__ Branches
|__ SenecaEmailID
2. Create a subdirectory under your brach under the task name. (ex. BkSpcBug)
Repo
|__ Branches
|__ SenecaEmailID
|____ BkSpcBug
3. Update your branch to set the files in (BkSpcBug)
Repo
|__ Branches
|__ SenecaEmailID
|____ BkSpcBug
|_____file1.cpp
|_____file2.cpp
4. Start working on (BkSpcBug).
5. When complete (Bug Fixed).
5.1 Set the trunk status on the team page to: COMITTING by your Seneca ID.
5.2 Merge the branch (BkSpcBug) to Trunk.
5.2.1 Edit possible conflicts.
5.2.2 Set conflicts to resolved.
5.3. Recompile the trunk.
5.4 Set the trunk status on the team page to: COMITTED by your Seneca ID.
