Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/home.html

73 lines
3.2 KiB
HTML
Raw Normal View History

Document what all the Django templates are for (imported from commit fa2b6c5327b0004f2c19502471f6717d84705ba7)
2012-10-16 06:03:29 +02:00
{# Home tab of the app, containing messages. #}
Rework recipient bar template to have color block and label column. (imported from commit 423a5becc0f81ee816e38983720b2002777913b0)
2013-06-21 23:17:27 +02:00
<div class="message_area_padder message_list" id="main_div">
Use consistent terminology for loading indicators and spinners (imported from commit 54d14c7176e8feb125de253d1bf6205013d53760)
2013-01-16 19:50:18 +01:00
<div id="loading_more_messages_indicator"></div>
Use not-tables for loading indicators (imported from commit 37a18feea4366e66d4e0a42d8f66edc55928c5f7)
2013-01-15 21:41:16 +01:00
<div id="page_loading_indicator"></div>
When a narrow would have no messages and just be grey, show a notice instead. (imported from commit 2b2b653805cb1ebdb545f83b20c01f1d6cbde9b7)
2013-02-23 19:38:25 +01:00
<div id="first_run_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _('Welcome to') }} {{product_name}}</h4>
<p>{% trans %}See, the thing about it is... there aren't any messages
Add an initial message to greet you. (And to let you know that it's OK that you have no messages.) This fixes Trac #850 for the case where you first log in. (imported from commit 47741856e34f67bfc2cc91bdc21def75ab6fe09d)
2013-02-12 19:28:21 +01:00
here for you right now. I'm sure someone will eventually send
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
you one.{% endtrans %}</p>
Add an initial message to greet you. (And to let you know that it's OK that you have no messages.) This fixes Trac #850 for the case where you first log in. (imported from commit 47741856e34f67bfc2cc91bdc21def75ab6fe09d)
2013-02-12 19:28:21 +01:00
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<p>{{ _('Or') }}, <strong>{{ _('take matters into your own hands') }}</strong>,
{{ _('and') }} <a href="#" class="empty_feed_compose_stream">
{{ _('compose a new stream message') }}</a>.</p>
Add an initial message to greet you. (And to let you know that it's OK that you have no messages.) This fixes Trac #850 for the case where you first log in. (imported from commit 47741856e34f67bfc2cc91bdc21def75ab6fe09d)
2013-02-12 19:28:21 +01:00
</div>
When a narrow would have no messages and just be grey, show a notice instead. (imported from commit 2b2b653805cb1ebdb545f83b20c01f1d6cbde9b7)
2013-02-23 19:38:25 +01:00
<div id="empty_narrow_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _("Nothing's been sent here yet!") }}</h4>
When a narrow would have no messages and just be grey, show a notice instead. (imported from commit 2b2b653805cb1ebdb545f83b20c01f1d6cbde9b7)
2013-02-23 19:38:25 +01:00
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<p>{{ _('Why not') }} <a href="#" class="empty_feed_compose_stream">
{{ _('start the conversation') }}</a>?</p>
When a narrow would have no messages and just be grey, show a notice instead. (imported from commit 2b2b653805cb1ebdb545f83b20c01f1d6cbde9b7)
2013-02-23 19:38:25 +01:00
</div>
Add empty feed notices for private messages (imported from commit e4067336f6b2e9e82b794599d30dfc3825852652)
2013-04-02 20:57:53 +02:00
<div id="empty_narrow_all_private_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _('You have no private messages yet!') }}</h4>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<p>{{ _('Why not') }} <a href="#" class="empty_feed_compose_private">
{{ _('start the conversation') }}</a>?</p>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
</div>
Add empty feed notices for private messages (imported from commit e4067336f6b2e9e82b794599d30dfc3825852652)
2013-04-02 20:57:53 +02:00
<div id="empty_narrow_private_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _('You have no private messages with this person yet!') }}</h4>
Add empty feed notices for private messages (imported from commit e4067336f6b2e9e82b794599d30dfc3825852652)
2013-04-02 20:57:53 +02:00
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<p>{{ _('Why not') }} <a href="#" class="empty_feed_compose_private">
{{ _('start the conversation') }}</a>?</p>
Add empty feed notices for private messages (imported from commit e4067336f6b2e9e82b794599d30dfc3825852652)
2013-04-02 20:57:53 +02:00
</div>
<div id="empty_narrow_multi_private_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _('You have no private messages with these people yet!') }}</h4>
Add empty feed notices for private messages (imported from commit e4067336f6b2e9e82b794599d30dfc3825852652)
2013-04-02 20:57:53 +02:00
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<p>{{ _('Why not') }} <a href="#" class="empty_feed_compose_private">
{{ _('start the conversation') }}</a>?</p>
Add empty feed notices for private messages (imported from commit e4067336f6b2e9e82b794599d30dfc3825852652)
2013-04-02 20:57:53 +02:00
</div>
Improve error message when narrowed to nonexistant or silent users. Fixes #1418.
2016-07-29 16:15:50 +02:00
<div id="silent_user" class="empty_feed_notice">
<h4>{{ _("You haven't received any messages sent by this user yet!") }}</h4>
</div>
<div id="non_existing_user" class="empty_feed_notice">
<h4>{{ _("This user does not exist!") }}</h4>
</div>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
<div id="nonsubbed_stream_narrow_message" class="empty_feed_notice">
Add subscribe button in narrowed view when stream has no messages. A temporary message appears on successful subscription, with a button offering to unsubscribe in case the user subscribed by accident.
2016-03-22 16:50:09 +01:00
<h4>{{ _("You aren't subscribed to this stream and nobody has talked about that yet!") }}</h4>
<div class="sub_button_row">
<button class="btn empty_feed_sub_unsub btn-default" type="button" name="subscription">
Subscribe
</button>
</div>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
</div>
<div id="empty_star_narrow_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _("You haven't starred anything yet!") }}</h4>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
</div>
Add "Mentioning messages" to the upper left sidebar. Treat "mentioned" messages like "starred" messages for narrowing. Lots of ugly copy/paste here. There might be opportunity for some cleanup in places. (imported from commit e7629890d42643c0000e1cc85422b2a0690f2cc4)
2013-05-29 00:33:03 +02:00
<div id="empty_narrow_all_mentioned" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _("You haven't been mentioned yet") }}.</h4>
Add "Mentioning messages" to the upper left sidebar. Treat "mentioned" messages like "starred" messages for narrowing. Lots of ugly copy/paste here. There might be opportunity for some cleanup in places. (imported from commit e7629890d42643c0000e1cc85422b2a0690f2cc4)
2013-05-29 00:33:03 +02:00
</div>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
<div id="empty_search_narrow_message" class="empty_feed_notice">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<h4>{{ _('Nobody has talked about that yet!') }}</h4>
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
</div>
Transition from tables to divs for the message list. This breaks our casperjs tests. (imported from commit c63181c73a24eed4a80bfa56966d1f0871c5edb2)
2013-12-09 20:15:33 +01:00
<div class="message_table focused_table" id="zhome">
</div>
<div class="message_table" id="zfilt">
</div>
Reindent. (imported from commit 58b50e4e8cf39da6986fd0a03202b4b1c4655d51)
2012-10-11 21:13:12 +02:00
<div id="bottom_whitespace"></div>
Responsive compose window. (imported from commit 432223391cf158a6c8902370a911a08fd3179401)
2012-10-11 20:58:44 +02:00
</div>
Switch to fixed sidebar layout and remove bootstrap layout hooks. (imported from commit 060340a2febb7b8df6477a3419e7588a8503e377)
2013-08-13 12:52:26 +02:00
Refactor our different pages into separate templates. They are all included by index.html in different divs. (imported from commit bd8b485516007075d33c2614b1de9f08999e927c)
2012-09-17 20:59:26 +02:00
[manual] Rename Django app from zephyr to zerver. This needs to be deployed to both staging and prod at the same off-peak time (and the schema migration run). At the time it is deployed, we need to make a few changes directly in the database: (1) UPDATE django_content_type set app_label='zerver' where app_label='zephyr'; (2) UPDATE south_migrationhistory set app_name='zerver' where app_name='zephyr'; (imported from commit eb3fd719571740189514ef0b884738cb30df1320)
2013-07-29 23:03:31 +02:00
{% include "zerver/compose.html" %}
Add the ability to show a custom notification in the bar (imported from commit b7b763dc364e143409d862838322d63a05daacc1)
2013-01-31 21:09:23 +01:00
<div id="notifications-area">
</div>