#NETLOGO LINUX ZIP FILE#
#NETLOGO LINUX FULL#
#NETLOGO LINUX DOWNLOAD#

Also, the zip file name must match the codeName. There are no namespaces or aliasing for NetLogo extensions (yet), so the only way to differentiate them is with unique identifiers when they're added in code. Make sure your codeName field is unique among extensions in the library already. Some editors also like to insert so-called smart-quotes ( “”) around text, but our configuration file format requires straight quotes ( ''). '''value''') in order to hold a multiline string. longDescription may be wrapped in triple-quotes (i.e. All values to the right of the colon should be wrapped in single-quotes (i.e. Homepage: 'The URL that users may go to for documentation about this extension'Īll of these fields are mandatory.

#NETLOGO LINUX FULL#

LongDescription: '''A full description of what the extension does''' ShortDescription: 'A one-sentence description of what the extension does' Name: 'The human-friendly name of the extension'ĬodeName: 'The name that will be used to refer to this extension in NetLogo code' 'Fetch' comes after 'Dist' and before 'GoGo'). Regarding (2), if you are adding a new extension, you should make an insertion into nf, in alphabetical order according to the 'name' field (e.g. If you add the netLogoShortDescription, netLogoLongDescription, and netLogoHomepage settings to your build file, a snippet will be generated as the below when you run packageZip for easy copy/pasting into the nf file, too. If you're using at least version 5.2.3 of the NetLogo Extension Plugin for sbt, it can generate an appropriate file for you using the packageZip sbt command, including adding extra files such as documentation and example models. Make sure your jar files are in the 'root' of the. jar and any other supporting files that accompany the extension (e.g. zip file should have a name that follows the format -.zip. zip file added to the extensions directory.įor (1), the. There was no Extension Manager before 6.1 (actually, before 6.0 development builds), so there cannot be any branches here for earlier versions of NetLogo. If your extension targets a different version of NetLogo, it must go on the appropriate branch for that version of NetLogo. Please make sure that you are making your pull request to the correct branch! The 6.1 branch is only for extensions that work with NetLogo 6.1.x. All that you need to do is submit a pull request to this repository and wait for us to merge it (which shouldn't take more than a few days, for a properly-formatted pull request).

#NETLOGO LINUX DOWNLOAD#

If you want to make a new extension (or new version of an extension) available to the NetLogo community for download from the Extension Manager, this is the place to do it. This repository houses the files that power NetLogo's Extension Manager.

Netlogo linux