Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/zephyr/static/templates/actions_popover_content.han...

61 lines
1.7 KiB
Handlebars
Raw Normal View History

Rename userinfo_popover -> actions_popover (imported from commit fab5a44af1acaf93640a2f57ffc25b3e97f55d2e)
2013-02-08 23:03:33 +01:00
{{! Contents of the "message actions" popup }}
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<ul class="nav nav-list actions_popover pull-right">
Combine the actions popover with the timeinfo popover The message timestamp is now always clickable, and the popover contains the full long-form date and time. This addresses one problem from usability testing (see #470). (imported from commit ad502dff128ad1c934fc0d3faaf5e2931c91c37e)
2013-02-09 03:29:40 +01:00
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="respond_button">
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
<i class="icon-share-alt"></i>
{{#if message.is_stream}}
Store the recipient stream name in message.stream. Previously we were using message.display_recipient everywhere, which is actually pretty confusing. (imported from commit a58471172e28c039af8e290362e54b6660543924)
2013-04-18 17:13:43 +02:00
Reply to this subject on stream <b>{{message.stream}}</b>
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
{{else}}
Reply to this private message
{{/if}}
Combine the actions popover with the timeinfo popover The message timestamp is now always clickable, and the popover contains the full long-form date and time. This addresses one problem from usability testing (see #470). (imported from commit ad502dff128ad1c934fc0d3faaf5e2931c91c37e)
2013-02-09 03:29:40 +01:00
</a>
</li>
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
{{#unless message.is_private}}
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="respond_personal_button">
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
<i class="icon-user"></i> Reply to <b>{{message.sender_full_name}}</b> only
</a>
</li>
{{/unless}}
actions: Add narrowing to the popover This addresses another usability problem from #470. I decided it was too confusing to have menu options for both stream and subject narrowing, so I went with the latter. (imported from commit 948fca954a265029ceb27c72ae178015d513785d)
2013-02-09 08:47:01 +01:00
{{#if message.is_stream}}
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="popover_narrow_by_subject_button" data-msgid="{{message.id}}">
actions: Add narrowing to the popover This addresses another usability problem from #470. I decided it was too confusing to have menu options for both stream and subject narrowing, so I went with the latter. (imported from commit 948fca954a265029ceb27c72ae178015d513785d)
2013-02-09 08:47:01 +01:00
<i class="icon-bullhorn"></i>
Store the recipient stream name in message.stream. Previously we were using message.display_recipient everywhere, which is actually pretty confusing. (imported from commit a58471172e28c039af8e290362e54b6660543924)
2013-04-18 17:13:43 +02:00
Narrow to this subject on stream <b>{{message.stream}}</b>
actions: Add narrowing to the popover This addresses another usability problem from #470. I decided it was too confusing to have menu options for both stream and subject narrowing, so I went with the latter. (imported from commit 948fca954a265029ceb27c72ae178015d513785d)
2013-02-09 08:47:01 +01:00
</a>
</li>
{{else}}
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="popover_narrow_by_recipient_button" data-msgid="{{message.id}}">
actions: Add narrowing to the popover This addresses another usability problem from #470. I decided it was too confusing to have menu options for both stream and subject narrowing, so I went with the latter. (imported from commit 948fca954a265029ceb27c72ae178015d513785d)
2013-02-09 08:47:01 +01:00
<i class="icon-user"></i>
Narrow to this private message conversation
</a>
</li>
{{/if}}
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
{{#if narrowed}}
Pop up a little box of info/actions when you click a name or gravatar. Known issues: * Not all of the options in the menu are functional yet * The wording isn't totally perfect on some of these options; I kind of want to use a 'first name' in some of them. (imported from commit 5a333fb939fcca7e0d0ecb2c43e79501139ac0db)
2012-10-18 20:23:57 +02:00
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="popover_narrow_by_time_travel_button" data-msgid="{{message.id}}">
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
<i class="icon-time"></i> Narrow to messages around this time
Pop up a little box of info/actions when you click a name or gravatar. Known issues: * Not all of the options in the menu are functional yet * The wording isn't totally perfect on some of these options; I kind of want to use a 'first name' in some of them. (imported from commit 5a333fb939fcca7e0d0ecb2c43e79501139ac0db)
2012-10-18 20:23:57 +02:00
</a>
</li>
In the actions popover, put the most basic/common actions first (imported from commit b2de5c1accffc776abe651c2140643ad380bb1e8)
2013-03-19 19:35:11 +01:00
{{/if}}
Add user interface frontend for editing messages. The only known outstanding bug with this is that it doesn't properly handle the updating of a message's highlighting/presence in a narrowed view (e.g. in theory, a message should disappear if it is edited such that its subject doesn't match your narrow or it no longer matches your search). I think I'll just open a trac ticket about that once this is merged, since it's a little hairy to deal with and kinda a marginal use case. Also it's not pretty, but that should be easy to tweak once we get the framework merged. Conflicts: tools/jslint/check-all.js (imported from commit 2d0e3a440bcd885546bd8e28aff97bf379649950)
2013-05-15 00:22:16 +02:00
{{#if can_edit_message}}
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="popover_edit_message" data-msgid="{{message.id}}">
Add user interface frontend for editing messages. The only known outstanding bug with this is that it doesn't properly handle the updating of a message's highlighting/presence in a narrowed view (e.g. in theory, a message should disappear if it is edited such that its subject doesn't match your narrow or it no longer matches your search). I think I'll just open a trac ticket about that once this is merged, since it's a little hairy to deal with and kinda a marginal use case. Also it's not pretty, but that should be easy to tweak once we get the framework merged. Conflicts: tools/jslint/check-all.js (imported from commit 2d0e3a440bcd885546bd8e28aff97bf379649950)
2013-05-15 00:22:16 +02:00
<i class="icon-pencil"></i> Edit this message
</a>
</li>
{{/if}}
Add support for completely collapsing messages through the info popover. (imported from commit 0a01c4cc8f99019233659c175d73826e16cc95ee)
2013-05-08 23:17:49 +02:00
<li>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<a href="#" class="popover_toggle_collapse" data-msgid="{{message.id}}">
Add support for completely collapsing messages through the info popover. (imported from commit 0a01c4cc8f99019233659c175d73826e16cc95ee)
2013-05-08 23:17:49 +02:00
<i class="{{#if message.collapsed}}icon-plus{{else}}icon-minus{{/if}}"></i>
{{#if message.collapsed}}Un-collapse{{else}}Collapse{{/if}} this message
</a>
</li>
Pop up a little box of info/actions when you click a name or gravatar. Known issues: * Not all of the options in the menu are functional yet * The wording isn't totally perfect on some of these options; I kind of want to use a 'first name' in some of them. (imported from commit 5a333fb939fcca7e0d0ecb2c43e79501139ac0db)
2012-10-18 20:23:57 +02:00
</ul>