News for hackers. Stuff that matters.
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by jawngee on Tuesday January 15, 2013 @03:44PM (#5062868)
As someone who builds app for big brands (Conde Nast, Nike, Porsche, etc.) I will not use this, despite any desire to actually do so.

Why?

You're shipping me a binary only. I want the source. I don't want to wait for you to fix some shit that you may or may not get around to doing. I have a really strict rule about this when it comes to client work, even stricter for personal work.

Your idea that I should base an entire application on a closed source binary that may or may not work is customer hostile, imho. You are inadvertently leaving customers out to dry when something breaks or doesn't work correctly. Unless your company has a team of devs ready to handle these cases ...

Would have been a good idea when the component market was roaring in the Borland Delphi days, but we're in the future now were open source is the way to go.

Pass.

Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by aaronbrethorst on Tuesday January 15, 2013 @04:30PM (#5063137)
I'm really torn about this. I was a Kickstarter backer of Pixate, and I love their tools, but I brought up the exact same concern to them over a few months ago. The response I got from them can best be paraphrased as 'we'll do our best'[1].

Accordingly, I'll likely use Pixate for apps shipped under my own brand, but I'd never use it for client work until this situation is resolved. The risk is simply too great.

There's an open source solution that does roughly the same thing but not as nicely, called NUI (http://www.cocoacontrols.com/platforms/ios/controls/nui), that you might want to check out.

[1] In case Paul or Kevin see this and want more context, the reply I got was via Kickstarter on July 24 2012 at 8:40AM Pacific.

Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by pcolton on Wednesday January 16, 2013 @02:44PM (#5068623)
Pixate is not an all-or-nothing solution. You can just style what you want via CSS, and do the rest in code. Do it all in code and just inline some CSS if you like. This isn't a "use UIKit or us" type of decision, but more of a "how can I write a lot less code and more dynamically style my apps". Lastly, at the Enterprise level, we offer source code escrow.
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by kurtpimentel on Tuesday January 22, 2013 @10:51AM (#5097646)
Local to Dallas?
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by hnriot on Tuesday January 15, 2013 @04:21PM (#5063081)
This is crazy, you're already using closed source when you link with the SDK, which links with numerous other closed source components.
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by jawngee on Tuesday January 15, 2013 @05:01PM (#5063334)
God grant me the serenity to accept the things I cannot change, the courage to change the things I can and the wisdom to know the difference.

That applies here.

Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by reidmain on Tuesday January 15, 2013 @08:46PM (#5064595)
UIKit is designed to be built upon. A lot of Apple stuff may be a black box but it is designed to be subclassed. This is really an all or nothing affair. Either this works perfectly for you or you are shit out of luck and you have to compromise to fit inside their box.
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by Zev on Wednesday January 16, 2013 @02:00AM (#5065745)
A lot of Apple stuff may be a black box but it is designed to be subclassed.

Aside from a small number of top-level classes[1] UIKit isn't designed to be subclassed. When you subclass things like UIAlertView, UIButton, UISwitch, UITextField, UIWebView… etc, you're in for a world undocumented gotchas and spending hours to do small simple things.

1. UIView, UIControl, UITableViewCell, UIScrollView, UIGestureRecognizer, UIViewController, UIApplication and maybe one or two other classes.

Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by reidmain on Wednesday January 16, 2013 @09:10AM (#5066802)
And you've listed about 90% of the things I usual end up subclassing because I've hit some limitation.

Also I wasn't talking specifically about UIKit. Foundation is another great framework that I've subclassed many times.

It's not perfect but Apple puts a lot of work into documenting how to subclass their frameworks. Third-party UI frameworks like this are much less forgiving.

Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by Zev on Wednesday January 16, 2013 @01:04PM (#5068102)
Can you give an example of some things that you subclass?
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by reidmain on Wednesday January 16, 2013 @03:05PM (#5068744)
From Foundation? NSDictionary, NSArray and NSOperation instantly jump to mind.
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by Zev on Wednesday January 16, 2013 @11:25PM (#5070924)
What do you get out of subclassing NSDictionary or NSArray that you don't get out of a category?
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by reidmain on Friday January 18, 2013 @09:34AM (#5078733)
Well in this case I subclassed them so I could have the backing data source only weakly reference the items in the dictionary/array and because I subclassed them I can use them wherever NSDictionary or NSArray is an accepted parameter.

Apple's documentation also gives some examples:

https://developer.apple.com/library/ios/#documentation/Cocoa...

https://developer.apple.com/library/ios/#documentation/Cocoa...

Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by Zev on Friday January 18, 2013 @07:47PM (#5082058)
Why not use CFDictionaryRef and pass it along via toll-free bridging?
Re:Native Mobile Apps Styled With CSS - Pixate (YC S12) Laun... by reidmain on Sunday January 20, 2013 @08:54AM (#5086878)
I'm confused. How is that any easier? It's six of one, half dozen of the other.

I'd much prefer to write Objective-C code than pure C.