Sashipa-Melba

<body bgcolor=#FFE8B4> <p> <a class="link" href="home.htm">Home</a><br> <a class="link" href="presentation.htm">Presentation</a><br> <a class="link" href="installation.htm">Installations</a><br> <a class="link" href="sashipa_tutorial.htm">Tutorial</a><br> <a class="link" href="download.php">Downloads</a><br> <a class="link" href="demo_applet.php">Demo Applet<br>(600 Ko)</a><br> <a class="link" href="compatibility.htm">Compatibilities</a><br> </p> <p> <a class="link" HREF="mailto:thomas.mur@sashipamelba.com">Technical contact</a><br> <a class="link" HREF="mailto:line.lauret@sashipamelba.com">Webmaster</a><br> </p> <p> In brief, </p><p> Interfaces built on this technology are based on the <b>same presentation logic</b>. So final users quickly learn to use a new application or a new fonctionality. </p><p> Applications are built <b>without programming</b>. So there is no bug. More exactly, they contains only the Melba library bugs. And Melba is quite fiable, because it used by a lot of applications. </p><p> Applications are <b>build very quickly</b>: no programming / debugguage, just a fiew tests are required. You have just to write an XML file. </p><p> The <b>Architecture flexibility</b>: just change a word in your XML file, and your application become an <b>applet</b>. Or switch another word and your <b>client-database</b> architecture become <b>client-servlet-database</b>, with multi-users management... If you modify the name or the type of a column in your database, you have to do only one modification in your XML file. Idem if you <b>migrate on an other DBMS</b>, without SQL dialect problems ! It's even possible to access to your database through a PHP, as the demonstration applet on this Web site. </p><p> Applications are built-on Java technology, so they are <b>independent of the Operating System</b>. </p> </body>