Rifidi:Source Code - Revision history

Bppause at 09:38, 30 August 2016

2016-08-30T09:38:32Z

Bppause: /* Downloading the Code */

2016-08-30T09:31:15Z

‎Downloading the Code

Bppause: /* Organization */

2016-08-30T09:30:24Z

‎Organization

Bppause: /* Organization */

2016-08-30T09:29:43Z

‎Organization

Bppause: /* Quick Instructions */

2016-08-30T09:29:19Z

‎Quick Instructions

Bppause at 10:37, 10 July 2015

2015-07-10T10:37:47Z

Bppause at 10:35, 10 July 2015

2015-07-10T10:35:43Z

Nurban: /* Organization */

2015-01-07T22:19:30Z

‎Organization

Nurban: /* Organization */

2015-01-07T22:17:13Z

‎Organization

Matt: /* Add Repository */

2014-08-14T23:05:24Z

‎Add Repository

@@ Line 11: / Line 11: @@
 =Rifidi Source Code=
-For those who need to see the source code for the Rifidi products, you will have to check out the code from svn.  This section explains how to check out and run the code from source.
+For those who need to see the source code for the Rifidi products, you will have to check out the code from Github.  This section explains how to check out and run the code from source.
 ==Organization==
 In general the code for Rifidi is organized into Eclipse plugins or bundles.  Eclipse handles the loading and execution of the plugins.  For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
-* '''Github Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
+* '''Github Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main Guthub repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our Github, see [[Development and Release Process#SVN Structure]]
 * Target Platform - A target platform is the base set of plugins that an Eclipse application needs to run.  In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products.  You can find these in the trunk.  They will be named something like <code>org.rifidi.emulator.target</code>.  For more information see [[Development and Release Process#Target Platforms]].
-* org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins.  In order to simplify things, there is a folder in the svn into which stable binaries of each of the plugins used in the rifidi project will be placed.  This folder is used in conjunction with the target platform.
+* org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins.  In order to simplify things, there is a folder in the Github into which stable binaries of each of the plugins used in the rifidi project will be placed.  This folder is used in conjunction with the target platform.
 * Product File - In Eclipse, a product file is used to define the needed eclipse plugins.  Running this file will create a new Eclipse 'Run Configuration' in your IDE.  You can then tweak this run configuration as needed.
 * Source Code Plugins - A stable binary version of each of the plugins is contained in the org.rifidi.binary folder.  However, if you wish to view the source of a particular plugin or run a plugin from source, you must download the code from either the version in the trunk or a tagged version in the tags directory.

@@ Line 22: / Line 22: @@
 ==Downloading the Code==
-Our code is hosted at https://transcends.svn.cloudforge.com/rifidi and https://transcends.svn.cloudforge.com/emulator.  The svn repository allows anonymous read access.  Because the svn repository is the same one that developers submit to, it contains the latest Rifidi code.
+Our code is hosted at https://github.com/mattrifidi/rifidi and https://github.com/mattrifidi/emulator.  The Github repository allows anonymous read access.  Because the Github repository is the same one that developers submit to, it contains the latest Rifidi code.
 The following steps explain how to check out and run Rifidi Emulator.  The other products in the Rifidi Suite follow similar steps.  If you need help with them, you can ask questions on IRC or our forums.

@@ Line 14: / Line 14: @@
 ==Organization==
 In general the code for Rifidi is organized into Eclipse plugins or bundles.  Eclipse handles the loading and execution of the plugins.  For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
-* '''Githib Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
+* '''Github Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
 * Target Platform - A target platform is the base set of plugins that an Eclipse application needs to run.  In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products.  You can find these in the trunk.  They will be named something like <code>org.rifidi.emulator.target</code>.  For more information see [[Development and Release Process#Target Platforms]].
 * org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins.  In order to simplify things, there is a folder in the svn into which stable binaries of each of the plugins used in the rifidi project will be placed.  This folder is used in conjunction with the target platform.

@@ Line 14: / Line 14: @@
 ==Organization==
 In general the code for Rifidi is organized into Eclipse plugins or bundles.  Eclipse handles the loading and execution of the plugins.  For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
-* '''SVN Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
+* '''Githib Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
 * Target Platform - A target platform is the base set of plugins that an Eclipse application needs to run.  In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products.  You can find these in the trunk.  They will be named something like <code>org.rifidi.emulator.target</code>.  For more information see [[Development and Release Process#Target Platforms]].
 * org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins.  In order to simplify things, there is a folder in the svn into which stable binaries of each of the plugins used in the rifidi project will be placed.  This folder is used in conjunction with the target platform.

@@ Line 5: / Line 5: @@
 # Download the Eclipse for plugin developers (3.5 is what we are using)
 # Install the subclipse plugin
-# Add this svn to the list of repositories: emulator, prototyper - https://transcends.svn.cloudforge.com/emulator, edge, workbench - https://transcends.svn.cloudforge.com/rifidi
+# Add this github to the list of repositories: emulator, prototyper - https://github.com/mattrifidi/emulator, edge, workbench - https://github.com/mattrifidi/rifidi
 # Check out the following projects from rifidi/trunk: org.rifidi.binary, org.rifidi.emulator.target, org.rifidi.ui.ide
 # Open up the target file in org.rifidi.emulator.target and click the button that says "set as target platform"
 # Open up the .product file in org.rifidi.ui.ide and click "launch an eclipse application"
 =Rifidi Source Code=

@@ Line 1: / Line 1: @@
 [[category:developerDoc]]
-This page explains how to download and run the source code for Rifidi Edge.  However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.
+This page explains how to download and run the source code for Rifidi Edge, Protptyper, Tagstreamer and Workbench (Edge Server steps can be found here - http://wiki.rifidi.net/index.php?title=Edge_Server_Development_Environment). However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.
 =Quick Instructions=
 The following are the basic steps needed to begin running Rifidi from source.  If you have trouble or need more explanation, please see the more detailed instructions on this page.

@@ Line 15: / Line 15: @@
 ==Organization==
 In general the code for Rifidi is organized into Eclipse plugins or bundles.  Eclipse handles the loading and execution of the plugins.  For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
-* '''SVN Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of <span class="plainlinks">[http://www.timewing.com.sg/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">aircon service</span>] the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
+* '''SVN Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi).  The ''trunk'' folder contains the code that is being developed.  It is ''not'' guaranteed to be stable.  The ''tags'' folder contains tagged versions of the source for each of the plugins.  The source in these plugins should be relatively stable.  The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers.  These changes can then later be merged back in.  For more details about our SVN, see [[Development and Release Process#SVN Structure]]
 * Target Platform - A target platform is the base set of <span class="plainlinks">[http://www.timewing.com.sg/ac_service.html <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">ac repair</span>] plugins that an Eclipse application needs to run.  In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products.  You can find these in the trunk.  They will be named something like <code>org.rifidi.emulator.target</code>.  For more information see [[Development and Release Process#Target Platforms]].
 * org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins.  In order to simplify things, there is a folder in the <span class="plainlinks">[http://www.timewing.com.sg/refrg_service.html<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> refrigerator repair</span>] svn into which stable binaries of each of the plugins used in the rifidi project will be placed.  This folder is used in conjunction with the target platform.

@@ Line 57: / Line 57: @@
 * Add the rifidi repository
 ** Click 'Add SVN Repository' button
-** Add ' https://transcends.svn.cloudforge.com/rifidi'[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]
+** Add ' https://transcends.svn.cloudforge.com/rifidi '[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]
 ===Check Out Code===