mirrors
/
planiverse
mirror of https://git.stjo.hn/planiverse
1
0
Fork 0
Code Releases Activity
planiverse/resources/views/status.blade.php

59 lines
1.7 KiB
PHP
Raw Normal View History

Add some hr elements for formatting in text-only browsers Added some hr elements to separate statuses when viewing in a text-only browser.
2018-08-25 23:48:58 +01:00
<hr />
Add navigation to the top of the page, rework some CSS Added navigation links to the top of the timeline pages. Updated the HTML/CSS to be a bit more semantic (using article tags), and replaced the broken tooltips with HTML title attributes.
2018-08-19 18:02:02 +01:00
<article>
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
@component('event_info', [
Implement notifications page Created a new page that displays notifications and added it to the global nav. Abstracted out the pagination methods from the timeline controller and put it in a helper class. Abstracted out the event info (account, timestamp, etc.) into its own component.
2018-08-26 01:29:36 +01:00
'account' => $status['account'],
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
'created_at' => $status['created_at'],
'type' => $status['in_reply_to_id'] === null ? null : 'reply'
Implement notifications page Created a new page that displays notifications and added it to the global nav. Abstracted out the pagination methods from the timeline controller and put it in a helper class. Abstracted out the event info (account, timestamp, etc.) into its own component.
2018-08-26 01:29:36 +01:00
])
@endcomponent
Hide statuses if they have spoiler text Hide statuses behind an HTML details element if they have spoiler text.
2018-08-19 18:30:15 +01:00
@if ($status['spoiler_text'] !== '')
<details>
<summary>{{ $status['spoiler_text'] }}</summary>
@component('status_content', ['status' => $status])
@endcomponent
</details>
Display reblogs Made statuses a recursive component so we can display reblogs correctly.
2018-08-12 17:55:07 +01:00
@else
Hide statuses if they have spoiler text Hide statuses behind an HTML details element if they have spoiler text.
2018-08-19 18:30:15 +01:00
@component('status_content', ['status' => $status])
Display reblogs Made statuses a recursive component so we can display reblogs correctly.
2018-08-12 17:55:07 +01:00
@endcomponent
@endif
Introduce pagination and action icons Added action icons (reply, favourite, etc.) to the bottom of every status. Implemented pagination on the timeline views.
2018-08-13 00:28:45 +01:00
<div class="actions">
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
<!-- Context -->
<span title="Expand thread">
<a href="/status/{{ $status['id'] }}/thread">&#10568;</a>
</span>
Introduce pagination and action icons Added action icons (reply, favourite, etc.) to the bottom of every status. Implemented pagination on the timeline views.
2018-08-13 00:28:45 +01:00
<!-- Reply -->
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
<span title="Reply">
Implement reply functionality Created a new status view that shows a single status and permits replies if you're logged in.
2018-08-14 06:19:55 +01:00
<a href="/status/{{ $status['id'] }}">&#8629;</a>
Introduce pagination and action icons Added action icons (reply, favourite, etc.) to the bottom of every status. Implemented pagination on the timeline views.
2018-08-13 00:28:45 +01:00
</span>
<!-- Reblog -->
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
<span title="Reblog">
Implement reblogging Implemented ability to reblog a status.
2018-08-19 18:50:28 +01:00
@if ($status['reblogged'])
<span class="reblogged">
Favour redirects over re-using the same paths I was re-using the same paths for a bunch of stuff in order to minimise redirects (POSTing new statuses to the timeline, or performing actions on a status), but then this breaks the behaviour of the browser's refresh button. I've moved all those actions to their own paths, which helps break up the code, makes the URLs more semantic, and lets you use the refresh button without accidentally performing an action. This is at the expense of an additional HTTP request, but I've tried to minimise the cost by passing through the status from the previous action so we don't have to requery for it on the server side.
2018-08-26 22:34:01 +01:00
<a href="/status/{{ $status['id'] }}/unreblog">&#8634;</a>
Implement reblogging Implemented ability to reblog a status.
2018-08-19 18:50:28 +01:00
</span>
@else
Favour redirects over re-using the same paths I was re-using the same paths for a bunch of stuff in order to minimise redirects (POSTing new statuses to the timeline, or performing actions on a status), but then this breaks the behaviour of the browser's refresh button. I've moved all those actions to their own paths, which helps break up the code, makes the URLs more semantic, and lets you use the refresh button without accidentally performing an action. This is at the expense of an additional HTTP request, but I've tried to minimise the cost by passing through the status from the previous action so we don't have to requery for it on the server side.
2018-08-26 22:34:01 +01:00
<a href="/status/{{ $status['id'] }}/reblog">&#8634;</a>
Implement reblogging Implemented ability to reblog a status.
2018-08-19 18:50:28 +01:00
@endif
{{ $status['reblogs_count'] }}
Introduce pagination and action icons Added action icons (reply, favourite, etc.) to the bottom of every status. Implemented pagination on the timeline views.
2018-08-13 00:28:45 +01:00
</span>
<!-- Favourite -->
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
<span title="Favourite">
Add ability to favourite a status Implemented the ability to favourite and unfavourite a status.
2018-08-18 23:48:00 +01:00
@if ($status['favourited'])
Implement reblogging Implemented ability to reblog a status.
2018-08-19 18:50:28 +01:00
<span class="favourited">
Favour redirects over re-using the same paths I was re-using the same paths for a bunch of stuff in order to minimise redirects (POSTing new statuses to the timeline, or performing actions on a status), but then this breaks the behaviour of the browser's refresh button. I've moved all those actions to their own paths, which helps break up the code, makes the URLs more semantic, and lets you use the refresh button without accidentally performing an action. This is at the expense of an additional HTTP request, but I've tried to minimise the cost by passing through the status from the previous action so we don't have to requery for it on the server side.
2018-08-26 22:34:01 +01:00
<a href="/status/{{ $status['id'] }}/unfavourite">&#9733;</a>
Implement reblogging Implemented ability to reblog a status.
2018-08-19 18:50:28 +01:00
</span>
Introduce pagination and action icons Added action icons (reply, favourite, etc.) to the bottom of every status. Implemented pagination on the timeline views.
2018-08-13 00:28:45 +01:00
@else
Favour redirects over re-using the same paths I was re-using the same paths for a bunch of stuff in order to minimise redirects (POSTing new statuses to the timeline, or performing actions on a status), but then this breaks the behaviour of the browser's refresh button. I've moved all those actions to their own paths, which helps break up the code, makes the URLs more semantic, and lets you use the refresh button without accidentally performing an action. This is at the expense of an additional HTTP request, but I've tried to minimise the cost by passing through the status from the previous action so we don't have to requery for it on the server side.
2018-08-26 22:34:01 +01:00
<a href="/status/{{ $status['id'] }}/favourite">&#9734;</a>
Introduce pagination and action icons Added action icons (reply, favourite, etc.) to the bottom of every status. Implemented pagination on the timeline views.
2018-08-13 00:28:45 +01:00
@endif
{{ $status['favourites_count'] }}
</span>
</div>
Add navigation to the top of the page, rework some CSS Added navigation links to the top of the timeline pages. Updated the HTML/CSS to be a bit more semantic (using article tags), and replaced the broken tooltips with HTML title attributes.
2018-08-19 18:02:02 +01:00
</article>
Add some hr elements for formatting in text-only browsers Added some hr elements to separate statuses when viewing in a text-only browser.
2018-08-25 23:48:58 +01:00
<hr />