archive/pillar
0
0
Fork 0
Code Issues 42 Pull Requests Projects Releases Wiki Activity
Files
47474ac936ffb1d179161c8a3cac5d20e6005659
pillar/src/templates/menus/user_base.pug

51 lines
1.1 KiB
Plaintext
Raw Normal View History

Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% block menu_body %}
| {% if current_user.is_authenticated %}
General cleanup
2018-08-28 15:52:50 +02:00
li.dropdown
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% block menu_avatar %}
a.navbar-item.dropdown-toggle(href="#", data-toggle="dropdown", title="{{ current_user.email }}")
Replaced Gravatar with self-hosted avatars Avatars are now obtained from Blender ID. They are downloaded from Blender ID and stored in the users' home project storage. Avatars can be synced via Celery and triggered from a webhook. The avatar can be obtained from the current user object in Python, or via pillar.api.users.avatar.url(user_dict). Avatars can be shown in the web frontend by: - an explicit image (like before but with a non-Gravatar URL) - a Vue.js component `user-avatar` - a Vue.js component `current-user-avatar` The latter is the most efficient for the current user, as it uses user info that's already injected into the webpage (so requires no extra queries).
2019-05-24 17:36:06 +02:00
current-user-avatar
script.
new Vue({el: 'current-user-avatar'})
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% endblock menu_avatar %}
General cleanup
2018-08-28 15:52:50 +02:00
ul.dropdown-menu.dropdown-menu-right
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% if not current_user.has_role('protected') %}
| {% block menu_list %}
Navigation: Unified cloud navigation * Removed main drop down menu * Added "My cloud" to user menu * Attract/Flamenco is found under Production Tools menu * Attract/Flamenco has the same navigation as its project
2019-02-06 10:31:36 +01:00
li
a.navbar-item.px-2(
href="{{ url_for('projects.home_project') }}"
title="My cloud")
| #[i.pi-home] My cloud
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
li
Navbar: Padding for items
2018-09-12 19:00:29 +02:00
a.navbar-item.px-2(
href="{{ url_for('settings.profile') }}"
title="Settings")
Layout: use bootstrap classes
2018-08-31 19:31:36 +02:00
| #[i.pi-cog] Settings
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% endblock menu_list %}
General cleanup
2018-08-28 15:52:50 +02:00
li.dropdown-divider(role="separator")
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% endif %}
li
a.navbar-item(
Navbar: Padding for items
2018-09-12 19:00:29 +02:00
href="{{ url_for('users.logout') }}")
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
i.pi-log-out(title="Log Out")
| Log out
Navbar: Padding for items
2018-09-12 19:00:29 +02:00
a.navbar-item.subitem.pt-0(
href="{{ url_for('users.switch') }}")
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
i.pi-blank
| Not {{ current_user.full_name }}?
| {% else %}
Cleanup and replace custom styles with bootstrap classes.
2018-09-17 17:08:46 +02:00
li.pr-1
Layout: use bootstrap classes
2018-08-31 19:31:36 +02:00
a.btn.btn-sm.btn-outline-primary.px-3(
href="{{ url_for('users.login') }}")
| Log In
Switch from macros to blocks for navigation menus This affects the user and notifications menus. It happens for two reasons: - the only argument passed to the macros was current_user, which is always available - we want to enable overriding and adding items to the menus via extensions At the moment only the user menu takes advantage of the base template, since the blender-cloud extension makes use of it, while notifications.pug does not need it yet.
2017-12-13 11:08:33 +01:00
| {% endif %}
| {% endblock menu_body %}
Reference in New Issue Copy Permalink