##// END OF EJS Templates
scm-app: allow to set documented pyro4 as scm_app_implementation....
scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app

File last commit:

r518:9f9ffd3a default
r632:064401fe default
Show More
sequence.pt
23 lines | 698 B | text/plain | TextLexer
<div tal:define="
item_tmpl item_template|field.widget.readonly_item_template;
oid oid|field.oid;
name name|field.name;
title title|field.title;"
class="deform-seq"
id="${oid}">
<div class="panel panel-default">
<div class="panel-heading">${title}</div>
<div class="panel-body">
<div class="deform-seq-container">
<div tal:define="subfields [ x[1] for x in subfields ]"
tal:repeat="subfield subfields"
tal:replace="structure subfield.render_template(item_tmpl,
parent=field)" />
</div>
<div style="clear: both"></div>
</div>
</div>
</div>