On Thu, Oct 6, 2011 at 1:38 PM, Charles Strahan <charles.c.stra...@gmail.com > wrote:
> The biggest reason why CoApp doesn't have that right now is because there >> have been almost as many unexpected barriers as there have been days of work >> on the project. > > > Which reminds me of the symlink issue on Windows (it requires elevated > user privileges, necessitating the use of an intermediate service). And the > beautifully designed *sn.exe*... > > Seriously, Microsoft? Just *had* to go make everyone's life harder with > seemingly arbitrary, bizarre design choices. > > Major kudos to all the contributors - I can only imagine how monumental > this effort must be. > > -Charles > > On Thu, Oct 6, 2011 at 12:55 PM, Tim Rogers <tiro...@microsoft.com> wrote: > >> I can understand that, Olaf. If you can hold out for another week or so >> we should have everything on the dev side (I think) and much of the >> client-side working well enough that common use will be practical. The >> biggest reason why CoApp doesn't have that right now is because there have >> been almost as many unexpected barriers as there have been days of work on >> the project. Add to that that one of my first acts upon joining the project >> was to punch holes into the then existing project structure and we end up a >> little behind original schedule, but with a much more robust system upon >> completion. >> >> I promise it's coming, and if you want to help by pushing code updates >> that would be appreciated. Otherwise, I'm afraid that everyone will just >> need to be patient a little bit longer. Seriously, it should be usable >> soon. >> >> -Tim >> >> -----Original Message----- >> From: Olaf van der Spek [mailto:olafvds...@gmail.com] >> Sent: Thursday, October 06, 2011 10:43 AM >> To: Tim Rogers >> Cc: coapp-developers@lists.launchpad.net >> Subject: Re: [Coapp-developers] First useful pkgs? (libz, libpng) >> >> On Thu, Oct 6, 2011 at 7:13 PM, Tim Rogers <tiro...@microsoft.com> wrote: >> > By the same token, releasing early makes the assumption that >> > significant portions of the software in question are believed to >> > operate correctly unless stated otherwise. We could absolutely >> > release CoApp “early” in its present state, but I would only wish to >> > do so with a disclaimer that we do not believe the software to be >> functioning properly at this time. >> > >> > >> > >> > I, at least, am not willing to promise that it won’t light your >> > computer on fire if you try using it right now. I don’t think it >> > will, but I really can’t make that promise. Nor can I promise that it >> > will do anything that it is supposed to until we have had a chance to >> seriously look it over first. >> > >> > >> > >> > With all of this in mind, if you would like to build it yourself and >> > try using the tools to construct packages and install them, I’d be >> > happy to get input from test systems outside my control. Just don’t >> > blame us if the system becomes unstable. >> >> I understand you can't release something like a RC or even a beta. >> However, 1.5 years into the project, I had expected some things to be >> available. Like a tool to build a (native) Hello world lib to produce .lib >> and .dll files (not even a pkg). To some, that's already very useful >> functionality and it'd allow other developers to start playing with, and >> possibly contributing to, the coapp project. >> >> Olaf >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~coapp-developers >> Post to : coapp-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~coapp-developers >> More help : https://help.launchpad.net/ListHelp >> > >
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
