Wedge

Okay, so... These last few days have been hectic IRL. Not in bad sense. It's been gotten hard to work on Wedge, I'm expecting 'full recovery' next weekend. I've worked exclusively on this popup, trying to make it less annoying, and been plagued with different bugs.
So, right now, what I have is a popup that only shows on focus, and gets hidden on blur, so that's all good, but I can't seem to animate it (not sure why... Have yet to look into it seriously), and most importantly, it closes as soon as I click somewhere in the popup, ah ah... I didn't think of that one, but clicking there will trigger a blur on the input box, that's very, coldly logical... I tried to turn to .focusout instead, but I can't seem to get a way to determine the current target, I'm only getting the input text I'm blurring from, so it looks like it's going to be hard. And I don't want to introduce some weird hack using some kind of static variable to keep track of where the focus is.
One of the good things of my current code, though, though, is that it no longer adds extra HTML to all pages, just a hundred bytes of JavaScript to script.js, or something like that. (It was the whole point for me, originally...)

Am I to understand that no one is interested in an implementation that's conceptually similar to what can be experienced in xenForo..? It's ultimately what I'm trying to replicate. (Without some of its bells and whistles, though.)

I'm a bit tired of the XML syntax, especially these days, since I had to refactor an Ajax query to return plain text due to a bug in jQuery 2.0 beta 1 (which was fixed in beta 2, and my bug report is the first on their changelog, yay :P)

I'd tend to favor plain text or JSON...
Anyway.
Oh, that reminds me -- I've recently read that the CDATA stuff inside script tags was only needed for XHTML pages. Which makes sense... And that since Wedge is using HTML5, there's no need for them at all. So I'll remove them. I'm only postponing because I'm not exactly sure whether I can also remove the HTML comments around script text... And yes, I think I can. I think it's an old thing related to some old browser that reacted badly to these things.

I'll just need to gather data on that.

Spam. Pretty sure about it... old topic + unrelated post + generic content + commercial website link but no forum in it...

Nice mockup, but it's a kind of button that would be a hassle to implement, compared to the level of use in Wedge... :^^;:

Dragooon, well, good question but... Honestly, have you tried Wedge without JavaScript on...? It's usable, but barely. (Select boxes will not show up, for starters!)
Those users can start their search in the search box (which will STILL work without JS on), then on the next page, they can click the linktree to go back to the full search page... Or whatever suits them.

Okay, current status, the popup is called on focus, it still disappears after blur though, but it's just 'the beginning'... Also, the contents of the popup are now loaded through Ajax, as I previously announced. I'm having difficulties with jQuery though -- it looks like it's giving me internal errors. Oh, and it just froze my PC, too, for like a minute, while I was writing this post... Nice! :^^;:

I don't get what you're trying to say...
If the popup shows up on focus, nothing forces anyone to use it..? Dismissing it (i.e. leaving its options as is) would then perform a regular quick search.

I was thinking, maybe I could push the destination select box to that popup, actually...

But apparently, here, it converts them...When I say Wysiwyg editor, I simply mean post box, with all smileys etc. I don't use Wysiwyg either, as you well know, so I'd hardly enable it by default... ;)

So, the extra line is in 'normal' mode.I dunno, maybe having the Master/Current captions in italics, the actual strings in regular, and if the current version is different from master, show it in bold...? (Like in Firefox's hidden setting page ;))Is there a problem in simply updating the link...? :unsure:All right then. I tend to overlook the changelog, it reminds me too much that I have to finish translations... :lol:It's a bit strange to be in a situation where missing strings are again generating errors... :^^;: (e.g. EmailTemplates.)

rev 1969 - I'm stepping through the door, and I'm floating in a most peculiar way...[1]
(6 files, 3kb)

+ As promised, here's a dropdown for the 'Advanced Search' link in the search box... It uses the HTML and CSS for main menus, adding about 12 gzipped bytes of HTML, 19 of CSS and 4 of JavaScript. It looks... All right. Especially for the cheap price.[2] (index.template.php, index.css, script.js)

* Simplified and improved the board list/label list areas in search pages. (PersonalMessage.template.php, Search.template.php)

! Fixed search input background in some pages. (sections.css)

1.	Remember an old sig of mine? :P
2.	Very interested in opinions! Should I switch to a mini-menu style instead..? It'll probably be a bit more expensive. And what about an Ajax-called panel? I'm still interested in doing that.