Wedge

I'll deal with the OT later, but menus -- I don't understand what you're trying to say. Any real-life cases of a layout change that happens often enough for absolutely-positioned menus to be a big con for you...?

So, it's fixable right...?

Your posts make me feel like it's a bad idea to use the file cache for... pretty much anything?!

Re: topic, so I've made a working prototype that uses the parent's offset position to show the element, rather than relative+nested absolute positioning (which always had my preference).

Pros:
- it will work everywhere... hopefully...
- it's relatively easier to understand what it does
- no, or less, esoteric hacks that even I can barely understand

Cons:
- if you resize the window while the menu is open (e.g. in Opera if I press F4 to show or hide the sidebar that holds my tab list), it'll be repositioned somewhere else (usually not under the parent item!)
- if you modify the CSS layout or HTML structure while a menu is open, the same will happen...
- and it does the same even if the menu isn't open, unless you store the parent's coordinates on all mouseenter events (which is what I'm doing right now, it's probably a tad slower too...)
- it's not as cool.
- it takes a bit more JS code (~20 bytes...)
- did I say more code..?
- and more code, too.

I could apply this to the main menu, too... This would avoid similar issues with IE8, although I fixed them with an odd hack as mentioned in the other topic.

I'm not exactly sure at this point, which way I should follow...

Oh... Also: absolute positioning makes it harder to work in non-JavaScript environments, unless I'm very careful. Basically, I'd need to add position:relative to the parent in CSS, and remove it through JS to allow for positioning relative to the document. Meh...!

No problem. I told you to look at our changelogs :P

Is it as desired, that we're not caching likes in the posts table...? (ot topic table even? per first-post or for all posts in the topic?)

I could see it as an interesting sort method, even if we still need to tell if our own likes are in these.

+1.

I take that back... :P
$last_thought = id_thought.
I'm doing strlen($last_thought) because that's what it looks like when it's serialized... (I know it's a bit odd to do a search on a serialized array, but it's always going to be stored the same way, so why bother...)

Do you mean the clear cache function doesn't clear non-file cache alternatives...?I totally agree, and it was my plan to move it to after the word, actually... Because it looks like it's two icons side to side, so it's a bit unbalanced with the text coming to the right.

However, there's the minor problem of what the text should say. Which is why I haven't tackled it yet...

(like icon) (empty) Like
Pressing Like.
(unlike icon) (1) Unlike
It sort of implies, "1 person unlikes this"...
So, it should say:
(like icon) (1) Like/Likes whatever you want that is positive...
And on hover, have the mini-menu open with a "(unlike icon) Unlike" link among other things.I didn't think you'd care about such a little detail as the underlining... ;)
Actually, I did notice it and I hate that kind of thing -- it can be fixed very easily by simply duplicating the link and adding a space in between...They're not gone, they're just no longer transparent ;)I tried that, but wasn't happy with it.Now, here's the thing...
Do you remember our blog style on wedge.org when I was using the Noisen codebase...?
If not, open an account (or use it if you already have one) at noisen.com, go to http://nao.noisen.com/ and check out the "Action" button on the upper right of any post... This is something of an innovation (SMF-wise) that I strived not to reproduce in Wedge, but the more I played with my layouts, the more I felt compelled to go there... And pretty much unaware, because I only recently realized that even the word 'Action' was from there. (It's how the More button is called in Mobile mode... And will probably even be renamed to Actions everywhere once I decide to go ahead and merge the Modify link and the Quick Edit button together into a Quick Edit button with a mini-menu to open a full edit version...)I'm an amateur design. My designs suck. I'm always glad to hear suggestions on where I could improve Wedge's layouts.
Heck, Pete knows quite well that I'm constantly struggling with my bad taste -- he has to cope, along with me, with numerous style changes to Weaving that I'm applying to admins only (custom.admin.css, yay!), so right now we both have Calibri as our main font in Wedge and it'll probably change again before you know it... :P

(And just to be clear: too many fonts in the kitchen!! I'm aware of that!!)
The thing is that it has a styling like you like ;)
(Forgot to be clear on this...)