Investigate if we can use Stately repo for state designs #13

Open
boboroshi opened this Issue Mar 27, 2013 · 8 comments

Comments

Projects
None yet
4 participants
Owner

boboroshi commented Mar 27, 2013

This will only work in IE9 and above (because it's SVG). Do we care abotu IE8? If so, we'd need a PNG fallback for IE8.

excanvas can be used to make svg play nice in ie8. may be too much trouble than it's worth though.

waldoj commented Mar 27, 2013

I am not looking to go out of the way to support IE8. To the extent to which there are easy changes that can be made to accommodate it, great. Making PNGs of all of these is not an easy change, so I'm inclined to just let it break on IE8 (although as gracefully as it can).

Stately's MIT license is GPL compatible, so it's A-OK in a legal sense.

if you guys show me how to do it, i'll do it. i'm good at menial tasks. happy to help.

Owner

boboroshi commented Mar 27, 2013

You just made Lynn do a happy dance. IE9 and everyone else support SVG. I'd say we just have a single fallback image that's a generic "seal" for non SVG users.

On Mar 27, 2013, at 4:03 PM, Waldo Jaquith notifications@github.com wrote:

I am not looking to go out of the way to support IE8. To the extent to which there are easy changes that can be made to accommodate it, great. Making PNGs of all of these is not an easy change, so I'm inclined to just let it break on IE8 (although as gracefully as it can).

Stately's MIT license is GPL compatible, so it's A-OK in a legal sense.


Reply to this email directly or view it on GitHub.

John Athayde
Meticulous
Design | Web | 3d & Visual Effects | Music

mobile: 202.285.3544
email: jmpa@meticulous.com
web: http://www.meticulous.com

waldoj commented Mar 27, 2013

@jalbertbowden, I think the challenge isn't so much the conversion (Photoshop could automate that batch SVG->PNG conversion pretty easily), but rather having to maintain two sets of assets, indefinitely, along with the code to detect SVG compatibility and then act on it. It just simplifies things so much to have a single seal image, with a vector image overlaid on it. IE8 is very much on the way out, and I'm hoping that the uptake of The State Decoded will mirror the decline of IE8, thus minimizing the impact of shunning IE8 and its weirdnesses. So I'm really trying to hold the line on IE8 support, tempting as it is to do, because once we start accommodating it a bit, I'm not sure I'll know when to stop. :)

It's the front-end stuff that you're particularly interested in, right? (As opposed to regular expressions or batch conversions or anything like that?) I'm thinking that, once John and Lynn pass their work back into the main repository, there's going to be a bunch of a small things to try and stitch everything together. Plus, the stuff that I inevitably forgot to tell them to do. :) If at that very-soon point you have any time to pitch in, there should be plenty of issues that we could use some help on, and I know I'd appreciate it.

waldoj commented Mar 27, 2013

I'd say we just have a single fallback image that's a generic "seal" for non SVG users.

That's entirely sensible.

kewlio. i'll keep lurking.

lynnwallenstein removed their assignment Sep 15, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment