Hi,
I'm just getting started with ModX and am at the very earliest stages of finding my way around, so please feel free to point me to very obvious places if I'm missing some fundamentals.
Most of the content on the site we're building (a student of mine with my help) will be "hypervideo" created with the popcorn.js library (
https://github.com/cadecairos/popcorn-js). Popcorn dynamically adds content to a web page as a media element plays -- so that content is synced to the media player. Site visitors will use the experimental "butter" interface to popcorn to create popcorn videos and submit them to the site, where they will be vetted and then published.
The creation of these videos involves a javascript-heavy UI that allows users to drag and drop elements around -- see here for an example:
http://sandbox.hackinghistory.ca/OHM/assets/butter/test/template.html
What I want to do is to present users with an interface like this one, and allow them to save their work to a custom field in a ModX resource (butter exports the project data in JSON, so everything we need could pro bably be saved in a single field). Then when the resource is displayed back to the viewer, the JSON data will be read and probably munged or fed into a javascript program the reads it, instantiates a popcorn object, and displays the resultant popcorn video.
That second step will also be kinda difficult, but for now I'm stuck on the first part. Is it possible to radically change the appearance of the modX admin interface? Or, failing that, is it possible to allow content to be created outside of the admin interface? If the latter, how would I figure out, for instance, what functions to call when the user hits the "save this video" button?
Again, any level of help would be appreciated. We're trying to get up to speedo n ModX as quickly as possible but might need some guidance if you have the time. thanks!
Matt
