@@ -757,7 +757,7 @@ function.
757
757
758
758
Compiling a text ` rfwtxt ` file to the binary ` rfw ` format can be done
759
759
by calling
760
- [ ` encodeLibraryBlob ` ] ( https://pub.dev/documentation/rfw/latest/formats /encodeLibraryBlob.html )
760
+ [ ` encodeLibraryBlob ` ] ( https://pub.dev/documentation/rfw/latest/rfw /encodeLibraryBlob.html )
761
761
on the results of calling ` parseLibraryFile ` .
762
762
763
763
The example in ` example/remote ` has some [ elaborate remote
@@ -848,7 +848,7 @@ with the `DynamicContent` under the name `server`.
848
848
> This data is parsed by calling
849
849
> [`parseDataFile` ](https://pub.dev/documentation/rfw/latest/formats/parseDataFile.html),
850
850
> which turns it into
851
- > [`DynamicMap`](https://pub.dev/documentation/rfw/latest/formats /DynamicMap.html).
851
+ > [`DynamicMap`](https://pub.dev/documentation/rfw/latest/rfw /DynamicMap.html).
852
852
> That object is then passed to a
853
853
> [`DynamicContent`](https://pub.dev/documentation/rfw/latest/rfw/DynamicContent-class.html),
854
854
> using
@@ -862,9 +862,9 @@ with the `DynamicContent` under the name `server`.
862
862
>
863
863
> Ideally, rather than dealing with this text form on the client, the
864
864
> data would be turned into a binary form using
865
- > [`encodeDataBlob`](https://pub.dev/documentation/rfw/latest/formats /encodeDataBlob.html)
865
+ > [`encodeDataBlob`](https://pub.dev/documentation/rfw/latest/rfw /encodeDataBlob.html)
866
866
> on the server, and then parsed on the client using
867
- > [`decodeDataBlob`](https://pub.dev/documentation/rfw/latest/formats /decodeDataBlob.html).
867
+ > [`decodeDataBlob`](https://pub.dev/documentation/rfw/latest/rfw /decodeDataBlob.html).
868
868
869
869
First, let's render a plain Flutter `ListView` with the name of each
870
870
product. The `Shop` widget below achieves this:
0 commit comments