Releases: dktr0/estuary
19 Oct 2018
This is built release of the Estuary client (major performance improvements in this release). For instructions on how to use this built release see the main README by scrolling down here https://github.com/d0kt0r0/estuary
If you are using this Estuary client with your own deployment of an Estuary server, it is strongly recommended that you also rebuild the server.
18 Oct 2018 release
This is built release of the Estuary client (major performance improvements in this release). For instructions on how to use this built release see the main README by scrolling down here https://github.com/d0kt0r0/estuary
If you are using this Estuary client with your own deployment of an Estuary server, it is strongly recommended that you also rebuild the server.
5 Oct 2018 release
This is built release of the Estuary client (text code editors have configurable numbers of rows in this release). For instructions on how to use this built release see the main README by scrolling down here https://github.com/d0kt0r0/estuary
If you are using this Estuary client with your own deployment of an Estuary server, it is strongly recommended that you also rebuild the server.
02 Oct 2018 release
This is built release of the Estuary client (improvements to MiniTidal in this release). For instructions on how to use this built release see the main README by scrolling down here https://github.com/d0kt0r0/estuary
If you are using this Estuary client with your own deployment of an Estuary server, it is strongly recommended that you also rebuild the server.
22 Sept 2018 release
This release contains a pre-built Javascript client for Estuary. As of this release, mini-languages over Tidal are unified such that choice of language is an "in-performance" notation (ie. choice of language can be made on the fly in an editor window via a drop-down menu). For installation/use instructions, see the main README by scrolling down here https://github.com/d0kt0r0/estuary
Note for anyone intending to use this release with an existing server: there is a breaking change to the client-server communication protocol inherent to this release. You'll need to rebuild the server, and also delete any previous Estuary databases (ie. the Estuary.db file in the Estuary project folder that contains the current state of ensembles for that deployment).
18 Sept 2018 client release
This is a release of a pre-built JavaScript client for Estuary to be used with or without an Estuary server (just add samples, though!). For help with getting started with it, see the instructions in the main README here https://github.com/d0kt0r0/estuary (and scroll down).
17 Sept 2018 client release
This is a release of a pre-built JavaScript client for Estuary to be used with or without an Estuary server (just add samples, though!).
17 Sept 2018 client release (updated version b)
20180917b change to EstuaryProtocol.js to be robust to situations where web con…
16 June 2018 release
This release contains a JavaScript build of Estuary's client. In all cases you'll need to add samples to it - folders of samples should be in a subfolder called samples in a subfolder called Dirt of the main folder/directory you get when you unpack the release. It is possible to just download Dirt with its samples and move it into the unpacked build folder. There are two main ways you might use this built release:
-
For local, non-networked, non-collaborative use: you can just load the file index.html from the Estuary.jsexe folder with a web browser, then proceed to enjoy Estuary's solo modes.
-
For collaborative use with an Estuary server - especially when you are able to build the server (using ghc, typically a straightforward process on many machines) but are unable (or don't have the time) to build the client (using the sometimes less straightforward ghcjs toolchain). In this case, follow the instructions to build the server, then place the Estuary.jsexe folder in your Estuary folder (the one you cloned from github). Launch the server from the same place (Estuary folder) something like this: EstuaryServer/EstuaryServer someAdminPassword - now you can connect to your local server by pointing your browser to 127.0.0.1:8002 (and others can connect to your server by replacing 127.0.0.1 with your IP address on a network you share).
Note: if you just want to try Estuary out, easier and faster than both of the above methods is just connecting to a server someone already has running. No installation is required - just pointing your web browser to the right place. As of June 2018 there is typically a running Estuary server at intramuros.mcmaster.ca:8002, with discussion/help about it on the #estuary channel on talk.lurk.org.
27 July 2017 release
This release contains a JavaScript build of Estuary's client. To use it, unpack the ZIP folder somewhere. You'll need to add samples to it. Folders of samples should be in a subfolder called samples in a subfolder called Dirt of the main folder/directory you get when you unpack the build. It is possible to just download Dirt with its samples and move it into the unpacked build folder.
Note: For full collaborative use of Estuary, you'll need to use a server that someone has running somewhere, or build and run your own Estuary server (the server binary is not currently provided in the attached JavaScript folder, although we could include such binaries for various platforms in the future).
Conversely: if you just want to try it out, it's way easier and faster to just connect to a server someone already has running. No installation is required - just pointing your web browser to the right place. As of July 2017 there is typically a running Estuary server at intramuros.mcmaster.ca:8002. If you don't find one there, feel free to post an issue here asking for pointers to where a server might be found!