Correct, The language behind the look and feel does not matter. It is only the look and feel that has to be webbased. The reason for this is that many different applications are used who are all using their own different codes but are used in one workflow by one operator : Some use Perl, some use Java, some use Tcl/Tk, some use some other application owned languages, etc.... but the common wraparound (GUI) for those applications should be a webbased look and feel so that the operator is guided through the different applications in the same look and feel. In that way the different applications are wrapped around one GUI which makes the use easy. Today were soo many applications can be used to achieve target automation is an important factor but besided from automation ease of use is the next important factor and the only way this can be achieved when using different applications is try to wrap them around one GUI that guides the users through the different steps, through the different applications.