Storyboarding feature? sooner or later...

[ben]

hi guys,

yet again,
(don't mind my asking, but) do we need to think about a storyboard support for cappuccino?
anyone uses storyboards for their os x apps or already ported some xib apps?

the class reference has some great description, but wouldn't it be nice to
have the view and window controllers represented in one ib view?

best greetings,
ben

[ben]

the appkit release notes has also some great infos...

i already touched some files, but still have questions...

Compiling [Browser] _CPStoryboardPrivateData.j...

Compiling [Browser] CPStoryboard.j.............

Compiling [Browser] CPStoryboardSegue.j..........

Compiling [Browser] CPStoryboardSegueTemplate.j................

some particular cases would be the CP*ViewController (page, split, tab) changes...   

is there a right place to ask? (only github? - i don't see any activity on the dev group...)

lg

ben

[Dogild]

Hi Ben,

Yeh right now when don't have something about the storyboard and I'm pretty sure that nobody is currently working on this part. So feel free to help :D

To ask questions, the best would be to open a pull request with your work, and then we could check your code and help you ;). Another good option would be to come in the cappuccino gitter.

Thanks and good luck !

[Martin Carlberg]

Hi Ben,

This looks really interesting.

Looking forward to see your code on this.

- Martin

--
You received this message because you are subscribed to the Google Groups "Cappuccino & Objective-J" group.
To unsubscribe from this group and stop receiving emails from it, send an email to objectivej+...@googlegroups.com.
To post to this group, send email to objec...@googlegroups.com.
Visit this group at http://groups.google.com/group/objectivej.
For more options, visit https://groups.google.com/d/optout.

[Cacaodev cacaodev]

This is a great initiative, thanks.

We could really benefit from the new *Controller classes because it's a way to reduce the loading at run time (a problem we have in cappuccino since the beginning). And the storyboard feature seems to be *the* way to easily use these classes in IB.

If you need to know more precisely how the Storyboard classes work in cocoa, just ask me (here or privately), I might be able to help.

[ben]

(of course) an important thing is:

you can not create connection in different scenes, so there is no reference/link to your application

and/or delegate for bindings/outlets/actions, except in your application scene…

hence nothing to retrieve from your app delegate (or app controller, like nib2cib named it),

without creating code for your dozens window/view controllers!?, really?

esp. if you create a single(non-document based) app that want’s the core data stack…

is one (or the only!?) option the main window’s content view controller??

--

i have setup my github account by now :)

but i need to get more familiar with it…

@Dogild

you already created the issues ;)

[ben]

hi guys,

would the above scenario didn’t bother your core-data based app?

now, another wtf!? - as far as i can tell, there seems to be a major

bug in xcode (6.3.2), which prevents you from compiling storyboards

at all :/

to be more specific, a view based table view with a popup binding :/

ibtool/d (depending on how you invoke the compilation) will eat up

all your mem, if you don’t kill it :/

while in a xib file, you can (always) bind to your application

(not anymore in storyboards - see above), but the view based

table view with a popup does work, even though you have to

use a workout-around like this: [1].

hardly surprising that there are any storyboard osx apps out there :D

pretty sad... am i missing an important part here??

lg ben

--

[1] http://stackoverflow.com/questions/14708947/nspopupbutton-in-view-based-nstableview-getting-bindings-to-work