# Treeview GLPI plugin

[![License](https://img.shields.io/github/license/pluginsGLPI/treeview.svg?&label=License)](https://github.com/pluginsGLPI/treeview/blob/develop/LICENSE)
[![Follow twitter](https://img.shields.io/twitter/follow/Teclib.svg?style=social&label=Twitter&style=flat-square)](https://twitter.com/teclib)
[![Telegram Group](https://img.shields.io/badge/Telegram-Group-blue.svg)](https://t.me/glpien)
[![Project Status: Active](http://www.repostatus.org/badges/latest/active.svg)](http://www.repostatus.org/#active)
[![GitHub release](https://img.shields.io/github/release/pluginsGLPI/treeview.svg)](https://github.com/pluginsGLPI/treeview/releases)
[![GitHub build](https://travis-ci.org/pluginsGLPI/treeview.svg?)](https://travis-ci.org/pluginsGLPI/treeview/)

![3.-Screenshot](./treeview.gif "Treeview")


This plugin allows you to browse through your inventory via a tree view in a panel located on the left side of the screen. 

You can browse the tree of your site to see the equipment.


## Documentation

We maintain a detailed documentation here -> [Documentation](https://glpi-plugins.readthedocs.io/en/latest/treeview/index.html)

## Contact

For notices about major changes and general discussion of treeview, subscribe to the [/r/glpi](https://www.reddit.com/r/glpi/) subreddit.
You can also chat with us via [@glpi on Telegram](https://t.me/glpien).

## Professional Services

![GLPI Network](./glpi_network.png "GLPI network")

The GLPI Network services are available through our [Partner's Network](http://www.teclib-edition.com/en/partners/). We provide special training, bug fixes with editor subscription, contributions for new features, and more.

Obtain a personalized service experience, associated with benefits and opportunities.

## Contributing

* Open a ticket for each bug/feature so it can be discussed
* Follow [development guidelines](http://glpi-developer-documentation.readthedocs.io/en/latest/plugins/index.html)
* Refer to [GitFlow](http://git-flow.readthedocs.io/) process for branching
* Work on a new branch on your own fork
* Open a PR that will be reviewed by a developer

## Copying

* **Code**: you can redistribute it and/or modify