-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor & Update Progress Bars #379
Conversation
…TURE BRANCH, PROMISE
re: 8c9cd3cI tried git stashing this to keep the pull request clean, but actually some re-working the header layout was needed to get the bars working right. |
Awesome! You're totally right about the gradient, that was pointless. Glad I'm a bit concerned about the progress bars, because that introduces new On Tuesday, February 12, 2013, Zachary Kain wrote:
|
I checked it out, Bootstrap just uses |
And, I imagine one day in the future we won't be using any bootstrap code anymore, and we can cut the 120kb of css that it weighs |
Fair enough - I'll check it out soon, and thanks again for the PR! |
Tested locally. Beautiful. As always, friend Zack, you are awesome. |
Refactor & Update Progress Bars
heads up - getting some funkyness on my android, and iphone: screenshot |
On it. I removed a few lines because they didn't seem to do anything on desktop... seems that I wrote them for mobile in the first place. |
Don't stress too hard either, next push will be a bit down the pike. Thanks again for all your help |
No problem, I'll figure it out. Unfortunately, I don't have an iOS device to test with, just my Galaxy Nexus. Try just adding |
Closer, no fills: screenshot. I just use xcode emulator for iphone on my laptop, and my android 2.2 (could use eclipse android emulator) |
got a big derby-auth fix in the pipe, might be pushing soon. I'll take a stab at the missing fills, just chiming in in case you have a top-of-the-dome recommendation |
Ok, couldn't get it working on mobile even with those 3 things you mentioned. I reverted all these commits in 064abc9 (also see ec2ec3e). When you sit down to it again, just revert my revert. I think for now, unless you're thinking "oh it's an obvious bug!", we should go back to the original progress-bars, just so we have less to maintain in the short term. Keep them on a separate branch or some such. I wanna get all your avatar box code back in though |
OK, cool. You do your thing, I'll work out all the kinks with the progress I'm not very good at using Git for big projects/with others, sorry for the On Wed, Feb 13, 2013 at 3:34 PM, Tyler Renelle notifications@github.comwrote:
– Zachary Kain Designer, Creative Technologist |
Not at all, you were fine - I was the one that merged into master before On Wednesday, February 13, 2013, Zachary Kain wrote:
|
…rs-names Link for Tyler and Vicky's names
(trying this again)
Got rid of a lot of markup, replaced with the HTML5 element, which has a cool javascript API and is generally rad. Polyfilled for older browsers too, so should work everywhere IE8+, and on Android/iOS.
Having no iOS device myself, we'll need to test. But performs smashingly on my Nexus.