From ace36b37eb19609d83bc8aa45aea905ca567d297 Mon Sep 17 00:00:00 2001 From: Penguin-Guru Date: Fri, 8 Oct 2021 10:52:44 -0700 Subject: [PATCH] Improves Writing and Removes References to "Functionalities". I am not sure if there is a concept of "functionalities" that is different from applications but, since I have not happened across that information and since this is the "community-apps" repo, I have taken the liberty of removing those references. Feel free to add them back in if they do refer to something other than applications, but in that case it might be good to (1) add some documentation to clarify what "functionalities" are and (2) rename this repo to something that does not specify "apps". --- web/index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/web/index.html b/web/index.html index c42b3b8..3047d65 100644 --- a/web/index.html +++ b/web/index.html @@ -17,12 +17,12 @@

Vircadia Community Applications Repository

-

This repository stores optional tablet applications and functionalities provided by the contributions of the community members. - If you have created an Application or functionality script and want to offer it to the community, this is where you can do it.

+

This repository stores optional tablet applications and functionalities provided by the contributions of community members who are not core developers of Vircadia. + If you have created a Vircadia application and want to offer it to the community, this is where you can do it.

Before going further:

    -
  1. If your application/functionality is a core feature that you think should be delivered out-of-the-box with Vircadia, you must instead consider making your contribution directly in the Vircadia code repository. See instead the Vircadia repository and contact the core team.

  2. -
  3. If your application/functionality has a dependency with on an external server or services (if it has to deal in any ways with other servers than a Vircadia Domain or Metaverse API), then this repository is not where you should publish your application. It will have to be published to a different source like the Marketplace (when it is created) or another web site.
  4. +
  5. If your application is a core feature that you think should be installed by default for all Vircadia users, you should instead consider making your contribution directly in the Vircadia code repository. See the Vircadia repository and contact the core team.

  6. +
  7. If your application is dependent on an external server or service (if it has to deal in any way with servers other than a Vircadia Domain or Metaverse API), then this repository is not where you should publish your application. It will have to be published to a different source, like the Marketplace (when it is created) or another web site.

Conditions for acceptance:

    @@ -32,10 +32,10 @@
  1. Avoid spaces and special characters in your folders and file names.
    (Stay with: "a-z", "A-Z", "0-9", "-", "_", ".")

  2. -
  3. Add your application/functionality in a folder under the "applications" directory.
    +
  4. Add your application in a folder under the "applications" directory.
    (Your main js file and your icon must be directly in that folder)

  5. -
  6. You must add your application/functionality to the "metadata.js" file (in the "applications" directory) by generating a new one using this tool: Metadata Generator
  7. +
  8. You must add your application to the "metadata.js" file (in the "applications" directory) by generating a new one using this tool: Metadata Generator

Submit a "Pull Request" to add your "application folder" and the new "metadata.js" file.
@@ -52,4 +52,4 @@

- \ No newline at end of file +