CMS Builder 1.0
The tools you produce can be, and eventually are very useful. Just don't kill the buzz with products that have not been tested enough to prevent these kind of crash and burn "new product" releases. You guys are way better than that. And like I said...
really...consider asking for help from the WebAssist user community before offering a production release if you don't have the resources in-house to find these kind of problems.
NO ONE can afford to do testing on every possible platform...but if you had a beta testing team made up of (your client's Alpha Dog skilled developers) using their environments... everyone wins...faster, more robust, and better thought out products to market.
We all have different tolerance levels for software defects. The version "1.0" should be enough in itself to warn experienced developers that rough water is ahead.
I just think that when you market products to the general public, it is always best to put appropriate warnings on the box up front.
Also, you are right on target about the product writing to the wrong database. I finally found the database that CMS Builder 1.0 was writing to. It created new tables in one of my other [thank God] "Test" databases...without warning, without asking.
I consider any 3rd party developer application that chooses (through its own internal logic) to create new tables and records to a database that has not been explicitly selected by the developer...to be potentially VERY dangerous.
I'll suggest you should not try to "automate" the application's internal selection of databases beyond providing a list of databases that the developer must choose from...never program any application to go "Hal 9000" on us and choose databases that we have not signed-off on.
As that famous NASA contractor once said about the fatal flaws in the O-rings on the shuttle...He was being pressured to sign-off on flight worthiness before the shuttle launched and then exploded... He told the NASA pre-flight team that launching at temperatures that exceeded the O-ring's specifications... "would be a risky decision...'a step away from the good.'"
If you want CMS Builder to play nice with PowerCMS and CSS Site Builder...do the automated database survey...BUT then ASK THE DEVELOPER what databases to use in that instance. IF the developer is too confused to know which one...the process should politely inform the developer to come back when they have a clue about what is going on.
I think that you underestimate just how important this new product is to the retrofitting of the 1,000s of non-CMS websites...Hey man, it's almost like a Java "face lift" to COBAL...lol.
"Your going to be rich man! Your going to be rich.":)