Split View controller

[smtm]

If I understand the project correctly the goal is to provide a base for most used layouts. So eventually there will be a split View controller that can be set up with the motion-layout approach. As a OBj-C Noob I find the nesting and declaration as performed by Xcode boilerplate still a little bit daunting...

[malkomalko]

I think that's right rolando. Ultimately, the goal is to get every UI element wrapped up so that way you can make changes and have it look and feel like css in a way.

This is why you can define colors with hex codes and set alignment and such.

My hope is is that once this becomes the case, people can share their pre-defined layouts.

Does that make sense? I have big plans for this.

[smtm]

Yeah makes sense totally, I find myself trying to set up a split view controller to wrap an existing web app with web views. Important Actions I want the recreate with good looking Popovers.

I want to use the split view endless scrolling list and pupulate it with JSON from a rails backend and push in some 200 recs or so(think rails index). If I tap on the item the detail page (think rails show) opens. I want to implement a Navigation within the native app that checks the dependencies.

I will also want a breakout fullscreen, with only a nav Bar and a Tabbar, the rest is webview- In this area I am sort of trying to figure out how the wiring up of items work with Obj-C. The code looks messy and some wrapper that encapsulates this would be awesome.

I am currently working to extend this https://github.com/rjowens/SplitViewControllerExample to get my desired results and am sort of stuck at how to call a to switch to the full screen view.. I Obj-C Noob, but pretty fluent in Ruby...