| #import "UIImage+UIViewCapture.h" | |
| #import <QuartzCore/QuartzCore.h> | |
| @implementation UIImage (UIViewCapture) | |
| + (UIImage *)imageWithView:(UIView *)view{ | |
| UIGraphicsBeginImageContextWithOptions(view.bounds.size, view.opaque, 0.0); | |
| [view.layer renderInContext:UIGraphicsGetCurrentContext()]; | |
| UIImage * img = UIGraphicsGetImageFromCurrentImageContext(); |
| #import <Foundation/Foundation.h> | |
| @interface JNWThrottledBlock : NSObject | |
| // Runs the block after the buffer time _only_ if another call with the same identifier is not received | |
| // within the buffer time. If a new call is received within that time period the buffer will be reset. | |
| // The block will be run on the main queue. | |
| // | |
| // Identifier and block must not be nil. | |
| + (void)runBlock:(void (^)())block withIdentifier:(NSString *)identifier throttle:(CFTimeInterval)bufferTime; |
| //viewDidload | |
| if ([self respondsToSelector:@selector(setNeedsStatusBarAppearanceUpdate)]) { | |
| // iOS 7 | |
| [self prefersStatusBarHidden]; | |
| [self performSelector:@selector(setNeedsStatusBarAppearanceUpdate)]; | |
| } else { | |
| // iOS 6 | |
| [[UIApplication sharedApplication] setStatusBarHidden:YES withAnimation:UIStatusBarAnimationSlide]; | |
| } |
| function cd() { | |
| async() { | |
| { | |
| $2 $($1) | |
| }& | |
| } | |
| notify_callback() { | |
| [[ $1 > 0 ]] && echo "You have new stuff to pull!" | |
| } |
| 13:15 <xQuasar> | HASKELL IS FOR FUCKIN FAGGOTS. YOU'RE ALL A BUNCH OF | |
| | FUCKIN PUSSIES | |
| 13:15 <xQuasar> | JAVASCRIPT FOR LIFE FAGS | |
| 13:16 <luite> | hello | |
| 13:16 <ChongLi> | somebody has a mental illness! | |
| 13:16 <merijn> | Wow...I suddenly see the error of my ways and feel | |
| | compelled to write Node.js! | |
| 13:16 <genisage> | hi | |
| 13:16 <luite> | you might be pleased to learn that you can compile | |
| | haskell to javascript now |
| // note: none of this is implemented yet -- this is just a brainstorm | |
| // problem: there isn't a well defined solution for publishing modules to NPM that | |
| // include their own markup and styles. consider this contrived example: | |
| module.exports = function makesButtonBlue(buttonId) { | |
| var button = document.getElementById(buttonId) | |
| button.className = 'blue' | |
| } |
In addition to awesome docs #228, Bower deserves a proper logo. See below for sketches. I'm curious if you think any of these are worth me putting more effort into.
Take a look at Yeoman right now.
The other two entities have awesome logos. Bower's got to represent.
| gifify() { | |
| if [[ -n "$1" ]]; then | |
| if [[ $2 == '--good' ]]; then | |
| ffmpeg -i $1 -r 10 -vcodec png out-static-%05d.png | |
| time convert -verbose +dither -layers Optimize -resize 600x600\> out-static*.png GIF:- | gifsicle --colors 128 --delay=5 --loop --optimize=3 --multifile - > $1.gif | |
| rm out-static*.png | |
| else | |
| ffmpeg -i $1 -s 600x400 -pix_fmt rgb24 -r 10 -f gif - | gifsicle --optimize=3 --delay=3 > $1.gif | |
| fi | |
| else |
| module.exports = function(grunt) { | |
| // Project configuration. | |
| grunt.initConfig({ | |
| test: { | |
| non_expand: { | |
| files: [ | |
| {src: '*', dest: 'build', dot: true}, | |
| ] | |
| }, |
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.
