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

Renderer #60

Open
8 of 12 tasks
nibra opened this issue Oct 12, 2015 · 0 comments
Open
8 of 12 tasks

Renderer #60

nibra opened this issue Oct 12, 2015 · 0 comments

Comments

@nibra
Copy link
Member

nibra commented Oct 12, 2015

Channel Dependant Renderers

Each possible output channel might require its own output format. The Accept: header is used to determine the requested format. For channels without such a header, like CLI, a fake header is created.

The Accept: header contains a MIME type. The MIME types are assigned to Renderers using an editable map.

  • MIME Mapping
  • JSON Renderer
  • XML Renderer
  • Plain Text Renderer
  • HTML Renderer

Script Strategies

The HTML Renderer supports script strategies, i.e., classes that abstract JavaScript libraries.

Templating

Some Renderers, like HTML, will need a templating system.

Possible Enhancements

These things could be beneficial; they are up to discussion.

  • Jason lets you instantly turn any data, website, or API into your own custom app. It would require its own Renderer.
@nibra nibra self-assigned this Oct 12, 2015
@nibra nibra added this to the 4.0 milestone Oct 12, 2015
@nibra nibra modified the milestones: CDH, 4.0 Jun 2, 2016
@laoneo laoneo closed this as completed Jun 3, 2016
@nibra nibra reopened this Jun 3, 2016
@nibra nibra modified the milestones: EPIC, CDH Jun 16, 2016
@nibra nibra removed their assignment Jun 16, 2016
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

2 participants