Use Xcodeproj to generate the example (and framework) project

[kylef]

I think it would be nice to replace the current Example project which is just renamed to some code that can generate framework targets for all selected platforms along with test target and example target depending on the users options.

I'd suggest the new layout would look something like this (using Stencil as the name of this pod).

.
├── LICENSE
├── README.md
├── Stencil.podspec
├── Stencil.xcodeproj

├── Stencil
│   ├── (Shared Code).swift
│   ├── ios
│   │   ├── (iOS only code)
│   ├── osx
│   │   ├── (OSX only code)
├── StencilTests
│   ├── The tests
│   ├── ios
│   │   ├── (iOS only tests)
│   ├── osx
│   │   ├── (OSX only tests)
├── StencilExample
│   ├── Any example code

The project would have the following targets:

• Stencil-iOS (Framework)
• Stencil-OSX (Framework)
• Stencil-iOSTests
• Stencil-OSXTests
• Stencil-Example (Example OS X or iOS application?)

Would also have some script (Makefile, Rakefile or .travis.yml) that can build everything and run both platform tests.

[kylef]

Adding to this, it could create a universal iOS and OS X framework so we can put them all in one target.

Example: https://github.com/kylef/URITemplate.swift

[kylef]

Depends on: CocoaPods/Xcodeproj#227

[fulldecent]

FWIW, https://github.com/MengTo/Spring works like this proposal recommends.

[orta]

I'd much rather we re-shuffle everything to format how SwiftPM works ( this was mentioned in #152 ) so that people building pods now will get it "for free" as soon as possible

[fulldecent]

That is a way better idea. Since #78 and #152 are mutually competing and #152 has more future proofing, I recommend to close #78 at this time.

[fulldecent]

More notes coming at #152.

[orta]

👍