A collection of assets for Pro Motion NG, the pixel drawing and animation software by Cosmigo.
Repository: | |
Website: |
Project created and maintained by Tristano Ajmone. Started on Dec, 2018.
The goal of this project is to provide a collection of useful assets for Cosmigo Pro Motion NG, ranging from documentation, technical specifications of images, animations, palettes and pixeal art fonts format, to plugins code templates and intefaces in various programming languages, and community contributed assets like color formulas, palettes, etc.
Hopefully, these resources will be useful to both Pro Motion NG users as well as to other PM NG related projects, and version control via Git should provide an efficient way of keeping the assets always up to date, both locally as well as inside other repositories.
I would like to thank Jan Zimmerman for all the personal support and time dedication, and for having kindly allowed me to utilize the original Pro Motion assets found in this project.
The creator of this repository (Tristano Ajmone) is not affiliated to Cosmigo GmbH. Although permission was asked to reproduce the material by Cosmigo herein contained, the granted permissions don’t imply any official endorsment of this project by Cosmigo GmbH. Furthermore, Jan Zimmerman and Cosmigo GmbH can’t be held accountable for any inacurracies or mistakes found in this project.
This project is not intended as a replacement for the official Pro Motion Documention and no guarantees are made that its contents will always be up to date with the latest Pro Motion NG developements. End users of this project should always refer to the official Pro Motion NG channels, provided by Cosmigo, to obtain up to date information and official assets.
-
/_assets/
— project assets required by the build and test toolchains. -
/docs/
— HTML documents. -
/docs_src/
— AsciiDoc sources and assets to build the HTML docs. -
/fonts/
— over 1000 pixel art fonts. -
/palettes/
— the Base16 schemes (107) converted to PM palettes. -
/plugins/
— resources for plugin developers. -
/specs/
— technical stuff about standards and specs. -
/templates/
— golden ratio PM templates. -
CONTRIBUTING
— guidelines for submitting contents and collaborating. -
LICENSE
— Apache 2.0 license.
Here are some quick links to the HTML version of the documents via GitHub Pages:
The /docs/
folder contains an HTML converted version of every *.asciidoc
file found inside the repository.
This folder was created for the following purposes:
-
Enable end users to read local copies of the documents without needing an AsciiDoc viewer/converter.
-
The contents of that folder can be served over the WWW via GitHub Pages.
-
Direct links to these docs won’t break if their AsciiDoc sources are moved around in the project.
All HTML documents are placed directly in the /docs/
folder, without replicating the directory structure of their AsciiDoc sources within the project.
Therefore, even if the repository folder structure is reorganized, links to the HTML docs will remain unchanged (unless the AsciiDoc source files are renamed).
The whole idea is that *.asciidoc
files should be placed in the folder to which they belong contents-wise, so that they can be read on GitHub while navigating the repository.
GitHub provides live HTML rendering of AsciiDoc, so these documents will be previewable in a nicely formatted manner on GitHub.
The HTML converted docs, on the other hand, are intended for providing direct links which won’t (shouldn’t) break over the course of time, as well as for offline reading via the browser for end users who cloned the repository locally but might not have the required tools to view/convert AsciiDoc files.
Regarding the possibility of serving the HTML files over the Internet (statically) via
GitHub Pages
it can be done
using the /docs/
folder in the master
branch
of every repository (instead of serving the whole master
branch over the Internet, or using a separate gh-pages
branch).
Hence, the /docs/
folder was chosen since it’s treated as a special folder in GitHub when it comes to serving web contents.
Although this is entirely optional, I’ve chosen to leave this possibility open, so that any GitHub clone of the repository can be set to serve these docs over the WWW.
Unless otherwise specified, all assets are release under Apache License v2.0; third party assets and components retain their original license. For the sake of simplicity, any new assets contributed to the project should fall under the same license, or an Apache-compatible license.
This project uses third party resources, either readapted or in their original form. Full credits and licenses can be found in the assets subfolders; here’s an abridged list of authors' aknowledgments and their resources:
-
André Simon — Highlight configuration and langDefs (GNU GPL v3.0).
-
Bram de Haan — Base16 Atelier Sulphurpool color scheme (MIT License).
-
Chris Kempson — Base16 Eighties and Base16 Tomorrow color schemes (MIT License).
-
Dan Allen and The Asciidoctor project — Asciidoctor Backends (MIT License).
-
Jan Zimmerman (PM author) — Pro Motion documentation and assets.
-
Peter Mescalchin — Sass boilerplate (MIT License).
-
Seth Wright — Base16 Google color scheme (MIT License).
-
The Asciidoctor project — Asciidoctor Extensions Lab (MIT License).
-
Thiadmer Riemersma — C implementation of PM DDE plugin interface.