Dear Andrew,<div><br></div><div>despite being a not-yet-user of CQP, your plans rang a bell somewhere.</div><div>(a) it may be a good idea to introduce templating (e.g. Smarty for PHP) to allow more</div><div> substantial modifications to the interface. I have seen a number of web sites</div>
<div> that embed CQP (and, I think, CQPweb) within their own designed site to allow</div><div> access to their corpora, and separating design from functionality would make it</div><div> easier for them to use the latest version while still keeping the old UI</div>
<div>(b) Considering that CQPweb already uses a MySQL database, I'd consider session</div><div> cookies to be an easier alternative than .htaccess/htpasswd files.</div><div> (At least for me, popup blocking eliminated the need to turn Javascript off on</div>
<div> unknown sites; and sometime in the last 10 years I've grown indifferent towards</div><div> cookies too. I suspect that other people are similar in that regard).</div><div>(c) I've been developing a moderately complex web application (an annotation tool,</div>
<div> also using Chrome) and met different (usually small) things that behaved or</div><div> looked different in Firefox or IE. Using a library such as JQuery (or Dojo, or ...) solves many of</div><div> the cross-browser compatibility problems, but not all of them (i.e., especially not</div>
<div> those that depend on your own CSS or low-level Javascript code).</div><div><br></div><div>Best,</div><div>Yannick</div>