search

monome / dust

norns incantations
GNU General Public License v3.0
72 stars 51 forks source link

Update Awake to 2.0 #297

Closed okyeron closed 5 years ago

okyeron commented 5 years ago

Updated justmat/paths as well.

simonvanderveldt commented 5 years ago

(seems like your commits are done with a different e-mail than your GitHub user)

okyeron commented 5 years ago

Ack. Not sure how that would be, but I’ll try to sort it out

tehn commented 5 years ago

hello everyone.

please do not push 2.0 updates to dust as this repo will cease to exist after the update.

i'd also suggest people update their own scripts--- and if you're going to update someone elses' script please ask first as the update may already be in progress or finished (as is the case with my copy of awake)

i'll be clarifying the approach to sharing and collecting going forward--- in the meantime check out https://github.com/monome/norns/wiki/dust-2.0

in short, i suggest people begin storing scripts in their own repositories. if you're working on a shared library or engine, consider PR'ing to norns and shared/collab scripts can go in we https://github.com/monome/we

thank you for your enthusiasm for 2.0!

okyeron commented 5 years ago

Ok great. But we’re gonna need some starter scripts to beta test.

What is the correct format for “our own repository” (if there is one)

tehn commented 5 years ago

aha, I didn't realize my fixed awake didn't make it into the pre beta update, apologies.

proper format for a repo is described in the dust-2.0 wiki. just a folder with lua files is fine for simple scripts.

On Sat, Feb 23, 2019, 12:25 PM Steven Noreyko notifications@github.com wrote:

Ok great. But we’re gonna need some starter scripts to beta test.

What is the correct format for “our own repository” (if there is one)

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/monome/dust/pull/297#issuecomment-466670974, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPEcPSENgXdWiGdbnSVEZranksDCwAuks5vQXlxgaJpZM4bNzPJ .

okyeron commented 5 years ago

Right - but I'm a bit confused about naming things.

If I start my own new repo for norns scripts - what should that be called? It seems like this should be a consistent thing like "dust" or ? so it can be searchable/findable. If I just call the repo "okyeron" (as it seems you're suggesting in the wiki) then I have a git path that is recursive on my own username github.com/okyeron/okyeron/dust ? and not very descriptive.

So yeah - I'm confused.

tehn commented 5 years ago

one possibility (which I intend to pursue) is the have a repo for a particular script or series of scripts. ie mlr and meadowphysics (where my is actually a series of variations of scripts)

I don't think having just one repo for all of your norns scripts is the best approach to presentation. ie, not everyone is going to want to clone your work in progress everything repo when they want to just try out one more polished script.

re: sorting by author, that was random that it happened with dust 1.0. i would suggest adding an author line to the about text at the top of the list file

TODO copy/refine this text to docs/wiki (I am on a phone now)

On Sat, Feb 23, 2019, 12:36 PM Steven Noreyko notifications@github.com wrote:

Right - but I'm a bit confused about naming things.

If I start my own new repo for norns scripts - what should that be called? It seems like this should be a consistent thing like "dust" or ? so it can be searchable/findable. If I just call the repo "okyeron" (as it seems you're suggesting in the wiki) then I have a git path that is recursive on my own username github.com/okyeron/okyeron/dust ? and not very descriptive.

So yeah - I'm confused.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/monome/dust/pull/297#issuecomment-466671968, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPEcNrCjAuNtfe9jd0gV8lPYnSjKcB3ks5vQXwcgaJpZM4bNzPJ .