Since the library is written in Swift, why not issue a demo project in Swift ?
frederic-adda
All 4 comments
It's to make sure the objective-c still works.
pmairoldi
on 19 Jan 2017
ok, but that's not really consistent with advertising about the framework being written in Swift.
I mean, a lot of developers are using this library BECAUSE it's written in Swift, and therefore expect to find some Swift in the demo project.
Also, the big changes in Charts 3.0.1 are related to Swift 3.
I agree that it's not that difficult to re-translate from obj-C to Swift, but, once you have chosen the future, why look back? ;-)
frederic-adda
on 19 Jan 2017
It would be very helpful if there were Swift 3 examples.
kevinburandt
on 30 Jan 2017
The framework is written in Swift. Demos are in ObjC to make sure and to demonstrate interoperability. If you are a developer you can take a function name from ObjC and call it in Swift, it's not rocket science.
danielgindi
on 30 Jan 2017
Related issues
heumn
路
3Comments
PrashantKT
路
3Comments
JW00332
路
4Comments
Bharati555
路
4Comments
cilasgimenez
路
4Comments
Most helpful comment
ok, but that's not really consistent with advertising about the framework being written in Swift.
I mean, a lot of developers are using this library BECAUSE it's written in Swift, and therefore expect to find some Swift in the demo project.
Also, the big changes in Charts 3.0.1 are related to Swift 3.
I agree that it's not that difficult to re-translate from obj-C to Swift, but, once you have chosen the future, why look back? ;-)