We're looking to add a new upload capability - a media package .zip file. To do so we tracked down how the inbox upload works and it blows my mind. We have a filechooser-inbox.html loaded into an iframe but this isn't really an html file, it's a rest endpoint that creates a job and returns some html.
This was hella confusing to me; is there some overarching strategy to how the admin ui file interaction happens, or is this just a case of cruft coming in as features came up? Or am I out to lunch and is this the modern way of doing html in an SOA world? And you'll have to forgive me as I'm not a web dev, but the templates that are html fragments; is there a reason they are named *.tpl (is this a framework of some kind? Or just a naming convention?) Regards, chris _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
