[ rss / options / help ]
post ]
[ b / iq / g / zoo ] [ e / news / lab ] [ v / nom / pol / eco / emo / 101 / shed ]
[ art / A / beat / boo / com / fat / job / lit / map / mph / poof / £$€¥ / spo / uhu / uni / x / y ] [ * | sfw | o ]
logo
sheds

Return ]

Posting mode: Reply
Reply ]
Subject   (reply to 13736)
Message
File  []
close
>> ID: 85c23c No. 13736 Anonymous
4th May 2016
Wednesday 11:23 am

ID: 85c23c
13736 spacer
>Message too long. Click here to view the full text.

Instead of this, could we have "mouseover here to see the rest of the text"? Or maybe "click to expand the rest of this post" in the same page? I have no experience of web development and consequently no idea how feasible/easy that is, but it'd be nice, in /*/ especially and for those long threads.
Expand all images.
>> ID: ae580c No. 13737 Anonymous
4th May 2016
Wednesday 11:43 am

ID: ae580c
13737 spacer
lol
>> ID: 1acd08 No. 13738 Anonymous
4th May 2016
Wednesday 1:23 pm

ID: 1acd08
13738 spacer
The problem with 'click here' is that it takes you to the full page, which is crap when the thread is thousands of replies long and you only wanted to quickly read that post, or you're on a mobile device or similar that can't load that large and thread and crashes.
>> ID: ae580c No. 13739 Anonymous
4th May 2016
Wednesday 1:35 pm

ID: ae580c
13739 spacer
>>13738
Retraining yourself to click "Last 50 messages" will be quicker than waiting for the site to be updated.
>> ID: 1acd08 No. 13740 Anonymous
4th May 2016
Wednesday 1:46 pm

ID: 1acd08
13740 spacer
>>13739
I do do that. But you have to scroll all the way down to the bottom, which is aother problem, especially in large, discussion-heavy threads. Not including having to scroll back up to the last 50 link in the first place.

It's just not ergonomic at all.
>> ID: ae580c No. 13741 Anonymous
4th May 2016
Wednesday 1:57 pm

ID: ae580c
13741 spacer
>>13740
We can start a gofundme to raise enough money to try and employ some new programmers if you like.
>> ID: 1acd08 No. 13742 Anonymous
4th May 2016
Wednesday 2:37 pm

ID: 1acd08
13742 spacer
>>13741
Can we start one to pay you to not be a sarcastic arse when posters make reasonable requests?
>> ID: ae580c No. 13744 Anonymous
4th May 2016
Wednesday 2:46 pm

ID: ae580c
13744 spacer
>>13742
I'm not being entirely sarcastic. You think I don't have the same problems with the site as you do?
>> ID: 4437b8 No. 13745 Anonymous
4th May 2016
Wednesday 2:50 pm

ID: 4437b8
13745 spacer
>>13744
You're doing a crap job. If I could hurl £5 coins at you I would.
>> ID: ae580c No. 13746 Anonymous
4th May 2016
Wednesday 3:03 pm

ID: ae580c
13746 spacer
>>13745
Yeah, sure, dude hiding behind a proxy.
All the admin, of which I'm not one, have put in a shit load of time and effort, and even money on purple's part to keep this place going. It's no less functional than it was on day one. I don't know how quickly or if ever they'll keep updating it, but it's a massive cheek of you lot to keep getting pissy about this free service that's provided to you not being quite as perfect as you'd like it to be. Yeah, it'd be great if it was, but we don't have the staff, or the ability to pay for new staff, unless you want to step up and open your wallets.
That's just me saying that, by the way. purple isn't asking for donations, I'm just trying to explain basic economics to you.
>> ID: 1acd08 No. 13748 Anonymous
4th May 2016
Wednesday 3:31 pm

ID: 1acd08
13748 spacer
>>13746
Yeah yeah I knew a rant like this was coming. If someone requests something and there aren't the resources to do it, then there's nothing stopping the mods from saying so plainly and simply. I only took issue with you being a smartarse. Anyway, let the mods speak for themselves if you don't actually know what's going on.
>> ID: e09ba8 No. 13749 Anonymous
4th May 2016
Wednesday 5:01 pm

ID: e09ba8
13749 spacer
>>13748
I like how you're implying that being a mod and being a right smartarse are mutually exclusive states. Have you even been here before?
>> ID: ae580c No. 13752 Anonymous
4th May 2016
Wednesday 9:28 pm

ID: ae580c
13752 spacer
>>13748
If you knew it was coming then you know perfectly well that we don't have the resources you numpty.
>> ID: 2414f2 No. 13753 Anonymous
4th May 2016
Wednesday 9:40 pm

ID: 2414f2
13753 spacer
>>13752

There's been quite a few of us over the years who've offered in various ways to do ad-hoc dev to help the site out; for a community driven site it makes a lot of sense.

In any case we already have mouse-over to view off-screen posts within a thread so being able to do that from /* or /sfw shouldn't be that much of a problem famous last words .

If I have time at some point I'll have a look at the javascript responsible for it and if it's an easy patch I'll throw it up here.

Only for it to be completely ignored. Probably.
>> ID: 2414f2 No. 13754 Anonymous
4th May 2016
Wednesday 11:11 pm

ID: 2414f2
13754 spacer
>>13753

Actually, just realised that the site already has off-screen post preview via mouseover only it's not implemented on the "Click here to view the full text" links.
>> ID: 1acd08 No. 13755 Anonymous
5th May 2016
Thursday 1:38 am

ID: 1acd08
13755 spacer
>>13752
By which I meant a 'you ungrateful sods' rant.
>> ID: 2414f2 No. 13756 Anonymous
5th May 2016
Thursday 3:07 am

ID: 2414f2
13756 spacer
>>13754

Ok. I honestly wish I hadn't started digging into the AJAX surrounding this site. I only have five beers left. Anyway, I did, so here's the deal:

This is the anchor tag for "Post too big"
<a href="/pol/res/64990.html">here</a>

And here's the anchor tag that shows up a post preview upon mouseover:
<a href="/shed/res/13736.html#13752" onclick="javascript:highlight('13752', true);" class="ref|shed|13736|13752">>>13752</a>

That class= value there causes the javascript function addpreviewevents() to add an onMouseOver event to any anchor tag that has it. This event is then fed that class string which eventually ends up in a call to http://britfa.gs/brian/wire/read.php?b=<boardname>&t=<id of first post in thread>&p=<target post to preview>&single - the returned html of which is parsed and chucked into a <div> tag by the javascript function addreflinkpreview().

In any case, I'd imagine the "class='ref|shed|13736|13752'" gubbins is added somewhere in the PHP code while the html is being generated. It should be a fairly (very?) simple change to make sure the "Post too big" links are generated by the same PHP that generates the other previewable links.

Sage very, very firmly ticked.
>> ID: 8de99f No. 13757 Anonymous
6th May 2016
Friday 1:26 am

ID: 8de99f
13757 spacer
>>13754 >>13756
This isn't how I'd have fixed it and it has obvious flaws but you're absolutely right it's a trivial change so consider it done.
>> ID: 8de99f No. 13758 Anonymous
6th May 2016
Friday 1:34 am

ID: 8de99f
13758 spacer
>>13757
I should probably do it properly because it's not much of an improvement when the bit you're interested in is drawn off-screen.
>> ID: 165961 No. 13759 Anonymous
6th May 2016
Friday 8:18 am

ID: 165961
13759 spacer
>>13757
>>13758
This appears to be expanding the OP rather than the actual too-long post.
>> ID: ae580c No. 13760 Anonymous
6th May 2016
Friday 9:36 am

ID: ae580c
13760 spacer

Untitled.png
137601376013760
>>13759
It's also still mostly offscreen.
>> ID: 252bde No. 13761 Anonymous
6th May 2016
Friday 10:17 am

ID: 252bde
13761 spacer
>>13760
Also it reveals the OP comment, not the post it should.
>> ID: ae580c No. 13762 Anonymous
6th May 2016
Friday 10:21 am

ID: ae580c
13762 spacer
>>13761
That's what I was "also"ing to.
>> ID: 165961 No. 13763 Anonymous
6th May 2016
Friday 10:49 am

ID: 165961
13763 spacer
>>13762
Also it spills off the bottom of the screen.
>> ID: 85c23c No. 13764 Anonymous
6th May 2016
Friday 2:42 pm

ID: 85c23c
13764 spacer
>>13761
This.

I didn't really mean to kick up a fuss though. It's long overdue of me to say cheers to everyone who's been involved with maintaining the site over the years, petty quibbles (like my OP) aside you've done a cracking job. Thanks.
>> ID: 8de99f No. 13766 Anonymous
6th May 2016
Friday 4:50 pm

ID: 8de99f
13766 spacer

leftover-spaghetti[1].jpg
137661376613766
>>13759 >>13760 >>13761 >>13763 >>13764
All should work now. A forcible refresh (Ctrl + F5) is probably required.
>> ID: 85c23c No. 13767 Anonymous
7th May 2016
Saturday 6:47 am

ID: 85c23c
13767 spacer
>>13766
Working like a charm. Thank you.
>> ID: 252bde No. 13768 Anonymous
7th May 2016
Saturday 2:07 pm

ID: 252bde
13768 spacer
>>13766
I've always loved you.
>> ID: b83f9f No. 13769 Anonymous
10th May 2016
Tuesday 7:30 pm

ID: b83f9f
13769 spacer
Works great. Thanks for this, mysterious nameless admin, and more thanks to the lad who actually did all the work, >>13756.
>> ID: f375ef No. 13770 Anonymous
10th May 2016
Tuesday 8:29 pm

ID: f375ef
13770 spacer
>>13769

> more thanks to the lad who actually did all the work

While I'd love to, I'm afraid I can't take any credit for this other than perhaps for the sin of motivation; as per >>13758 and >>13759 the Mysterious Admin was unable to get my (admittedly nasty and hacky) suggestion to work and ended up implementing something much more elegant in its place. All hail our mysterious admin/mod overlords.
>> ID: b83f9f No. 13771 Anonymous
11th May 2016
Wednesday 8:03 pm

ID: b83f9f
13771 spacer
Just discovered it doesn't work on my mobile device. I think it's to do with the type of hyperlink it's been changed to, one of these fancy modern scripty ones that doesn't change the cursor to a hand when you mouseover it. They don't play nicely in Firefox for Android (though very little does). Can it please be changed back to the type of link it was before, or is that not possible?
>> ID: b83f9f No. 13772 Anonymous
11th May 2016
Wednesday 8:06 pm

ID: b83f9f
13772 spacer
>>13771
And hopefully you understand that my post is asking if it's possible to keep the fix, not that the whole change should be reversed because I'm a selfish bastard.
>> ID: 884eb1 No. 13773 Anonymous
12th May 2016
Thursday 9:09 pm

ID: 884eb1
13773 spacer
>>13771

I just tested on Android Chrome, had the same problem, tested on desktop Chrome and had the same problem and now I've just figured out what was causing it.

What's happened is that your phone's browser has a copy of http://britfa.gs/brian/lib/javascript/brian.js cached and that old copy doesn't have the fullPost() function defined in it. I couldn't find a way to clear the cache on my phone so what I did to fix it was to visit the url http://britfa.gs/brian/lib/javascript/brian.js directly in my phone's Chrome browser and then forcibly refresh that page (by selecting the url bar and hitting enter). After that the fullPost() function showed up in the javascript file and the "click here to expand" link worked correctly.
>> ID: b83f9f No. 13774 Anonymous
13th May 2016
Friday 10:46 pm

ID: b83f9f
13774 spacer
>>13773
Many thanks, that fixed it.
>> ID: 0f8e53 No. 15008 Anonymous
16th August 2019
Friday 12:37 am

ID: 0f8e53
15008 spacer
>>13774

Return ]
whiteline

Delete Post []
Password