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

Use "client" and "mediatype" value in Code Objects to selectively show and/or choose how to render code #28

Open
juliendorra opened this issue Nov 30, 2015 · 1 comment

Comments

@juliendorra
Copy link
Collaborator

juliendorra commented Nov 30, 2015

add an optional client value to the Code Object:
"client": "creatureprogrammer" for creatures programmed with Code Créatures workshop dedicated page
Or
"client": "programmer" for the generic objects created from the generic programmer

And a mediatype (mime) value :
"mediatype": "text/processing"
or
"mediatype": "text/javascript"

This is useful because:

  • the client (the code editor page for example) can decide to edit only the code objects it created itself, if it doesn't know how to handle the rest.
  • the renderer (playground page) can make informed choices on how to render things. Example: d3js code doesn't need a canvas and could be rendered without using one.
@juliendorra
Copy link
Collaborator Author

juliendorra commented Dec 14, 2015

client and mediatype are now send from programmer (standard) and creature programmer and stored server side.
But they are not actually used neither by the creature programmer (where it could be useful to sort creatures and standard processing script) nor the renderer (where it could be useful to render differently say d3js, processing pde script and p5js scripts)

@juliendorra juliendorra changed the title "client" and "mediatype" value in Code Objects Use "client" and "mediatype" value in Code Objects to selectively show and/or choose how to render code Jun 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant