Book Image

Flutter Cookbook

By : Simone Alessandria, Brian Kayfitz
4 (1)
Book Image

Flutter Cookbook

4 (1)
By: Simone Alessandria, Brian Kayfitz

Overview of this book

“Anyone interested in developing Flutter applications for Android or iOS should have a copy of this book on their desk.” – Amazon 5* Review Lauded as the ‘Flutter bible’ for new and experienced mobile app developers, this recipe-based guide will teach you the best practices for robust app development, as well as how to solve cross-platform development issues. From setting up and customizing your development environment to error handling and debugging, The Flutter Cookbook covers the how-tos as well as the principles behind them. As you progress, the recipes in this book will get you up to speed with the main tasks involved in app development, such as user interface and user experience (UI/UX) design, API design, and creating animations. Later chapters will focus on routing, retrieving data from web services, and persisting data locally. A dedicated section also covers Firebase and its machine learning capabilities. The last chapter is specifically designed to help you create apps for the web and desktop (Windows, Mac, and Linux). Throughout the book, you’ll also find recipes that cover the most important features needed to build a cross-platform application, along with insights into running a single codebase on different platforms. By the end of this Flutter book, you’ll be writing and delivering fully functional apps with confidence.
Table of Contents (17 chapters)
About Packt

How it works...

In this recipe, you have seen how to create a package comprising multiple files and depend on it using a git repository.

The part and part of keywords allow a library to be split into several files. In the main file, you specify all the other files that make the library, using the part statement. Note the commands:

part 'rectangle.dart';
part 'triangle.dart';

The preceding commands mean that the triangle.dart and rectangle.dart files are parts of the area library. This is also where you put all the import statements, which are visible in each linked file. In the linked files, you also add the part of statement:

part of area;

This means that each file is a part of the area package.

It's now generally recommended that you prefer small libraries (also called mini-packages) that avoid using the part/part of commands, when possible. Still, knowing that you can separate complex code into several files can be useful in certain circumstances...