Closed Poll: Show Raw
-
Continuing the discussion from Doing it wrong userscripts - Show raw:
So... update: apparently the code was fine all along, but Discourse URL fuckery messes up the matching rule. Matching the whole site seemingly fixes it.
I've seen this mentioned recently again....
Ok - so I could, if there's enough interest, implement this site-wide (desktop only - the option isn't there to add to <head> on mobile, which is where it apparently needs to go.)
[poll]
-
I look at the raw fairly often, but would probably do it more if it wasn't so clunky having to grab the url and mess with it. Haven't used the user script because when it's mentioned I never seem to be at the computer I usually browse TDWTF on
-
I don't do view raw that often, but it would be nicer than mucking with the URL when I want to.
-
Almost seems "too intrusive" to me in that setup, but I don't know that I have a constructive comment of how I'd do it differently.
Useful feature to me. +1
-
Just the </> icon seems like a good proposal.
-
Now that i've been in my thinking location, i was thinking "what if it was up in the top/right, around the area where the edit icon would show up"
But yeah, more minimalist sounds gooder, in my mind's eye.
-
?
.. well absent the icons that the rest of you don't normally see of course..
-
wooooo! now viewing raw is 20% cooler
-
I have, on occasion and not for a while, wanted to see raw posts. I don't know how, so this would help.
-
Seems better than the first draft to me.
-
I have, on occasion and not for a while, wanted to see raw posts. I don't know how, so this would help.
-
Without this scripty add on you replace the "/t/titlename/" part of the URL with "/raw/".
HANZO by PJH
-
I think it's a great implementation, but the
pessimistrealist in me expects it to break about every other Discoupdate.
-
expects it to break about every other Discoupdate.
Look at the date of the quoted post - the only change I've made is to remove the topic_id:post_number from the UI.
-
Look at the date of the quoted post - the only change I've made is to remove the topic_id:post_number from the UI.
I meant that as a shot at the ever-changing discourse code, not at the 'show raw' script.
-
Oh - I know what you were getting at - but the show raw code is still working after 5 months of changes to DC - I think it'll last a while longer....
-
DONT
TEMPT.MURPHY!
-
I was just considering a passive aggressive update, based on the flak that the Discodevs get here
-
I vote yes on that, and hope we made it XSS-proof with @Onyx
(where is this guy, by the way?)
-
You can break the current implementation by bookmarking a post.
And the highlighting doesn't remove itself properly.
-
DONT
TEMPT.
MURPHY!Yeah, she worked out how to get us off the planet. Using Morse code from a black hole or something. I don't know, I was pretty confused by that part of the movie
-
Ok - so this is looking like one of the more conclusive polls on here...
Will probably wait for a full 24 hrs to give those that visit during work-hours state-side a chance to pipe up, but it looks like it's going in.
(where is this guy, by the way?)
Not been seen since early December - if changes are going to be needed I'm probably going to have to ask for help since JS isn't entirely my forte (then again, neither is/was SQL until we got DC...)
-
You're in a programmers' forum. I think we can figure something out...
(for the record, I'm OK with JS, but I know nothing about Ember - or Discourse's DOM structure for that matter).
-
but I know nothing about Ember - or Discourse's DOM structure for that matter
Well, you know what I meant... ;)
I can probably hack something on pre-existing code (like removing the topic:postnum on this one,) but creating new stuff I'd be a little more reluctant about.
-
- [Preview][1]
I think I've finally fixed the CSS style selection (apart from the CSS on the menu itself!) in the top right menu and have added TDWTF+raw:
I'll probably move the raw stuff to the main one some time and reduce that list back to 3 (managing more than one CSS style is a PITA at the moment since there's no concept of 'stuff to be used regardless of which style is current'.)
-
Welp, I broke the styling:
That took about 0.4 seconds to break. And it appears semi-random, too.
Not that big of a deal, though.Filed Under: Why are you putting ­ into your posts? Are you doing that manually or is Discourse doing stuff for you?
-
Welp, I broke the styling:
How?
Why are you putting into your posts?
I find ;) rather less expresses what I mean than ;)
And it's manual.
-
How?
I just clicked the button a few times. Sometimes I highlighted text inbetween. As I said, it seemed semi-random.
It's really minor, though. I wouldn't worry about it.Filed Under: Have you tried using ;) <-- view source to find out what I did!
Addendum: Bug: Newly streamed posts don't get the view-Source-thing!
-
Bug: Newly streamed posts don't get the view-Source-thing!
Beyond my current area of expertise to fix I'm afraid...
-
Yes. That's a thing that happens.
It also brakes when a post is renamed for some reason..
Has for as long as I have been using the plugin.
-
It also brakes when a post is renamed for some reason
Does it actually stop or just slow down?
-
Slows down. Unless the breaks lock, in which case it stops and needs a type to the mechanics.
-
-
-
I'm tyred of the misspellings.
We really need a dislike button.... I make fake one someday...
-
I'm tyred of the misspellings
It does start to boar you eventually. I grow wary of it all
-
Anyway, spelling aside, I like the new "show roar" functionality.
-
-
-
based on the flak that the Discodevs get here
It's been positively tame lately. Though now they're provokin' us!
-
I don't give a shit how many buttons you crap all over, I'm not ever viewing raw. Don't put shit in there if you want people to see it.
If we're going to have some means of meta-post-ing, we need tags back or to adopt something else. (Something VISIBLE, not something that's only in the DOM or font size 2.)
-
It also helps with "how did they manage that effect", especially for someone like me, with a passing familiarity to HTML and no particular desire to get expert at it
-
It shows the difference between what a person typed and what Discourse decided to show. Any "neat HTML effects" will be visible in the actual HTML, you don't need raw to see those.
-
we need tags back
Indeed. But the current effort that's going on doesn't look too promising....
(Ok - that particular one's been fixed, but only
becauseafter we pointed it out to them.)And per-post tagging, which is what we really need, is still a pipe dream.
or to adopt something else. (Something VISIBLE
Filed under: this method is particularly crap.
-
That screenshot looks like we could really have some fun. Ship it!
-
Going back to last May/June is not something I'm particularly keen on....
-
i wouldn't mind (briefly) visiting then. i missed all the fun y'all had
-
There's some gifs around somewhere if you haven't seen them yet.
Someone probably has them bookmarked....
-
There's some gifs around somewhere if you haven't seen them yet.
it's just not the same as being there.
i'll agree with you that it's not a good place to be, but it would be a fun place to visit for an hour or so!
-
Don't put shit in there
+1Additionally, blank-looking posts are obnoxious as hell. Too bad that some people seem to have taken the addition of the raw button as an invitation to post those even in threads that aren't bot-centered or /t/1000.