I haz a forum!
-
@cabrito said in I haz a forum!:
Nitpick: quotes all the post, not only the selected area
Yeah, that would take significantly more work, and it would need to be done by someone who knows a lot more about JS than I do.
-
@masonwheeler said in I haz a forum!:
Also, not implemented in Python.
Firebird + @masonwheeler == Delphi
-
@anotherusername said in I haz a forum!:
Or you can use an actual link to submit the form; something like . But that does require Javascript.
Or use css on a button. Style it to look like a link.
#logoutbutt { border: none; color: blue; text-decoration: underline; background-color: none; }
-
@kuro said in I haz a forum!:
Jeez, Why don't you just post image memes and ban him from the forums?
Probably because banning is not implemented yet
-
-
@lorne-kates said in I haz a forum!:
Or use css on a button. Style it to look like a link.
#logoutbutt { border: none; color: blue; text-decoration: underline; background-color: none; }
I like that. It's nicer (and less javascripty) than the current solution. I think I'll try that when I get home.
-
@masonwheeler said in I haz a forum!:
@boomzilla said in I haz a forum!:
Firebird + @masonwheeler == Delphi
No, actually. :P
Boo?
-
@boomzilla Now you're just guessing wildly...
-
@masonwheeler I see you are using a forum thread as your bug tracker. Very progressive of you
-
-
@boomzilla said in I haz a forum!:
Not wildly.
Yeah, actually you're the only one here who's tried using things that you know about me, rather than things that you know about web development, to guess how I'd implement the project.
...and you turned out to be right. This forum is the first project built on the Web.Boo framework, which I designed last year, mostly as a fun way to play around with metaprogramming.
-
@boomzilla said in I haz a forum!:
Boo?
No, it's Boo* to match your name
Learn you fucking wildcards.
:RAAAAAAAAAAAAAAGE:
-
@masonwheeler Clicking on category under a topic takes you to the categories page. I would expect it to take me to the category itself
-
@lorne-kates said in I haz a forum!:
@boomzilla said in I haz a forum!:
Boo?
No, it's Boo* to match your name
Learn you fucking wildcards.
:RAAAAAAAAAAAAAAGE:
That would be
Boo.*
.
-
@homobalkanus It should. I'll look into that this evening.
-
@pleegwat said in I haz a forum!:
That would be Boo.*.
Wildcard != regex! :BOOM:
wait, why didn't that become ?!?
-
@lorne-kates said in I haz a forum!:
Wildcard != regex! :BOOM:
wait, why didn't that become ?!?
Case sensitivity?
-
@masonwheeler said in I haz a forum!:
@lorne-kates said in I haz a forum!:
Wildcard != regex! :BOOM:
wait, why didn't that become ?!?
Case sensitivity?
/cc @ben_lubar
Feature request. Different emojis for:
:booM:
:boOm:
:boOM:
:bOom:
:bOoM:
:bOOm:
:bOOM:
:Boom:
:BooM:
:BoOm:
:BoOM:
:BOom:
:BOoM:
:BOOm:
:BOOM:
-
@lorne-kates said in I haz a forum!:
Feature request. Different emojis for:
Pull requests considered.
-
@lorne-kates what about variations on "kaboom" ?
-
@masonwheeler said in I haz a forum!:
@boomzilla said in I haz a forum!:
Not wildly.
Yeah, actually you're the only one here who's tried using things that you know about me, rather than things that you know about web development, to guess how I'd implement the project.
...and you turned out to be right. This forum is the first project built on the Web.Boo framework, which I designed last year, mostly as a fun way to play around with metaprogramming.
I knew it was Boo already. It's in the source, I forget where.
-
@pie_flavor It shouldn't be in the page sources anywhere. You may have seen it in the name of the session cookie, though.
-
@masonwheeler said in I haz a forum!:
@pie_flavor It shouldn't be in the page sources anywhere. You may have seen it in the name of the session cookie, though.
*snaps fingers* THAT was it! Yeah, I poked around the cookie seeing what would happen.
-
@homobalkanus said in I haz a forum!:
@masonwheeler Clicking on category under a topic takes you to the categories page. I would expect it to take me to the category itself
OK, I'm looking at this now, and not seeing it. Can you elaborate?
I open a topic. In the page header is a link marked Categories, which takes you to the categories page. Below is the topic header, marked with the category name, which takes you to the category page for that category. I don't see any place where the two are confused...
-
@masonwheeler try clicking the category name under the topic title. For instance: click "General" under "Test in General"
-
@homobalkanus said in I haz a forum!:
@masonwheeler try clicking the category name under the topic title. For instance: click "General" under "Test in General"
To clarify in terms that might help a developer, clicking on the category name goes to
/categories/1
but it should go to/category/1
-
@masonwheeler said in I haz a forum!:
I open a topic
That's the problem.
On the thread list, click the category under the topic title
-
So, when can we start playing Mafia on it?
-
@lorne-kates said in I haz a forum!:
On login/session start, per user, create a GUID. That's the logout nonce.
I will never get used to this meaning of it.
-
@jaloopa said in I haz a forum!:
That's the problem.
On the thread list, click the category under the topic title
OK, yeah, that's the part I was missing. Fixed now. Also tried @Lorne-Kates 's CSS idea, but it didn't quite work out as well as I'd have liked. I'll have to poke at it some more.
-
@lorne-kates said in I haz a forum!:
Or use css on a button. Style it to look like a link.
#logoutbutt { border: none; color: blue; text-decoration: underline; background-color: none; }
That was what I was implying when I said:
@anotherusername said in I haz a forum!:
You can style the submit button so that it doesn't look like a button, if desired.
Although, your CSS is incomplete as it'll still move when it's clicked down. Also, Firefox says that
background-color: none
isn't valid; it needs to bebackground: none
.To make a button look and behave exactly like the default appearance of a link
in Firefox...
form[action="/logout"] input[type="submit"] { border: none; color: blue; text-decoration: underline; background: none; margin: 0; padding: 0; outline: 0; cursor: pointer; font-family: serif; font-size: 100%; } form[action="/logout"] input[type="submit"]:active { outline: dotted 1px red; color: red; } form[action="/logout"] input[type="submit"]:focus:not(:active) { outline: dotted 1px blue; } form[action="/logout"] input[type="submit"]::-moz-focus-inner { border: 0; }
in Chrome...
form[action="/logout"] input[type="submit"] { border: none; color: blue; text-decoration: underline; background: none; margin: 0; padding: 0; cursor: pointer; font-family: serif; font-size: 100%; outline: none; } form[action="/logout"] input[type="submit"]:active { color: red; } form[action="/logout"] input[type="submit"]::-moz-focus-inner { border: 0; }
(Either of those produces identical results in either browser, but links don't behave exactly the same in Firefox and Chrome. Firefox adds a dotted outline when they're focused/active, and Chrome doesn't. You might just want to pick the one you like better, and then style real links so that they behave the same way in both browsers too.)
-
@anotherusername said in I haz a forum!:
Firefox adds a dotted outline when they're focused/active, and Chrome doesn't
-moz-user-select: none
(or something close to that) should remove the dotted lines, right?EDIT: Oh, do you want the dotted lines? Never mind, go back to ignoring me...
-
@anotherusername Not bad. Now is there any way to make the
<form>
element containing the button appear on the same line as the rest of it that doesn't involve gross hacks and ery?
-
@masonwheeler use
display: inline
. Also, don't put it inside ap
element.
-
@nedfodder said in I haz a forum!:
-moz-user-select: none
(or something close to that) should remove the dotted lines, right?If you want to remove the dotted outline in Firefox, this
a:focus, a:active { outline: 0; }
will work. No
-moz-
trickery is required.edit: for links, at least. Removing Firefox's dotted outline around the text on an active button does require some
-moz-
trickery, which you can see in either of the versions of CSS (it wasn't displaying in the correct place to look like Firefox's dotted outline for a link anyway, so it's hidden in both versions).
-
@anotherusername You shouldn't remove the keyboard focus indicator unless you hate users.
Chrome draws a rectangle around the element in the OS' highlight color, this is actually probably a better behavior than Firefox's dotted line. But don't get rid of the focus indicator entirely, that would be stupid.
-
@blakeyrat Is anything special required to make the keyboard focus indicator look like the one for a link rather than the one for a button?
-
@masonwheeler I don't use Firefox. In Chrome there's no difference between the two.
-
@blakeyrat said in I haz a forum!:
@anotherusername You shouldn't remove the keyboard focus indicator unless you hate users.
Chrome draws a rectangle around the element in the OS' highlight color, this is actually probably a better behavior than Firefox's dotted line. But don't get rid of the focus indicator entirely, that would be stupid.
well shit, Chrome's more broken than I realized. It's simply impossible to make the focus on a button act like the focus on a link does* (unless you change the way the focus on a link behaves). Leastwise, not without using some seriously Javascript to try to set the outline when it's clicked on and reset the outline when it loses focus. What's more, digging into how to reproduce the focus style that Chrome uses yields a higher ratio than I care to really mess with.
*Chrome only displays the focus around a link when the user tabs to it. Buttons will get the focus outline if you tab to them, but they also get the focus outline if you click on them, and links won't.
-
@masonwheeler said in I haz a forum!:
@blakeyrat Is anything special required to make the keyboard focus indicator look like the one for a link rather than the one for a button?
Just eliminate the
outline
andborder
styles that I used, I guess.
-
Well that was fun.
My 1-month free trial is up now, so the server's been shut down. But I managed to get a lot done to improve things and fix bugs with your guys' help. Thanks!