Frontend improvements

[co-dan]

Requires DB schema change

• [x] Parent paste

  a way to visualize all descendents and/or ancestors of a diagram, in a tree??

• [ ] Github login
• [ ] ability to "star" pastes; paste ranking based on the stars

  Does not require DB schema change

• [x] RSS feed
• [x] checkboxes above the box for pasting code listing some common imports and/or pragmas (Diagrams.Prelude, Diagrams.Backend.SVG, etc.), with some checked by default, so users can just easily opt into some standard imports without having to type them out every time
• [ ] expose a simple API for creating new pastes, which could be used for things like pasting directly from emacs/vim. GET request that fetches the code from the url
• [ ] ability to evaluate code without saving it as a paste
• [ ] share pastes (on twitter, facebook?)
• [ ] Switch to the "official" haskell palette: http://www.haskell.org/haskellwiki/Brand
• [x] Change the coursor when hovering over an image, suggesting the ability to pan it
• [x] "about" page with instructions, list of installed packages etc
  • [ ] list of installed packages

Feel free to drop your ideas in the comments. I am not setting a milestone for this right now

[co-dan]

@byorgey proposed that we show diagrams above the code, not below this does make sense, especially if the result is pretty/prettier than the code

[co-dan]

I like it!

Is it also possible to use this as a plain web service, i.e. for evaluating diagrams without creating a new paste first?

Somewhat related: Would it be possible to render diagrams from arbitrary URIs? This way, I could render code from a public etherpad.

http://www.reddit.com/r/haskell/comments/1n4ips/the_aftermath_of_my_gsoc_project/ccfp64r?context=3