Thread: Re: [cotvnc-devel] Chicken 2.0b2
Project superseded by http://chicken.sourceforge.net/
Brought to you by:
smeger
From: Sean K. <ka...@ge...> - 2004-08-31 06:45:14
|
[In a message on Thu, 26 Aug 2004 08:25:32 PDT, Jason Harris wrote:] >It's out! Get it while it's hot! Did you guys see the posting on macosxhints.com about changing the cursors? The followup post complained about problems with 1.3.6. . . Sean |
From: Sean K. <ka...@ge...> - 2004-08-31 17:27:51
|
[In a message on Tue, 31 Aug 2004 07:06:49 PDT, Jason Harris wrote:] >Nice! > >It seems our only "large" problems now are Tight encoding when >connecting to TightVNC server, a color issue with Solaris servers, and >an AppleScript incompatibility with You Software. > >Jason I'm thinkin' it might be a good idea to have a "known issues" file, both in the distribution, and the web site. Perhaps just the website, since we won't find issues when we ship (then again, we might). This would help a LOT, I think, to cut down on duplicate bugs, because a lot of people *don't* want to read the bug database to see if their issue is already been reported (it's often easier to submit a bug than search for one). On the other hand, if I go to a site for some software (everything from Toast to Mozilla), I'll check the "known issues" section of the release site *every time*. Sean |
From: Jason H. <sm...@ge...> - 2004-08-31 17:59:51
|
Prolly a good plan. There's a "known issues" section in the readme, but who reads the readme? If we ever get a website together, that'll be a part of it. Jason On Aug 31, 2004, at 10:27 AM, Sean Kamath wrote: > > [In a message on Tue, 31 Aug 2004 07:06:49 PDT, > Jason Harris wrote:] >> Nice! >> >> It seems our only "large" problems now are Tight encoding when >> connecting to TightVNC server, a color issue with Solaris servers, and >> an AppleScript incompatibility with You Software. >> >> Jason > > I'm thinkin' it might be a good idea to have a "known issues" file, > both in the distribution, and the web site. Perhaps just the website, > since we won't find issues when we ship (then again, we might). > > This would help a LOT, I think, to cut down on duplicate bugs, because > a lot of people *don't* want to read the bug database to see if their > issue is already been reported (it's often easier to submit a bug than > search for one). On the other hand, if I go to a site for some > software (everything from Toast to Mozilla), I'll check the "known > issues" section of the release site *every time*. > > > Sean > > |
From: Sean K. <ka...@ge...> - 2004-08-31 21:10:50
|
[In a message on Tue, 31 Aug 2004 10:59:33 PDT, Jason Harris wrote:] >Prolly a good plan. There's a "known issues" section in the readme, >but who reads the readme? You got a point there. :-) >If we ever get a website together, that'll be a part of it. OK, *that's* something I can do, even with a newborn (the sprog is due Sept 26, and I'll be home for three weeks, so I should have lotsa time). Granted, I usually run the machines that host the website (that's what geekoids.com is), I am fairly handy when it comes to PhotoShop and GoLive. Shall I work on a web site? If so, do you have input, or shall I just mock something up and ship you guys a URL (I won't link it live to the existing site). Oh, I forgot to mention, SourceForge has 100 MB free for projects. I just logged into the shell server and verified it, so we won't need a domain and all that jazz (unless you guys want to get one. I might be convinced to chip in the $14.95 it would cost from dotster for a year. (whom I'd stick with, since I have a couple billion domains registered with them already).). Also, there is the Documentation section of the Project web pages. . . Sean |
From: Jason H. <sm...@ge...> - 2004-08-31 23:26:40
|
Yeah, absolutely make a website! It's been on the to-do list for like two and a half years! I'd envision the following sections in no particular order: - Home: A brief description of what Chicken is, what VNC is, and a summary of the contents of the other sections of the site. - Great big shiny Download button: self explanatory. Download page might include CVS directions, or a link to the Developer page. - Documentation: The bundled documentation file with our email addresses stripped out of it (I hate spam). Needs a Tips & Tricks section. - Known Issues: ala Jared's recent suggestions - Developers: goes to the current SourceForge site. - Support: Links to the Bugs, RFE, Support and Forums in the sf.net site Sourceforge's webhosting seems totally sufficient to me - there's no way the above will fill a 100MB site. We've got PHP and mySQL (which we don't really need for this site), but that's totally sufficient. I've always been very careful to publish the address of the Chicken site as http://cotvnc.sf.net/, so all we need to do is replace my meta-refresh that's currently there and we're golden. I'd say to just put the site at http://cotvnc.sf.net/test/ or something like that. We'll all check it out and change whatever needs to be changed, and then move it to the root. I've mentioned this before, but from my other life as the dev of ShapeShifter, I've got all sorts of graphic design contacts, many-all of whom would like nothing more than to do the graphics for the website of some popular software. So if you need graphic work, just let me know. Jason On Aug 31, 2004, at 2:10 PM, Sean Kamath wrote: > > [In a message on Tue, 31 Aug 2004 10:59:33 PDT, > Jason Harris wrote:] >> Prolly a good plan. There's a "known issues" section in the readme, >> but who reads the readme? > > You got a point there. :-) > >> If we ever get a website together, that'll be a part of it. > > OK, *that's* something I can do, even with a newborn (the sprog is due > Sept 26, and I'll be home for three weeks, so I should have lotsa > time). > > Granted, I usually run the machines that host the website (that's what > geekoids.com is), I am fairly handy when it comes to PhotoShop and > GoLive. Shall I work on a web site? If so, do you have input, or > shall I just mock something up and ship you guys a URL (I won't link > it live to the existing site). > > Oh, I forgot to mention, SourceForge has 100 MB free for projects. I > just logged into the shell server and verified it, so we won't need a > domain and all that jazz (unless you guys want to get one. I might be > convinced to chip in the $14.95 it would cost from dotster for a > year. (whom I'd stick with, since I have a couple billion domains > registered with them already).). > > Also, there is the Documentation section of the Project web pages. . . > > Sean > > |
From: Jared M. <jmc...@df...> - 2004-09-01 02:56:44
|
>OK, *that's* something I can do, even with a newborn (the sprog is due >Sept 26, and I'll be home for three weeks, so I should have lotsa >time). Congrats. Your first? Jared |
From: Jason H. <sm...@ge...> - 2004-08-31 14:07:00
|
Nice! It seems our only "large" problems now are Tight encoding when connecting to TightVNC server, a color issue with Solaris servers, and an AppleScript incompatibility with You Software. Jason On Aug 30, 2004, at 11:45 PM, Sean Kamath wrote: > > [In a message on Thu, 26 Aug 2004 08:25:32 PDT, > Jason Harris wrote:] >> It's out! Get it while it's hot! > > Did you guys see the posting on macosxhints.com about changing the > cursors? The followup post complained about problems with 1.3.6. . . > > > Sean > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > cotvnc-devel mailing list > cot...@li... > https://lists.sourceforge.net/lists/listinfo/cotvnc-devel > > |