|
Winter is Cuming posted:http://macaw.co/peek/ PHP code:
|
# ¿ Jul 24, 2013 06:05 |
|
|
# ¿ May 2, 2024 07:00 |
|
Flaggy posted:This is what Adobe is moving towards, buying everything month to month and not being able to pay just one price for software. I hate it. If you do the math of when upgrades were released and what an upgrade usually costs, it's actually cheaper month to month. They're no longer planning major versions you have to upgrade to anymore; they release features when they're done.
|
# ¿ Jul 24, 2013 18:29 |
|
Lumpy posted:I'm still working my way through this, but here's another good read (so far!) on typography: http://practicaltypography.com/ This site hurts my eyes. Also, the links are invisible. Please don't treat the internet like a book, even if you really, really want to.
|
# ¿ Jul 26, 2013 18:53 |
|
His name is BonzaiBuddy, you dolt.
|
# ¿ Jul 26, 2013 22:21 |
|
Lumpy posted:Legible text hurts your eyes? Can you give some examples as to why you disagree, or are you just going to be your normal, dismissive self and not actually provide anyone the benefit of your knowledge? "That sucks" isn't a very helpful critique. http://practicaltypography.com/summary-of-key-rules.html #000000 on #FFFFFF is hard to read. Making it #333333 on #ECE6E6 would be better. Try and identify where the hyperlinks are. They're not underlined. I haven't found any consistent pattern about where they'll appear. The weight is also fairly inconsistent between the numbers on the left and the prose on the right. The SOMETIMES WE'RE GOING TO USE CAPS also seems more heavy than the text around it and is distracting. By removing the style entirely, I can actually read the prose a lot easier.
|
# ¿ Jul 27, 2013 01:46 |
|
Skiant posted:You do realize the all-caps is the consistent pattern you tried so hard to find for the links, right? I thought that, but I swore there were some all-caps on some page that weren't linked. That's a really, really bad way to do links, just pointing that out.
|
# ¿ Jul 27, 2013 18:56 |
|
SlightlyMadman posted:My boss is asking me to write up a comparison of Google Maps and MapQuest for a client who currently uses MapQuest but is considering switching. I've of course tried googling but the comparisons are mostly based on UI and usability, and for the most part are several years old (which makes sense, considering most sites made the switch back then already). Does anybody know of a good resource out there for a feature comparison from a development standpoint? I'd like to be able to point out things that they can do with Google Maps that would be expensive or impossible with MapQuest. MapQuest has been contributing data and development resources to OpenStreetMaps data, and MapQuest runs the big OpenStreetMaps servers now, and have also been the main developers and data sources behind their new route planning service Nominatim, and MapQuest's main source of income comes from government contracts to add GTFS data to transit systems. MapQuest has really pulled a 180 since you last heard of them. I wouldn't use the MapQuest APIs directly, but I think that anything that uses OpenStreetMaps (Leaflet, MapBox, Mapnik) would be better than the GMaps API.
|
# ¿ Aug 15, 2013 18:15 |
|
Have you seen SageMath Notebook, or its replacement, SageMath Cloud? It sounds to be somewhat similar to what you want to do, and the code for it is open-source.
|
# ¿ Aug 16, 2013 13:53 |
|
The future will have no Z-sorting.
|
# ¿ Aug 23, 2013 12:58 |
|
To be honest, I'd just do this using a static site and edit the HTML when I want to add a new cheat. But if you want to learn something basic for backend programming, try Flask or Django with Python?
|
# ¿ Sep 24, 2013 01:11 |
|
"Mathematics for Computer Science" by Lehman, Leighton, and Meyer is exactly what you want.
|
# ¿ Oct 3, 2013 15:17 |
|
Ghostlight posted:Out of unskilled curiosity - I have a page with a dozen or so identical static elements (publications with author/date/blurb) that will conceivably stretch to a couple of dozen over time, and this is the third revision of exactly how they would be presented. I have no CMS or MYSQL, so how batshit is it for me to write it so the actual text is just a series of php arrays passed into a function that dumps them into the current design structure of <div><img=""><p> etcetera? Sounds simple enough to me.
|
# ¿ Oct 10, 2013 13:54 |
|
What's the reason you can't use a simple webserver that serves static files from disk, like Apache or nginx?
|
# ¿ Nov 8, 2013 23:26 |
|
No, because HTML5 is a dumb buzzword. http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#is-this-html5?
|
# ¿ Nov 18, 2013 16:25 |
|
SA's HTML is semantic? News to me.
|
# ¿ Nov 18, 2013 20:32 |
|
It's an abuse of the GIF specification. Basically, the image header says it's 125x125, but it contains a 146x377 frame at 0x0. This is undefined behavior, so different viewers will view it differently. Firefox crops it to 125x125. Chrome/WebKit show it at 146x377. Photoshop crops it to 125x125. The Windows preview shows it at 146x377. My own GIF viewer crops it to 125x125. The source code to Chrome/WebKit says that it's a workaround for old GIF87a images that contain weird sizes in the images, and that no test images were found that actually have animations. http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageReader.cpp#L655 Suspicious Dish fucked around with this message at 06:51 on Jan 3, 2014 |
# ¿ Jan 3, 2014 06:46 |
|
Ask Null Byte how he did it. I'd simply use a hex editor along with the GIF87a specification, and modify the image header myself.
|
# ¿ Jan 3, 2014 08:03 |
|
What's wrong with just using icons? Spritesheets are a terrible hack to deal with the fact that HTTP has poo poo support for parallel downloads, which is fixed by SPDY/HTTP2. Spritesheets use more memory and are more expensive to decode.
|
# ¿ Jan 10, 2014 01:52 |
|
Mister Chief posted:What do you guys think of this scanline effect? I want to use it on my hero graphics but wanted to check with some people who know more about design to see if they think it looks like poo poo. Uh, it's an effect. Can you show us how it looks in context with the rest of the site? It's an effect that can look really bad or really good depending on how the rest of the environment around it looks.
|
# ¿ Jan 11, 2014 04:52 |
|
DreadCthulhu posted:Can anyone confirm for me that there's no reliable way of making a last minute ajax request in window.onunload? I've yet to be able to pull this off in Chrome, even with async: false. It works in window.onbeforeunload, except I don't want to make that request if the user decides NOT no navigate away, and as far as I can tell browsers don't notify you of the user's choice in that alert box outside of window.onunload being called. SO seems to vaguely confirm this as well, but you never know. The user is trying to kill your website. You have no guarantees of any code being ran.
|
# ¿ Jan 13, 2014 03:49 |
|
code:
|
# ¿ Jan 19, 2014 19:03 |
|
You can also just do transform: translate(-50%, 0);
|
# ¿ Feb 13, 2014 22:48 |
|
I'm disappointed it's not open-source, and OS X-only.
|
# ¿ Feb 28, 2014 21:40 |
|
Don't use :after.
|
# ¿ Mar 24, 2014 00:14 |
|
kedo posted:This is bad advice. It's mostly the opinion of the WHATWG. ::before / ::after lacks accessibility, scriptability, and visibility in devtools. See the discussion here: http://lists.w3.org/Archives/Public/www-style/2012Aug/0771.html
|
# ¿ Mar 24, 2014 15:11 |
|
Are you seriously asking a bunch of engineers for legal advice and hoping the response you get back is correct? Talk to a lawyer. Trust none of us. We aren't lawyers.
|
# ¿ Apr 1, 2014 23:21 |
|
code:
code:
code:
|
# ¿ Apr 5, 2014 01:34 |
|
Yeah, the dumb trick is html, body { height: 100%; }. Nobody ever thinks about putting a selector on html. Once you learn it, though, you won't forget it.
|
# ¿ Apr 23, 2014 18:21 |
|
kedo posted:Indeed. http://www.w3fools.com/ w3schools changed most of the quotes to equally bad information, and they got tired of maintaining it and answering emails about "oh hey is this correct now?"
|
# ¿ May 5, 2014 17:03 |
|
SVGs can be slower to render than PNGs, especially on mobile, so keep that in mind. Otherwise, reminder that vector isn't a panacea. Be aware of the tradeoffs involved and you should be OK.
|
# ¿ May 16, 2014 16:15 |
|
Just use flexbox instead.
|
# ¿ May 20, 2014 23:33 |
|
pipes! posted:Flexbox-shmexbox. Let's just use Grid Stylesheets. This is cool.
|
# ¿ May 21, 2014 03:22 |
|
cbirdsong posted:It seems super-interesting, but I can't imagine shifting stuff this fundamental onto a weird Javascript dependency. Yeah, I'm just saying that the idea solves a lot of problems. Perhaps the implementation isn't great.
|
# ¿ May 21, 2014 05:40 |
|
fletcher posted:New version of Firefox & Firebug released today. World class new theme that looks exactly like the old one.
|
# ¿ Jun 10, 2014 21:58 |
|
That said, there are some problems you just can't fix without changing the order of elements in the HTML. It's not a perfect system, however much it tries to be so. Don't be afraid of hacking up your HTML and putting some extra wrapper elements or reordering things if you can't get it to work.
|
# ¿ Jul 2, 2014 20:50 |
|
Or just use <a download href="foo">
|
# ¿ Jul 20, 2014 13:48 |
|
|
# ¿ May 2, 2024 07:00 |
|
vOv posted:Because the baseline is still defined by the 'normal' text, not the huge text. Not really? http://jsfiddle.net/3thK7/9/ I don't pretend to understand CSS.
|
# ¿ Jul 24, 2014 21:17 |