Wedge

Great :)Yes, good!
It's still saying hreflang="en" in index.template.php, should I update it myself..? Just so I don't forget...Ah, these weird bugs eh..?
I've been fighting for half an hour on my local install trying to figure out why my notifications disappeared. Turns out if was because all plugins had been disabled. Then I re-enabled them, played again, and ten minutes later... Bam, they were disabled, once again, all of them! I don't know why... The only thing I did today, was to move my forum to a different folder, and update the database to reflect it. I can understand the first time they got disabled, but not the second...I'm still not sure what the difference is going to be between warning and infractions, but I trust it'll be better... ;)Oh, regarding that... I've split it into three different functions, return_raw, return_xml and return_json, which do exactly what they say. It adds about 120 bytes to the source file, but it also has the benefit of variable parameters, so... It's all good I'm guessing. I chose camel_case because, well, redirectexit doesn't say redirectExit, does it..? :^^;: And that's a bit similar to it, I'd say...

As mentioned in another topic... Let's see my uncommitted files one by one.
This topic is mainly to satisfy Pete's curiosity, if it exists. Also evaluate whether we'll have conflicts, and for anyone to give me their opinion on some topic when I'm unsure which way I should fix something...

It may also give you an insight into a genius madman's mind... :lol:

- Class-CSS: just disables can_flex manually... It's a hack. For testing.  I still don't know what's best anyway.

- Class-DB: another file I've had in this state for months... It simply removes the return false on __clone(), and moves __construct() to the getInstance() code. I was planning to modify all files to do simpler things like that, but then I realized I really wasn't the guy to do the proper OO code optimizations, and I left it hanging... I'm guessing I'll leave it that way for another couple of years. Until I'm bored disabling the file's commit status, and remove my code. Maybe you want to do this kind of thing yourself...? Or maybe you think it's pointless..? I just don't think __construct() and getInstance() should both be in a class, as they have the same purpose really.

- Class-Notification: minor and short optimizations... Planning to commit this along with the rest of my notification changes.

- Feed: uhh... Just a spacinazi. But I'm not committing it, as it's a reminder that I should change all <' . '? strings to just have <?, since it's not going to change anything, and only ?> needs to be escaped... (Unless I'm wrong? In which case, there are plenty of files we need to fix!)

- JSEditor: part of my AJAX rewrite (i.e. remove Xml.template.php, and move everything to use returnAjax)

- JSModify: part of my AJAX rewrite

- Notifications: part of my Notifications rewrite

- QuoteFast: part of my AJAX  rewrite

- Subs-Cache: this one has two changes:
   - part of my quote escaping rewrite in JSE (code related to $txt handling inside JS files),
   - and a stand-alone change that optimizes CSS filesize for Chrome and Firefox, by using a magic trick. It's actually been in use at Wedge.org for a few weeks, but I can't decide whether to commit or not, because (1) it's not a free hack, it takes time to run, (2) it only saves about 100 bytes... :(, (3) there's an alternative solution that involves moving my code to CSS files and only have a fallback implemented in Subs-Cache, it'd be more solid, but also more confusing to CSS developers...

- Subs-Template: has three changes...
   - part of my Prism implementation; i.e. better syntax highlighter. Never finished that, as it doesn't play well with... flexbox. Ah.
   - a one-liner that converts underscores to dashes in classes and ID's, at runtime. Only keeping it in there as a reminder that, well... It actually compresses worse :(
   - part of my quote escaping rewrite in JSE (restore quotes after moving inline events.)

- Subs:
    - my returnAjax hacks...
    - my quote escaping rewrite in JSE -- not finishing it yet, because of issues with Wess.

- Suggest: part of my AJAX rewrite

- Home.template: a playground to see how I can easily vertically align embedded icons next to text, instead of having to use vertical-align. Well, although it does work, it also implies a site-wide rewrite, which I'm not excited about... So I'm leaving this as a reminder, again.

- index.template: part of my Notifications rewrite (moved the main skeleton's block there, for logical reasons.)

- ManagePermissions.template: part of my quote escaping rewrite in JSE.

- Notifications.template: part of my Notifications rewrite

- editor.js: I actually got rid of the iframe, in Wysiwyg mode... But couldn't figure out how to fix focus when clicking buttons.

- moved notifications.js to script.js, and heavily rewrote it.

- sbox.js: an IE hack that I never committed, for some reason... Probably because it works without the hack, but 'officially' I should be using the hack, so... This one has been in the file for at least a year. Every time I've committed sbox.js, I've ensured I didn't commit that single line change... I'm silly.

- topic.js: my flexbox fallback. It doesn't work in Firefox, so I'm not committing...

- editor.css: part of the Wysiwyg iframe rewrite. Saves 400 bytes of text, mostly comments...

- index.css: part of my Notifications rewrite

- sections.css: part of my flexbox hack. Uncommittable...

- Wine/extra.css: fixes some issues, but adds more issues in Warm -- and as I can't fix-commit Warm, I'm leaving this here.

- Warm/extra.css: quite a visible overhaul of the Warm skin... Only, I like the current one BETTER. Don't ask me... I should post screenshots, and ask for opinions. Generally speaking anyway, I'm thinking of tearing the skin apart and making it a Web 2.0-style skin.

- Xml.template.php: will eventually go away, part of my AJAX rewrite...

So, there you go. We've got about 4-5 main features I'm working on at the same time, none of which are ready for primetime (except maybe notifications).

rev 2046 -- my skeleton object rocks. It just needs to be tested from a plugin author's point of view. ;)
(4 files, 5kb)

! Fixed a situation in skeleton handling that I didn't consider. If we're using a target array with a fallback to 'default', and the skeleton is currently hidden (e.g. an XML template), Wedge would still force the layer to be shown in default, even though it's very unlikely to be the desired solution. For instance, my current code has the Notification block added to all XML templates by default because of said fallback, effectively breaking all Ajax responses due to malformed XML. Eh, silly me... Obviously, fixed by ensuring we skip the block if we're in that situation. (Class-Skeleton.php)

+ Added a new skeleton method, insert(), which is basically a generic operation function to add a layer/block. Instead of doing wetem::add(array('somewhere', 'default'), 'block'), you can now do wetem::insert(array('somewhere' => 'add', 'default' => 'first'), 'block'), meaning that if the 'somewhere' layer is available, 'block' will be added ('add') to it, and if it isn't there, it will be prepended ('first') to the 'default' layer. Is that clear enough...? It gives you greater flexibility if you're writing a plugin and want to have a variety of layers or blocks as fallback targets. Calling for opinions on the method name, as I want it to be as generic as possible, and 'insert' might not be. Maybe 'push', or 'put'..? (Class-Skeleton.php)

* Disable CSS/JS output compression by default at install time on non-Apache servers. Output compression may work, but only if you declare the proper MIME types manually in your configuration files. (install.php, install.sql)

* Made $full_board available for 'determine_location' hooks to modify. Not that it'll be very helpful, though... (QueryString.php)

Pete, do you still have this problem..?

It's not that a workaround was needed for this... I've always suppressed double quotes in these situations when embedding in an inline event. It's just that when you include some JSE string in these, sometimes you'll get a double quote, whether you want it to not. Originally it was handled differently (i.e. would convert it to a quot entity), but I recently figured (and documented it) that I could get away with a chr() call, like I'm doing in other situations.

I really need to get started committing stuff...!

Thanks!
Doing my best to finish a public version ASAP... But sometimes, hurrying up is not the 'solution'.

Yes of course, and that's really good news for jQuery distribution, among other things... Another kilobyte saved :)

There are two PHP implementations so far:
https://github.com/kjdev/php-ext-zopfli
https://github.com/clickalicious/php_zopfli

May the best one win!
Couldn't find a compiled DLL for local tests though, so I guess it'll have to wait... (And yes, I'm not against adding support for zopfli in Wess, as long as low-iteration passes have similar performance to gzip -9 and still save more bytes.)

I'm not seeing any of this, Pete... :-/
Can you analyze the DOM with dev tools..? Thanks.
(.postarea is what's supposed to have the flex display.)

:edit: Quick Edit fixed... :)