1. Rendering large amounts of data seems to be of poor performance
2. Developers reported having a hard time using XSL
Trimpath Template Engine (JST) .
Regarding point of criticism 1. : I conducted a little experiment in which
the same dataset (of variable size) was rendered using our current
approach the JQuery.xslt plugin and the JST library . The outcome was
that JST was nearly twice as fast as XSL.
Regarding point of criticism 2. : With JST the developer can use use
a way analogous to who things work in PHP. This should for the most people
be more convenient to use than XSLs resolution like mechanism.
Also the possibility to uses JS inside the templates offers more
flexibility when rendering the data. Easy example: endpoint returns
timestamp, but we want to have the value of Date.toLocaleString() shown in
What has to be done in order to switch to JST:
On Client side the JST js library must be included and the XSL templates
have to be rewritten as JST templates.
On Server side every endpoint that should be used together with JST must
provied the data in JSON format. JST is not able to deal with XML.
In a first step I will switch to Trimpath in the Recording Screens. Since there are several UI and endpoints that must be switched to JST / JSON (for the endpoints), I think it's reasonable to convert this to a task with subtasks for the individual UIs and endpoints.
Benjamin, my understanding is that both you and Micah have spare cycles this iteration. I'd like to extend this to all of the admin UI components to fill in the gap. Beyond recordings, upload, scheduling, edit/view, and hold panes, what else needs to be converted? What other endpoints need to be addressed? Please break these up into additional tasks split amongst you and Micah with estimates. Thanks!