Charts 2.1 Release – Top TipsPosted on 27 Sep 2012 Written by Stuart Grey
We’ve made quite a few changes to how the charts look – which inevitably means a few changes to the way they work. Here I’ll go through a few of the key points to help with the transition.
A whole new look
The first thing you’ll notice is that we’ve changed the default look and feel of the chart with two new themes. We want users to have these fancy new visuals out-of-the-box, and of our two new themes SChartLightTheme and SChartDarkTheme – SChartLightTheme is our new default.
Fear not, the original themes still exist and you can revert back to them with one simple line of code if you like! Just after creating your chart, adding the following line will take you back to how life used to be:
chart.theme = [SChartTheme new];
Brand new samples
We’ve been listening! We do love answering your support emails, but we thought that a few of the more common ones are best explained in our sample apps. Not only are they now prettier, they’re more realistic and offer much wider coverage of the more popular configurations. Even if you’re a seasoned ShinobiCharts pro, it really is worth checking them out for some new styling ideas and tips.
A picture says a thousand words….
But here at ShinobiHQ, we think you need a good font to really get those words onto the screen. Not satisfied with the native offering, we think we’ve picked one of the best – it just requires a little extra magic to make it work.
By now, you’ll have seen the font we’ve picked in action in our sample apps. It’s distributed in our new framework bundle but you’ll need to let Xcode know where to find it. In the plist file for your project you’ll need to add an entry for Fonts… and three sub nodes, one for each font. There’s an image below with an example, but also check out the sample app config if you’re a bit more cut-and-paste.
Wrapping it up
ShinobiCharts still comes to you in the same framework format, but it’s now bundled with a few extra treats – and in the future we think they’ll be even more. This is why the framework is now a layer deeper in an embeddedFramework. What does this mean to you? Good news – nothing really changes. You still drag the embedded framework into your project – check all of the boxes for your targets and away you go. Simple, just as before – we just thought you’d like to know why it looks different.
Enjoy and keep in touch
Those are my top tips for now – for a full list of changes check out the change log. And don’t forget – if you have any questions just contact us at email@example.com
Back to Blog