Description:

yet another layout builder

Yet Another Layout Builder #





Yet another Flutter library for building layouts from xml assets (YALB). Using builder for
generating most of needed code to perform transform from xml to widgets.
Features #

Automatic resolving Widget classes from xml nodes using it's names.
Automatic resolving widgets constructor by used xml attributes / subnodes.
This library tries to use builder to provide as much as possible code from xml assets.
Parse of xml and processing data is separated from Widgets build phase. This allow to create
runtime builder which can be used any time needed without time consuming parsing.

Getting started #
It is worth to look first into examples to get general overview what's going on. There are two
major phases of working with YALB:

Writing xml files with layouts and generating code using builder.
Integration of engine with application (delivering runtime data, providers or other needed things).
Keep in mind that you probably will go to each phase several times across application development,
every time you add new attributes/nodes it's worth to run builder to prepare needed helpers. However
if you don't add any new elements (no new node types, no new attributes) just reusing already present
then there is no need to perform build. Next sections guide you through those phases.

First layout #
Create empty flutter app and put simple layout named layout.xml into assets folder:
<Container>
<_color a="255" r="100" g="100" b="100"/>
<_padding __EdgeInsets="" value="15"/>
<Column>
<Text data="This is Big Text" textScaleFactor="3.3"/>
</Column>
</Container>
copied to clipboard
Don't forget to add it to pubspec.yaml as follow:
flutter:
assets:
- assets/layout.xml
copied to clipboard
Now we have to run builder, go to folder with your application and execute following line:
dart run build_runner build
copied to clipboard
Done, you should see new file named widget_repository.g.dart in your lib folder.
Bind layout to code #
After creating empty flutter app you should have single stateful widget with single state generated.
In our example class with this state is called _MyHomePageState, we need to do few things to
use YALB in it. First let's add imports at top of file:
import 'package:yet_another_layout_builder/yet_another_layout_builder.dart' as yalb;
import 'widget_repository.g.dart';
copied to clipboard
Before we use other widget builder, we need to register all needed code helpers. To do so add
following line into your main function:
void main() {
registerWidgetBuilders(); //<---- add this line
runApp(const MyApp());
}
copied to clipboard
Now we can move to _MyHomePageState, we add filed in which we hold builder, and modify
build method, to use YAML builder for part of widgets tree. We keep Scaffold with title
but, inject layout into body. To perform this we need helper function _loadFileContent which
loads xml from asset into string:
Future<String> _loadFileContent(String path) {
return rootBundle.loadString(path);
}
copied to clipboard
This method can be used with FutureBuilder along with YALB builder:
FutureBuilder<String>(
future: _loadFileContent("assets/layout.xml"), //Loads a xml
builder: (context, snapshot) {
if (snapshot.hasData) {
builder ??= yalb.LayoutBuilder(snapshot.data!, {}); //Create builder if it not exists
return builder!.build(context); //Performs build of widget tree
}
return Container();
})
copied to clipboard
Final code should look similar to:
class _MyHomePageState extends State<MyHomePage> {
yalb.LayoutBuilder? builder;

Future<String> _loadFileContent(String path) {
return rootBundle.loadString(path);
}

@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text(widget.title),
),
body: FutureBuilder<String>(
future: _loadFileContent("assets/layout.xml"),
builder: (context, snapshot) {
if (snapshot.hasData) {
builder ??= yalb.LayoutBuilder(
snapshot.data!, {"MyText": "This is my text"});
return builder!.build(context);
}
return Container();
}));
}
}
copied to clipboard
Now it's time to run it and see if it works!
Registry. #
To instruct LayoutBuilder how to interpret xml elements, and how to create Widget tree,
some helper code is needed. Registry is a static class which should be used to bind xml elements to
code snippets which do the work. In many situations manual usage of Registry is not needed,
usually all needed code can be generated by build_runner. However it's worth to know structure and
how to extend functionality by providing your own code for this framework. There are just few
methods to cover, however reading first documentation for
processing tree will make things more easy to
understand. We will use code parts generated by build_runner to reduce abstraction in explanation.
Widget Builders #
First lets describe what is really Widget builder. For this package we call "Widget builder" any
function or method which takes data in form of WidgetData and returns as a result instance of
Widget. Supported signature is:
Widget _anyNameYouLike(WidgetData data) {...}
copied to clipboard
It's important to understand that there are two types of Widget builders:

for container like widgets, it's any widget which can have child or children widgets. For example
Container, Column, etc
for non owning widgets, this mean that this widget can't have any child widget. For example:
Text, Checkbox
For each class of widget dedicated add method is provided.

Both addWidgetContainerBuilder and addWidgetContainerBuilder have very similar
signatures:
static void addWidgetBuilder(String elementName, WidgetBuilder builder, {DelegateDataProcessor dataProcessor = _nopProcessor})
static void addWidgetContainerBuilder(String elementName, WidgetBuilder builder,{DelegateDataProcessor dataProcessor = _nopProcessor});
copied to clipboard
There mandatory arguments are elementName which states for name of xml element to which
builder will be assigned, and a builder which will be called when layout will be created.
This form should be used if all argument for Widget ar Strings or there is no arguments at all,
example of delegate to build Text widget might look like:
Registry.addWidgetBuilder("Text", _textBuilderAutoGen);

Widget _textBuilderAutoGen(WidgetData data) {
return Text(
data["data"]!,
);
}
copied to clipboard
When widget expect parameter of different type, for example int we still can use this approach, but
delegate need to do conversion in fly:
Registry.addWidgetBuilder("Checkbox", _checkboxBuilderAutoGen);

Widget _checkboxBuilderAutoGen(WidgetData data) {
return Checkbox(
value: data["value"] == "true", //convert from String to bool
...
);
}```
However this conversion is done each time when layout is build, in many situations it's not
necessary. Usually conversion can be done only once while parsing xml, for such purpose there is
optional ```dataProcessor``` argument. It allows to give additional function which will be called
while parsing xml to do needev conversion. So our example with ```Checkbox``` now can look like:
```dart
Registry.addWidgetBuilder("Checkbox", _checkboxBuilderAutoGen, dataProcessor:_checkboxDataProcessor);

Widget _checkboxBuilderAutoGen(WidgetData data) {
return Checkbox(
value: data["value"],
...
);
}```

dynamic _checkboxDataProcessor(Map<String, dynamic> inData) {
inData.updateBool("value");
// or if not use custom extensions
// inData["value"] = inData["value"] == "true";
return inData;
}
copied to clipboard
Function which is given to dataProcessor will receive map of parameters where values are
usually strings (if taken from xml) or can be any object if they are injected ($ or @
used in xml). And this function should replace needed parameters inside map to converted, finally
function MUST return this input parameter, as shown in example. Until now we used
addWidgetBuilder method, but this same principles applies for addWidgetContainerBuilder
the only difference is that for Container like widgets it's needed to add children which can be
found inside WidgetData type, here is example of such delegate:
Registry.addWidgetContainerBuilder("Column", _columnBuilderAutoGen);

Widget _columnBuilderAutoGen(WidgetData data) {
return Column(
children: data.children!
);
}
copied to clipboard
Value builders (Const values) #
As mentioned in many places in this documentation YALB distinguish two types of xml elements:
Widgets and "Const Values". As a Const Value we consider any object which is needed as an parameter
to create Widget instance. For example Color or EdgeInsets are classes considered as
Const Values. Xml parser tries to create const value when encounter xml element which name starts
with _ character. To register delegate for such elements use this method:
static void addValueBuilder(String parentName, String elementName, ConstBuilder builder);
copied to clipboard
Those delegates are called while parse xml process, then value it's considered as created and put
into Widget data pack. Example of usage:
Registry.addValueBuilder("Container", "color", _colorValBuilderAutoGen);

Color _colorValBuilderAutoGen(String parent, Map<String, dynamic> data) {
return Color.fromARGB(
int.parse(data["a"]!),
int.parse(data["r"]!),
int.parse(data["g"]!),
int.parse(data["b"]!),
);
}
copied to clipboard
Xml Structure #
YALB supports two main structures of xml files. First one which starts directly with widget tree.
There must be Widget component root, and then it's children and attributes. This approach disables
usage of styles and blocks described later. Example of such xml can look like:
<Center>
<Column>
<Text data="Hello world!"/>
</Column>
</Center>
copied to clipboard
If usage of styles or blocks is needed then xml file must have root node named YalbTree. Then
any combination of YalbBlockDef and YalbStyle nodes might be put before widget root.
In general order of usage should be taken into consideration, before use any block or style it
should be defined. Example of xml:
<YalbTree>
<!-- Define styles -->
<YalbStyle name="Pink">
<_color a="255" b="250" g="0" r="233" />
</YalbStyle>
<!-- more styles can be put here-->

<!-- Define blocks -->
<YalbBlockDef name="SomeBlock">
<Container _yalbStyle="Pink">
<Text data="This is Pink Styled Block" />
</Container>
</YalbBlockDef>
<!-- more blocks can be put here-->

<!-- this is root of widgets tree -->
<Center>
<Column>
<Text data="Hello world!"/>
</Column>
</Center>
</YalbTree>
copied to clipboard
Support for styles #
YALB support simple styling, it allows to collect pack of values and give it a name.
Single style definition must be put in node <YalbStyle> in YalbTree parent. It must have
unique name and must have at least one attribute node. After defining name of style can be
referenced by any xml element to use stored values. Again values might be any type not
necessary strings, so same as for addWidgetBuilder we can provide delegate which perform
conversion. To register such delegate use method:
static void setStyleDataProcessor(DelegateDataProcessor prc);
copied to clipboard
example of usage:
Registry.setStyleDataProcessor(_yalbStyleDataProcessor);

dynamic _yalbStyleDataProcessor(Map<String, dynamic> inData) {
inData["height"] = double.tryParse(inData["height"]);
return inData;
}
copied to clipboard
Support for blocks. #
In situations when some subtree of widgets is reused (for example in rows in list or buttons) it
can be defined as block. Single block definition must be put in node <YalbBlockDef> in
YalbTree parent. It must have unique name and must have single root widget. From this point
there is possible to use two other specialised nodes to put such block in widget tree. This can be
done through nodes YalbBlock and YalbWidgetFactory. Both usages are shown in examples.
How to use YalbBlock #
This node comes in two flavours, shown below:
<YalbTree>
<YalbBlockDef name="PinkBlock">
<Container>
<_color value="F0F" />
<_padding __EdgeInsets="" value="15" />
<_height value="100" />
<Text data="This is Pink Block" />
</Container>
</YalbBlockDef>

<Center>
<Column>
<YalbBlock name="BlueBlock" /> <!-- #1 type of usage -->
<YalbBlock widget="@widget" /> <!-- #2 type of usage -->
</Column>
</Center>
</YalbTree>
copied to clipboard
As shown one of two syntax can be used. If attribute name is used then proper block must be
previously defined in YalbBlockDef node. There is also possibility to inject widget from
outside xml, by usage of attribute widget, in this situation parameter @widget must
be injected to builder by while creating or updating builder, for example:
LayoutBuilder(xmlString, {"widget" : const CircularProgressIndicator()});
//... and can be later replaced by
builder?.updateObjects({"widget" : const CircularProgressIndicator()});
copied to clipboard
How to use YalbWidgetFactory #
If more control over injected block is needed then YalbWidgetFactory comes in play. It expects
one attribute named provider which must point to function with following signature:
List<WidgetFactoryItem> _factoryDataProvider();
copied to clipboard
Depending on application logic this function must return list with data which will be used to build
blocks in widget tree in which node YalbWidgetFactory is used. So it's important to insert
this node into parent which can handle one or many children. Returned WidgetFactoryItem
instances contains two elements: Unique name of block to be build, data pack which will be injected
into block. This implies that any block which can be used with factory must be first defined in
YalbTree. And for each newly created instance of block different parameters can be injected.
Please refer to listview example for more details.
How LayoutBuilder works? #
Before you read this paragraph please read info about registry, and how things are designed. Ok, so
in reality our builder is just a provider of code blocks (widget builders or other classes needed by
widgets) for registry. What code needs to be generated is decided by analyze of xml assets from
folder assets. If for some reason you don't want to use builder it's up to you, it's totally fine to
fill registry by manually written code.
LayoutBuilder rule: Node name #
Builder follows specific rules for code generation. Depending what it finds some parsers and
extensions will be included, and sometimes not.

If xml node name doesn't start with '_' character: It's considered to be name of widget class. It
is case sensitive! Builder will try to find widget class which match this name.
If xml node name start with '' character: Then it's considered as a parameter to parent widget
node, name of parameter is name of node without '', note lower case! Again this is case sensitive.
There are more important information about this nodes in later section!

So let's look at example for this rules:
<Container>
<_color a="255" r="233" g="100" b="0"/>
<Text/>
</Container>
copied to clipboard
So we have two widgets: Container and Text, and Container has a single attribute color. What this
give us? If you look into documentation of flutter widget classes, then you can use any class
constructor listed there, but you have to preserve names of attributes. If you do so, then builder
will resolve it correctly.
For example consider class constructor:
const Text(
String data,
{Key? key,
TextStyle? style,
StrutStyle? strutStyle,
TextAlign? textAlign,
TextDirection? textDirection,
Locale? locale,
bool? softWrap,
TextOverflow? overflow,
double? textScaleFactor,
int? maxLines,
String? semanticsLabel,
TextWidthBasis? textWidthBasis,
TextHeightBehavior? textHeightBehavior}
)
copied to clipboard
you can use it in xml in following way:
<Text data="some text to show" maxLines="4">
copied to clipboard
or (equivalent)
<Text>
<_data value="some text to show"/>
<_maxLines value="4"/>
</Text>
copied to clipboard
When to use which form? It's up to you however there is one limitation: If parameter is not a
primitive (String, int, double, bool) then it must be used as child node, for example:
<Container>
<_color a="255" r="0xFF" g="0" b="0xFF"/>
</Container>
<Container>
<_color value="FF00FF"/>
</Container>
copied to clipboard
As you can see Color class have several constructors, builder can detect it by matching node
attributes and prepare one or several builders. All depends what it find in xml.to
LayoutBuilder rule: Attribute node (const value) #
As mentioned earlier if node starts with '_' it's considered as a parameter for parent node (widget).
Ok we know name of attribute but what about type? There are two things which you need to know:

If name of attribute is also type name of this attribute then you have to nothing to do (see
above example with usage of color).
If name and type name are different, then you have to add special attribute which name starts with
2x '_' sign. Name of this attribute should be same as requested type name, value of it is ignored.
Ok, example:

<Container>
<_color a="255" r="0xFF" g="0" b="0xFF"/>
</Container>
<Container>
<_padding __EdgeInsets="" value="5"/>
</Container>
copied to clipboard
Color is straight forward: name and type are this same. But for padding we manually pointing
EdgeInsets class (note capital case!).
LayoutBuilder rule: Node attributes #
As mentioned earlier, for each node attributes are collected and later used to identify proper
constructor. So attribute names must match names of parameters in constructor. It's not necessary to
keep order (unless class have positional parameter!) however keeping it might prevent some
unexpected behaviours. Please keep in mind that attributes should be used only for primitive types
(String, int, double, bool) for all other types use Attribute node.
LayoutBuilder rule: Children #
Some widgets allows (or requires) child or children. To do so just embed xml node into other xml
node. But keep in mind that child must be a widget! Look at this:
<Container>
<_color a="255" r="233" g="100" b="0"/>
<Text>
<_data value="text"/>
</Text>
</Container>
copied to clipboard
Container has a single child: Text. But Text doesn't have any child! If some widget can have
multiple children it might look like:
<Column>
<Text data="line 1"/>
<Text data="line 2"/>
<Text data="line 3"/>
</Column>
copied to clipboard
LayoutBuilder: Using external data #
While creating widgets there is often need to deliver some runtime information to newly created
layout. YALB supports this in two ways:

When creating builder through call to LayoutBuilder(xmlString, {}) second argument is a
Map with String keys and dynamic. Values from this map can be accessed in XML.
Before call to build() method on LayoutBuilder it's possible to update objects passed
while constructing builder by call to updateObjects(). Note that updated will be only
objects which are used by widgets.

How to access objects passed to LayoutBuilder from XML? There are two ways to do it, let's
look into simple code:
final builder = LayoutBuilder(xmlString, {
"MyText": "This is my Text",
"MyPadding": EdgeInsets.all(22),
"ButtonCallback": () {
setState((){
print("Pressed!");
});
},
});
return builder.build(context);
copied to clipboard
and corresponding xml:
<Container padding="@MyPadding">
<TextButton onPressed="@ButtonCallback">
<Text data="$MyText"/>
</TextButton>
</Container>
copied to clipboard
As you probably noted accessing to objects is done by using proper key (case sensitive!) preceded by
$ or @ sign. What is difference?

If you want force String value to be used, place $ in front. On object taken from map
will be executed toString() method and result will be used as a parameter. NOTE it is not
this same ad Dart string interpolation, no extra magic can be done.
If you want to pass object without any change of type, then use @, it pass value as it is
directly to constructor parameter.

You probably noticed that any kind of data can be passed, so it's straight forward way to:

Pass some code build widget or styling and attach it to xml based build.
Pass callbacks and functions which can be called by widgets.
Pass texts if any of them can be changed in runtime.
Pass dynamic information for special nodes (described later).
Pass builders for widgets like ListView.

LayoutBuilder: Designated constructors #
After analyze of widget_repository.g.dart file sometimes methods with name
...ValSelectorAutoGen can be found. This is special case when several different constructors
are used to create instance of object. There are two patterns which are used:
Compare by given attributes, code will take form:
if ({"a", "b", "g", "r"}.containsAll(data.keys)) {
return _color0ValBuilderAutoGen(parent, data);
}
copied to clipboard
Compare by designated constructor, code will take form:
if (data["_ctr"] == "only") {
return _edgeInsets0ValBuilderAutoGen(parent, data);
}
copied to clipboard
Notice _ctr key name. This is special case, when builder detect attribute in form:
<_margin __EdgeInsets="only"/>
copied to clipboard
Then to data associated with this node will be added key _ctr with value of attribute
which name starts with __. In this case data["_ctr"] = "only".
PITFALLS
Because YALB separates parse and build phases there are some nasty pitfalls when working with
external data. Here are most common with explanation:
Passing class field as an object.
This might look like:
class MyState extends State<MyHomePage> {
yalb.LayoutBuilder? builder;
String _myField = "This is text";

@override
Widget build(BuildContext context) {
return FutureBuilder<String>(
future: _loadFileContent("assets/layout.xml"),
builder: (context, snapshot) {
if (snapshot.hasData) {
builder ??= yalb.LayoutBuilder(snapshot.data!, {
"MyText": _myField,
"callback": () {
setState((){
_myField = "Second text"
});
},
});
return builder!.build(context);
}
return Container();
}));
}
}
copied to clipboard
Let's assume in xml you have button which call callback from objects, as a result text in some
widget should change. But this will not work. Why? Because when LayoutBuilder perform parsing
of xml it collects all data referenced by widgets described in xml. Then whole build process is
structured along with all needed data in needed places. From this moment build structure is "baked"
and will not change even if you change value of field _myField. Because value taken from it
is copied and Strings in Dart are immutable. Okay... how to fix this? Here is solution:
"callback": () {
setState((){
builder!.updateObjects({"MyText" : "My next text"});
});
},
copied to clipboard
or ...
"callback": () {
setState((){
builder!.updateObjects({"MyText" : _myField});
});
},
copied to clipboard
if value of _myField changed and you don't want to use const text.
My data processor is not used? (advanced)
If you remember section about Registry there are methods like:
Registry.addWidgetBuilder("name", _builder, dataProcessor:_dataProcessor);
copied to clipboard
When xml is parsed, all arguments from xml node are collected and passed to _dataProcessor
which can change it as needed. But this will happen only on parse phase! When you call
updateObjects on LayoutBuilder newly given values will not be passed to
_dataProcessor. So keep this in mind updating objects!
Builder configuration options #
As mentioned earlier Dart/Flutter build_runner is used to execute code generation for widget. There
are some extra options which can be passed to this builder. First create file build.yaml in
root of your project, and add following keys:
targets:
$default:
builders:
yet_another_layout_builder|widgetRepoBuilder:
options:
copied to clipboard
Then add required options described in next sections.
Option: ignore_input #
Thi is list of xml files which should be ignored while parsing assets directory. Example:
targets:
$default:
builders:
yet_another_layout_builder|widgetRepoBuilder:
options:
ignore_input:
- ignored.xml
- another_file.xml
copied to clipboard
Option: ignore_nodes #
By default builder will not process any xml elements which doesn't match with classes in packages.
However sometimes it might match some name, and for some reasons this is not wanted. To prevent such
match use this option. Example:
targets:
$default:
builders:
yet_another_layout_builder|widgetRepoBuilder:
options:
ignore_nodes:
- Container
- Color
copied to clipboard
Option: collect_progress #
By default some basic information about parse process are collected and put as a comment into
generated file. If this is unwanted specify this option with value false. Example:
targets:
$default:
builders:
yet_another_layout_builder|widgetRepoBuilder:
options:
collect_progress: false
copied to clipboard
Option: extra_widget_packages #
By default several common flutter packages are used to find Widgets. However if some 3rd party
packages should be also used in this process please add it like:
targets:
$default:
builders:
yet_another_layout_builder|widgetRepoBuilder:
options:
extra_widget_packages:
- package:flutter/painting.dart
copied to clipboard
Option: extra_attribute_packages #
This option is similar to extra_widget_packages, however it applies for attributes (xml
elements started with _ character). Different set of packages is used for class search, it
can be extended in following way:
targets:
$default:
builders:
yet_another_layout_builder|widgetRepoBuilder:
options:
extra_attribute_packages:
- package:flutter/painting.dart
copied to clipboard
Thanks #
I would like to thanks guys who created xml_layout package
for inspiring me to create my own variation in this area. It was fun to analyze and extend you work.

License

For personal and professional use. You cannot resell or redistribute these repositories in their original state.

Share

• Share on Facebook
• Share on Twitter