A Flutter package for a fully customisable tree view
Let's assume we want to show a tree view with this structure:
Desktop |-- documents | |-- Resume.docx | |-- Billing-Info.docx |-- MeetingReport.xls |-- MeetingReport.pdf |-- Demo.zip
In this example
Billing-Info.docxare Child widgets with
documentsas the Parent.
Demo.zipare Child widgets with
Desktopas a Parent widget.
TreeView would look like this
var treeView = TreeView( parentList: [ Parent( parent: Text('Desktop'), childList: ChildList( children: <Widget>[ Parent( parent: Text('documents'), childList: ChildList( children: <Widget>[ Text('Resume.docx'), Text('Billing-Info.docx'), ], ), ), Text('MeetingReport.xls'), Text('MeetingReport.pdf'), Text('Demo.zip'), ], ), ), ], );
<a href="https://imgur.com/d4n4p1b"><img src="https://i.imgur.com/d4n4p1b.gif" title="source: imgur.com" /></a>
A new Flutter project.
This project is a starting point for a Flutter application.
A few resources to get you started if this is your first Flutter project:
For help getting started with Flutter, view our online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.
Add this to your package's pubspec.yaml file:
dependencies: tree_view: ^0.0.5
You can install packages from the command line:
$ flutter packages get
Alternatively, your editor might support
flutter packages get.
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|0.0.5||Jan 14, 2019|
|0.0.3||Jan 14, 2019|
|0.0.2||Jan 14, 2019|
|0.0.1||Jan 14, 2019|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Jan 15, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter
References Flutter, and has no conflicting libraries.
Package is pre-v0.1 release. (-10 points)
While there is nothing inherently wrong with versions of
0.0.*, it usually means that the author is still experimenting with the general direction of the API.