david.shanske.comcreated /smart_watch (+774) "Created page with "A <dfn>smart watch</dfn> is a mobile device designed to be worn on the wrist. Designed to be similar in appearance to traditional watches, and often defaulting to mimicking the f..."" (view diff)
KartikPrabhutantek: I am thinking of making marginalia.js show and hide using only CSS with the "show/hide" button being an <input type="radio"/> element. Is this an abuse of HTML input elements?
tantekbecause all you do is put a "hide" link inside the shown marginalia, on top of where the show link was, so when they click that, it effectively toggles and hides itself
tantekI'm also thinking of this as a design that would work with server-side embedded marginalia, and client-side pure CSS UI - no JS needed to hide/show
tantekthe "hide" buttons should simply have a link to the paragraph that the marginalia is about - so that the document does not scroll / move when the hide button is clicked, however, the URL is still "sensible" in the URL bar
kylewmI mean I think it would be super nice, and obviously doing these little interactions are easier on the silos than any of our current UIs, but it kind of feels like giving up
Loqitantek meant to say: those last 2 previews are showing a last 2 previews of liking the *old* u-like-of link in tantek.com/2015/023/f3 - not the current value
GWGgRegor`: The description of Normalize.css sounds good. But I'm not enough of an expert to comment. But I figured they were trying it upstream, so why not?
JonathanNealgRegor`: In the old reset.css, the resetting of div was pointless, and there was no advantage over the plain * selector (people burned `*` at the stake because they didn’t know the difference between it and `.foo *`).
JonathanNeal99% of the time, you do not want to reset your document, and you inevitably add back styles like strong { font-weight: 700 } etc. Normalize is what you want.
JonathanNealThings like normalize.css and html5shiv are intended to bridge the gap between the old days and the future. We’re very close to the future, where things like normalize.css will hopefully be optional.
JonathanNealNow we’re moving into the era of micro-libraries and polyfills. We see this with the fork in jQuery 1 vs jQuery 2, where jQuery 1 maintains compatibility with the older browsers, but the majority of development is now focused on evergreen browsers, aka browsers that update themselves and are rarely further back than the last two versions.
JonathanNealI thought you were saying the original normalize developers thought normalize was less disruptive than reset. You’re saying the original developers of a theme you used thought reset was less disruptive than normalize?
GWGBut, the theme I used is a starter theme...almost no styling. They switched from a more aggressive reset to normalize this month. That was why I was looking at it. My plan is to incorporate any changes they make downstream into my fork, which is an mf2/Indieweb version.
GWGI've backported a lot of the modifications that were in SemPress, which was also based on _s, and am continuing to add modifications as _s commits them
GWGMy fork also changes the behavior specifically for the image post format or the photo post kind(if support is available) to use the Featured Image, if available, instead of the content.
JonathanNealOh, okay. Well, the best / hardest thing about a fork that you intend to redistribute is this: focus on what you do and do it well. If the image post thing is tangental to the goals of the project, I would drop it.
GWGI thought about writing a version of this that mirrors the built-in WordPress functionality and sending it as a pull request to the Semantic Linkbacks plugin.
prtksxnaIf its available in (lets say) Hindi then people want it to have better support. If there is no support whatsoever they look for other products
GWGprtksxna: Either way, I'm just adding in the textdomain stuff. I have to go through the wiki and make sure I didn't miss anything...replace every hardcoded string.
GWGBut it will be a happy day if someone, for example, emails me and says... "I like your plugin...but it doesn't support Hindi(to use your example), I'd like to send you the translation."
GWGprtksxna: I'm relatively new to development. While I'm writing stuff because I want to use it, and it doesn't exist....it is always nice to know someone likes the work.
GWGpfefferle had me playing with Grunt, because he used it in the plugin I signed on as a second contributor on, so I fiddled with it a bit and got it generating translation templates automatically for my code.