nla / pavo Goto Github PK

Import the core of PAVO and just enough supporting files to get a single runnable example widget.

We should include a minimal Sinatra demo app that you can just run. Just include this in the top-level now until we've decided on #2.

Include a bundler Gemfile but don't commit the gems themselves. While it's convenient for our internal deploys it's frowned upon for proper projects. ;-)

Many of PAVO's dependencies are dual-licensed under MIT and GPL so that would be a starting point.

If we want to include a widget that wraps the Internet Archive Bookreader, pay attention to implications of its AGPL licensing.

Do we have to get some sort of approval on the licensing choice?

Should we just bundle all our js dependencies (jQuery etc)? Is there a better way to pull them down at packaging time and minify them (like bundler, maven and friends do for server-side code).

Alternatively we could pull them by default from a CDN see this SO.

How do we package PAVO widgets for use by end-user applications like AMAD? Are we a js library, ruby gem, web service or a project skeleton?

I've included Payten's helloworld widget in the README but it could be improved a little. I think we should:

• Tidy up some of the names so they're a bit shorter.
• Include a example of using config.json. Maybe make the message text settable there.