Re: problem about writeInBackgroundAndNotify
On 22 Aug 2009, at 04:35, Guo Xu wrote: Hi Richard Thank you very much for your answer. But I have tried it again at a different machine which also have Windows7 Build 7127 platform. All my computer have platform of Windows7, I don't test on any other environment. What about your environment? Ah, I didn't realise you were using windows. I guess there could quite easily be a problem with async sockets on windows. I haven't noticed it in other programs, but I don't use windows much, in fact I don't have a windows development environment at the moment. I'll try to find time to get a windows system set up, but in the meantime perhaps someone else who uses windows might be able to help. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] r28488 - /libs/gui/branches/testplant_1/
Hi, sorry if I'm not following protocol. These are my first direct commits. I entered a log message on each change, but I guess that doesn't automatically go to the ChangeLog. How should I go about entering information in the ChangeLog? As for the purpose of the branch: We need a known version that we have verified works for us, for our production builds. We would like to be using the tip of the trunk, in order to get recent fixes, but some of the recent commits have broken things for us. Until we have time to track those down and get them corrected, we need a place to add some of our own fixes based on a version that is stable for us. We will also try to build from the trunk when we have a chance during our development, and find, report, or fix any issues we run into. But we've found that the tip is too risky (understandably!) for deployment builds. Hopefully, our fixes can be merged into the trunk, and we can jump our branch ahead (or create new branches, I guess) to later points along the trunk periodically, when we are able to verify a version that works for us. -- Doug Simons Principal Developer TestPlant Inc T+1 720-890-0211 ext 13 4730 Walnut Street F+1 720-890-0209 Boulder, CO 80301 doug.sim...@testplant.com USA http://www.testplant.com This email and any attachments may contain privileged / confidential information. If you have received this email in error or believe that you are not the intended recipient, please delete all content and attached files and contact TestPlant via the switchboard on +1 720-890-0211 or via return e-mail. You should not copy, forward or use any part of the contents in any way. Any such unauthorised use or disclosure may be unlawful. On Aug 21, 2009, at 8:43 AM, Riccardo Mottola wrote: Fred Kiefer wrote: Gregory Casamento schrieb: Author: gcasa Date: Thu Aug 20 00:25:33 2009 New Revision: 28488 URL: http://svn.gna.org/viewcvs/gnustep?rev=28488&view=rev Log: Add new branch with corrected revision number. Added: libs/gui/branches/testplant_1/ - copied from r28233, libs/gui/trunk/ Hi Greg, could you please explain the purpose of this new branch? I can see that Doug and Jonathan have started using it. Most of the changes they made up to now are perfectly legitimate for trunk (Apart from those already in trunk and that GSContext change. I am unsure about the NSOpenPanel patch) Who will be porting these changes back to trunk? Currently the commits on the branch are without Change log entries, how are we going to add these? I think I can agree with Fred here, keeping the ChangeLog would make things much easier in the futuere event of a merge. Riccardo ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] r28488 - /libs/gui/branches/testplant_1/
On 21 Aug 2009, at 18:01, Doug Simons wrote: Hi, sorry if I'm not following protocol. These are my first direct commits. I entered a log message on each change, but I guess that doesn't automatically go to the ChangeLog. How should I go about entering information in the ChangeLog? If people really care about duplicating the commit messages in the ChangeLog[1] then perhaps they could write a pre-commit hook that simple prepends the output of svn log to the ChangeLog. David [1] Compare and contrast: Commit messages: http://cia.vc/stats/project/gnustep ChangeLog: http://svn.gna.org/viewcvs/gnustep/libs/base/trunk/ChangeLog?rev=28504&view=auto ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: problem about writeInBackgroundAndNotify
Hi, Richard Frith-Macdonald wrote: On 22 Aug 2009, at 04:35, Guo Xu wrote: Hi Richard Thank you very much for your answer. But I have tried it again at a different machine which also have Windows7 Build 7127 platform. All my computer have platform of Windows7, I don't test on any other environment. What about your environment? Ah, I didn't realise you were using windows. I guess there could quite easily be a problem with async sockets on windows. I haven't noticed it in other programs, but I don't use windows much, in fact I don't have a windows development environment at the moment. I'll try to find time to get a windows system set up, but in the meantime perhaps someone else who uses windows might be able to help. First I tested on linux and it works. Then I did a test on Windowx XP and I get the following behaviour: 1. I start the webserver (I am admin, on linux you need to be root, since it opens port 80) 2. I retrieve a page from it 3. windows firewall notices the port access, I unlock it 4. on the standard output of the gnustep console, I see the response, but the connecting client doesn't get any data back until it timeouts. 5. the only error I see comes form an NSLog and says "Unable to set blocking mode - Invalid argument" [*] Riccardo [*] I find it interestng that it goes onto the stdout. Usually error messages are routed to the windows event console ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: problem about writeInBackgroundAndNotify
The behavior you described is exactly the same as me.I also tested it on Windows server2003, It seems all of the Windows platform have the same problem. 2009/8/23 Riccardo Mottola > Hi, > > > Richard Frith-Macdonald wrote: > >> >> On 22 Aug 2009, at 04:35, Guo Xu wrote: >> >> Hi Richard >>> Thank you very much for your answer. >>> But I have tried it again at a different machine which also have >>> Windows7 Build 7127 platform. All my computer have platform of Windows7, I >>> don't test on any other environment. What about your environment? >>> >> >> Ah, I didn't realise you were using windows. I guess there could quite >> easily be a problem with async sockets on windows. I haven't noticed it in >> other programs, but I don't use windows much, in fact I don't have a windows >> development environment at the moment. I'll try to find time to get a >> windows system set up, but in the meantime perhaps someone else who uses >> windows might be able to help. >> >> First I tested on linux and it works. > > Then I did a test on Windowx XP and I get the following behaviour: > > 1. I start the webserver (I am admin, on linux you need to be root, since > it opens port 80) > 2. I retrieve a page from it > 3. windows firewall notices the port access, I unlock it > 4. on the standard output of the gnustep console, I see the response, but > the connecting client doesn't get any data back until it timeouts. > 5. the only error I see comes form an NSLog and says "Unable to set > blocking mode - Invalid argument" [*] > > > > Riccardo > > > [*] I find it interestng that it goes onto the stdout. Usually error > messages are routed to the windows event console > > > ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
NSSound Commit
I just committed the new NSSound implementation. Keep in mind it's very rough at this point. A few things, off the top of my head: * Need to check for libsndfile and libao, and only build SndfileSource and AudioOutputSink if they exist; * There's a hack in Sounds/GNUmakefile or else I could not get this thing to build; * Incorporate David C.'s suggestions. This thing needs lots of testing. I'll post my test app tomorrow (I'm pretty tired now) so you all can try it, too. Stefan ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSSound Commit
Hey Stefan, I saw the commit. Checking it out now. :) Thanks, GC On Sat, Aug 22, 2009 at 11:37 PM, Stef Bidi wrote: > I just committed the new NSSound implementation. Keep in mind it's very > rough at this point. A few things, off the top of my head: > > * Need to check for libsndfile and libao, and only build SndfileSource and > AudioOutputSink if they exist; > * There's a hack in Sounds/GNUmakefile or else I could not get this thing to > build; > * Incorporate David C.'s suggestions. > > This thing needs lots of testing. I'll post my test app tomorrow (I'm > pretty tired now) so you all can try it, too. > > Stefan > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > http://lists.gnu.org/mailman/listinfo/gnustep-dev > > -- Gregory Casamento Open Logic Corporation, Principal Consultant ## GNUstep Chief Maintainer yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell), (301)362-9640 (Home) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSSound Commit
Stefan, I just tested it with the standard sounds I made from within Gorm (It's had a sound inspector for a while) and it's excellent! Great stuff. :) Thanks, Gregory On Sat, Aug 22, 2009 at 11:50 PM, Gregory Casamento wrote: > Hey Stefan, > > I saw the commit. Checking it out now. :) > > Thanks, GC > > On Sat, Aug 22, 2009 at 11:37 PM, Stef Bidi wrote: >> I just committed the new NSSound implementation. Keep in mind it's very >> rough at this point. A few things, off the top of my head: >> >> * Need to check for libsndfile and libao, and only build SndfileSource and >> AudioOutputSink if they exist; >> * There's a hack in Sounds/GNUmakefile or else I could not get this thing to >> build; >> * Incorporate David C.'s suggestions. >> >> This thing needs lots of testing. I'll post my test app tomorrow (I'm >> pretty tired now) so you all can try it, too. >> >> Stefan >> >> ___ >> Gnustep-dev mailing list >> Gnustep-dev@gnu.org >> http://lists.gnu.org/mailman/listinfo/gnustep-dev >> >> > > > > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > ## GNUstep Chief Maintainer > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell), (301)362-9640 (Home) > -- Gregory Casamento Open Logic Corporation, Principal Consultant ## GNUstep Chief Maintainer yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell), (301)362-9640 (Home) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSSound Commit
I should, perhaps, rephrase. I made the sounds on the Mac, I played them from within Gorm. On Sun, Aug 23, 2009 at 12:04 AM, Gregory Casamento wrote: > Stefan, > > I just tested it with the standard sounds I made from within Gorm > (It's had a sound inspector for a while) and it's excellent! > > Great stuff. :) > > Thanks, Gregory > > On Sat, Aug 22, 2009 at 11:50 PM, Gregory > Casamento wrote: >> Hey Stefan, >> >> I saw the commit. Checking it out now. :) >> >> Thanks, GC >> >> On Sat, Aug 22, 2009 at 11:37 PM, Stef Bidi wrote: >>> I just committed the new NSSound implementation. Keep in mind it's very >>> rough at this point. A few things, off the top of my head: >>> >>> * Need to check for libsndfile and libao, and only build SndfileSource and >>> AudioOutputSink if they exist; >>> * There's a hack in Sounds/GNUmakefile or else I could not get this thing to >>> build; >>> * Incorporate David C.'s suggestions. >>> >>> This thing needs lots of testing. I'll post my test app tomorrow (I'm >>> pretty tired now) so you all can try it, too. >>> >>> Stefan >>> >>> ___ >>> Gnustep-dev mailing list >>> Gnustep-dev@gnu.org >>> http://lists.gnu.org/mailman/listinfo/gnustep-dev >>> >>> >> >> >> >> -- >> Gregory Casamento >> Open Logic Corporation, Principal Consultant >> ## GNUstep Chief Maintainer >> yahoo/skype: greg_casamento, aol: gjcasa >> (240)274-9630 (Cell), (301)362-9640 (Home) >> > > > > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > ## GNUstep Chief Maintainer > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell), (301)362-9640 (Home) > -- Gregory Casamento Open Logic Corporation, Principal Consultant ## GNUstep Chief Maintainer yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell), (301)362-9640 (Home) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: problem about writeInBackgroundAndNotify
On 22 Aug 2009, at 23:23, Riccardo Mottola wrote: Hi, Richard Frith-Macdonald wrote: On 22 Aug 2009, at 04:35, Guo Xu wrote: Hi Richard Thank you very much for your answer. But I have tried it again at a different machine which also have Windows7 Build 7127 platform. All my computer have platform of Windows7, I don't test on any other environment. What about your environment? Ah, I didn't realise you were using windows. I guess there could quite easily be a problem with async sockets on windows. I haven't noticed it in other programs, but I don't use windows much, in fact I don't have a windows development environment at the moment. I'll try to find time to get a windows system set up, but in the meantime perhaps someone else who uses windows might be able to help. First I tested on linux and it works. Then I did a test on Windowx XP and I get the following behaviour: 1. I start the webserver (I am admin, on linux you need to be root, since it opens port 80) 2. I retrieve a page from it 3. windows firewall notices the port access, I unlock it 4. on the standard output of the gnustep console, I see the response, but the connecting client doesn't get any data back until it timeouts. Not sure what you mean by this ... do you mean that, after a timeout, the client receives the response? Or, do you mean that a timeout occurs and the client gives up without ever receiving a response? Either way, how long is the timeout? ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
