Create post component with @links, reply chains and #tags

[marksyzm]

• Create the API for feeding the posts in (all crud abilities).
• Create the layout for displaying a list
• User permissions on buttons
• Add @linkToUsername, #tag parsing
• Add reply chains
• Add posting functionality with reply chains (full chain, last reply button).
• Add default reply as main thread post item if none set
• Keep screen at bottom of page when editing?

[marksyzm]

So far this is the layout for the posts list:
Desktop:

Mobile:

I'm working on the pagination at the moment too. There's a fair bit to go on this one yet.

[marksyzm]

@toerag @MNI1 thoughts, anyone?

[toerag]

nice and clean 🍡 🍡 double dango

[marksyzm]

It's pretty similar to what we had, but I don't really have a problem with that. I'll start showing off the chains and replies soon after I've done the pagination, and I'll work in the automatic linking for @'s and #'s too

I'm fine with having a dropdown on desktop view.

[marksyzm]

We can always change stuff as we go along. It's less code for me too! @toerag ?

[toerag]

Yup, it's not like they are buttons you're going to be pushing on a regular basis anyway. Hidden is good. 🍡

[marksyzm]

Will do! The only one I do see as being regularly used is the reply button
though... I'm looking to use that to replace the quote button that copies
entire blocks of text. Call me crazy but I have an idea where you can
maintain context of a conversation without having to copy paste stuff in
quotes and trace back through a giant thread, so the reply button will
allow the user to maintain that link whilst keeping it all in one straight
flow like a standard forum. Basically what I'm going to do is put at the
top of each post the user who's speaking to which user, a button to show
the post that's been replied to as a toggle and a button to display a
chain.

It will look like this:
marksyzm > REALITY [last post] [chain]

Where last post is just a picture of a post or something and the chain will
be 2 chains... Something like that.

The quote button will still exist as a manual entry button in the text
editor.

On Thu, 3 Dec 2015, 17:45 Jon notifications@github.com wrote:

Yup, it's not like they are buttons you're going to be pushing on a
regular basis anyway. Hidden is good. [image: 🍡]

—
Reply to this email directly or view it on GitHub
#39 (comment).

I was going to say about the reply button. That function would be used constantly so it should probably be viewable.

You think there'd be room in the mobile view for the reply button too? The bigger the selection area for big greasy thumbs, after all.

[marksyzm]

I reckon we could just have it as a text link and it would look okay, maybe

On Thu, 3 Dec 2015, 21:35 mni1 notifications@github.com wrote:

I was going to say about the reply button. That function would be used
constantly so it should probably be viewable.

You think there'd be room in the mobile view for the reply button too? The
bigger the selection area for big greasy thumbs, after all.

—
Reply to this email directly or view it on GitHub
#39 (comment).

Instead of
Report
Reply
Edit
Delete

It should be
Reply (if included)
Edit
--small padding--
Report
Delete

And maybe colour red below padding.

[marksyzm]

Yeah true :) you don't want those so close together

On Thu, 3 Dec 2015, 21:43 mni1 notifications@github.com wrote:

Instead of
Report
Reply
Edit
Delete

It should be
Reply (if included)
Edit
--small padding--
Report
Delete

And maybe colour red below padding.

—
Reply to this email directly or view it on GitHub
#39 (comment).

[toerag]

couldn't you make it a reply button with a half sized arrow for the drop down to the right of it?

[toerag]

[marksyzm]

That was actually pretty much what I was going to say! Nice one :)

On Thu, Dec 3, 2015 at 11:53 PM Jon notifications@github.com wrote:

[image: captukjhkjhre]
https://cloud.githubusercontent.com/assets/13705627/11577902/fb80dfbe-9a18-11e5-93c1-e1eb4292556a.PNG

—
Reply to this email directly or view it on GitHub
#39 (comment).