Discourse DMZ
-
'[edit]' seriously. nice markdown implementation [/edit]
[wtf] what is with the '[edit] being reserved depending randomly on whether there is a letter immediately after the edit bracket?
also, why does [edit]: [/wtf] make edit go away but [edit]e oh now that is effing hilarious [/edit]
-
as [why]: is that edit up above a link[/why] but not this next one? [edit]: affasd [/edit] sdfasdf
-
I hope @codlnghorror is at least willing to make a compromise in the name of usability:
https://meta.discourse.org/t/new-indicator-far-too-visually-strong/19575/25
-
That seems like a reasonable suggestion. It doesn't stand a chance.
-
Do it.
Personally, I'd have used goatse or frame grabs from swap.avi, but nyan cat is ok, I guess.
-
It's so inconsistent it's stupefying. "Hey, let's change the 'Cancel' button on our dialogs to Metro style, but let's leave "OK" at Win95!"
-
Every build that passes the test suites and a smoke test are automatically deployed to meta. It's often deployed a dozen times a day or more.
Out of curiosity, how long does this build/test/deploy cycle usually take?
-
Oh, look.
@codinghorror deleted my post about leaving the blue asterisk.
He must like you.
Filed under: silent deletes are a really shitty way to moderate a forum
-
I hope @codlnghorror is at least willing to make a compromise
raucous laughterJeff is the worst kind of developer - Makes unilateral changes to suit his whims and expects everyone else to just 'deal with it'.
-
Jeff is the worst kind of developer - Makes unilateral changes to suit his whims and expects everyone else to just 'deal with it'.
+;
JUST FIX FUCKING SEARCH ALREADY
-
"Just use google-search" - Jeff
Filed Under: Is Google doing it righttm?
-
I know that @sam is interested in improving search. He's done a few things that have made it a lot better. But until we get to a full page search, I don't think it's going to be good enough.
https://meta.discourse.org/t/double-stuf-improved-search-feedback/19490/15?u=boomzilla
-
Didnt Sam implement a quick and dirty hack of a search page if you type ?search=query into the url?
Filed Under: Use the search to find that. | Yes, I am aware that only fixes half of the problems ... and I have never used it
-
Yes, but while that returns a full page of topics, it doesn't allow you to jump right to the post and it doesn't give you any context preview of what search found.
-
"Just use google-search" - Jeff
Too bad that you can't use Google search, because all Google has is the page on which the search phrase is found, but because Discourse uses InfiniScroll tm and is incapable of translating a page number into a post number, so Google search doesn't work on Discourse threads with more than 15 posts.Seriously, whats so difficult in translating "page=3" into 3 * 15 + 1 and arriving at 46 as post id to maneuver Discourse to?
-
If I was Jeff, I would now post a funny meme-picture, tell you that the software is openSource and that you should please just submit a plugin for Discourse.
Filed Under: CLOSEDWONTFIXITSMATH
-
Just posted this over on meta.d:
codinghorror said:
I was struck visiting ... with how overwhelming the NEW indicators were:
Apropos overwhelming - if you select the "New" tab instead of latest, all you see is new topics.
It would be nice if the "new" badge trailing each topic wouldn't be visible on this tab, as it is a) redundant and b) indeed overwhelming since there or no topics that are not new.
Filed under: replicated here for the usual reasons.
-
t's a simple CSS-change. @PJH or @ChaosTheEternal should be able to reverse this in a few seconds flat
cc @PJH
.badge-notification.new-topic { background-color: #6cf; color: #fff; font-size: 11px; font-weight: normal; } .topic-list .badge-notification.new-topic { padding-left:3px; top:0; } .badge-notification.new-topic:before { content:''; }
This'll make it look roughly like it used to:
-
Possible to center horizontal and vertical? Inside the bubble?
-
Looks fairly centered to me in the suggested topics list...
Edit: Ah - see what you mean..
-
Guessing this just got applied as the bullet thing before the New just disappeared as I was looking at the New list.
-
Always room for tweaks, I was just getting it back to the bubble.
The styles I mentioned above is where you'd want to add them.
-
Screenshot has a few px extra in the ss on new, most of the numbers are oval instead of circles
-
most of the numbers are oval instead of circles
I didn't try to fix that, not yet at least. It is more noticeable on mobile.
-
Maybe that's why I noticed it?
Mornings are mobile for me. (It's a screenshot. )
-
Update:
.badge-notification.new-topic { background-color: #6cf; color: #fff; font-size: 11px; font-weight: normal; } .topic-list .badge-notification.new-topic { padding-left:3px; top:-1.5px; } .badge-notification.new-topic:before { content:''; } .badge-notification { min-width:10px; padding:5px; }
Added styles for .badge-notification to fix the "oval", changed the top on .topic-list .badge-notification.new-topic to try and make it more centered vertically.
Screenshot:
-
Added styles for .badge-notification to fix the "oval", changed the top on .topic-list .badge-notification.new-topic to try and make it more centered vertically.
This one is the current one.
-
Looks much better, it's still a few px off center top and left, but Iit's no longer making my ocd to details scream at me.
-
-
Out of curiosity, how long does this build/test/deploy cycle usually take?
You're so optimistic. From what we've seen, it's more like a build/deploy cycle.
-
Your an optimist.
-
Sorry, did I get them backwards?
-
I feel words like develop, build, design are too strong.
-
It takes about 10 minutes to run both test suites, the smoke test and then the deploy to the meta servers.
-
This one is the current one.
@Matches OCD was spot on. You should be able to change the top on
.topic-list .badge-notification.new-topic
to -2px and the bubbles should line up vertically.it's still a few px off center ... left
You'll have to clarify. The closest I can see is that the "new" text gets closer to the edge than the #'s in the bubbles (only single digit, though), but I don't know if I can fix that and keep it so unread post #s are in circles, not ovals.
-
@Matches OCD was spot on. You should be able to change the top on .topic-list .badge-notification.new-topic to -2px and the bubbles should line up vertically.
Done...
-
It takes about 10 minutes to run both test suites, the smoke test and then the deploy to the meta servers.
As much flack as you're getting in this thread, I for one wanted to stand up and applaud actually running tests before deploying to a testing environment. I'm currently building a CI system for a company that's never had one and getting people to acknowledge the value is an uphill battle :/
-
I tried to figure out how to display it in paint, but I'm really bad with graphics. Maybe a supersize will help...
the '1' starts right shifted by 1-2 pixels, it should be moved left to be centered. (Note: I say this without actually knowing what you're changing, or how - I'm only talking about from a straight 'look at the picture' kind of way.
What's weird, is larger numbers look 'OK'
The 'New' image that I SS'd looks ok as well, but the one I looked at earlier was wrong. I don't know why it's not ... oh. Discoursistency it is then.
I wonder... Is it assigning the same size for '1' as it does for '2' or '8'? That might explain it, since the '1' doesn't need the extra room, and has a different 'center' point than an '8' would.
-
There's nothing wrong with testing by machines, but if you don't do any human testing you get... well you get Discourse.
Machines are fucking terrible at spotting bugs in the UI. And something like a web forum is 95% UI.
-
Machine testing is absolutely great for things like regressions, and data integrity. But, like Blakey mentioned, they are really bad with UI. There are some testing suites to help with UI testing, but I seriously doubt they are being employed by discourse build tests.
-
Well sure, obviously, but since they're using a live forum as their human testing, it only makes sense to do automated smoke tests to ensure something totally broken is never deployed.
-
Machine testing is absolutely great for things like regressions,
Then they're doing it WAY wrong here, because DAMN.
But, like Blakey mentioned, they are really bad with UI. There are some testing suites to help with UI testing, but I seriously doubt they are being employed by discourse build tests.
The fallacy here is that testing can be 100% offloaded to a computer program. It can't. Not if you want a decent product. Anybody who says it can is an idiot who you should shun.
I'd actually argue that the focus on automated testing in recent years has made average software quality worse, although I admit I don't have any good data.
Is QA thrilling and exciting? To most developers: no. This is one of the reasons why open source software (like Discourse, for example) is always so fucking terrible: nobody does the boring work necessary to make a quality product.
The amazing thing to me is that Atwood does the boring stuff like: creating a corporate entity, figuring out payroll and benefits for a team distributed in like 6 different countries, etc. But he doesn't do the significantly-less-boring stuff that would actually make his product better. I don't get it.
-
they're using a live forum
Worse - they seem to be using every forum that presses the Update button to test.
-
Bubbles taken from Chrome:
The styles do say to center the text in that area, and it has even padding on both sides, but it looks like it misaligns itself. Only way I see to fix it is to add an extra pixel of padding on the right side:
.badge-notification { min-width:10px; padding:5px 6px 5px 5px; }
Fun times while trying to mock up unread post numbers for this post, any time a new post came in in this topic, it reloaded the "suggested topics" list. So, in the future, note to self, do it from the main topic list.
-
The fallacy here is that testing can be 100% offloaded to a computer program. It can't. Not if you want a decent product. Anybody who says it can is an idiot who you should shun.
No, the fallacy here is your tired strawman, once again.
-
That is really weird.
-
It takes about 10 minutes to run both test suites, the smoke test and then the deploy to the meta servers.
Wow, that's pretty impressive. :-)
-
What strawman, I'm looking at the end-product of this testing philosophy right now. With my two eyes. It's on the computer monitor I'm looking at. While I'm typing this.
-
Worse - they seem to be using every forum that presses the Update button to test.
Now that V1 is out, we're splitting into channels. You can follow latest, beta or stable. Most people will not be on latest.
There are some testing suites to help with UI testing, but I seriously doubt they are being employed by discourse build tests.
You thought wrong.
-
And yet, the evidence we see disagrees...