On Wed, Mar 6, 2013 at 12:38 AM, H. Hirzel <span dir="ltr"><<a href="mailto:hannes.hirzel@gmail.com" target="_blank">hannes.hirzel@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 3/5/13, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> It may be you can't use that browser without OB which requires<br>
> OCompletion. For a web-framework to require a fat-client UI framework<br>
> seems nutty to me. :)<br>
<br>
</div>Yes, we had discussed that a few years ago. Just loading OB to have a<br>
very small panel app is a bit too much.<br></blockquote><div><br>The metacello configuration was done by Dale based on the dependencies that the development team use to build complete development images and one-click images, all of which include the OB tools.<br>
<br>The OB tools—along with everything else non-essential—are purposely separated out into their own packages specifically so that they don't need to be loaded. My suggestion was always that the OB tools be loaded *if* you have Omnibrowser, but as far as I know Metacello still doesn't support that kind of rule.<br>
<br>There's no reason we can't ensure that Metacello makes it easy to load subsets that people want—someone just has to do it.<br><br>Julian<br></div></div>