Mulberry 0.2 is out today, with several new features to make it even easier to customize your apps:
- In Mulberry 0.1, you had to be very verbose when overriding the default
styles. As of 0.2, when an app is scaffolded, the default theme is copied
into the app, where it can be modified directly. To pull any upstream changes
to the built-in themes, we added
mulberry update_themesto the CLI.
- A new
toura.app.Phonegap.registerAPImethod lets you create your own wrappers that make it easier to do development in a browser. Read more about browser-based development with Mulberry.
- We beefed up
mulberry create component; it now automatically creates a stub .scss file for the component, and adds an @import statement to your theme’s
- Now when you add pages to your sitemap, you can just run
mulberry scaffoldinside your Mulberry project to create them all at once, rather than having to remember which ones to create yourself. Read about all the command line options.
- It’s often necessary to repopulate a component or a piece of a component when
it gets new data or its state changes. Mulberry 0.2 introduces the
populateElementmethods on components to make this easier – just pass it a template and the data for the template, and it handles the rest. Read more about custom components.
We also landed a few other features, several bug fixes, some improvements to the command line, and lots of docs. Read the full release notes here.