To go along with the new Firebase support added in #48 and #49 we should support loading cTrees from Firebase instead of hard coding them. We should continue to support the hard coded cTrees for test configurations, but when using Firebase we should only see Firebase backed cTrees.
As part of this, we'll need the ability to create new cTrees. Probably the easiest way to do this is to leverage the search box, and when someone types a search term there should be a button at the end of the list results for creating a new cTree, named with by the search query. This would NOT be visible if an exact match was found (cTree with the same name).
New cTrees would have the element types and any other required cTree data pushed into Firebase with default values for now.
To go along with the new Firebase support added in #48 and #49 we should support loading cTrees from Firebase instead of hard coding them. We should continue to support the hard coded cTrees for test configurations, but when using Firebase we should only see Firebase backed cTrees.
As part of this, we'll need the ability to create new cTrees. Probably the easiest way to do this is to leverage the search box, and when someone types a search term there should be a button at the end of the list results for creating a new cTree, named with by the search query. This would NOT be visible if an exact match was found (cTree with the same name).
New cTrees would have the element types and any other required cTree data pushed into Firebase with default values for now.