<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Oli,<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>First off, thanks for all the suggestions and feedback — we love it. Keep it coming (this applies to everyone!). The sticking point of course is though ChimeraX does a lot of things that Chimera doesn’t, the converse is also true: Chimera does a lot of things that ChimeraX doesn’t, and we are working hard to close that gap. So working on suggestions from you and others has to be prioritized and slotted into that process. So some suggestions may get incorporated quickly while others “wait their turn” — it doesn’t mean we’ve forgotten them.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>As for this specific suggestion for simple programming-like language features, it could be the hardest one for us to do. It really it something much easier to integrate if it is part of your original design rather than a later addition. The command line parsing is already quite complex to allow non-core bundles to add commands and to add keywords to the open and save commands. There was no provision for multi-line command constructs. Though I could be overlooking some means of implementing this without a major overhaul of the command parsing — I am not the true expert on the parser (that would be Greg Couch).</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>I guess it might be possible to implement some kind of preprocessor that looks at the original input with it’s simple logic constructs, and executes it and generates a series of one-line commands that would be executed by the “real” command processor. Would it be a problem if these constructs were only available if you had opened a script file, rather than directly typing them?</div><div class=""><br class=""></div><div class="">—Eric</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Eric Pettersen</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>UCSF Computer Graphics Lab</div><div class=""><br class=""></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On May 7, 2017, at 12:46 PM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" class="">olibclarke@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi, <br class=""><br class="">Is there any possibility of adding simple scripting features to the ChimeraX command syntax in the future? Obviously more complex things will be done in a python script, but if/then/for/while statements would be very handy to add to the power of one liners and aliases on the command line - e.g. for each chain in molecule1, if chain is protein, fit to map, things like that?<br class=""><br class="">Cheers<br class="">Oli<br class="">_______________________________________________<br class="">ChimeraX-users mailing list<br class=""><a href="mailto:ChimeraX-users@cgl.ucsf.edu" class="">ChimeraX-users@cgl.ucsf.edu</a><br class="">Manage subscription:<br class="">http://www.rbvi.ucsf.edu/mailman/listinfo/chimerax-users<br class=""></div></div></blockquote></div><br class=""></div></body></html>