<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Colin,<div><br></div><div><font class="Apple-style-span" color="#000000" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">Thanks for releasing a new version of OmniBrowser. I just played with it a little in the Squeak3.10.2-trunk. It looks great with the icons and the refactoring commands. I especially like the fact, that the buttons height does not change when you resize the browser. ;-)</span></font></div><div><br></div><div>One thing I don't like at all, though: the fact that some Monticello packages are dirty after I install the .sar. With the new development process I got used to the fact that only the packages I work on are dirty. As an old ENVY user dirty packages make me very nervous. ;-)</div><div><br></div><div>However, I <font class="Apple-style-span" color="#000000" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">loaded OB-ExtDeps and OB-Umbrella from source.wiresong.ca/ob as you have explained on the OmniBrowser Development group. That seemed to have worked. Do I have all the code from the release now?</span></font></div><div><br></div><div><span class="Apple-style-span" style="font-size: 12px; ">At first I had tried only loading OB-Umbrella which did not work. </span>Wouldn't it be the best - as in least confusing - way to just load a package named OmniBrowser from the repository source.wiresong.ca/ob?</div><div><br></div><div>Cheers,</div><div>Bernhard</div><div><br><div><div>Am 02.09.2009 um 09:33 schrieb Colin Putney:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi all,<br><br>I'm happy to announce a new release of OmniBrowser. It's been quite a while since the last official release, and that has force folks that want to run the current code base to download and install directly from the Monticello repositories used for development. There have been a lot of contributors, each pulling in different directions, and it's been difficult for the various Squeak distributions that use OmniBrowser to put together a coherent installation. I think moving to more formal release practices, with explicit version numbers, supported platforms, release testing and so on will make it a lot easier to install and use OmniBrowser without having to understand the ins and outs of the code base and development community.<br><br>In putting together this release, I wanted to tighten up and repackage the existing functionality–b=new features can wait until 2.1. I've tried to find the best mix of framework flexibility, browser features, code quality and performance that I could. This has meant cutting some features, and probably will mean further simplification and streamlining in subsequent releases. It'll also mean pulling OmniBrowser "extensions" into the standard distribution as the become stable.<br><br>This is the third release in the 2.0 series; the first two releases were "private" releases announced only on the omnibrowser-dev list, to gain feedback and flush out issues with the distribution format.<br><br>Download it from: <a href="http://www.wiresong.ca/static/releases/OmniBrowser-2.0.3.zip">http://www.wiresong.ca/static/releases/OmniBrowser-2.0.3.zip</a><br><br>Colin<br></div></blockquote></div><br></div></body></html>