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

96 lines
3.6 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. #}
Add a tab bar at the top of the Message list to aid navigation The intent is that this will also make it easier to tell when you are narrowed. (imported from commit 5e37721fbad304d30fc725aacf2cc9e6560e9da2)
2013-05-09 21:12:53 +02:00
<div id="tab_bar" class="notdisplayed">
</div>
<div id="tab_bar_underpadding">
</div>
Make layout more responsive. To be fully responsive, we can basically never specify the width of our container in a fixed number of pixels; otherwise we'll run into the situation where there's an inordinate amount of wasted space on our left and right. So everything needs to change from, e.g. row to row-fluid, and that has a whole cascading series of changes that that implies. (imported from commit 7e2771d916f429548c65c0a00fc4c11397054656)
2013-02-28 19:04:58 +01:00
<div id="floating_recipient_bar">
Make the floating recipient bar visible in Safari (imported from commit 89d73c59a30dd3f8ca3e187834c1f1a56edcf788)
2013-08-22 03:51:38 +02:00
<div class="recipient-bar-content">
<div class="recipient-bar-main">
Make layout more responsive. To be fully responsive, we can basically never specify the width of our container in a fixed number of pixels; otherwise we'll run into the situation where there's an inordinate amount of wasted space on our left and right. So everything needs to change from, e.g. row to row-fluid, and that has a whole cascading series of changes that that implies. (imported from commit 7e2771d916f429548c65c0a00fc4c11397054656)
2013-02-28 19:04:58 +01:00
<table class="floating_recipient">
<tr id="floating_recipient_layout_row" class="ztable_layout_row">
<td class="ztable_col1" />
<td class="ztable_col2" />
</tr>
<tr style="display: none;" id="current_label_stream" class="recipient_row">
Rework recipient bar template to have color block and label column. (imported from commit 423a5becc0f81ee816e38983720b2002777913b0)
2013-06-21 23:17:27 +02:00
<td class="message_header_colorblock"></td>
<td class="message_label_clickable message_header message_header_stream right_part"></td>
Make layout more responsive. To be fully responsive, we can basically never specify the width of our container in a fixed number of pixels; otherwise we'll run into the situation where there's an inordinate amount of wasted space on our left and right. So everything needs to change from, e.g. row to row-fluid, and that has a whole cascading series of changes that that implies. (imported from commit 7e2771d916f429548c65c0a00fc4c11397054656)
2013-02-28 19:04:58 +01:00
</tr>
<tr style="display: none;" id="current_label_private_message" class="recipient_row">
Rework recipient bar template to have color block and label column. (imported from commit 423a5becc0f81ee816e38983720b2002777913b0)
2013-06-21 23:17:27 +02:00
<td class="message_header_colorblock message_header_private_message"></td>
<td class="message_label_clickable message_header message_header_private_message right_part"></td>
Make layout more responsive. To be fully responsive, we can basically never specify the width of our container in a fixed number of pixels; otherwise we'll run into the situation where there's an inordinate amount of wasted space on our left and right. So everything needs to change from, e.g. row to row-fluid, and that has a whole cascading series of changes that that implies. (imported from commit 7e2771d916f429548c65c0a00fc4c11397054656)
2013-02-28 19:04:58 +01:00
</tr>
</table>
Make the floating recipient bar visible in Safari (imported from commit 89d73c59a30dd3f8ca3e187834c1f1a56edcf788)
2013-08-22 03:51:38 +02:00
</div>
Make layout more responsive. To be fully responsive, we can basically never specify the width of our container in a fixed number of pixels; otherwise we'll run into the situation where there's an inordinate amount of wasted space on our left and right. So everything needs to change from, e.g. row to row-fluid, and that has a whole cascading series of changes that that implies. (imported from commit 7e2771d916f429548c65c0a00fc4c11397054656)
2013-02-28 19:04:58 +01:00
</div>
Move the floating stream/subject bar into #narrowbox. This allows us to reposition both of them more cleanly when we resize things. (imported from commit a772d2390bd80146e91181e348930559a9e2f4eb)
2012-10-15 16:53:48 +02:00
</div>
Un-remove the normal narrowbar. (imported from commit 2dbaa7e482db40b65865c252b9eee081655d5f72)
2012-10-15 16:23:20 +02:00
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">
HTML templates: Switch from Humbug to Zulip in user-visible text. (imported from commit 07b4e92c270d3b7b0967ea5b6cf5821bf95d166a)
2013-07-10 22:14:08 +02:00
<h4>Welcome to Zulip</h4>
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
<p>See, the thing about it is... there aren't any messages
here for you right now. I'm sure someone will eventually send
you one.</p>
<p>Or, <strong>take matters into your own hands</strong>,
Remove all inline event handlers This allows blueslip to catch exceptions from the event handlers on these elements in addition to the other benefits that not using inline handlers provide. (imported from commit 2bdcb2496c6c08fa7228a20ce6164b527cf64e41)
2013-04-02 20:47:18 +02:00
and <a href="#" class="empty_feed_compose_stream">
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
compose a new stream message</a>.</p>
</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">
<h4>Nothing's been sent here yet!</h4>
Remove all inline event handlers This allows blueslip to catch exceptions from the event handlers on these elements in addition to the other benefits that not using inline handlers provide. (imported from commit 2bdcb2496c6c08fa7228a20ce6164b527cf64e41)
2013-04-02 20:47:18 +02:00
<p>Why not <a href="#" class="empty_feed_compose_stream">
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
start the conversation</a>?</p>
</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">
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
<h4>You have no private messages yet!</h4>
Remove all inline event handlers This allows blueslip to catch exceptions from the event handlers on these elements in addition to the other benefits that not using inline handlers provide. (imported from commit 2bdcb2496c6c08fa7228a20ce6164b527cf64e41)
2013-04-02 20:47:18 +02:00
<p>Why not <a href="#" class="empty_feed_compose_private">
Tailor empty narrow messages to what you were narrowing for. (imported from commit 876afce2a63d4d6a522ac5300349b2be8805405f)
2013-03-29 19:55:28 +01:00
start the conversation</a>?</p>
</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">
<h4>You have no private messages with this person yet!</h4>
<p>Why not <a href="#" class="empty_feed_compose_private">
start the conversation</a>?</p>
</div>
<div id="empty_narrow_multi_private_message" class="empty_feed_notice">
<h4>You have no private messages with these people yet!</h4>
<p>Why not <a href="#" class="empty_feed_compose_private">
start the conversation</a>?</p>
</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">
<h4>You aren't subscribed to this stream!</h4>
Remove all inline event handlers This allows blueslip to catch exceptions from the event handlers on these elements in addition to the other benefits that not using inline handlers provide. (imported from commit 2bdcb2496c6c08fa7228a20ce6164b527cf64e41)
2013-04-02 20:47:18 +02:00
<p>Want to <a href="#" class="empty_feed_join">join it</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>
<div id="empty_star_narrow_message" class="empty_feed_notice">
<h4>You haven't starred anything yet!</h4>
</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">
<h4>You haven't been mentioned yet.</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="empty_search_narrow_message" class="empty_feed_notice">
<h4>Nobody has talked about that yet!</h4>
</div>
Reindent. (imported from commit 58b50e4e8cf39da6986fd0a03202b4b1c4655d51)
2012-10-11 21:13:12 +02:00
<table class="message_table focused_table" id="zhome">
<tbody>
</tbody>
</table>
<table class="message_table" id="zfilt">
<tbody>
</tbody>
</table>
<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 id="notifications-bar"></div>
</div>