Build errors with Xcode 6.1

[sebastianwr]

Hi,

I was just trying to run the project but there a countless issues regarding the use of Optionals and some other stuff that seems new with the evolution of Swift. Are you going to fix it or are you interested in a pull request?

Kind regards,
Sebastian

[jasperblues]

We'd love a pull request! Thanks.

[sebastianwr]

Done, see pull request here: #3

Very optimistic since it just unwraps Optionals most of the time. Had to change the behavior of the sequentialTheme method. Hope it is still correct.

[jasperblues]

Merged. Thanks so much.

Yes, the code is a port of the original ObjC example. We still need to come back and stylize for Swift.

Meanwhile, we've got a few enhancements planned to make Typhoon work better with Swift.

We've set aside a block of time in November to work on this.

[danydev]

@jasperblues cool!....in the while can we have some insights about those enhancements? :D

[jasperblues]

@danydev

Autowiring:

Aleksey has implemented a much-improved auto-wiring feature for Objective-C. This is already in 2.3.0, but still private. Nonetheless can be tried :)

Feature: appsquickly/typhoon#252

Typhoon Bootrapping:

Currently Swift applications can only plist bootstrapping. Fine for full-Typhoon powered apps. . the are some ugly quirks to manual instantiation of Typhoon (libraries, tests, etc).

Also, even on Objective-C the feature is complicated and presents too many concepts to learn at once.

We'll make TyphoonComponentFactory an internal API and replace with TyphoonAssemblyBuilder.

Feature: appsquickly/typhoon#253

Factory Components:

There's a longhand way to create a definition produced by other components: https://github.com/typhoon-framework/Typhoon/wiki/Types-of-Injections#injecting-objects-produced-by-other-components

There's also a short-hand way that has quirks in Objective-C and doesn't work in Swift.

This will be fixed: appsquickly/typhoon#245

I think these are the highest priority issues (incl. documentation, testing and sample for #252).

Other issues:

• We don't have a Storyboard sample. And until yesterday the documentation was wrong.
• Sample app does not sure usage of runtime args - one of Typhoon's most useful features.
• User guide still needs work.
• There are not enough tutorials and blogs about Typhoon.
  Factory Components

[danydev]

@jasperblues wow....lot of things. I'm looking forward to use it!....keep up the good work!

[jasperblues]

@danydev Thanks! We're very interested to get your feedback on these new features or any other ideas you have for Typhoon.

[jasperblues]

@sebastianwr Did you come across any other free weather APIs? App is not looking so good with world weather online's v2 API (no forecast).

[sebastianwr]

First result on Google: http://openweathermap.org/api
Should I try this one out and update the Swift project?

Maybe I can also do the screencast in the next days. I'm a little busy but I'll see what I can do.

[jasperblues]

@sebastianwr You're very welcome to do either task any time you're free. I'm also juggling lots of other task, so its not always easy to find time for Typhoon.

[sebastianwr]

The current version works fine. Or is it using v1 API that becomes deprecated soon? Is that the reason for an API change?