<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2018-08-25 05:29 PM, Scott McKay
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:79109FC2-55FF-4031-B82B-D82B51B388EE@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>+1</div>
<div><br>
</div>
<div>I think we did OK in CLIM: an API package, and an internal
package to implement in. <br>
<br>
<div>--Scott </div>
</div>
<div><br>
On Aug 25, 2018, at 7:53 PM, Ken Tilton <<a
href="mailto:kentilton@gmail.com" moz-do-not-send="true">kentilton@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_default" style="font-size:large">Packages
are massively overrated. [...]<br>
</div>
</div>
</div>
</blockquote>
</blockquote>
<br>
Scott, <br>
<br>
Are you referring to the earlier CLIM from CMU [1] or McCLIM [2] or
another specific implementation? My understanding is that "CLIM"
today usually implies the spec, but I've yet to use any of these
packages.<br>
<br>
What did you or others appreciate most about its package
organization?<br>
<br>
McCLIM seems to separate API from internals and uses various systems
named `mcclim/foo` and packages named `mcclim-foo` invoked by those
systems. This is just from glancing at various *.asd files and
package.lisp.<br>
<br>
The older CMU version seems to be more fine-grained by separating
platform-specific bits under `impl_dep` subdirectory.<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/gui/clim/0.html">http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/gui/clim/0.html</a><br>
[2] <a class="moz-txt-link-freetext" href="https://github.com/McCLIM/McCLIM">https://github.com/McCLIM/McCLIM</a><br>
<br>
Thanks,<br>
-Daniel<br>
</body>
</html>