Schalk: Tell us a little bit about yourself, your background and what you are currently doing.
Robert: I work mainly as an Interface Developer/Architect, doing consultancy work. Started out with HTML coding in 1998, and while I have dabbled with both design and some heavier System Development, coding web interfaces has always been my big interest. At the moment, I work in two projects: development work for an e-commerce web site and doing auditing and mentoring for Interface Developers at another company.
Schalk: What gave you the inspiration to create DOMAssistant?
Schalk: How does DOMAssistant help developers?
Schalk: What other similar solutions are there and why should we choose DOMAssistant?
Schalk: Although initially created by yourself I see some developers have joined the project. What has led to this decision?
Robert: Work load, and getting other perspectives, I'd say. Some of the people in the team are testing or doing evangelizing, while others contribute with great code that complements my ideas and visions. It helps me to avoid coding errors or missing some specific scenario, hence leading to better and more efficient and stable releases.
Schalk: With the recent release of version 2.7 of DOMAssistant please give us some insider info with regards to your focus for the next release.
Robert: Currently, we're just doing minor tweaking to existing functions, to make the code even smaller and maintainable. Our next step is rather working more on useful plugins and spreading the word, than adding features to the core code.
Schalk: How can the community and users out there get involved with the evolution of DOMAssistant?
Schalk: Anything you want to leave us with?
Robert: Make sure you cooperate with the other skill sets around you. Develop code which is both accessible and cross browser/cross platform, since we have had enough of lock-ins throughout the years. And, naturally, I wish for you to try out DOMAssistant if you haven't already. :-)