3rd Party Libraries Used

In the Geo software, we utilize a number of 3rd party software libraries, which are listed below in sort-of directory listing order. Feel free to reference any of these libraries in your Addon, but pay attention to the notes on each library as some are slated for removal in future releases. If you see any out of date information, or if you know of a library with a newer version than listed below let us know about it!

Note that if you have a version earlier than what is listed under last updated, you will need to refer to your version's files to see what version of the library is included with your version.

<tip c w>Warning: Take note of the use of Prototype JS and Scriptaculous along side jQuery, which are not compatible with some other JS libraries such as MooTools. If you use jQuery, make sure you ALWAYS use the jQuery() and not the shortcut $(), as currently that will be used by Prototype. See the notes in the Prototype (Javascript Framework) for more info.</tip>

Usage Notes: We advise to not use this library directly, but use the Geo data accessor DataAccess which wraps the ADOdb class, and adds additional functionality on top of that. See the PHP Docs for the DataAccess class for more information.

Usage Notes: This is now (as of version 7.3.0) included as part of the Modernizr library, in earlier versions it was referenced in the default templates on it's own. This ensures that those HTML5 elements will work properly on older browser versions.

Usage Notes: First added in version 7.3.0. Note that this includes html5shiv so renders the stand-alone html5shiv library unnecessary. Also note that unlike other JS libraries, this needs to be loaded after all of the CSS is loaded, but before the body is loaded²⁾, in order to avoid FOUC.

At the moment just a few places make use of Modernizr's tests to it's full extent, going forward we plan to incrementally improve that to fully leverage what this library can accomplish.

Usage Notes: This library first added / used in Version 7.3.0. We recommend to not use this directly, instead go through the methods exposed in the geoTemplate class and geoSession class, to ensure best "forward compatibility".

Usage Notes: Added in Geo 4.1.0. The old location is in the Services/ directory, we have updated it (we were previously using a beta version from 2006) and moved its home to the directory noted.

Usage Notes: Added in Geo 5.2.0. This library is only used on servers where the built in zip extension is not loaded in PHP, which apparently is often enough to warrant using an alternative. We advise not to use this class directly, if the Zip extension ever becomes "common place" enough, we may remove this library.

Usage Notes: In 4.0 just use the geoEmail::sendMail() method to send e-mails, see that method's documentation for more info.

Future Plans: There is a new version of Swift Mailer out which is a total re-write from previous versions. We have plans to move the e-mail functionality totally into the geoEmail class (right now that class just acts as a wrapper, relying on the addon to do the actual e-mailing), and at that time we will recode it to use the new version of the Swift Mailer. This is planned for a future release but since it is not done yet, no word on how soon that will be. The 5.0 line will continue to use the 3.3.3 version.

Usage Notes: If you plan to do any JS stuff that requires a javascript framework, we highly recommend to use jQuery rather than Prototype and Scriptaculous. We plan to phase those libraries out, being replaced by jQuery over time, and new features will be using jQuery. In the mean time, both jQuery and Prototype/Scriptaculous will be used, until we are able to convert all built-in functionality over to jQuery.

If you are using Prototype / Scriptaculous now, we highly recommend to start making the switch over to use jQuery.

Customization Note: Some sites have started using jQuery already, if your site is already using jQuery make sure that you remove any calls to the jQuery JS file when you update to version 7.1.0 since the software will already load that built in. It will result in duplicate calls to jQuery if you leave your own in, and in some cases where you might be using an older version, may result in breaking features in the software.

<tip c w>Warning: Until we entirely "phase out" Prototype, avoid using Mootools as it will directly conflict with Prototype, causing you problems. This applies to any JS libraries that conflict with Prototype or Scriptaculous, before you decide to use something JS based ensure that it is compatible.

There's nothing wrong with Mootools any of the others, we just happened to choose Prototype & Scriptaculous starting out so until they are removed entirely, you will need to make sure you only use compatible libraries..</tip>

Note that it is possible to load this library from Google Libraries API rather than off the local site. See the Use Google Libraries API setting in the admin at Design > Template Sets in the Advanced Settings section.

Customization note: As noted in the jQuery entry, we are switching from using Prototype to using jQuery. There is a LOT of existing code, so we're not going to do it all in one version. Until everything is converted over, Prototype and Scriptaculous will continue to be used. So be careful of using $() - that must ONLY be used for Prototype, it will not work (unless properly encapsulated) for calling jQuery or jQuery UI. Instead use the jQuery(…) syntax instead of the short-hand $(…) syntax.

Note that it is possible to load this library from Google Libraries API rather than off the local site. See the Use Google Libraries API setting in the admin at Design > Template Sets in the Advanced Settings section.

Usage Notes: If you plan to do any JS stuff that requires a javascript framework, we highly recommend to stick to using jQuery, as starting in version 7.1.0 the use of Prototype is being phased out. If you have custom scripts using Prototype we recommend to start converting them to use jQuery instead, or find alternative scripts that do the same that using jQuery. Once we have entirely phased out Prototype and Scriptaculous it will be removed from the software completely, however this may take some time.

JQuery Compatibility: During the time that we work to phase out Prototype, the software will be loading both Prototype and jQuery (running in compatibility mode) at same time.

<tip c w>Warning: Avoid using Mootools as it will directly conflict with Prototype, causing you problems in the software until all use of Prototype has been converted to jQuery. This applies to any JS libraries that conflict with Prototype or Scriptaculous, before you decide to use something JS based ensure that it is compatible.

There's nothing wrong with Mootools or any of the others, we just happened to choose Prototype & Scriptaculous jQuery now that it has become the most popular JS library.</tip>

Note that it is possible to load this library from Google Libraries API rather than off the local site. See the Use Google Libraries API setting in the admin at Design > Template Sets in the Advanced Settings section.

Usage Notes: We recommend to use jQuery instead, starting in version 7.1.0 Scriptaculous is being phased out, to be replaced by jQuery. This will not happen all at once, it will be done in phases. Any new features will use jQuery.

Note that it is possible to load this library from Google Libraries API rather than off the local site. See the Use Google Libraries API setting in the admin at Design > Template Sets in the Advanced Settings section. At least it will be once the Google Library API is updated with the latest version of Scriptaculous, version 1.9.0.

Usage Notes: We recommend to avoid using this as it will be removed as soon as we replace it with something that is compatible with jQuery.

Usage Notes: When using the Remote API you don't have to worry about communication with the "client" script, in the remote API call all you need to do is return the data as you want the client to receive it, and the Geo Remote API system will take care of it for you.

Usage Notes: See the geoView and geoTemplate documentation.

Usage Notes: If you wish to customize the TinyMCE configuration that is used, see Customizing the TinyMCE Display (WYSIWYG editor) V5

Usage Notes: This is only available starting on version 6.0.0. See documentation on http://codemirror.net/ for usage on other pages within the software.

Usage Notes: The actual complete library is pretty big, we only include 2 parts of the library: A file in the minify folder used to minify the JS. And a file used to minify CSS that was actually integrated directly into the "geo_templates/min.php" file and heavily modified.