Why no ComponentScreens?

Jun 17, 2011 at 8:42 AM

Why isn't the current release leveraging ComponentScreens? Wouldn't the PhoneChrome, StatusBar and the ApplicationBar, all be suitable as ComponentScreens?

Coordinator
Jun 17, 2011 at 11:56 PM

As PhoneChrome is used on everyscreen it made sense to build it into the template rather than use a Component Screens (which would have added an extra link to every screen in the app). It might have been worthwhile building StatusBar and the ApplicationBar into the PhoneChrome/default template in the same way a regular Phone project does, though for this release we didn't want to make the controls more complex than they needed to be.

In terms of ApplicationBars, they are not often the same across different screens so again we felt it made more sense to have these as standard components that you use as necessary rather than pre-built as component screens. Of course you can always make Component Screens of your ApplicationBar if that works for you - that’s the beauty of SketchFlow :)