...more recent posts
I tweaked the post/edit editor so that it preserves line breaks in the source code. Still not perfect, but better. The "feature" where it strips out lots of code you might enter by hand in Source view (classes, inline styles, etc...) still needs some work. I just have to decide how to handle things.
Also, since it's not necessarily clear, the enter key makes a new paragraph, wrapping the content in <p></p> tags and thus creating a double line break (although the size of this break can ultimately be determined through CSS on a page by page basis.) To get a regular single line break ( <br> ) you can use shift + enter.
Bluepen visual CSS editor looks interesting.
Finally made some progress integrating the Ace editor into my software. Unlike the new WYSIWYG editor on [post] and [edit] pages (based on CKEditor), Ace is for editing HTML (and CSS and Javascript.) So this will only be for end users who want to get their hands a little dirty. But my target market will hopefully include a lot of these sorts of people. For others it will be possible to just select templates and never have to edit HTML directly.
This document defines a new request Client Hint header field, "CH", that allows the client to make available hints, both static and dynamic, to origin and intermediate servers about its preference and capabilities. "CH" allows server-side content adaption without imposing additional latency on the client, requiring the use of additional device databases, while allowing cache-friendly deployments.
This is such an obvious thing to do I've always wondered why it wasn't already implemented. At least it's being worked on. The idea here, if you can believe it, is when a URI is requested from a server, the server has very little information about the requesting client, and the information it does get (mainly, the "User-Agent" string), is difficult to convert into anything reliable or helpful. As URIs have transitioned away from being static documents towards more dynamic applications, our client browsers have multiplied along with device screen sizes and screen pixel densities. To serve an acceptable experience to the myriad of device types, we need to know more about the device which initiated the request. This is exactly what Client Hints hopes to accomplish. Good luck!
Image uploads from post and edit pages are now a little more robust and can handle filenames with potentially illegal characters in them.
Hook.js is a javascript library for mobile browser style "pull to refresh" on the desktop.
Noticed this font, Lato, and want to remember to use it for something.
I am continuing to (hopefully) improve the image upload support on [post] pages. Please leave me comments if you are finding any bugs. I'm particularly interested if anyone is using Internet Explorer.
Note that once you upload an image and insert it into the posting box you can double click the image and get a pop up (which I need to simplify and make look nicer) where you can change a bunch of the image attributes (notably the image size.) In FireFox you can click the image once and you should get image resize handles you can click and drag to resize the image.
Logged in users with posting permission can now select previously uploaded images from their image libraries (as well as upload new images) right from the [post]ing page.
Super interesting discussion about going with all SSDs in servers, ditching both spinning hard drives and hardware RAID cards. I hadn't thought we were there yet, but Chong Lee (cwl@apaqdigital on the forum linked to), who is making the case, is a giant supplier of custom servers (he built our server) and just incredibly knowledgable. His data shows that it's time on all counts: cost, performance, and reliability. At least for some use cases. I'm sold. Now if I could just afford a new server. I'd love to not have to worry about drives, and worse, the RAID card. Man, if that thing failed it would be a disaster.