LOVR Documentation and examples
#lovr #gamedev #examples #docs #documentation #lua

bjorn 1094a5a2db Rename Android guide to Quest guide oh no; 4 年之前
api f7b1ad5aa7 Fixes; 4 年之前
examples f7a47995e3 TextureData -> Image; 4 年之前
guides 1094a5a2db Rename Android guide to Quest guide oh no; 4 年之前
showcase 509c8c9d44 Fix spatialization in Break for 0.15 alpha standard 4 年之前
README.md cef397c095 Update README; 5 年之前

README.md

lovr-docs

This repository contains the documentation for LÖVR.

There are four main types of documentation here:

  • The api folder contains a Lua table with metadata for all LÖVR functions and objects.
    • This is used to generate documentation, but is also useful for integrating with other tools (e.g. autocomplete for the LÖVR API in text editors).
    • Each function, object, etc. has a Lua file that exports its metadata. These are aggregated into a single table stored in init.lua. The aggregator is a LÖVR script, you can run it by typing lovr api at the root of this repository.
  • The examples folder contains small LÖVR projects demonstrating a specific task/technique. They aim to be minimal and easy to understand/copy.
    • The ones listed in the init.lua file are shown on the website.
  • The showcase folder contains full LÖVR projects that implement entire games or demos. The code is less important for these and it is more about the end result.
    • The ones listed in the init.lua file are shown on the website.
    • Also, each showcase project may contain its own init.lua with metadata about the project. Currently, this can contain an author table with name and link strings.
  • The guides folder contains markdown files that explain LÖVR-related concepts in depth.
    • Similarly, init.lua contains a manifest used to populate the sidebar on the website.

Note that each release of LÖVR has its own branch. Cherry picks are used to propagate fixes to relevant branches as needed. Which will totally scale.

All the code in the example/showcase projects is released under CC0. However, the models, textures, sounds, and other assets used may use different licensing, so be sure to double check those.