Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"passive art" mode? #2

Closed
iangilman opened this issue Nov 11, 2017 · 6 comments
Closed

"passive art" mode? #2

iangilman opened this issue Nov 11, 2017 · 6 comments

Comments

@iangilman
Copy link
Contributor

Beautiful work!

I'm building a website for collecting and enjoying passive art made with code:

http://www.artywidget.com/

… and I'd love to add Field Play as one of the artworks, but it would need a passive mode, with no UI, where it periodically shuffles its own settings. Would you be up for that? I can help with the implementation if you want, but I wanted to check in with you on the possibility first.

Here's a little more about what I mean by "passive art":

https://github.com/pixfabrik/artywidget/wiki/Artwork-Guidelines

Thank you for your consideration!

@anvaka
Copy link
Owner

anvaka commented Nov 15, 2017

Thank you!

I like your website. I think we could add a special query string argument which would serve as a flag to hide all UI elements from the field play.

As for progressively randomizing - need to think more about it. Technically you could just have a list of nice looking vector fields and loop over it.

The equation randomizer in this repository is very naive and becomes repetitive after a while.

@iangilman
Copy link
Contributor Author

Awesome... Glad you like the idea!

I've been suggesting ui=0 as the UI-hiding query string param. I think it's reasonable that the randomizing could be triggered by the same param, since it's sort of a logical extension of not having UI.

I like the idea of doing the "randomization" for the passive mode with a list of nice looking settings (which could of course be shuffled). I imagine you've already collected a good number of them.

Do you want me to take a wack at getting this rolling, or is it something you want to do?

@anvaka
Copy link
Owner

anvaka commented Nov 18, 2017

Please, feel free to try it. I'd still keep ui=0 separate from the code generation, to conform to single responsibility principle.

I was thinking about adding scripted support of field manipulation, where a single JSON file could define timeline of a field evolution. E.g.

evolution: [{
  time: timeOffsetInMilliseconds,
  state: object that defines application state (field, code settings, etc.)
}, {
  time: ...
  state: ...
}, {
  ...
}]

Maybe some elements of this timeline could trigger random function generation, and some elements would allow to route control to a given element (allowing loops). This is a long term feature, which would allow artists to script their fields.

@iangilman
Copy link
Contributor Author

Great! I've made a PR for ui=0. I'll make a second one for the "progressive" mode; any thoughts on what that url param should be called? Progressive? Random? Shuffle? Changing? :)

Also, the param could be a number of seconds rather than just a flag, so you can control how often it changes. changetime=60 for instance.

The scripting feature sounds cool! I guess this can be a first step towards that.

@iangilman
Copy link
Contributor Author

I guess this is well under way, so we can close this issue.

@iangilman
Copy link
Contributor Author

… And added!

http://www.artywidget.com/artwork/5a7f76ffcba62e0029f53498/

Thank you for working with me on this :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants