A strategy that I found works really well to quickly style everything is to create a category on UIView that defines a block property decorated with UI_APPEARANCE_SELECTOR, then on the setter, invoke the block. Then set the appearance proxy on app startup:
The advantage is that you can style properties that aren't supported by UIAppearance natively, since a block just gets run when the view is ready to be styled. You also can style subviews from the same block (ie. title label inside of a warning view should be red and bold).
I was very excited about Pixate when I followed your link, but after the initial excitement it turned out that it's one of those stupid MVP (potentially) vaporwares that's just a cute landing page with a form for "give us your email so we can let you know when it's available" in the signup/download link... It's a concept, not a product. And for all we know, it could take a year or two before it's released. Yet, the landing page makes you believe you can use it today:
"Long gone are the days of tedious image slicing [..]. With Pixate, designers and developers alike can conceive, [..]. etc., etc."
I really hate such "tricks". If it's a concept, just say so in the landing page - we won't kill you! We will find out in the end - it's hardly a secret, and will be pissed when we click "Download SDK Now!" and find out it's in the early stages of development...
I might've been interested in backing them up on KickStarter, but I really don't trust them now (because of this trick they pulled on me). What if their framework has a serious bug (a severe memory leak)? Can I trust these guys to tell me so if I build my (imaginary) $50,000 app using their framework? No, I don't feel that confident.
I'd use something like this if it was built by apple but I can style apps quickly enough as is without going out of my way to implement this.
As others have mentioned it's not really a "drop-in solution" and it doesn't look to be much faster than just creating categories that return styled objects you need eg: [UIButton greenButtonWithText:@"Sign up"]; [UILabel headerLabelWithText:@"etc, etc"];
Looks good I may use it. Looks like you are using the MIT license which is nice and permissive but could I suggest that you leave the heading ("The MIT License") in so that people can see at a glance that it is that.
That assumes that you haven't changed the licence at all.
[Edit: License does seem unchanged. I've sent a Pull request if the creator does want to make this change.]
I REALLY want something like this. Like the others said, it must use appearance proxies whenever possible. I literally want to add the source files, edit the .nss file and it works.
I wonder if something could be done with the appearance proxy, or even something as simple as a #define from UIView to NUIView in the pch, that would make this even more drop in.
[+] [-] borgopants|13 years ago|reply
As an iOS developer however, I find that using Interface Builder or pure code is much more flexible and simpler to use than a CSS stylesheet.
[+] [-] wlue|13 years ago|reply
[+] [-] kreutz|13 years ago|reply
[+] [-] pooriaazimi|13 years ago|reply
"Long gone are the days of tedious image slicing [..]. With Pixate, designers and developers alike can conceive, [..]. etc., etc."
I really hate such "tricks". If it's a concept, just say so in the landing page - we won't kill you! We will find out in the end - it's hardly a secret, and will be pissed when we click "Download SDK Now!" and find out it's in the early stages of development...
I might've been interested in backing them up on KickStarter, but I really don't trust them now (because of this trick they pulled on me). What if their framework has a serious bug (a severe memory leak)? Can I trust these guys to tell me so if I build my (imaginary) $50,000 app using their framework? No, I don't feel that confident.
[+] [-] bradfol|13 years ago|reply
Pixate appears to be a large project and very ambitious, so I am surprised to see NUI appear, seemingly out of nowhere.
[+] [-] bengl3rt|13 years ago|reply
As it happens, I was going to build something like that for an app I'm due to start tomorrow, but now I don't have to.
[+] [-] pdenya|13 years ago|reply
As others have mentioned it's not really a "drop-in solution" and it doesn't look to be much faster than just creating categories that return styled objects you need eg: [UIButton greenButtonWithText:@"Sign up"]; [UILabel headerLabelWithText:@"etc, etc"];
[+] [-] josephlord|13 years ago|reply
That assumes that you haven't changed the licence at all.
[Edit: License does seem unchanged. I've sent a Pull request if the creator does want to make this change.]
[+] [-] frankus|13 years ago|reply
It's a pretty neat concept, particularly if you have web content that needs to be styled in coordination with your app's chrome.
[+] [-] jquave|13 years ago|reply
HN discussion url: http://news.ycombinator.com/item?id=4880974
[+] [-] kyle_martin1|13 years ago|reply
[+] [-] supercoder|13 years ago|reply
I could never use this based on that requirement.
[+] [-] RandallBrown|13 years ago|reply
[+] [-] shawn-butler|13 years ago|reply
Of course, usually my first glances are wrong.
[+] [-] eclipxe|13 years ago|reply
[+] [-] adelevie|13 years ago|reply
[+] [-] gry|13 years ago|reply
[+] [-] max81|13 years ago|reply
[+] [-] dia123|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] chrismetcalf|13 years ago|reply
[+] [-] schraeds|13 years ago|reply
[deleted]