Differences

This shows you the differences between two versions of the page.

--- developers:start [2008/12/08 19:55]
jonyo created
+++ developers:start [2014/09/25 16:55] (current)
@@ Line 2: / Line 2: @@
 ====== Developers ======
-This is a rather new section of the user manual, meant to help developers better understand the ins and outs of the software.  We here at Geo strive to be "developer friendly":
+This section of the user manual is here to help developers better understand the ins and outs of the software.  We here at Geo strive to be "developer friendly":
-  * We provide the software Open Source ((Open source meaning that all the files are in "plain text", except for any file(s) directly relating to the software licensing.  We allow and encourage modifications to the base code to anyone inclined to do so, however any issues relating to PHP source code modifications are not supported by the Geo support.)).
+  * We provide the software Open Source ((Open source meaning that all the files are in "plain text", except for any file(s) directly relating to the software licensing.  We allow and encourage modifications to the base code to anyone inclined to do so, however any issues relating to PHP source code modifications are not supported by the Geo support.)) for non-trial purchased packages((Trial packages and leased packages have all PHP files fully encoded.)).
-  * We have created a robust //Addon System//, who's goal in life, is to make any [reasonable] changes to the Geo software, without needing to modify the //base source code//, and instead be done through the use of a custom addon.  We fully document this addon system through the available **Example Addon** which documents the addon system //by example//.  It basically implements every single possible thing an addon can do.
+  * We have created a robust [[developers/addons/start|Addon System]], whose goal in life, is to make any [reasonable] changes to the Geo software, without needing to modify the //base source code//, and instead be done through the use of a custom addon.  We fully document this addon system through the available **Example Addon** which documents the addon system //by example//.  It basically implements every single possible thing an addon can do.
-  * Our developers work directly with outside 3rd party developers (Thats You!) to add further functionality to the addon system.  A lot of the //hooks// in the software are direct results of this communication.  If you as a developer want to do something in the software that is not currently possible using an addon, send in a support ticket to get a direct line to one of our developers.  If there is already a way to do what you are requesting, we'll send you in the right direction.  If what you need requires a new //software hook//  to be added, in most cases we will add the hook so that the next release will contain it((We treat adding a new hook like adding a [very] minor feature, which means at our own discretion.  We will only add a new hook that is requested if we feel it will benefit the software.  That being said, we have only "denied" a request for a hook a very small handful of times, usually when the requested thing can already be accomplished in another way.)).
+  * Our developers work directly with outside 3rd party developers (That's You!) to add further functionality to the addon system.  A lot of the //hooks// in the software are direct results of this communication.  If you as a developer want to do something in the software that is not currently possible using an addon, send in a support ticket to get a direct line to one of our developers.  If there is already a way to do what you are requesting, we'll send you in the right direction.  If what you need requires a new //software hook//  to be added, in most cases we will add the hook so that the next release will contain it((We treat adding a new hook like adding a [very] minor feature, which means at our own discretion.  We will only add a new hook that is requested if we feel it will benefit the software.  That being said, we have only "denied" a request for a hook a very small handful of times, usually when the requested thing can already be accomplished in another way.)).
-  * We have started this section in the user manual to further help developers understand how the software works.
+  * We have started this section in the user manual to further help developers understand how the software works.  Be sure to check out the sub-pages which you can navigate to in the menu on the left-hand side, such as the [[developers/addons/start|Developers > Addons]] page and sub-pages.
+  * We have created several step-by-step instructions on doing specific development tasks in [[tutorials/development/start|Tutorials > Development]] section in this wiki.
+  * We have generated [[http://geodesicsolutions.com/phpdocs/|PHPDocs]], always updated for the latest release.  It includes documentation for the "publicly accessible" classes and methods found in the 2 files that are encoded for licensing purposes.  These are generated directly from the PHP "doc block" comments in the source code, and can be very useful as an API reference.
 This area of the user manual, like most of the rest of the manual, explains things people usually have questions about.  If you don't find the answer to what you are looking in this manual, send in a support ticket!

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools