Hi Chris,
so comments inline
Am 07.12.2011 18:21, schrieb [email protected]:
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.
yes, it's a bit confusing on first sight. This iFrame is needed, because
there may be more than one file that needs to be uploaded. So the
Restendpoint creates a WatchedJob (in order to track the progress of the
upload) and renders the HTML file with the jobId as a field. Further
fields are the flavor and a type (eg. catalog/track)
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?
Sure this is not ideal and not very common, but thats how the
requirements looked like.
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?)
with version 1.3 I changed the structure of the admin UI. Before we had
about 8 or 9 different HTML pages, which needed to be maintained. Now
it's only the index.html and its templates (*.tpl) which are rendered on
client side via a modified version of jquote
(http://aefxx.com/jquery-plugins/jqote/). Because of this changes it's
much easier to maintain the admin UI and we can assure that every page
looks the same.
If you have further questions or need some advice, go ahead. I'll try to
answer.
Regards,
Markus
Regards,
chris
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
