<!doctype html public "-//W3C//DTD W3 HTML//EN">
<head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [slimp3-dev] 2.1 is only a few bugs
away...</title></head><body>
<blockquote type="cite" cite>I posted the new manual on the web site
just a few minutes ago. For the<br>
first time in the history of an OSS project, the docs are ahead of
the</blockquote>
<blockquote type="cite" cite>release. :)</blockquote>
<div><br></div>
<div>We should make slashdot for this if nothing else.</div>
<div><br></div>
<blockquote type="cite" cite><br>
I'll pound on the server this afternoon.</blockquote>
<div><br></div>
<div>Great.<br>
</div>
<blockquote type="cite" cite>We seem to be catching the attention of
the MacOSX community now. Sorry<br>
to pester, but what's the word on the Aqua interface? I still have
an<br>
ancient beta of OSX on my machine, but I'm going to get up to speed
here<br>
so I can help with the startup/install scripts if
necessary.</blockquote>
<div><br></div>
<div>Ok, I'll stop fixing bugs and concentrate on the OSX shell.</div>
<div><br></div>
<div>No need to do startup/install scripts. It will all be in a
single application package containing the shell application and all
the perl scripts. Double-click on the app and it launches.
Drag it to your login items in preferences and it will start up when
you do.</div>
<div><br></div>
<div>I might need a bit of help with the build process (I haven't
looked at what you've done so far), but my intent is to check in both
source and intermediate object so that anybody can build the OSX
version by running the existing build script. If the OSX source
changes, the person who changes it will need to make sure to check in
the changes.</div>
<div><br></div>
<div>My first Aqua application, so it may be a bit rocky to start, but
I'll get it.</div>
<div><br></div>
<div>-dean</div>
<div><br></div>
</body>
</html>