Concept, Design, Coding
By the time I completed the design of the Qubed Peas Patch Viewer it was clear that I needed to stick to some traditional patterns common to development concepts. It simply made no sense to walk away from tried-and-true mental patterns that developers would have very firmly established.
The tree control was the main one of those concepts. I was going to need a way to present information in a truly hierarchical way, and folders have served us all very well over the years.
To do this I was going to need a Folder Tree component to do the work. It would need to support many of the common tree patterns:
A lot goes into building a Tree. I looked around and thought about using some of the great plugins that exist out there already. Indeed many may have more features than I would ever write into my own. But that is really the problem. And that is against the Qubed Peas concept that writing it and owning it is never as hard as it seems; but infinitely more valuable.
So I set out to create a tree that would be easy to use, but also include all of the deep requirements of advanced tree components. PTree hit the mark.
As with any other Qubed Peas component usage couldn’t be easier. Notice the live component on this page. It only took 1 line of HTML to get the whole component in there. And it’s not even hosted on this domain.