b8110c11a4
kfet.open app - Base data (raw_open, last_update...) is stored and shared through cache system. - 2 websockets groups: one for team users, one for other users. - UI is initialized and kept up-to-date with WS. - raw_open and force_close can be updated with standard HTTP requests. At this time, there isn't any restriction on raw_open view. Common sense tell us to change this behavior. Misc - Clean channels routing. - 'PermConsumerMixin': user who sent the message is available as argument in connection_groups method, which returns groups to which the user should be appended on websocket connection (and discarded on disconnection). - New kfet.utils module: should be used for mixins, whatever is useful and not concerns the kfet app. - Clean JS dependencies.
13 lines
390 B
HTML
13 lines
390 B
HTML
{% load static %}
|
|
|
|
<link rel="stylesheet" type="text/css" href="{% static "kfetopen/kfet-open.css" %}">
|
|
<script type="text/javascript" src="{% static "kfetopen/kfet-open.js" %}"></script>
|
|
|
|
<script type="text/javascript">
|
|
$( function() {
|
|
kfet_open = new OpenKfet(
|
|
"{% url "kfet.open.edit_force_close" %}",
|
|
{{ perms.kfet.is_team|yesno:"true,false" }}
|
|
);
|
|
});
|
|
</script>
|