<div dir="ltr">Hi Daniel;<div><br></div><div>Thank you for the detailed feedback.</div><div><ul><li>Re: synching on each tab switch & resultant unresponsiveness - I implemented a caching scheme for both client info and dist info. Hope this makes the program perkier.</li><li>Re: the dependency graph - FYI is it a dependency graph of the known-to-ASDF systems (often updated after installing a quicklisp release/system). I suppose one could argue that it is out of place here. Please let me know what you think.</li><li>Re: the dependency graph - I also suppose one could argue that perhaps I should have instead/additionally drawn a dependency diagram of the selected quicklisp system. I only go so far as to textually indicate which quicklisp systems are provided by the selected quicklisp release, and textually indicate which quicklisp systems depend upon the selected quicklisp system.</li><li>Re: single-box t - what is the best idiomatic way/place to do this? </li></ul><div>I also have tried to increase responsiveness by making use of incremental redisplay, but the logic is more complex (well, for somebody who is new to the presentation system), and I hope I have not introduced bugs.</div></div><div><br></div><div>Thanks again!</div><div><br></div><div>-jm</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Nov 5, 2017 at 4:22 AM, Daniel Kochmański <span dir="ltr"><<a href="mailto:daniel@turtleware.eu" target="_blank">daniel@turtleware.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hey,</p>
<p>cool application. My two cents:</p>
<p>- I don't like that it synchronizes over http on each tab switch
(even if I go back to already visited tab) - some cache maybe?<br>
</p>
<p>- Fetching makes window unresponsive for a sec or two, maybe it
is worth to consider fetching in background, so user can change
his mind and switch to another tab</p>
<p>- I like dependency graph, I'd add some margin though</p>
<p>- For presentations :single-box t, so you have only one box for
selection when you hover with mouse</p>
<p>- Having two layouts - one with inspector and the second without
it would be nice</p>
<p>- Looking at ASD definition - mcclim-truetype is enabled by
default now anyway (it is commented)</p>
<p>- Add dependency on #:mcclim-layouts/tab since you use it</p>
<p>That is what comes to my head. I like the idea and general
organization of panes. Congrats :)<br>
</p>
<p>Best regards,</p>
<p>Daniel<br>
</p><div><div class="h5">
<br>
<div class="m_-5151112497410203149moz-cite-prefix">On 04.11.2017 21:46, John Morrison
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi All;</div>
<div><br>
</div>
<div><a href="https://bitbucket.org/symbolicsimulation/com.symsim.oss.ql-gui" target="_blank">https://bitbucket.org/<wbr>symbolicsimulation/com.symsim.<wbr>oss.ql-gui</a><br>
</div>
<div><br>
</div>
<div>Interested in (roughly decreasing order of importance to
me):</div>
<div>
<ul>
<li>usability/usefulness</li>
<li>aesthetics (I am not a front end guy in any language)</li>
<li>compatibility with CLIM best practices and idioms (as
this is my first CLIM program in decades, or should I say
Dynamic Windows?)</li>
<li>compatibility with CL best practices and idioms (as this
is my first real Common Lisp program after decades of
C/C++, or should I say Zetalisp?)</li>
</ul>
<div>Please be kind, and thanks for all your contributions to
McCLIM!</div>
</div>
<div><br>
</div>
<div>-jm</div>
<div><br>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>