Thanks. I’ve read back through a bunch of postings, and really appreciate your responsiveness! This is how I ran my own start up way back in the day (co-founded the world’s first self-service web hosting company, Web Communications, LLC, in May of 1994): do the little things quick, be open and engaged about the bigger ones.
Re: 1. Great, thank you.
Re: 2. Awesome!
Re: 3. Documentation:
Have you thought about somehow enabling contributions from the community? I’d be more than happy to systematically write documentation covering items not currently included, to the maximum extent possible, and flag typos and grammatical flaws.
Also, looking at the help site your link to, you’re taking on a huge job by mixing “documentation” that describes the function of a particular item, with detailed tutorials teaching people how to use it who need more than that.
When I click on “more information” in the ? tooltop for a UI item in the Designer Pallete, I see 15 items out of 25 documented. I’d love to have equivalent information, at least at this level, for all these items, without having to dig.
Re: 4. Yes, that’s why I labeled it as “unrealistic”, although, just possibly, the code might be already structured so that the components are just another representation derived from the XML, and to enable the methods used to manipulate blocks in the designer preview area to be repurposed to perform the same function in the component view.