Commit 124b42eb authored by Jonathan Wilkes's avatar Jonathan Wilkes
Browse files

clean up links and add Albert's intro and guide

parent 9ddde963
Pipeline #1251 canceled with stage
in 9 minutes and 5 seconds
...@@ -6,15 +6,14 @@ maintainers: ...@@ -6,15 +6,14 @@ maintainers:
* Albert Graef <aggraef@gmail.com> * Albert Graef <aggraef@gmail.com>
* Jonathan Wilkes <jancsika@yahoo.com> * Jonathan Wilkes <jancsika@yahoo.com>
[Downloads](https://github.com/jonwwilkes/purr-data/releases)
[Mailing List](http://disis.music.vt.edu/cgi-bin/mailman/listinfo/l2ork-dev) [Mailing List](http://disis.music.vt.edu/cgi-bin/mailman/listinfo/l2ork-dev)
* [Downloads](#downloads)
* [One Paragraph Overview](#one-paragraph-overview) * [One Paragraph Overview](#one-paragraph-overview)
* [Three Paragraph Overview](#three-paragraph-overview) * [Three Paragraph Overview](#three-paragraph-overview)
* [Goals](#goals) * [Goals](#goals)
* [Introduction](#introduction-to-purr-data)
* [Relationship of Purr Data to Pure Data](#relationship-of-purr-data-to-pure-data) * [Relationship of Purr Data to Pure Data](#relationship-of-purr-data-to-pure-data)
* [Downloads](#downloads)
* [Build Guide](#build-guide) * [Build Guide](#build-guide)
* [Gnu/Linux](#linux) * [Gnu/Linux](#linux)
* [OSX](#osx-64-bit-using-homebrew) * [OSX](#osx-64-bit-using-homebrew)
...@@ -32,8 +31,6 @@ create software graphically by drawing diagrams instead of writing lines of ...@@ -32,8 +31,6 @@ create software graphically by drawing diagrams instead of writing lines of
code. These diagrams show how data flows through the software, displaying on code. These diagrams show how data flows through the software, displaying on
the screen what text-based languages require you to piece together in your mind. the screen what text-based languages require you to piece together in your mind.
### Three Paragraph Overview ### Three Paragraph Overview
Pd has been designed with an emphasis on generating sound, video, Pd has been designed with an emphasis on generating sound, video,
...@@ -66,6 +63,16 @@ Pd-L2ork has the following goals: ...@@ -66,6 +63,16 @@ Pd-L2ork has the following goals:
documentation. We like documentation, so it follows that we like consistent documentation. We like documentation, so it follows that we like consistent
interfaces. interfaces.
### Introduction to Purr Data
For a quick introduction to Purr Data see:
[https://agraef.github.io/purr-data/](https://agraef.github.io/purr-data/)
For a more in-depth look at Purr Data for new users and developers, see:
[https://agraef.github.io/purr-data-intro/Purr-Data-Intro.html](https://agraef.github.io/purr-data-intro/Purr-Data-Intro.html)
### Relationship of Purr Data to Pure Data ### Relationship of Purr Data to Pure Data
There are three maintained distributions of Pure Data: There are three maintained distributions of Pure Data:
...@@ -82,11 +89,15 @@ There are three maintained distributions of Pure Data: ...@@ -82,11 +89,15 @@ There are three maintained distributions of Pure Data:
### Downloads ### Downloads
You can download a precompiled installer for Gnu/Linux, Windows, or OSX For Ubuntu PPAs and Arch AUR, see the JGU Packages:
from the following site:
[https://github.com/jonwwilkes/purr-data/releases](https://github.com/jonwwilkes/purr-data/releases) [https://agraef.github.io/purr-data/#jgu-packages](https://agraef.github.io/purr-data/#jgu-packages)
Precompiled installer for Gnu/Linux, Windows, or OSX
are available here:
[https://github.com/jonwwilkes/purr-data/releases](https://github.com/jonwwilkes/purr-data/releases)
### Build Guide ### Build Guide
**NOTE:** The instructions below talk about running the `tar_em_up.sh` build **NOTE:** The instructions below talk about running the `tar_em_up.sh` build
...@@ -603,4 +614,4 @@ primitives (numbers, strings, and arrays). For the arrays, Javascript's array ...@@ -603,4 +614,4 @@ primitives (numbers, strings, and arrays). For the arrays, Javascript's array
notation is used. This is a highly idiosyncratic, quick-and-dirty approach. notation is used. This is a highly idiosyncratic, quick-and-dirty approach.
But the point is that the idiosyncracy exists in a single file of the source But the point is that the idiosyncracy exists in a single file of the source
code, and can be easily made more modular (or replaced entirely by something code, and can be easily made more modular (or replaced entirely by something
else) without affecting _any_ of the rest of the C code. else) without affecting _any_ of the rest of the C code.
\ No newline at end of file
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment