# Feature XEO-1 - Classes tab should have one aggregated tree, instead of a tree for each model

Project: Xeokit
Status: specified
URL: https://community.openproject.org/work_packages/XEO-1

## Planning

| Attribute | Value |
| --- | --- |
| Date | 2020-01-23 –  |
| Priority | Medium |
| Target versions | Wish List |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Lindsay Kay |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

After loading multiple models, the Classes tree shows classes partitioned into two trees, one for each model. There should be one tree, which is the aggregate of the classes of all the models in the scene. Or, would it be good UX to have separate trees for the models? user\#48453 maybe take a look and see if separate Classes trees makes sense?