<html><body bgcolor="#FFFFFF"><div>That smells of pragmatism:) You're quite right. <br><br>On Sep 2, 2010, at 12:51 PM, Chris Cunnington <<a href="mailto:smalltalktelevision@gmail.com">smalltalktelevision@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>"<span class="Apple-style-span" style="font-family: monospace; font-size: 12px; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Namespaces may be in line with the theme of "small, modular." I don't think OmniBrowser fits that theme."</span><div>
<span class="Apple-style-span" style="font-family: monospace; font-size: 12px; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><br></span></div><div><span class="Apple-style-span" style="font-family: monospace; font-size: 12px; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Actually, I think your absolutely right on this. We do want to have that option. But as a method of approach, I think that direction is premature. This is received, alien technology. It's better to learn to use it the way it was built, and then maybe shear the OmniBrowser from it later. So, I'd say our first step is to make it work as intended. </span></div>
<div><span class="Apple-style-span" style="font-family: monospace; font-size: 12px; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><br></span></div><div><span class="Apple-style-span" style="font-family: monospace; font-size: 12px; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Chris </span></div>
</div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></body></html>