Re: [Amsn-devel] aMSN 0.96 RC1
Hi Tom First of all, good job for everything, taking care of everything and stuff. Especially for Growl, I tried during many hours to compile it in Universal and it seems that you did it, good job. Did you commit your work on aMSN Svn? You're talking about modifying the info.plist and I don't get it. I mean, if you put the normal PPC version of aMSN, it will open in Rosetta on Intel and in normal on PPC right? What's the thing about modifying the info.plist? Yeah before making aMSN run in Intel, ALL the .dylib stuff inside /utils/macosx should be in Universal. For QuickTimeTcl, can I ask you where did you take it? I'm pretty sure the version you have is wrong. Are you using the version coming from Mac OS X-Intel Macs? If yes, this is totally wrong because we use a feature for the webcam that is inside a new version of QuickTimeTcl (later than QuickTimeTcl3.1) and it's not the version packed with Mac OS X. You should write to Mats Bengtsson Email: [EMAIL PROTECTED] To know if he made any progress about compiling QuickTimeTcl on Intel Macs. Also, I went in Cupertino 3 weeks ago to met Jim Ingham (yes, on Apple Campus!). This guy is working during his spare time on Tcl-Tk Aqua and we talked about the TCL-TK project a little bit. This is the guy I will try to contact when I will come back to try to fix this Intel Mac problem with aMSN. For sndplay, can you look around to see if aMSN still use it? I think we only use it for loop alarms in the file alarm.tcl. Not even sure tho. It's a small software independant from aMSN so it's not a big deal if it's still in Rosetta because aMSN Wish Shell can launch anyway without that. tclCarbonHICommand.dylib - 100% tclCarbonNotification.dylib - 100% GOOD JOB. I was too lazy for that, nice to do that you figured it out. And the last thing is TkCximage.dylib and webcamsn.dylib... I just remember that a month ago I sent a file package to Xavier, my friend in Montreal, with all the stuff to try to compile aMSN on Intel Macs. He's in the CC:, may be he will be able to send you what you are asking for, I don't know. I can't make the release because I'm in San Francisco right now and I don't have my computer. So you can do it. Just don't forget to change the default skin from the amsn normal skin to the amsn for mac skin (like 0.95), it's very important. ALSO, don't forget the default skin needs a 'null' file in ALL folders if you want to avoid bugreports (or may be 0.96 doesn't u se it anymore I don't know but don't take a chance). Also, did you fix the problem with webcam crashing after 5min? Or the memory leak? We didn't have this problem in 0.95 so it must be fixed for 0.96, it's an HIGH priority that's why the mailling list is in CC, I specially ask for it. I think the best way to find the bug is go back in time in the old cvs version server (TELL ME WE STILL HAVE IT!!!) and find the amsn-commits log message for this day. It can take a long time (finding the exact time), but still, it's the best way to do. I'm coming back on the 23rd, celebrating the St-Jean(kinda 4th of july of the french people in Quebec), then I should be free to work on the Intel macs version. This is my highest priority, I don't even know what is coming in 0.96 anyway, i'm in California without my laptop and I don't have time to read the mailling list. So i'll see ya around On Tuesday, June 13, 2006, at 10:14AM, Tom Hennigan [EMAIL PROTECTED] wrote: Original Attached Jérôme Gagnon-Voyer eMail: [EMAIL PROTECTED] MSNMessenger: [EMAIL PROTECTED] iChat AIM: gagnonje5000 (à Mac.com) Skype: germinator5000 Heya Jérôme,aMSN 0.96 RC1 is apparently being released tomorrow!! :OWould you like to make the release? Or do you want me to package up aMSN and put up an announcement? I don't mind either way, it's entirely up to you!!Btw I have made a fair bit of progress with aMSN Universal (http://dhost.info/climbtothesky/amsn.php). The universal Wish Shell doesn't bounce in the dock thousands of times before the login window appears, but it still takes some time to load the login window. MacTel users say that it uses 30% less CPU, but they need to make aMSN run using Rossetta to get it to load atall (I think I have a workaround for this, but it hasn't been tested yet. If you add the key LSRequiresNativeExecution=/false to the info.plist file, it should open using Rosstta on i386 Macs, and will work normally on PPC macs).Although, I still haven't heard a response from Fred on the compile app so I'm not able to work on TkCximage, and webcamsn... Will you be able to mail me the file in the near future??See you round!Tom Tom Hennigan[EMAIL PROTECTED]http://www.justclimbit.co.uk/ ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] aMSN 0.96 RC1
Heya Jérôme,Just quickly:QuickTimeTcl3.1 - I took this from an Intel Mac, so I'm guessing it isn't the right one. I'll test it with webcam tonight though, to see if Apple took their version from CVS or 3.1. (I contacted the dev. He hasn't worked on it yet as he's still on 10.2.8, and so he can't compile universal, and he doesn't have access to an intel box).Growl - I don't have an SVN account, but I can put it on my account for someone else to commit if you'd like.tclCarbonHICommand tclCarbonNotification - These were easy :-)! But it's not "universal". The tcl source file chooses either darwin-ppc/ or darwin-x86/, but it will be transparent to the end user!On the webcam bug, yes I'm working on it. I'm extremely busy with exams atm. So I'm getting an hour or two a night at most to work on it... But still I'm doing my best!See you round,TomOn 13 Jun 2006, at 17:06, Jerome Gagnon-Voyer wrote:Hi TomFirst of all, good job for everything, taking care of everything and stuff. Especially for Growl, I tried during many hours to compile it in Universal and it seems that you did it, good job. Did you commit your work on aMSN Svn?You're talking about modifying the info.plist and I don't get it. I mean, if you put the normal PPC version of aMSN, it will open in Rosetta on Intel and in normal on PPC right? What's the thing about modifying the info.plist?Yeah before making aMSN run in Intel, ALL the .dylib stuff inside /utils/macosx should be in Universal. For QuickTimeTcl, can I ask you where did you take it? I'm pretty sure the version you have is wrong. Are you using the version coming from Mac OS X-Intel Macs? If yes, this is totally wrong because we use a feature for the webcam that is inside a new version of QuickTimeTcl (later than QuickTimeTcl3.1) and it's not the version packed with Mac OS X. You should write to Mats Bengtsson Email: [EMAIL PROTECTED]To know if he made any progress about compiling QuickTimeTcl on Intel Macs.Also, I went in Cupertino 3 weeks ago to met Jim Ingham (yes, on Apple Campus!). This guy is working during his spare time on Tcl-Tk Aqua and we talked about the TCL-TK project a little bit. This is the guy I will try to contact when I will come back to try to fix this Intel Mac problem with aMSN.For sndplay, can you look around to see if aMSN still use it? I think we only use it for loop alarms in the file alarm.tcl. Not even sure tho. It's a small software independant from aMSN so it's not a big deal if it's still in Rosetta because aMSN Wish Shell can launch anyway without that.tclCarbonHICommand.dylib - 100%tclCarbonNotification.dylib - 100%GOOD JOB. I was too lazy for that, nice to do that you figured it out.And the last thing is TkCximage.dylib and webcamsn.dylib... I just remember that a month ago I sent a file package to Xavier, my friend in Montreal, with all the stuff to try to compile aMSN on Intel Macs. He's in the CC:, may be he will be able to send you what you are asking for, I don't know.I can't make the release because I'm in San Francisco right now and I don't have my computer. So you can do it. Just don't forget to change the default skin from the amsn normal skin to the amsn for mac skin (like 0.95), it's very important. ALSO, don't forget the default skin needs a 'null' file in ALL folders if you want to avoid bugreports (or may be 0.96 doesn't u se it anymore I don't know but don't take a chance). Also, did you fix the problem with webcam crashing after 5min? Or the memory leak? We didn't have this problem in 0.95 so it must be fixed for 0.96, it's an HIGH priority that's why the mailling list is in CC, I specially ask for it. I think the best way to find the bug is go back in time in the old cvs version server (TELL ME WE STILL HAVE IT!!!) and find the amsn-commits log message for this day. It can take a long time (finding the exact time), but still, it's the best way to do.I'm coming back on the 23rd, celebrating the St-Jean(kinda 4th of july of the french people in Quebec), then I should be free to work on the Intel macs version. This is my highest priority, I don't even know what is coming in 0.96 anyway, i'm in California without my laptop and I don't have time to read the mailling list.So i'll see ya around On Tuesday, June 13, 2006, at 10:14AM, Tom Hennigan [EMAIL PROTECTED] wrote: Original Attached Jérôme Gagnon-VoyereMail: [EMAIL PROTECTED]MSNMessenger: [EMAIL PROTECTED]iChat AIM: gagnonje5000 (à Mac.com)Skype: germinator5000 Heya Jérôme,aMSN 0.96 RC1 is apparently being released tomorrow!! :OWould you like to make the release? Or do you want me to package up aMSN and put up an announcement? I don't mind either way, it's entirely up to you!!Btw I have made a fair bit of progress with aMSN Universal (http://dhost.info/climbtothesky/amsn.php). The universal Wish Shell doesn't bounce in the dock thousands of times before the login window appears, but it still takes some time to load the login window. MacTel users say that it uses 30% less CPU, but they need to
Re: [Amsn-devel] aMSN 0.96 RC1
Op dinsdag 13 juni 2006 18:06, schreef Jerome Gagnon-Voyer: Also, did you fix the problem with webcam crashing after 5min? Or the memory leak? We didn't have this problem in 0.95 so it must be fixed for 0.96, it's an HIGH priority that's why the mailling list is in CC, I specially ask for it. I think the best way to find the bug is go back in time in the old cvs version server (TELL ME WE STILL HAVE IT!!!) and find the amsn-commits log message for this day. It can take a long time (finding the exact time), but still, it's the best way to do. All history from cvs is now in svn. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] ML still working ?
I totally agree with you... Users have to use perfect softwares and not buggy drivers... Anyway, I try to know where is the bug... Why ? Because with that it's the first time I hack in the kernel level... And I like that ;) It's so bad I haven't a pwc compliant cam. Else, I already had tracked the bug and sent a patch to Luc Saillard... (Doesn't open source means bring your help to all the edifice ?) Phil P.S. Totally OT but should we apply the holly_wood patch about DPs in directories ? Le Monday 12 June 2006 22:54, Youness Alaoui a écrit : not only that, but we'd need to shift the responsability... we really should stop being so nice to the users, look at what happened lately in the forums because of AA fonts and tcl/tk 8.5... he was a stupid bastard but let's take his example why bother if the problem isn't ours ? If users complain, we just need to say it's a driver bug, not an amsn bug, don't bother us, EVEN if we know the solution to it. We had so much work to do because of pwc, I'm fed up with it now. If a user has Tcl/Tk 8.0 and has a bug, we won't say ohh, you need to modify this and this line, no, we'll just say upgrade, you can't, then it's your problem, it's a requirement, in the same way a program can require Windows XP to run instead of Windows 3.1 for example. Now, if we let Luc Saillard know about this issue, he might fix it and provide a new version.. so when people complain, instead of telling them to fuck off, we'll just say upgrade your driver... The thing is, what you said below is not true, you say we cannot assume all users will upgrade, oh yeah ? then it's their problem, it's their choice, not ours, they didn't want to upgrade, so it's not our fault... also, the users will know how to upgrade and will have root access... you know why ? because the bug is with v4l2 not with v4l, and the only pwc driver that supports v4l2 is Saillard's driver, which is unofficial and not shipped anywhere, so if a user has the problem it means he has Saillard's driver which means he installed it himself, which means he has root access and he knows how to install it. If I'm wrong, then again, it's not our problem. Do you agree with me ? KKRT ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] ML still working ?
On Tue, 13 Jun 2006 12:44:24 -0400, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: I totally agree with you... Users have to use perfect softwares and not buggy drivers... Anyway, I try to know where is the bug... Why ? Because with that it's the first time I hack in the kernel level... And I like that ;) It's so bad I haven't a pwc compliant cam. Else, I already had tracked the bug and sent a patch to Luc Saillard... (Doesn't open source means bring your help to all the edifice ?) Cool! congrats! :) Phil P.S. Totally OT but should we apply the holly_wood patch about DPs in directories ? I think so, yes, but only in /trunk, it should never go in the 0.96 branch. Please include this info in the commit log so we don't forget... Le Monday 12 June 2006 22:54, Youness Alaoui a écrit : not only that, but we'd need to shift the responsability... we really should stop being so nice to the users, look at what happened lately in the forums because of AA fonts and tcl/tk 8.5... he was a stupid bastard but let's take his example why bother if the problem isn't ours ? If users complain, we just need to say it's a driver bug, not an amsn bug, don't bother us, EVEN if we know the solution to it. We had so much work to do because of pwc, I'm fed up with it now. If a user has Tcl/Tk 8.0 and has a bug, we won't say ohh, you need to modify this and this line, no, we'll just say upgrade, you can't, then it's your problem, it's a requirement, in the same way a program can require Windows XP to run instead of Windows 3.1 for example. Now, if we let Luc Saillard know about this issue, he might fix it and provide a new version.. so when people complain, instead of telling them to fuck off, we'll just say upgrade your driver... The thing is, what you said below is not true, you say we cannot assume all users will upgrade, oh yeah ? then it's their problem, it's their choice, not ours, they didn't want to upgrade, so it's not our fault... also, the users will know how to upgrade and will have root access... you know why ? because the bug is with v4l2 not with v4l, and the only pwc driver that supports v4l2 is Saillard's driver, which is unofficial and not shipped anywhere, so if a user has the problem it means he has Saillard's driver which means he installed it himself, which means he has root access and he knows how to install it. If I'm wrong, then again, it's not our problem. Do you agree with me ? KKRT ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] ML still working ?
I will do it tomorrow evening... Phil Le Tuesday 13 June 2006 20:17, Youness Alaoui a écrit : On Tue, 13 Jun 2006 12:44:24 -0400, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: I totally agree with you... Users have to use perfect softwares and not buggy drivers... Anyway, I try to know where is the bug... Why ? Because with that it's the first time I hack in the kernel level... And I like that ;) It's so bad I haven't a pwc compliant cam. Else, I already had tracked the bug and sent a patch to Luc Saillard... (Doesn't open source means bring your help to all the edifice ?) Cool! congrats! :) Phil P.S. Totally OT but should we apply the holly_wood patch about DPs in directories ? I think so, yes, but only in /trunk, it should never go in the 0.96 branch. Please include this info in the commit log so we don't forget... Le Monday 12 June 2006 22:54, Youness Alaoui a écrit : not only that, but we'd need to shift the responsability... we really should stop being so nice to the users, look at what happened lately in the forums because of AA fonts and tcl/tk 8.5... he was a stupid bastard but let's take his example why bother if the problem isn't ours ? If users complain, we just need to say it's a driver bug, not an amsn bug, don't bother us, EVEN if we know the solution to it. We had so much work to do because of pwc, I'm fed up with it now. If a user has Tcl/Tk 8.0 and has a bug, we won't say ohh, you need to modify this and this line, no, we'll just say upgrade, you can't, then it's your problem, it's a requirement, in the same way a program can require Windows XP to run instead of Windows 3.1 for example. Now, if we let Luc Saillard know about this issue, he might fix it and provide a new version.. so when people complain, instead of telling them to fuck off, we'll just say upgrade your driver... The thing is, what you said below is not true, you say we cannot assume all users will upgrade, oh yeah ? then it's their problem, it's their choice, not ours, they didn't want to upgrade, so it's not our fault... also, the users will know how to upgrade and will have root access... you know why ? because the bug is with v4l2 not with v4l, and the only pwc driver that supports v4l2 is Saillard's driver, which is unofficial and not shipped anywhere, so if a user has the problem it means he has Saillard's driver which means he installed it himself, which means he has root access and he knows how to install it. If I'm wrong, then again, it's not our problem. Do you agree with me ? KKRT ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
[Amsn-devel] amsn sounds
Hello. I recently downloaded a tarball to play with ir a little, with the idea of doing some stuff with the sounds amsn loads on certain events. Well, the thing is that I've been having a hard time trying to spot the piece of code that will let me tinker with the sounds associated with those events (specifically, I was looking for the place that handles when a contact goes online, and where does it load online.wav; I found the showUser proc in gui.tcl, but it doesn't seem to know anything about the sound); maybe you could lend me a hand here? Well, hope you can help me. In any case, thank you! Saludos from Argentina, Juan ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] amsn sounds
Hi, I suggest you use the 'development' forum on http://amsn.sf.net/forums instead of using the developer's mailing list. What I suggest you do is simply : grep play_sound * the play_sound command is used to play all the sounds (don't pay attention to snack_play_sound or play_sound_other... btw devels... I just noticed that we play sounds on notifyAdd... what happens if you want sounds but disabled notification windows ?? KKRT On Tue, 13 Jun 2006 15:10:40 -0400, Juan Manuel Lopez Baio [EMAIL PROTECTED] wrote: Hello. I recently downloaded a tarball to play with ir a little, with the idea of doing some stuff with the sounds amsn loads on certain events. Well, the thing is that I've been having a hard time trying to spot the piece of code that will let me tinker with the sounds associated with those events (specifically, I was looking for the place that handles when a contact goes online, and where does it load online.wav; I found the showUser proc in gui.tcl, but it doesn't seem to know anything about the sound); maybe you could lend me a hand here? Well, hope you can help me. In any case, thank you! Saludos from Argentina, Juan ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
