subject:"\[Amsn\-devel\] Something else\?\!"

Just let me know what you removed, I'll put that on my list and send that. 
Someone can add it to the wiki. The 'removed' langfiles should be kept on the 
Attic in cvs (make sure they stay there!). At your option, the wiki may have 
a link to them.

Also, on the translations page, it should be clear that partial translations 
exist for those languages!

Op zaterdag 3 december 2005 01:28, schreef Jérôme Gagnon-Voyer:
 Yeah

 Should we re-add them after the release? Or keep it in a zip
 somewhere on the wiki?

 Le 05-12-02 à 15:00, Youness Alaoui a écrit :
  I say go with it.
  Thanks,
  KaKaRoTo
 
  On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik
 
  [EMAIL PROTECTED] wrote:
  Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
   The third thing is to decide what languages to remove, if we
 
  remove
 
   them.
 
  wasn't that done already ? I'm not sure about removing them from
  CVS, but
  I do remember Harry (unless I got the wrong name) sending an
  updated list
  of languages.. did it exclude those langauges we didn't want in the
  release ?
 
  Yes, I sent it.
  All languages were on the list, including the ones that are
  outdated and not
  maintained.
  None have been removed yet. Based on earlier discussion about it,
  I'd say:
  remove any language with less than 80% of the keys translated
  (i.e. 153
  missing keys or more).
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_idv37alloc_id865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel
 
  --
  KaKaRoTo
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel

 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through log
 files for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
 http://ads.osdn.com/?ad_idv37alloc_id865op=Click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


You == MSN7.5
the other user == amsn
now..reread :

You send a video conversation
It gets canceled?
You get a webcam invitation, you accept it , and bam youre sending your  
webcam


Where in the whole process did the other user ACCEPT your video  
invitation 


Sander explained it better...

KaKaRoTo


On Sat, 03 Dec 2005 00:48:36 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



I read what you said...And I just don't understand what you said!

You send a video conversation
--Since when do we support videoconversation?

It gets canceled?
--So what? it gets canceled, so we don't have a conversation

You get a webcam invitation, you accept it , and bam youre sending your  
webcam

--Where's the problem? You just accepted it?

Where in the whole process did the other user ACCEPT your video  
invitation 

--HUH??!!

Sorry I just don't understand AT ALL!

Le 05-12-02 à 22:10, Youness Alaoui a écrit :


Hi,
I've been adding the refuse video conversation and send webcam  
invitation thing, but I got into a problem...
imagine, you send a video conversation, it gets canceled, you get a  
webcam invitation, you accept it, and bam, you're sending your webcam...
Where in the whole process did the other user ACCEPT your video  
invitation 
I'm tired and my gf is pissed at me because I was in front of the PC  
the whole afternoon, so I'll leave the thinking to you... other than  
that, I think that theorically, I've already done what we requested...  
I just don't want to commit it...


KaKaRoTo

On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED]  
wrote:



On Friday 02 December 2005 08:32, Youness Alaoui wrote:
I do think it's a good idea, and should be a safe commit, so I  
suggest we
do it. But I don't want little things to be added each time and we'd  
end
up with no deadline for 0.95. So I say do it if you want and have  
time,
but if it's not done before we decide to get 0.95 out, we won't wait  
for

it to be done.
Done, points to http://amsn.sf.net/skins.php which is the page that  
the new

site has skins in. Currently it just forwards the browser to the skins
section in the PHPNuke.

Also the Skin dialog is a bit bigger than required. There is an empty  
space
under the OK button the size of the button itself. Does anyone else  
have it?


I tried to add a Restart aMSN for new skins label somewhere, but I  
am not
sure where. Any suggestions? I was thinking having it in the title  
beside
Please select the skin you would like to use. Maybe have it appear  
after

the user selects a new skin.

Finally for post 0.95, I think we should make the skin and plugin  
dialog look
about the same. This isn't very hard as it requires mainly moving a  
punch of

pack commands around. I'll add it to wiki.

Jerome, you said you wanted to review all previous mails on the  
subject
and see what's missing before the 0.95 release, did you do it ? if  
yes,
can we get a summary of it ? Iremember you forwarded some emails  
saying
has it been done?, I'll look into that myself (too busy with the  
job for

today, maybe tonight)
but if you ALREADY have a list, it would be nice to share it.

Thanks,
KaKaRoTo





--KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Op zaterdag 3 december 2005 16:22, schreef Youness Alaoui:
 You == MSN7.5
 the other user == amsn

 now..reread :
  You send a video conversation
  It gets canceled?
  You get a webcam invitation, you accept it , and bam youre sending your
  webcam
 
  Where in the whole process did the other user ACCEPT your video
  invitation 

 Sander explained it better...

But there isn't any problem here

A (MSN7.5) sends a request 'Do you want to see my webcam (by VC)?'
B (aMSN) get's a message: Do you want to accept his webcam? Accept / Reject
B Clicks 'accept'
aMSN now rejects the VC and sends a 'May I view your webcam?' request.
A Clicks 'accept'
B will now see A's webcam.

that's what we want, isn't it?


 KaKaRoTo


 On Sat, 03 Dec 2005 00:48:36 -0500, Jérôme Gagnon-Voyer

 [EMAIL PROTECTED] wrote:
  I read what you said...And I just don't understand what you said!
 
  You send a video conversation
  --Since when do we support videoconversation?
 
  It gets canceled?
  --So what? it gets canceled, so we don't have a conversation
 
  You get a webcam invitation, you accept it , and bam youre sending your
  webcam
  --Where's the problem? You just accepted it?
 
  Where in the whole process did the other user ACCEPT your video
  invitation 
 
  --HUH??!!
 
  Sorry I just don't understand AT ALL!
 
  Le 05-12-02 à 22:10, Youness Alaoui a écrit :
  Hi,
  I've been adding the refuse video conversation and send webcam
  invitation thing, but I got into a problem...
  imagine, you send a video conversation, it gets canceled, you get a
  webcam invitation, you accept it, and bam, you're sending your webcam...
  Where in the whole process did the other user ACCEPT your video
  invitation 
  I'm tired and my gf is pissed at me because I was in front of the PC
  the whole afternoon, so I'll leave the thinking to you... other than
  that, I think that theorically, I've already done what we requested...
  I just don't want to commit it...
 
  KaKaRoTo
 
  On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED]
 
  wrote:
  On Friday 02 December 2005 08:32, Youness Alaoui wrote:
  I do think it's a good idea, and should be a safe commit, so I
  suggest we
  do it. But I don't want little things to be added each time and we'd
  end
  up with no deadline for 0.95. So I say do it if you want and have
  time,
  but if it's not done before we decide to get 0.95 out, we won't wait
  for
  it to be done.
 
  Done, points to http://amsn.sf.net/skins.php which is the page that
  the new
  site has skins in. Currently it just forwards the browser to the skins
  section in the PHPNuke.
 
  Also the Skin dialog is a bit bigger than required. There is an empty
  space
  under the OK button the size of the button itself. Does anyone else
  have it?
 
  I tried to add a Restart aMSN for new skins label somewhere, but I
  am not
  sure where. Any suggestions? I was thinking having it in the title
  beside
  Please select the skin you would like to use. Maybe have it appear
  after
  the user selects a new skin.
 
  Finally for post 0.95, I think we should make the skin and plugin
  dialog look
  about the same. This isn't very hard as it requires mainly moving a
  punch of
  pack commands around. I'll add it to wiki.
 
  Jerome, you said you wanted to review all previous mails on the
  subject
  and see what's missing before the 0.95 release, did you do it ? if
  yes,
  can we get a summary of it ? Iremember you forwarded some emails
  saying
  has it been done?, I'll look into that myself (too busy with the
  job for
  today, maybe tonight)
  but if you ALREADY have a list, it would be nice to share it.
 
  Thanks,
  KaKaRoTo
 
  --KaKaRoTo
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through log
  files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
  http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through log
  files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
  http://ads.osdn.com/?ad_idv37alloc_id865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!

Re: [Amsn-devel] Something else?!

On Sat, 03 Dec 2005 05:23:48 -0500, Sander Hoentjen [EMAIL PROTECTED]  
wrote:



On Sat, 2005-12-03 at 00:48 -0500, Jérôme Gagnon-Voyer wrote:

I read what you said...And I just don't understand what you said!

You send a video conversation
--Since when do we support videoconversation?

we don't


It gets canceled?
--So what? it gets canceled, so we don't have a conversation

but we want a webcam convo


You get a webcam invitation, you accept it , and bam youre sending
your webcam
--Where's the problem? You just accepted it?

 Where in the whole process did the other user ACCEPT your video
 invitation 
--HUH??!!

Sorry I just don't understand AT ALL!


Ok..
user A wants to send webcam to user B
user A = MSN7.5 - user B = amsn
user A presses webcam icon
video conversation invite (not webcam) will be sent by user A
amsn doesn't know video convo, so it doesn't work
we don't want that.. so we figured:
if user B gets the invite for VC it cancels it and instead sends an
invite for: I want to view your webcam so user A can accept that and B
can view A.. nice
Now Youness:
B gets invite. aMSN displays: A wants to show webcam, accept?
on accept we reject video conv and ask for webcam. Easy, right?



yeah, though of it, but then you'll have 2 accepts... too confusing for  
the user... you click on Accept, you expect to see a webcam, but in  
fact, you just sent an invite, so if the other end doesn't accept it right  
away, we'll get someone saying 'hey, I got a webcam request, I accepted  
it, but it took me over 5 minutes before the webcam appeared.. so.. I  
don't know, really...
we may do on accept a the video conversation invitation received was  
canceled because aMSN doesn't support it. a request for the other user to  
send his webcam was sent, please wait for him/her to accept it.
here's the diff from my version, you can use it to understand where it  
should be modified... what context we need, etc... I won't be able to  
finish this unfortunatly, so if someone can finish this up... :



Index: msnp2p.tcl
===
RCS file: /cvsroot/amsn/msn/msnp2p.tcl,v
retrieving revision 1.37
diff -r1.37 msnp2p.tcl
560,561d559

   SessionList set $sid [list  
0 0 0 $dest 0 $uid 0 webcam  $branchuid]

563c561,563
   ::CAMGUI::AcceptOrRefuse  
$chatid $dest $branchuid $cseq $uid $sid $producer

---
  set context  
[base64::decode $context]
  set context [FromUnicode  
$context]



566a567,580
 if { $context !=  
\{B8BE70DE-E2CA-4400-AE03-88FF85B9F4E8\} } {
  status_log  
Received a video conferenced invitation.. we do not support this
  ::CAMGUI::InvitationRejected  
$chatid $sid $branchuid $uid
  ::MSNCAM::AskWebcamQueue  
$chatid

 return
  }
 SessionList set $sid [list  
0 0 0 $dest 0 $uid 0 webcam  $branchuid]
 ::CAMGUI::AcceptOrRefuse  
$chatid $dest $branchuid $cseq $uid $sid $producer





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Op zaterdag 3 december 2005 16:50, schreef Youness Alaoui:
 here, we wait for A to click accept... for maybe 5 minutes... in the  
 meantime, B thinks it didn't work, he sends a bug report, then 5 minutes  
 later, A finally clicks accept, B sees the webcam, then he fills another  
 bug report either saying :
 I accepted and the webcam popuped up 5 minutes later or, if he suffers  
  from short memory losses, he'll say a webcam popuped from somewhere, I  
 don't know what happened, I never accepted anything...
Yes, now you are right, but this is something different than you were talking 
about in the first place. And we cannot avoid this, if we reply to a VC 
invitation with a webcam invitation, person A will always have to click 
accept... I just added that B should accept first, because you complained 
about 'the other user' not having to accept

So after all, I think there's only one possibility left: simply no VC support 
at all. Just reject the invitation.


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Op zaterdag 3 december 2005 16:57, schreef Youness Alaoui:
 we may do on accept a the video conversation invitation received was  
 canceled because aMSN doesn't support it. a request for the other user to  
 send his webcam was sent, please wait for him/her to accept it.
I bet we are going to get a lot of questions about this, if we are really 
going to do it this way. Users will not understand what's the difference 
between 'video conversation' and 'webcam'.


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Oh! It's not a problem.We just have to show a key or something."aMSN doesn't support video-conversation invite from MSN 7.5, but we will invite him to a webcam conversation instead, wait for his answer"Le 05-12-03 à 10:50, Youness Alaoui a écrit : here, we wait for A to click accept... for maybe 5 minutes... in the meantime, B thinks it didn't work, he sends a bug report, then 5 minutes later, A finally clicks accept, B sees the webcam, then he fills another bug report either saying : "I accepted and the webcam popuped up 5 minutes later" or, if he suffers from short memory losses, he'll say "a webcam popuped from somewhere, I don't know what happened, I never accepted anything"...

Re: [Amsn-devel] Something else?!

2005-12-03 Thread Vivia Nikolaidou


Actually, maybe the aMSN user doesn't actually want to accept the video 
conference/webcam/whatever. So, I think it's better to ask him before 
sending the webcam request, otherwise it can be annoying for some ppl... 
Including this message, of course.

On Sat, 3 Dec 2005, Jérôme Gagnon-Voyer wrote:

 Oh! It's not a problem.
 
 We just have to show a key or something.
 
 aMSN doesn't support video-conversation invite from MSN 7.5, but we will
 invite him to a webcam conversation instead, wait for his answer
 Le 05-12-03 à 10:50, Youness Alaoui a écrit :
 
   
  here, we wait for A to click accept... for maybe 5 minutes... in the
  meantime, B thinks it didn't work, he sends a bug report, then 5 minutes
  later, A finally clicks accept, B sees the webcam, then he fills another
  bug report either saying :
  I accepted and the webcam popuped up 5 minutes later or, if he suffers
  from short memory losses, he'll say a webcam popuped from somewhere, I
  don't know what happened, I never accepted anything...
 
 


---

Where is the life that we have lost in living?
 Where is the wisdom that we have lost in knowledge?
 Where is the knowledge that we have lost in information?

OEO;

Re: [Amsn-devel] Something else?!

2005-12-03 Thread Le Philousophe - Phil

Jay Rome you are ugly 
I see again that be alone isn't good for you !! It's great time for you to 
find someone to be with her !! (If you can find one with your bad mind)
Phil

Le Samedi 3 Décembre 2005 22:50, Jérôme Gagnon-Voyer a écrit :
 Seems a perfect workaround for me

 Did you watch the TV show Les invincibles Youness? At Radio-Canada.
 The guy used somnifer to asleep his girlfriend, that way she was not
 angry when he wanted to do something she didn't want him to do. So if
 you want to code, use that!

 :D

 Le 05-12-03 à 14:42, Youness Alaoui a écrit :
  if he doesn't want to accept it, then, he can press Refuse instead...
  how about, when we get a video conversation request, we do
  something like this :
  You just received a video conversation (bidirectional audio and
  video) request. This feature is not yet supported by aMSN and has
  been canceled.
  Click _here_ to ask for your contact's webcam or click _here_ to
  send your own webcam
 
  This way, they can even launch bidirectional webcam by launching
  both invites and they will understand.
 
  KaKaRoTo
 
  On Sat, 03 Dec 2005 13:12:52 -0500, Vivia Nikolaidou
 
  [EMAIL PROTECTED] wrote:
  Actually, maybe the aMSN user doesn't actually want to accept the
  video
  conference/webcam/whatever. So, I think it's better to ask him before
  sending the webcam request, otherwise it can be annoying for some
  ppl...
  Including this message, of course.
 
  On Sat, 3 Dec 2005, Jérôme Gagnon-Voyer wrote:
  Oh! It's not a problem.
 
  We just have to show a key or something.
 
  aMSN doesn't support video-conversation invite from MSN 7.5, but
  we will
  invite him to a webcam conversation instead, wait for his answer
 
  Le 05-12-03 à 10:50, Youness Alaoui a écrit :
   here, we wait for A to click accept... for maybe 5 minutes...
 
  in the
 
   meantime, B thinks it didn't work, he sends a bug report, then
 
  5 minutes
 
   later, A finally clicks accept, B sees the webcam, then he
 
  fills another
 
   bug report either saying :
   I accepted and the webcam popuped up 5 minutes later or, if
 
  he suffers
 
   from short memory losses, he'll say a webcam popuped from
 
  somewhere, I
 
   don't know what happened, I never accepted anything...
 
  ---
 
  Where is the life that we have lost in living?
   Where is the wisdom that we have lost in knowledge?
   Where is the knowledge that we have lost in information?
 
  OEO;
 
  --
  KaKaRoTo
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel

 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through log
 files for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
 http://ads.osdn.com/?ad_idv37alloc_id865op=Click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-12-03 Thread GrdScarabe

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Personaly I share this philosophy ... even if it is not really moral
However, the best way is yet to find a girlfriend who is part of a free
project ;)

GrdScarabe

Le Philousophe - Phil wrote:
 Jay Rome you are ugly 
 I see again that be alone isn't good for you !! It's great time for you to 
 find someone to be with her !! (If you can find one with your bad mind)
 Phil
 
 Le Samedi 3 Décembre 2005 22:50, Jérôme Gagnon-Voyer a écrit :
 
Seems a perfect workaround for me

Did you watch the TV show Les invincibles Youness? At Radio-Canada.
The guy used somnifer to asleep his girlfriend, that way she was not
angry when he wanted to do something she didn't want him to do. So if
you want to code, use that!

:D

Le 05-12-03 à 14:42, Youness Alaoui a écrit :

if he doesn't want to accept it, then, he can press Refuse instead...
how about, when we get a video conversation request, we do
something like this :
You just received a video conversation (bidirectional audio and
video) request. This feature is not yet supported by aMSN and has
been canceled.
Click _here_ to ask for your contact's webcam or click _here_ to
send your own webcam

This way, they can even launch bidirectional webcam by launching
both invites and they will understand.

KaKaRoTo

On Sat, 03 Dec 2005 13:12:52 -0500, Vivia Nikolaidou

[EMAIL PROTECTED] wrote:

Actually, maybe the aMSN user doesn't actually want to accept the
video
conference/webcam/whatever. So, I think it's better to ask him before
sending the webcam request, otherwise it can be annoying for some
ppl...
Including this message, of course.

On Sat, 3 Dec 2005, Jérôme Gagnon-Voyer wrote:

Oh! It's not a problem.

We just have to show a key or something.

aMSN doesn't support video-conversation invite from MSN 7.5, but
we will
invite him to a webcam conversation instead, wait for his answer

Le 05-12-03 à 10:50, Youness Alaoui a écrit :

here, we wait for A to click accept... for maybe 5 minutes...

in the


meantime, B thinks it didn't work, he sends a bug report, then

5 minutes


later, A finally clicks accept, B sees the webcam, then he

fills another


bug report either saying :
I accepted and the webcam popuped up 5 minutes later or, if

he suffers


from short memory losses, he'll say a webcam popuped from

somewhere, I


don't know what happened, I never accepted anything...

---

Where is the life that we have lost in living?
 Where is the wisdom that we have lost in knowledge?
 Where is the knowledge that we have lost in information?

OEO;

--
KaKaRoTo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDkheqPmfsnt4Id3wRAjuhAJ4nxRsKTWNwX7gyPyWYkeiFI0N9DACgrCIv
wJl9pW5B+R7KKrhUGiDwApE=
=cKGz
-END PGP SIGNATURE-


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


Vivia...where do you live? :P
Le 05-12-03 à 17:09, GrdScarabe a écrit :


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Personaly I share this philosophy ... even if it is not really moral
However, the best way is yet to find a girlfriend who is part of a  
free

project ;)

GrdScarabe

Le Philousophe - Phil wrote:

Jay Rome you are ugly 
I see again that be alone isn't good for you !! It's great time  
for you to
find someone to be with her !! (If you can find one with your bad  
mind)

Phil

Le Samedi 3 Décembre 2005 22:50, Jérôme Gagnon-Voyer a écrit :


Seems a perfect workaround for me

Did you watch the TV show Les invincibles Youness? At Radio- 
Canada.

The guy used somnifer to asleep his girlfriend, that way she was not
angry when he wanted to do something she didn't want him to do.  
So if

you want to code, use that!

:D

Le 05-12-03 à 14:42, Youness Alaoui a écrit :

if he doesn't want to accept it, then, he can press Refuse  
instead...

how about, when we get a video conversation request, we do
something like this :
You just received a video conversation (bidirectional audio and
video) request. This feature is not yet supported by aMSN and has
been canceled.
Click _here_ to ask for your contact's webcam or click _here_ to
send your own webcam

This way, they can even launch bidirectional webcam by launching
both invites and they will understand.

KaKaRoTo

On Sat, 03 Dec 2005 13:12:52 -0500, Vivia Nikolaidou

[EMAIL PROTECTED] wrote:


Actually, maybe the aMSN user doesn't actually want to accept the
video
conference/webcam/whatever. So, I think it's better to ask him  
before

sending the webcam request, otherwise it can be annoying for some
ppl...
Including this message, of course.

On Sat, 3 Dec 2005, Jérôme Gagnon-Voyer wrote:


Oh! It's not a problem.

We just have to show a key or something.

aMSN doesn't support video-conversation invite from MSN 7.5, but
we will
invite him to a webcam conversation instead, wait for his answer

Le 05-12-03 à 10:50, Youness Alaoui a écrit :


here, we wait for A to click accept... for maybe 5 minutes...


in the



meantime, B thinks it didn't work, he sends a bug report, then


5 minutes



later, A finally clicks accept, B sees the webcam, then he


fills another



bug report either saying :
I accepted and the webcam popuped up 5 minutes later or, if


he suffers



from short memory losses, he'll say a webcam popuped from


somewhere, I



don't know what happened, I never accepted anything...


---

Where is the life that we have lost in living?
Where is the wisdom that we have lost in knowledge?
Where is the knowledge that we have lost in information?

OEO;


--
KaKaRoTo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDkheqPmfsnt4Id3wRAjuhAJ4nxRsKTWNwX7gyPyWYkeiFI0N9DACgrCIv
wJl9pW5B+R7KKrhUGiDwApE=
=cKGz
-END PGP SIGNATURE-


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


LOL,
I was sure someone would say something like that... you see why girls  
don't want to be around you guys, you're freaks! leave her alone, she's  
married with 3 children already! ok, just kidding, I don't know, but maybe  
it's safer for her to say that she is :P

btw, she's in Greece.
and, if you remember My big fat greek wedding, you'll know greek girls  
don't go out with non-greek guys :P (j/k)



KaKaRoTo

On Sat, 03 Dec 2005 17:58:25 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



Vivia...where do you live? :P
Le 05-12-03 à 17:09, GrdScarabe a écrit :


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Personaly I share this philosophy ... even if it is not really moral
However, the best way is yet to find a girlfriend who is part of a free
project ;)

GrdScarabe

Le Philousophe - Phil wrote:

Jay Rome you are ugly 
I see again that be alone isn't good for you !! It's great time for  
you to
find someone to be with her !! (If you can find one with your bad  
mind)

Phil

Le Samedi 3 Décembre 2005 22:50, Jérôme Gagnon-Voyer a écrit :


Seems a perfect workaround for me

Did you watch the TV show Les invincibles Youness? At Radio-Canada.
The guy used somnifer to asleep his girlfriend, that way she was not
angry when he wanted to do something she didn't want him to do. So if
you want to code, use that!

:D

Le 05-12-03 à 14:42, Youness Alaoui a écrit :


if he doesn't want to accept it, then, he can press Refuse instead...
how about, when we get a video conversation request, we do
something like this :
You just received a video conversation (bidirectional audio and
video) request. This feature is not yet supported by aMSN and has
been canceled.
Click _here_ to ask for your contact's webcam or click _here_ to
send your own webcam

This way, they can even launch bidirectional webcam by launching
both invites and they will understand.

KaKaRoTo

On Sat, 03 Dec 2005 13:12:52 -0500, Vivia Nikolaidou

[EMAIL PROTECTED] wrote:


Actually, maybe the aMSN user doesn't actually want to accept the
video
conference/webcam/whatever. So, I think it's better to ask him  
before

sending the webcam request, otherwise it can be annoying for some
ppl...
Including this message, of course.

On Sat, 3 Dec 2005, Jérôme Gagnon-Voyer wrote:


Oh! It's not a problem.

We just have to show a key or something.

aMSN doesn't support video-conversation invite from MSN 7.5, but
we will
invite him to a webcam conversation instead, wait for his answer

Le 05-12-03 à 10:50, Youness Alaoui a écrit :


here, we wait for A to click accept... for maybe 5 minutes...


in the



meantime, B thinks it didn't work, he sends a bug report, then


5 minutes



later, A finally clicks accept, B sees the webcam, then he


fills another



bug report either saying :
I accepted and the webcam popuped up 5 minutes later or, if


he suffers



from short memory losses, he'll say a webcam popuped from


somewhere, I



don't know what happened, I never accepted anything...


---

Where is the life that we have lost in living?
Where is the wisdom that we have lost in knowledge?
Where is the knowledge that we have lost in information?

OEO;


--
KaKaRoTo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDkheqPmfsnt4Id3wRAjuhAJ4nxRsKTWNwX7gyPyWYkeiFI0N9DACgrCIv
wJl9pW5B+R7KKrhUGiDwApE=
=cKGz
-END PGP SIGNATURE-


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


can we also have checkboxs and select all - set as fixed...

KKRT

On Sat, 03 Dec 2005 18:49:26 -0500, Youness Alaoui  
[EMAIL PROTECTED] wrote:


On Sat, 03 Dec 2005 18:15:55 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



So, we're progressing!


yep :)


The bug with send button is fixed (just need to add a flag)
Plz confirm us that you will be able to fix the video-conference with
the last suggestion you gave us.

I confirmed that I probably won't have time for it... this is why I sent  
the diff




BTW the bug tracker...this thing is s COOL :D In the last week
with that I think we fixed at least 10 bugs just by looking at the
reports, that's so good.

yes, it really is.. only two problems so far :
1 - I'm not able to filter for a string that contains a quote char ''
2 - It would be nice if we can set regexps for bugs, like the SB bug, we  
could see it, and on admin, we would do a

error regex : invaild command name \::MSN::SB\d+\
stack regex : (?s:.*?)cmsn_reconnect $sb(?s:.*?)chatTo

and then, it would filter all reports, those that match (and new reports  
coming in that match these regexps) would go into a sublist of this bug,  
and we would have a ++ to the duplicate number...
so, we enter the bug report system, we get 10 bugs for example, only one  
has the invalid command name... and it would say reported 100 times,  
you click on it, you see the report, and a button will allow you to look  
at all the duplicates...
so, if this one is fixed, we will fix all duplicated at the same time,  
and we will have a cleaner view of the bugs currently present...

can this be added to the wiki, and done AFTER 0.95 please... thanx
(the quote  not being able to filter with it is a bug I'd like to be  
fixed as soon as possible, it probably is simple, I just don't know php)

thanks,


ALSO, you asked for comments for your fix on MSN::SB. We didn't
receive any bugreport about that issue since you did the fix. Good job.


great! but we need to wait more to be sure...


We are still set for monday for the cvs-export.

cool


Le 05-12-02 à 14:15, Youness Alaoui a écrit :


I'm working on it, it should be done by the end of the week-end, as
well as any other pending issue (like reading/commenting on the
FAQ). Here's my suggestion : Monday, we label the CVS as 0.95,
Phil, Vivia, you have to find and fix that issue with the crash
before Monday. What we'll do if it's not done by that time... we'll
see when the time comes, but I think we'll probably have to go with
the release...










--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Ordinateur-de-J-r-me-Gagnon-Voyer:/Applications/Utilities/amsn cvs-true/msn gagnonje$ patch -p0 msnp2p.patchcan't find file to patch at input line 9Perhaps you used the wrong -p or --strip option?The text leading up to this was:--|Index: msnp2p.tcl|===|RCS file: /cvsroot/amsn/msn/msnp2p.tcl,v|retrieving revision 1.37|diff -r1.37 msnp2p.tcl|560,561d559||                                               SessionList set $sid [list 0 0 0 $dest 0 $uid 0 "webcam" "" "$branchuid"]--File to patch: msnp2p.tclpatching file msnp2p.tclpatch:  `' expected at line 12 of patchHmmmLe 05-12-03 à 18:49, Youness Alaoui a écrit :I confirmed that I probably won't have time for it... this is why I sent the diff

Re: [Amsn-devel] Something else?!


argh.. you're such a pain
msnp2p.tcl
line 562, from there, everything becomes :
set producer 1
}

status_log we got an webcam 
invitation red

set context [base64::decode 
$context]
set context [FromUnicode 
$context]

#answerFtInvite $sid $chatid 
$branchuid $conntype
# Let's send an ACK
		SendPacket [::MSN::SBFor $chatid] [MakeACK $sid 0 $cTotalDataSize  
$cId $cAckId]



if { $context != 
\{B8BE70DE-E2CA-4400-AE03-88FF85B9F4E8\} } {
			status_log Received a video conferenced invitation.. we do not  
support this


::CAMGUI::InvitationRejected $chatid $sid $branchuid $uid

::MSNCAM::AskWebcamQueue $chatid

return
}

		SessionList set $sid [list 0 0 0 $dest 0 $uid 0 webcam   
$branchuid]


		::CAMGUI::AcceptOrRefuse $chatid $dest $branchuid $cseq $uid $sid  
$producer


status_log MSNP2P | $sid $dest - 
Sent ACK for INVITE\n red
return
}


easier this way...

KKRT

On Sat, 03 Dec 2005 23:07:43 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



Ordinateur-de-J-r-me-Gagnon-Voyer:/Applications/Utilities/amsn cvs-
true/msn gagnonje$ patch -p0 msnp2p.patch
can't find file to patch at input line 9
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|Index: msnp2p.tcl
|===
|RCS file: /cvsroot/amsn/msn/msnp2p.tcl,v
|retrieving revision 1.37
|diff -r1.37 msnp2p.tcl
|560,561d559
|
|   SessionList set $sid
[list 0 0 0 $dest 0 $uid 0 webcam  $branchuid]
--
File to patch: msnp2p.tcl
patching file msnp2p.tcl
patch:  `' expected at line 12 of patch

Hmmm

Le 05-12-03 à 18:49, Youness Alaoui a écrit :


I confirmed that I probably won't have time for it... this is why I
sent the diff






--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


LOL come on, i'm not a pain, I just hate diff inside messages :P

Anyway I finished to code it, plz someone find me a user with MSN 7.5  
and webcam so I can test everything and commit it.


This is the text on the screen, Click here will be clickable

If you want to correct something, tell me now!

You just received a video conversation (bidirectional audio and  
video) request.
This feature is not yet supported by aMSN and has been canceled.  
However, you can still use the standard webcam conversation.\n
Click Here to ask for your contact's webcam, or Click Here to ask for  
sending your own webcam



Le 05-12-03 à 23:47, Youness Alaoui a écrit :


argh.. you're such a pain
msnp2p.tcl
line 562, from there, everything becomes :
set producer 1
}

status_log we got an webcam 
invitation red

set context [base64::decode 
$context]
set context [FromUnicode 
$context]

#answerFtInvite $sid $chatid 
$branchuid $conntype
# Let's send an ACK
		SendPacket [::MSN::SBFor $chatid] [MakeACK $sid 0  
$cTotalDataSize $cId $cAckId]



if { $context != 
\{B8BE70DE-E2CA-4400-AE03-88FF85B9F4E8\} } {
			status_log Received a video conferenced invitation.. we do  
not support this


::CAMGUI::InvitationRejected $chatid $sid $branchuid $uid

::MSNCAM::AskWebcamQueue $chatid

return
}

		SessionList set $sid [list 0 0 0 $dest 0 $uid 0 webcam   
$branchuid]


		::CAMGUI::AcceptOrRefuse $chatid $dest $branchuid $cseq $uid  
$sid $producer


status_log MSNP2P | $sid $dest - 
Sent ACK for INVITE\n red
return
}


easier this way...

KKRT

On Sat, 03 Dec 2005 23:07:43 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



Ordinateur-de-J-r-me-Gagnon-Voyer:/Applications/Utilities/amsn cvs-
true/msn gagnonje$ patch -p0 msnp2p.patch
can't find file to patch at input line 9
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|Index: msnp2p.tcl
|===
|RCS file: /cvsroot/amsn/msn/msnp2p.tcl,v
|retrieving revision 1.37
|diff -r1.37 msnp2p.tcl
|560,561d559
|
|   SessionList set $sid
[list 0 0 0 $dest 0 $uid 0 webcam  $branchuid]
--
File to patch: msnp2p.tcl
patching file msnp2p.tcl
patch:  `' expected at line 12 of patch

Hmmm

Le 05-12-03 à 18:49, Youness Alaoui a écrit :


I confirmed that I probably won't have time for it... this is why I
sent the diff






--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-12-02 Thread Karel Demeyer

I didn't read this whole thrad so sorry if I say something that's
already said but I see you proposed tohave a kind of info-box telling
teh userr it's better to restart aMSN to have the new skin in it's full
glory ... but why not show this message inside the skin chooser window
in bold ?  Like Notice: you might want to restart aMSN to enjoy all the
skin's functionality  ...?

greets,

Karel.


Op di, 29-11-2005 te 21:49 -0500, schreef Youness Alaoui:
 On Tue, 29 Nov 2005 21:45:53 -0500, Jérôme Gagnon-Voyer  
 [EMAIL PROTECTED] wrote:
 
 
  Le 05-11-29 à 21:34, Youness Alaoui a écrit :
 
  hehe, no I didn't mean that, that would be too much trouble, like I
  said, just a little thing to do because now we're in a feature
  freeze...
  what I meant by some pixmaps are not used was that some pixmaps
  would remain from the old skin instead of the skin system using the
  new skin's pixmaps...
 
 
  I don't get that one :P If the skin has the pixmaps, the skin system
  takes it, if not, it takes the pixmaps from the default skin. That's
  the correct behavior.
 
 
 ok, that's probably why I said that I may say something stupid :P forget  
 about it :)
 
  Anyway, as you said, it's not a big deal to just add a message_box
  (but still, it can be feel as a pain for some people to always click
  on OK when switching skin, even if they just make a preview of the
  skin), I left the decision to others, I'm 50-50 :P
 
 to preview a skin, you enable the preview checkbox... to click ok, is  
 not that bad if anyways, you have to restart amsn...
 it's a suggestion, maybe other devs' opinions would help us decide...
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

I think it's perfect, a lot better since the user won't have any annoyin  
popup...

I suggest we go with that..

KaKaRoTo

On Fri, 02 Dec 2005 07:43:00 -0500, Karel Demeyer [EMAIL PROTECTED]  
wrote:



I didn't read this whole thrad so sorry if I say something that's
already said but I see you proposed tohave a kind of info-box telling
teh userr it's better to restart aMSN to have the new skin in it's full
glory ... but why not show this message inside the skin chooser window
in bold ?  Like Notice: you might want to restart aMSN to enjoy all the
skin's functionality  ...?

greets,

Karel.


Op di, 29-11-2005 te 21:49 -0500, schreef Youness Alaoui:

On Tue, 29 Nov 2005 21:45:53 -0500, Jérôme Gagnon-Voyer
[EMAIL PROTECTED] wrote:


 Le 05-11-29 à 21:34, Youness Alaoui a écrit :

 hehe, no I didn't mean that, that would be too much trouble, like I
 said, just a little thing to do because now we're in a feature
 freeze...
 what I meant by some pixmaps are not used was that some pixmaps
 would remain from the old skin instead of the skin system using the
 new skin's pixmaps...


 I don't get that one :P If the skin has the pixmaps, the skin system
 takes it, if not, it takes the pixmaps from the default skin. That's
 the correct behavior.


ok, that's probably why I said that I may say something stupid :P forget
about it :)

 Anyway, as you said, it's not a big deal to just add a message_box
 (but still, it can be feel as a pain for some people to always click
 on OK when switching skin, even if they just make a preview of the
 skin), I left the decision to others, I'm 50-50 :P

to preview a skin, you enable the preview checkbox... to click ok, is
not that bad if anyways, you have to restart amsn...
it's a suggestion, maybe other devs' opinions would help us decide...





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

On Friday 02 December 2005 06:02, Youness Alaoui wrote:
 I think it's perfect, a lot better since the user won't have any annoyin
 popup...
 I suggest we go with that..

Also we could add a link Get more skins! that when clicked will open a 
browser with our skin section, like in Firefox. Or should this be added 
after .95 release?

 KaKaRoTo

 On Fri, 02 Dec 2005 07:43:00 -0500, Karel Demeyer [EMAIL PROTECTED]

 wrote:
  I didn't read this whole thrad so sorry if I say something that's
  already said but I see you proposed tohave a kind of info-box telling
  teh userr it's better to restart aMSN to have the new skin in it's full
  glory ... but why not show this message inside the skin chooser window
  in bold ?  Like Notice: you might want to restart aMSN to enjoy all the
  skin's functionality  ...?
 
  greets,
 
  Karel.
 
  Op di, 29-11-2005 te 21:49 -0500, schreef Youness Alaoui:
  On Tue, 29 Nov 2005 21:45:53 -0500, Jérôme Gagnon-Voyer
 
  [EMAIL PROTECTED] wrote:
   Le 05-11-29 à 21:34, Youness Alaoui a écrit :
   hehe, no I didn't mean that, that would be too much trouble, like I
   said, just a little thing to do because now we're in a feature
   freeze...
   what I meant by some pixmaps are not used was that some pixmaps
   would remain from the old skin instead of the skin system using the
   new skin's pixmaps...
  
   I don't get that one :P If the skin has the pixmaps, the skin system
   takes it, if not, it takes the pixmaps from the default skin. That's
   the correct behavior.
 
  ok, that's probably why I said that I may say something stupid :P forget
  about it :)
 
   Anyway, as you said, it's not a big deal to just add a message_box
   (but still, it can be feel as a pain for some people to always click
   on OK when switching skin, even if they just make a preview of the
   skin), I left the decision to others, I'm 50-50 :P
 
  to preview a skin, you enable the preview checkbox... to click ok, is
  not that bad if anyways, you have to restart amsn...
  it's a suggestion, maybe other devs' opinions would help us decide...
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through log
  files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
  http://ads.osdn.com/?ad_idv37alloc_id865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel

-- 
Karol Krizka


pgpSVMFtt2Osd.pgp
Description: PGP signature

Re: [Amsn-devel] Something else?!

Le 05-12-02 à 11:32, Youness Alaoui a écrit :I do think it's a good idea, and should be a safe commit, so I suggest we do it. But I don't want little things to be added each time and we'd end up with no deadline for 0.95. So I say "do it if you want and have time", but if it's not done before we decide to get 0.95 out, we won't wait for it to be done. Jerome, you said you wanted to review all previous mails on the subject and see what's missing before the 0.95 release, did you do it ? Yesif yes, can we get a summary of it ? Iremember you forwarded some emails saying "has it been done?", I'll look into that myself (too busy with the job for today, maybe tonight) but if you ALREADY have a list, it would be nice to share it. The summary is there's only 2 things left-The crash  that Vivia talked about-The webcam auto-refuse/auto re-invite for MSN 7.5The third thing is to decide what languages to remove, if we remove them.That's all. Everything was fixed by me, Philousophe and Karol for the most. Other things are post-0.95.I must say, again, that I hope this release will come VERY SOON, because I won't have time for that during my exams time. DO IT AS SOON AS POSSIBLE before it's too late. I looked at the bug report database and the release is stable.

Re: [Amsn-devel] Something else?!

2005-12-02 Thread Harry Vennik

Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
  The third thing is to decide what languages to remove, if we remove
  them.

 wasn't that done already ? I'm not sure about removing them from CVS, but  
 I do remember Harry (unless I got the wrong name) sending an updated list  
 of languages... did it exclude those langauges we didn't want in the  
 release ?
Yes, I sent it.
All languages were on the list, including the ones that are outdated and not 
maintained.
None have been removed yet. Based on earlier discussion about it, I'd say: 
remove any language with less than 80% of the keys translated (i.e. 153 
missing keys or more).


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


I say go with it.
Thanks,
KaKaRoTo

On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik [EMAIL PROTECTED]  
wrote:



Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:

 The third thing is to decide what languages to remove, if we remove
 them.

wasn't that done already ? I'm not sure about removing them from CVS,  
but  
I do remember Harry (unless I got the wrong name) sending an updated  
list  

of languages.. did it exclude those langauges we didn't want in the  
release ?

Yes, I sent it.
All languages were on the list, including the ones that are outdated and  
not

maintained.
None have been removed yet. Based on earlier discussion about it, I'd  
say:

remove any language with less than 80% of the keys translated (i.e. 153
missing keys or more).


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


no,
if you don't restart amsn when changing the language, you will probably  
get a Tk error in the next 5 minutes..
if you don't restart amsn after a skin change, you'll only have a white  
border instead of a green one or something like that.. nothing major...
changing the language should have a more 'agressive' notification than  
just a bold label in a window...


KaKaRoTo

On Fri, 02 Dec 2005 15:06:46 -0500, Vivia Nikolaidou  
[EMAIL PROTECTED] wrote:





I think it's perfect, a lot better since the user won't have any annoyin
popup... I suggest we go with that..


Another suggestion: do the same for changing languages? Currently, after
you select the new language, a popup says that you have to restart aMSN,
so maybe write this one too inside the window?

Vivia


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-12-02 Thread Vivia Nikolaidou


 I think it's perfect, a lot better since the user won't have any annoyin 
 popup... I suggest we go with that..

Another suggestion: do the same for changing languages? Currently, after 
you select the new language, a popup says that you have to restart aMSN, 
so maybe write this one too inside the window?

Vivia


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


Yeah

Should we re-add them after the release? Or keep it in a zip  
somewhere on the wiki?

Le 05-12-02 à 15:00, Youness Alaoui a écrit :


I say go with it.
Thanks,
KaKaRoTo

On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik  
[EMAIL PROTECTED] wrote:



Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
 The third thing is to decide what languages to remove, if we  
remove

 them.

wasn't that done already ? I'm not sure about removing them from  
CVS, but
I do remember Harry (unless I got the wrong name) sending an  
updated list

of languages.. did it exclude those langauges we didn't want in the
release ?

Yes, I sent it.
All languages were on the list, including the ones that are  
outdated and not

maintained.
None have been removed yet. Based on earlier discussion about it,  
I'd say:
remove any language with less than 80% of the keys translated  
(i.e. 153

missing keys or more).


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-12-02 Thread Yves Manuel

Wowsers, amsn is almost ready to release.

Good job guys :)On 12/2/05, Jérôme Gagnon-Voyer [EMAIL PROTECTED] wrote:
YeahShould we re-add them after the release? Or keep it in a zipsomewhere on the wiki?Le 05-12-02 à 15:00, Youness Alaoui a écrit : I say go with it. Thanks, KaKaRoTo
On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik [EMAIL PROTECTED] wrote: Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui: The third thing is to decide what languages to remove, if we
remove them. wasn't that done already ? I'm not sure about removing them from CVS, but I do remember Harry (unless I got the wrong name) sending an
updated list of languages.. did it exclude those langauges we didn't want in the release ? Yes, I sent it. All languages were on the list, including the ones that are
outdated and not maintained. None have been removed yet. Based on earlier discussion about it, I'd say: remove any language with less than 80% of the keys translated
(i.e. 153 missing keys or more). --- This SF.net email is sponsored by: Splunk Inc. Do you grep through
log files for problems?Stop!Download the new AJAX search engine that makes searching your log files as easy as surfing theweb.DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo
--- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems?Stop!Download the new AJAX search engine that makes
searching your log files as easy as surfing theweb.DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel---This SF.net email is sponsored by: Splunk Inc. Do you grep through log filesfor problems?Stop!Download the new AJAX search engine that makes
searching your log files as easy as surfing theweb.DOWNLOAD SPLUNK!http://ads.osdn.com/?ad_idv37alloc_id865opclick___
Amsn-devel mailing listAmsn-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

On Friday 02 December 2005 16:28, Jérôme Gagnon-Voyer wrote:
 Yeah

 Should we re-add them after the release? Or keep it in a zip
 somewhere on the wiki?

Just remove them from the release but not from CVS.

 Le 05-12-02 à 15:00, Youness Alaoui a écrit :
  I say go with it.
  Thanks,
  KaKaRoTo
 
  On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik
 
  [EMAIL PROTECTED] wrote:
  Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
   The third thing is to decide what languages to remove, if we
 
  remove
 
   them.
 
  wasn't that done already ? I'm not sure about removing them from
  CVS, but
  I do remember Harry (unless I got the wrong name) sending an
  updated list
  of languages.. did it exclude those langauges we didn't want in the
  release ?
 
  Yes, I sent it.
  All languages were on the list, including the ones that are
  outdated and not
  maintained.
  None have been removed yet. Based on earlier discussion about it,
  I'd say:
  remove any language with less than 80% of the keys translated
  (i.e. 153
  missing keys or more).
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_idv37alloc_id865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel
 
  --
  KaKaRoTo
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that makes
  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel

 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through log
 files for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
 http://ads.osdn.com/?ad_idv37alloc_id865op=Click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel

-- 
Karol Krizka


pgpu2yDlwdyCF.pgp
Description: PGP signature

Re: [Amsn-devel] Something else?!


You're sure ?
I think we should remove them from CVS because it's not maintained.. if  
someone wants to maintain them, we'll get them back from CVS's Attic and  
he can work on them... in the meantime, it can be removed... it's better  
like this, makes cvs cleaner...

in any case, I suggest we leave the decision to the language maintainer.

KaKaRoTo

On Fri, 02 Dec 2005 19:43:36 -0500, Karol Krizka [EMAIL PROTECTED] wrote:


On Friday 02 December 2005 16:28, Jérôme Gagnon-Voyer wrote:

Yeah

Should we re-add them after the release? Or keep it in a zip
somewhere on the wiki?


Just remove them from the release but not from CVS.


Le 05-12-02 à 15:00, Youness Alaoui a écrit :
 I say go with it.
 Thanks,
 KaKaRoTo

 On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik

 [EMAIL PROTECTED] wrote:
 Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
  The third thing is to decide what languages to remove, if we

 remove

  them.

 wasn't that done already ? I'm not sure about removing them from
 CVS, but
 I do remember Harry (unless I got the wrong name) sending an
 updated list
 of languages.. did it exclude those langauges we didn't want in the
 release ?

 Yes, I sent it.
 All languages were on the list, including the ones that are
 outdated and not
 maintained.
 None have been removed yet. Based on earlier discussion about it,
 I'd say:
 remove any language with less than 80% of the keys translated
 (i.e. 153
 missing keys or more).


 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through
 log files
 for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD
 SPLUNK!
 http://ads.osdn.com/?ad_idv37alloc_id865op=click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel

 --
 KaKaRoTo


 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through
 log files
 for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD
 SPLUNK!
 http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel

---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems?  Stop!  Download the new AJAX search engine that  
makes

searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=Click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel






--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-12-02 Thread Lee Olson

As long as they're in the Attic they should be ok, but it would also
be a good idea to make a backup copy of them and post them on the wiki
before we package everything up for 0.95

~Lee

On 12/2/05, Youness Alaoui [EMAIL PROTECTED] wrote:
 You're sure ?
 I think we should remove them from CVS because it's not maintained.. if
 someone wants to maintain them, we'll get them back from CVS's Attic and
 he can work on them... in the meantime, it can be removed... it's better
 like this, makes cvs cleaner...
 in any case, I suggest we leave the decision to the language maintainer.

 KaKaRoTo

 On Fri, 02 Dec 2005 19:43:36 -0500, Karol Krizka [EMAIL PROTECTED] wrote:

  On Friday 02 December 2005 16:28, Jérôme Gagnon-Voyer wrote:
  Yeah
 
  Should we re-add them after the release? Or keep it in a zip
  somewhere on the wiki?
 
  Just remove them from the release but not from CVS.
 
  Le 05-12-02 à 15:00, Youness Alaoui a écrit :
   I say go with it.
   Thanks,
   KaKaRoTo
  
   On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik
  
   [EMAIL PROTECTED] wrote:
   Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
The third thing is to decide what languages to remove, if we
  
   remove
  
them.
  
   wasn't that done already ? I'm not sure about removing them from
   CVS, but
   I do remember Harry (unless I got the wrong name) sending an
   updated list
   of languages.. did it exclude those langauges we didn't want in the
   release ?
  
   Yes, I sent it.
   All languages were on the list, including the ones that are
   outdated and not
   maintained.
   None have been removed yet. Based on earlier discussion about it,
   I'd say:
   remove any language with less than 80% of the keys translated
   (i.e. 153
   missing keys or more).
  
  
   ---
   This SF.net email is sponsored by: Splunk Inc. Do you grep through
   log files
   for problems?  Stop!  Download the new AJAX search engine that makes
   searching your log files as easy as surfing the  web.  DOWNLOAD
   SPLUNK!
   http://ads.osdn.com/?ad_idv37alloc_id865op=click
   ___
   Amsn-devel mailing list
   Amsn-devel@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/amsn-devel
  
   --
   KaKaRoTo
  
  
   ---
   This SF.net email is sponsored by: Splunk Inc. Do you grep through
   log files
   for problems?  Stop!  Download the new AJAX search engine that makes
   searching your log files as easy as surfing the  web.  DOWNLOAD
   SPLUNK!
   http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
   ___
   Amsn-devel mailing list
   Amsn-devel@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/amsn-devel
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through log
  files for problems?  Stop!  Download the new AJAX search engine that
  makes
  searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
  http://ads.osdn.com/?ad_idv37alloc_id865op=Click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel
 



 --
 KaKaRoTo


 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
 for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
 http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

they should be available to download for those who want them, and the  
language managers should have a list of removed languages...
the document he sent has a date removed field.. which means all  
languages will be kept there for record...


KaKaRoTo

On Fri, 02 Dec 2005 20:12:14 -0500, Lee Olson [EMAIL PROTECTED] wrote:


As long as they're in the Attic they should be ok, but it would also
be a good idea to make a backup copy of them and post them on the wiki
before we package everything up for 0.95

~Lee

On 12/2/05, Youness Alaoui [EMAIL PROTECTED] wrote:

You're sure ?
I think we should remove them from CVS because it's not maintained.. if
someone wants to maintain them, we'll get them back from CVS's Attic and
he can work on them... in the meantime, it can be removed... it's better
like this, makes cvs cleaner...
in any case, I suggest we leave the decision to the language maintainer.

KaKaRoTo

On Fri, 02 Dec 2005 19:43:36 -0500, Karol Krizka [EMAIL PROTECTED]  
wrote:


 On Friday 02 December 2005 16:28, Jérôme Gagnon-Voyer wrote:
 Yeah

 Should we re-add them after the release? Or keep it in a zip
 somewhere on the wiki?

 Just remove them from the release but not from CVS.

 Le 05-12-02 à 15:00, Youness Alaoui a écrit :
  I say go with it.
  Thanks,
  KaKaRoTo
 
  On Fri, 02 Dec 2005 14:33:41 -0500, Harry Vennik
 
  [EMAIL PROTECTED] wrote:
  Op vrijdag 2 december 2005 20:15, schreef Youness Alaoui:
   The third thing is to decide what languages to remove, if we
 
  remove
 
   them.
 
  wasn't that done already ? I'm not sure about removing them from
  CVS, but
  I do remember Harry (unless I got the wrong name) sending an
  updated list
  of languages.. did it exclude those langauges we didn't want in  
the

  release ?
 
  Yes, I sent it.
  All languages were on the list, including the ones that are
  outdated and not
  maintained.
  None have been removed yet. Based on earlier discussion about it,
  I'd say:
  remove any language with less than 80% of the keys translated
  (i.e. 153
  missing keys or more).
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that  
makes

  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_idv37alloc_id865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel
 
  --
  KaKaRoTo
 
 
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that  
makes

  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
  ___
  Amsn-devel mailing list
  Amsn-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/amsn-devel

 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log

 files for problems?  Stop!  Download the new AJAX search engine that
 makes
 searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

 http://ads.osdn.com/?ad_idv37alloc_id865op=Click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click

Re: [Amsn-devel] Something else?!

On Friday 02 December 2005 08:32, Youness Alaoui wrote:
 I do think it's a good idea, and should be a safe commit, so I suggest we
 do it. But I don't want little things to be added each time and we'd end
 up with no deadline for 0.95. So I say do it if you want and have time,
 but if it's not done before we decide to get 0.95 out, we won't wait for
 it to be done.
Done, points to http://amsn.sf.net/skins.php which is the page that the new 
site has skins in. Currently it just forwards the browser to the skins 
section in the PHPNuke.

Also the Skin dialog is a bit bigger than required. There is an empty space 
under the OK button the size of the button itself. Does anyone else have it?

I tried to add a Restart aMSN for new skins label somewhere, but I am not 
sure where. Any suggestions? I was thinking having it in the title beside 
Please select the skin you would like to use. Maybe have it appear after 
the user selects a new skin.

Finally for post 0.95, I think we should make the skin and plugin dialog look 
about the same. This isn't very hard as it requires mainly moving a punch of 
pack commands around. I'll add it to wiki.

 Jerome, you said you wanted to review all previous mails on the subject
 and see what's missing before the 0.95 release, did you do it ? if yes,
 can we get a summary of it ? Iremember you forwarded some emails saying
 has it been done?, I'll look into that myself (too busy with the job for
 today, maybe tonight)
 but if you ALREADY have a list, it would be nice to share it.

 Thanks,
 KaKaRoTo

-- 
Karol Krizka


pgpT8RFgJ2dsm.pgp
Description: PGP signature

Re: [Amsn-devel] Something else?!


On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED] wrote:


On Friday 02 December 2005 08:32, Youness Alaoui wrote:
I do think it's a good idea, and should be a safe commit, so I suggest  
we

do it. But I don't want little things to be added each time and we'd end
up with no deadline for 0.95. So I say do it if you want and have  
time,

but if it's not done before we decide to get 0.95 out, we won't wait for
it to be done.
Done, points to http://amsn.sf.net/skins.php which is the page that the  
new

site has skins in. Currently it just forwards the browser to the skins
section in the PHPNuke.



thank you

Also the Skin dialog is a bit bigger than required. There is an empty  
space
under the OK button the size of the button itself. Does anyone else have  
it?




Yes I have it and I like it! it's better than having it all squashed up...
it reminds me we should, before Monday, make the select plugins and the  
auto-updater and the Notes windows bigger...



I tried to add a Restart aMSN for new skins label somewhere, but I am  
not

sure where. Any suggestions? I was thinking having it in the title beside
Please select the skin you would like to use. Maybe have it appear  
after

the user selects a new skin.



humm.. you're right, there's no appropriate place to put it...
I would suggest putting it in the upper frame, below the Please select  
the skin you would like to use, have it centered and have note that you  
may need to restart amsn to view the skin at its fullest, and make it  
red...


Finally for post 0.95, I think we should make the skin and plugin dialog  
look
about the same. This isn't very hard as it requires mainly moving a  
punch of

pack commands around. I'll add it to wiki.



good, ok, thanks.
but, we might want to think of it as being part of the new preferences  
dialog...



Jerome, you said you wanted to review all previous mails on the subject
and see what's missing before the 0.95 release, did you do it ? if yes,
can we get a summary of it ? Iremember you forwarded some emails saying
has it been done?, I'll look into that myself (too busy with the job  
for

today, maybe tonight)
but if you ALREADY have a list, it would be nice to share it.

Thanks,
KaKaRoTo





--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


Hi,
I've been adding the refuse video conversation and send webcam  
invitation thing, but I got into a problem...
imagine, you send a video conversation, it gets canceled, you get a webcam  
invitation, you accept it, and bam, you're sending your webcam...
Where in the whole process did the other user ACCEPT your video invitation  

I'm tired and my gf is pissed at me because I was in front of the PC the  
whole afternoon, so I'll leave the thinking to you... other than that, I  
think that theorically, I've already done what we requested... I just  
don't want to commit it...


KaKaRoTo

On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED] wrote:


On Friday 02 December 2005 08:32, Youness Alaoui wrote:
I do think it's a good idea, and should be a safe commit, so I suggest  
we

do it. But I don't want little things to be added each time and we'd end
up with no deadline for 0.95. So I say do it if you want and have  
time,

but if it's not done before we decide to get 0.95 out, we won't wait for
it to be done.
Done, points to http://amsn.sf.net/skins.php which is the page that the  
new

site has skins in. Currently it just forwards the browser to the skins
section in the PHPNuke.

Also the Skin dialog is a bit bigger than required. There is an empty  
space
under the OK button the size of the button itself. Does anyone else have  
it?


I tried to add a Restart aMSN for new skins label somewhere, but I am  
not

sure where. Any suggestions? I was thinking having it in the title beside
Please select the skin you would like to use. Maybe have it appear  
after

the user selects a new skin.

Finally for post 0.95, I think we should make the skin and plugin dialog  
look
about the same. This isn't very hard as it requires mainly moving a  
punch of

pack commands around. I'll add it to wiki.


Jerome, you said you wanted to review all previous mails on the subject
and see what's missing before the 0.95 release, did you do it ? if yes,
can we get a summary of it ? Iremember you forwarded some emails saying
has it been done?, I'll look into that myself (too busy with the job  
for

today, maybe tonight)
but if you ALREADY have a list, it would be nice to share it.

Thanks,
KaKaRoTo





--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


Hi,
I just commited a 'fix' to the commonly happening bug of the 'invalid  
command name ::MSN::SB...
I noticed they come from everywhere in the code, but the last two procs in  
the stack trace are cmsn_reconnect and chatTo.

I checked, msn_reconnect is call only from chatTo.
chatTo either creates an SB, or makes sure the SB is still in a connected  
state by calling cmsn_reconnect.
to use an old SB instead of creating a new one, it calls SBFor, which  
itself does a if {catch [$sb cget -stat]} (the call that causes the  
'invalid command' and thus makes sure that the SB command still exists...
problem is that it seems from the SBFor that checks for it to the  
cmsn_reconnect, there is a race condition and the SB gets deleted at the  
same time.

What I did to fix it is a
if { $sb == 0 || [catch {cmsn_reconnect $sb }] } {
createNewSB

...
cmsn_reconnect $sb
}


which means if there was no SB, it will enter the if and create a new one,  
if there was an SB, it will call the cmsn_reconnect proc, if it failed to  
reconnect it, it will enter the if, and create a new SB again and recall  
cmsn_reconnect...


I hope it fixes the bug, I just want some of you to massively test playing  
with chatwindows/SBs to make sure I didn't break anything.. the logic  
seems right, I need someone to test the logic though...


Thanks,
KaKaRoTo


On Fri, 02 Dec 2005 22:10:25 -0500, Youness Alaoui  
[EMAIL PROTECTED] wrote:



Hi,
I've been adding the refuse video conversation and send webcam  
invitation thing, but I got into a problem...
imagine, you send a video conversation, it gets canceled, you get a  
webcam invitation, you accept it, and bam, you're sending your webcam...
Where in the whole process did the other user ACCEPT your video  
invitation 
I'm tired and my gf is pissed at me because I was in front of the PC the  
whole afternoon, so I'll leave the thinking to you... other than that, I  
think that theorically, I've already done what we requested... I just  
don't want to commit it...


KaKaRoTo

On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED]  
wrote:



On Friday 02 December 2005 08:32, Youness Alaoui wrote:
I do think it's a good idea, and should be a safe commit, so I suggest  
we
do it. But I don't want little things to be added each time and we'd  
end
up with no deadline for 0.95. So I say do it if you want and have  
time,
but if it's not done before we decide to get 0.95 out, we won't wait  
for

it to be done.
Done, points to http://amsn.sf.net/skins.php which is the page that the  
new

site has skins in. Currently it just forwards the browser to the skins
section in the PHPNuke.

Also the Skin dialog is a bit bigger than required. There is an empty  
space
under the OK button the size of the button itself. Does anyone else  
have it?


I tried to add a Restart aMSN for new skins label somewhere, but I am  
not
sure where. Any suggestions? I was thinking having it in the title  
beside
Please select the skin you would like to use. Maybe have it appear  
after

the user selects a new skin.

Finally for post 0.95, I think we should make the skin and plugin  
dialog look
about the same. This isn't very hard as it requires mainly moving a  
punch of

pack commands around. I'll add it to wiki.


Jerome, you said you wanted to review all previous mails on the subject
and see what's missing before the 0.95 release, did you do it ? if yes,
can we get a summary of it ? Iremember you forwarded some emails saying
has it been done?, I'll look into that myself (too busy with the job  
for

today, maybe tonight)
but if you ALREADY have a list, it would be nice to share it.

Thanks,
KaKaRoTo









--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

On Friday 02 December 2005 19:06, Youness Alaoui wrote:
 On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED] wrote:
  On Friday 02 December 2005 08:32, Youness Alaoui wrote:
  I do think it's a good idea, and should be a safe commit, so I suggest
  we
  do it. But I don't want little things to be added each time and we'd end
  up with no deadline for 0.95. So I say do it if you want and have
  time,
  but if it's not done before we decide to get 0.95 out, we won't wait for
  it to be done.
 
  Done, points to http://amsn.sf.net/skins.php which is the page that the
  new
  site has skins in. Currently it just forwards the browser to the skins
  section in the PHPNuke.

 thank you

  Also the Skin dialog is a bit bigger than required. There is an empty
  space
  under the OK button the size of the button itself. Does anyone else have
  it?

 Yes I have it and I like it! it's better than having it all squashed up...
 it reminds me we should, before Monday, make the select plugins and the
 auto-updater and the Notes windows bigger...

I think it's too big. Could we maybe halve that space?

  I tried to add a Restart aMSN for new skins label somewhere, but I am
  not
  sure where. Any suggestions? I was thinking having it in the title beside
  Please select the skin you would like to use. Maybe have it appear
  after
  the user selects a new skin.

 humm.. you're right, there's no appropriate place to put it...
 I would suggest putting it in the upper frame, below the Please select
 the skin you would like to use, have it centered and have note that you
 may need to restart amsn to view the skin at its fullest, and make it
 red...

Done.

  Finally for post 0.95, I think we should make the skin and plugin dialog
  look
  about the same. This isn't very hard as it requires mainly moving a
  punch of
  pack commands around. I'll add it to wiki.

 good, ok, thanks.
 but, we might want to think of it as being part of the new preferences
 dialog...

I'll do it in case the preference dialog won't be finished for 0.96.

-- 
Karol Krizka


pgpe159s686AH.pgp
Description: PGP signature

Re: [Amsn-devel] Something else?!


On Fri, 02 Dec 2005 22:54:56 -0500, Karol Krizka [EMAIL PROTECTED] wrote:


On Friday 02 December 2005 19:06, Youness Alaoui wrote:
On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka [EMAIL PROTECTED]  
wrote:

 On Friday 02 December 2005 08:32, Youness Alaoui wrote:
 I do think it's a good idea, and should be a safe commit, so I  
suggest

 we
 do it. But I don't want little things to be added each time and we'd  
end

 up with no deadline for 0.95. So I say do it if you want and have
 time,
 but if it's not done before we decide to get 0.95 out, we won't wait  
for

 it to be done.

 Done, points to http://amsn.sf.net/skins.php which is the page that  
the

 new
 site has skins in. Currently it just forwards the browser to the skins
 section in the PHPNuke.

thank you

 Also the Skin dialog is a bit bigger than required. There is an empty
 space
 under the OK button the size of the button itself. Does anyone else  
have

 it?

Yes I have it and I like it! it's better than having it all squashed  
up...

it reminds me we should, before Monday, make the select plugins and the
auto-updater and the Notes windows bigger...


I think it's too big. Could we maybe halve that space?



don't know, I like it like that.. you can try to halve the space and see  
what it looks like and then decide whether you keep it like that or not.


 I tried to add a Restart aMSN for new skins label somewhere, but I  
am

 not
 sure where. Any suggestions? I was thinking having it in the title  
beside

 Please select the skin you would like to use. Maybe have it appear
 after
 the user selects a new skin.

humm.. you're right, there's no appropriate place to put it...
I would suggest putting it in the upper frame, below the Please select
the skin you would like to use, have it centered and have note that  
you

may need to restart amsn to view the skin at its fullest, and make it
red...


Done.


Thanks,

 Finally for post 0.95, I think we should make the skin and plugin  
dialog

 look
 about the same. This isn't very hard as it requires mainly moving a
 punch of
 pack commands around. I'll add it to wiki.

good, ok, thanks.
but, we might want to think of it as being part of the new preferences
dialog...


I'll do it in case the preference dialog won't be finished for 0.96.

as you wish, but whether you do it or not is not important, if it's in the  
wiki, then we're alright, sthat way it can be done later or not, we'll see  
as long as there's a trace of it.




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

I assigned Fred to do it, I found in my old mails a patch from june(yes!) for increasing the size of the notes window and we just forgot to commit the patch!Le 05-12-02 à 22:06, Youness Alaoui a écrit :Notes windows bigger...

Re: [Amsn-devel] Something else?!


I read what you said...And I just don't understand what you said!

You send a video conversation
--Since when do we support videoconversation?

It gets canceled?
--So what? it gets canceled, so we don't have a conversation

You get a webcam invitation, you accept it , and bam youre sending  
your webcam

--Where's the problem? You just accepted it?

Where in the whole process did the other user ACCEPT your video  
invitation 

--HUH??!!

Sorry I just don't understand AT ALL!

Le 05-12-02 à 22:10, Youness Alaoui a écrit :


Hi,
I've been adding the refuse video conversation and send webcam  
invitation thing, but I got into a problem...
imagine, you send a video conversation, it gets canceled, you get a  
webcam invitation, you accept it, and bam, you're sending your  
webcam...
Where in the whole process did the other user ACCEPT your video  
invitation 
I'm tired and my gf is pissed at me because I was in front of the  
PC the whole afternoon, so I'll leave the thinking to you... other  
than that, I think that theorically, I've already done what we  
requested... I just don't want to commit it...


KaKaRoTo

On Fri, 02 Dec 2005 21:46:41 -0500, Karol Krizka  
[EMAIL PROTECTED] wrote:



On Friday 02 December 2005 08:32, Youness Alaoui wrote:
I do think it's a good idea, and should be a safe commit, so I  
suggest we
do it. But I don't want little things to be added each time and  
we'd end
up with no deadline for 0.95. So I say do it if you want and  
have time,
but if it's not done before we decide to get 0.95 out, we won't  
wait for

it to be done.
Done, points to http://amsn.sf.net/skins.php which is the page  
that the new
site has skins in. Currently it just forwards the browser to the  
skins

section in the PHPNuke.

Also the Skin dialog is a bit bigger than required. There is an  
empty space
under the OK button the size of the button itself. Does anyone  
else have it?


I tried to add a Restart aMSN for new skins label somewhere, but  
I am not
sure where. Any suggestions? I was thinking having it in the title  
beside
Please select the skin you would like to use. Maybe have it  
appear after

the user selects a new skin.

Finally for post 0.95, I think we should make the skin and plugin  
dialog look
about the same. This isn't very hard as it requires mainly moving  
a punch of

pack commands around. I'll add it to wiki.

Jerome, you said you wanted to review all previous mails on the  
subject
and see what's missing before the 0.95 release, did you do it ?  
if yes,
can we get a summary of it ? Iremember you forwarded some emails  
saying
has it been done?, I'll look into that myself (too busy with  
the job for

today, maybe tonight)
but if you ALREADY have a list, it would be nice to share it.

Thanks,
KaKaRoTo





--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-11-29 Thread Juan Martín

2005/11/26, Youness Alaoui [EMAIL PROTECTED]:
 ok, here's the things I still think needs to be corrected before the
 release (minor things)... these things are what I noticed after extracting
 the deb file (make deb  dpkg -x -d dpkg amsn_0.95) :
 * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn-remote-CLI
 not just /usr/bin/amsn
 * there is a ~/msn/sndplay file that should be removed (Jerome ?)
 * when we create the deb file, there is a /usr/share/pixmaps/msn.png that
 points to the compile dir where the png file was :
 [EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
 total 0
 lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/amsn/amsn*
 [EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
 total 4
 lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png -
 /home/kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png

 you see, the bin points to the correct amsn file, but the msn.png points
 elsewhere .. I think it actually points to the temporary directory when
 the deb file was created...

 * In the lang directory, there are some files that should be removed :
 LANG-HOWTO
 genpage.c
 missing.py
 addkey.tcl
 lang1.tmpl
 lang2.tmpl
 lang3.tmpl
 langchk.sh
 sortlang
 complete.pl
 convert.tcl
 genlangfiles.c

 and when I say removed, I'm talking about 'not included in the package'
 only!
 * the AppMain.tcl file should be removed when we create a linux/windows
 package
 * amsn.desktop can be removed from the /usr/share/amsn/ directory...
 * the sxml.tcl file is made as executable, we should remove the executable
 flag...
 * These utils/ subdir should be removed, as they are not used yet :
 pixmapoption/   pixmapbutton/  pixmapprogbar/
 and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep, it
 seems it's only used in pixmapprogbar and pixmapbutton which are removed
 anyways...
 * the pixmaps in utils/pixmapscroll/horizontal and
 utils/pixmapscroll/vertical directories should be made skinable (although
 it might not be a good time to move all that)
 * the webcamsn.tcl file in utils/webcamsn should be removed since it was
 only used as a test.tcl file...
 * the utils/linux/capture/test.tcl file should be removed.
 * the libtray.so should have a pkgIndex.tcl file with it and we should do
 a package require instead of a load... (it might not be a good time to do
 it also)
 * fix the make deb so that it won't need to sign the deb file.. if it's
 needed to make an official release, then the package will have to do that
 additional step manually...
 I'll remind you of my problem :
 dpkg-deb: building package `amsn' in `../amsn_0.95cvs-20051126_i386.deb'.
 make[1]: Leaving directory `/home/kakaroto/msn/export'
   dpkg-genchanges -b
 dpkg-genchanges: binary-only upload - not including any source code
   signfile amsn_0.95cvs-20051126_i386.changes
 gpg: WARNING: unsafe permissions on configuration file
 `/home/kakaroto/.gnupg/gpg.conf'
 gpg: WARNING: unsafe enclosing directory permissions on configuration file
 `/home/kakaroto/.gnupg/gpg.conf'
 gpg: skipped Phil [EMAIL PROTECTED]: secret key not
 available
 gpg: [stdin]: clearsign failed: secret key not available


 The deb file seems to be created and perfectly 'healty', it just stays in
 the parent directory...

 * the control of the debian package might need some thing :
 conflicts: ccmsn
 depends: tcl8.4 tk8.4 tcltls


 * I'd also need someone to do the exact same thing with rpm files... I
 don't know how it works, but I'll see if I can extract the rpm to a
 directory...

you can do it with:

rpm2cpio yourarchive.rpm | cpio --extract --make-directories


 * we might need to check for this kind of things also in the src package
 (cvs export)..

 * one last thing... revert back the budy icons... please :(

 KaKaRoTo


 On Sat, 26 Nov 2005 10:57:31 -0500, Youness Alaoui
 [EMAIL PROTECTED] wrote:

  humm... well, even daily is ok, but in a digest, will we get the diff
  too ? yes, and that's the problem, it's a pain in the ass to go looking
  for the comments individually...
  anyways, now, I'm just looking at what CIA-13 has to say on the amsn IRC
  channel.. it gives me a summary
 
  KaKaRoTo
 
  On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier
  [EMAIL PROTECTED] wrote:
 
  I was going to say to go to:
  http://lists.sourceforge.net/lists/listinfo/amsn-commits
  and set your option to digest, but then realised the digest is daily
  instead
  of weekly.
 
  Lio.
 
  - Original Message -
  From: Youness Alaoui
 
  oups.. ok, sorry :)
  I don't read the commits because I filter them, get them to another
  directory (Opera names that a filter) and mark them as read.. if I
  don't,
  I'll have too much to look into and I don't have time to look at normal
  emails, so imagine with the commits...
  it would be nice to have a digest of all commits once per week so we can
  look at what was done, but only get the message that was sent, not the
  diff...
  maybe CIA would be a place to look at for

Re: [Amsn-devel] Something else?!

2005-11-29 Thread Le Philousophe - Phil

Done !
But I have troubles to install Debian I hope I will be able to fix the debian 
generation for the release... When is it ?? 1st December ??
Phil

Le Samedi 26 Novembre 2005 21:17, Youness Alaoui a écrit :
 On Sat, 26 Nov 2005 14:55:23 -0500, Jérôme Gagnon-Voyer

 [EMAIL PROTECTED] wrote:
  I think most of the things you said are for the makefile right?

 Yeah, I think so..

  Le 05-11-26 à 14:46, Youness Alaoui a écrit :
  ok, here's the things I still think needs to be corrected before
  the release (minor things)... these things are what I noticed after
  extracting the deb file (make deb  dpkg -x -d dpkg amsn_0.95) :
  * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn-remote-
  CLI not just /usr/bin/amsn
  * there is a ~/msn/sndplay file that should be removed (Jerome ?)
 
  You can remove it with  the makefile for Win and Linux but not yet
  from aMSN. This thing is used in only one place...alarm.tcl   Before,
  it was used to play sound everywhere in aMSN. But now I use quicktime
  for sound EXCEPT in alarm.tcl...why? This alarm.tcl file is such a
  mess, one day I took a full hour to try to figure out how to change
  things and..it's too hard!! I'll probably do it one day but man...who
  coded that?? LOL!!

 lol.. yeah, the alarm code was the first thing Burger coded (he didn't
 know tcl yet at that time) so that's probably why.. and it's very old code
 you know!
 but I though (and just checked, it's true) that the alarms code was
 modified and fixed and that now it uses the default procs from gui.tcl
 (play_snack, play_sound, play_loop).. so it should be compatible..
 I think all you need to change is the play_loop proc in gui.tcl in order
 to make it work, assuming that quicktime sound player supports looping or
 a way to get notified when the movie finishes...
 if you want to keep it, please move it to utils/macosx and change it's
 reference in here :
 [EMAIL PROTECTED]:~/msn$ grep sndplay *
 Makefile:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn amsn-remote
 amsn-remote-CLI amsn.desktop langlist
 Makefile.in:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn amsn-remote
 amsn-remote-CLI amsn.desktop langlist
 config.tcl: ::config::setKey soundcommand ./sndplay
 \$sound;#Soundplayer for Mac OS 10.3-10.4
 config.tcl: ::config::setKey
 soundcommand ./sndplay \$sound

  * when we create the deb file, there is a /usr/share/pixmaps/
  msn.png that points to the compile dir where the png file was :
  [EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
  total 0
  lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/
  amsn/amsn*
  [EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
  total 4
  lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png - /home/
  kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png
 
  you see, the bin points to the correct amsn file, but the msn.png
  points elsewhere .. I think it actually points to the temporary
  directory when the deb file was created...
 
  * In the lang directory, there are some files that should be removed :
  LANG-HOWTO
  genpage.c
  missing.py
  addkey.tcl
  lang1.tmpl
  lang2.tmpl
  lang3.tmpl
  langchk.sh
  sortlang
  complete.pl
  convert.tcl
  genlangfiles.c
 
  and when I say removed, I'm talking about 'not included in the
  package' only!
  * the AppMain.tcl file should be removed when we create a linux/
  windows package
 
  I confirm
 
  * amsn.desktop can be removed from the /usr/share/amsn/ directory...
  * the sxml.tcl file is made as executable, we should remove the
  executable flag...
  * These utils/ subdir should be removed, as they are not used yet :
  pixmapoption/   pixmapbutton/  pixmapprogbar/
  and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep,
  it seems it's only used in pixmapprogbar and pixmapbutton which are
  removed anyways...
  * the pixmaps in utils/pixmapscroll/horizontal and utils/
  pixmapscroll/vertical directories should be made skinable (although
  it might not be a good time to move all that)
  * the webcamsn.tcl file in utils/webcamsn should be removed since
  it was only used as a test.tcl file...
 
  So it's not used anymore? When we ask people to run the test.tcl
  file, it's not used?

 well.. we shouldn't ask people to do it... we won't say go find a
 test.tcl file in the directory /usr/share/amsn/utils/linux/capture .. if
 you have it installed there... and even if, we can't say ok, thx, I fixed
 it, update and recompile... those people will have a release, it
 shouldn't contain any test files or temp files...
 also, we never need to test the webcamsn stuff anymore.. and concerning
 the capture extension, we won't say try test.tcl, we'll say open the
 menu.. and click on webcam configuration setup item to get the same
 functionality as the test... (the webcam wizard code is almost a copy
 paste of the test.tcl code)

  * the utils/linux/capture/test.tcl file should be

Re: [Amsn-devel] Something else?!

I will probably take some time to reread the last week messages (yeah  
all of them :P) to be sure we don't forget anything that you  
suggested and said. So IMO we should still be able to take the cvs  
snapshot of 1st december. Anyway, whatever you do, we will always  
have new commits.


One thing remaining is dealing with clientid for videoconferencing  
for MSN 7.5 users

Le 05-11-29 à 16:19, Youness Alaoui a écrit :


Hi,
no, it's not for 1st december, it is preferable for 1st december,  
and that was in case we think nothing more is to be done, but if  
you're still active , I think it can be delayed a little...
the 1st december thing was because we though there is nothing more  
to be done, so I said let's wait until 1st december , JUST IN  
CASE... now, I suggest we wait 2 or 3 days after nothing is  
commited... just to make sure we forget nothing..


But I suggest we start the release process soon... Lee, how is the  
website going ? is it finally finished ? stable ? what is the  
status on trac (although not mandatory for now)...

anything else to be done ?
I tried working on the cam2mpeg, I'm able to compile it but it  
doesn't seem to work, I think it's because avcodec changed (again)  
their whole API...


KaKaRoTo

On Tue, 29 Nov 2005 14:19:52 -0500, Le Philousophe - Phil  
[EMAIL PROTECTED] wrote:



Done !
But I have troubles to install Debian I hope I will be able to fix  
the debian

generation for the release... When is it ?? 1st December ??
Phil

Le Samedi 26 Novembre 2005 21:17, Youness Alaoui a écrit :

On Sat, 26 Nov 2005 14:55:23 -0500, Jérôme Gagnon-Voyer

[EMAIL PROTECTED] wrote:
 I think most of the things you said are for the makefile right?

Yeah, I think so..

 Le 05-11-26 à 14:46, Youness Alaoui a écrit :
 ok, here's the things I still think needs to be corrected before
 the release (minor things)... these things are what I noticed  
after
 extracting the deb file (make deb  dpkg -x -d dpkg  
amsn_0.95) :
 * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn- 
remote-

 CLI not just /usr/bin/amsn
 * there is a ~/msn/sndplay file that should be removed (Jerome ?)

 You can remove it with  the makefile for Win and Linux but not yet
 from aMSN. This thing is used in only one place...alarm.tcl
Before,
 it was used to play sound everywhere in aMSN. But now I use  
quicktime

 for sound EXCEPT in alarm.tcl...why? This alarm.tcl file is such a
 mess, one day I took a full hour to try to figure out how to  
change
 things and..it's too hard!! I'll probably do it one day but  
man...who

 coded that?? LOL!!

lol.. yeah, the alarm code was the first thing Burger coded (he  
didn't
know tcl yet at that time) so that's probably why.. and it's very  
old code

you know!
but I though (and just checked, it's true) that the alarms code was
modified and fixed and that now it uses the default procs from  
gui.tcl

(play_snack, play_sound, play_loop).. so it should be compatible..
I think all you need to change is the play_loop proc in gui.tcl  
in order
to make it work, assuming that quicktime sound player supports  
looping or

a way to get notified when the movie finishes...
if you want to keep it, please move it to utils/macosx and change  
it's

reference in here :
[EMAIL PROTECTED]:~/msn$ grep sndplay *
Makefile:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn amsn- 
remote

amsn-remote-CLI amsn.desktop langlist
Makefile.in:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn  
amsn-remote

amsn-remote-CLI amsn.desktop langlist
config.tcl: ::config::setKey soundcommand ./ 
sndplay

\$sound;#Soundplayer for Mac OS 10.3-10.4
config.tcl: ::config::setKey
soundcommand ./sndplay \$sound

 * when we create the deb file, there is a /usr/share/pixmaps/
 msn.png that points to the compile dir where the png file was :
 [EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
 total 0
 lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/
 amsn/amsn*
 [EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
 total 4
 lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png - /home/
 kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/ 
msn.png


 you see, the bin points to the correct amsn file, but the msn.png
 points elsewhere .. I think it actually points to the temporary
 directory when the deb file was created...

 * In the lang directory, there are some files that should be  
removed :

 LANG-HOWTO
 genpage.c
 missing.py
 addkey.tcl
 lang1.tmpl
 lang2.tmpl
 lang3.tmpl
 langchk.sh
 sortlang
 complete.pl
 convert.tcl
 genlangfiles.c

 and when I say removed, I'm talking about 'not included in the
 package' only!
 * the AppMain.tcl file should be removed when we create a linux/
 windows package

 I confirm

 * amsn.desktop can be removed from the /usr/share/amsn/  
directory...

 * the sxml.tcl file is made as executable, we should remove the
 executable flag...
 * These utils/ subdir should be removed, as

Re: [Amsn-devel] Something else?!

2005-11-29 Thread Youness Alaoui


(This might be stupid)
I would like to suggest we either fix the problems with skins.. because  
now, from what I notice, if we change a skin, it doesn't completly change,  
some keys are not loaded (we should reload default keys before loading the  
skin), some pixmaps are not used... anyways, a few things I'm not sure  
they are right...
I may be the one who doesn't understand that the skin is supposed to be  
like that, but anyways, I would sugggest that if the fix is easy, then do  
it, if not, I would have a msg_box say We suggest you relaunch amsn to  
view the skin correctly.


as I said, it might be stupid... sorry if that's the case..

KaKaRoTo

On Tue, 29 Nov 2005 19:09:17 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:


I will probably take some time to reread the last week messages (yeah  
all of them :P) to be sure we don't forget anything that you suggested  
and said. So IMO we should still be able to take the cvs snapshot of 1st  
december. Anyway, whatever you do, we will always have new commits.


One thing remaining is dealing with clientid for videoconferencing for  
MSN 7.5 users

Le 05-11-29 à 16:19, Youness Alaoui a écrit :


Hi,
no, it's not for 1st december, it is preferable for 1st december, and  
that was in case we think nothing more is to be done, but if you're  
still active , I think it can be delayed a little...
the 1st december thing was because we though there is nothing more to  
be done, so I said let's wait until 1st december , JUST IN CASE...  
now, I suggest we wait 2 or 3 days after nothing is commited... just to  
make sure we forget nothing..


But I suggest we start the release process soon... Lee, how is the  
website going ? is it finally finished ? stable ? what is the status on  
trac (although not mandatory for now)...

anything else to be done ?
I tried working on the cam2mpeg, I'm able to compile it but it doesn't  
seem to work, I think it's because avcodec changed (again) their whole  
API...


KaKaRoTo

On Tue, 29 Nov 2005 14:19:52 -0500, Le Philousophe - Phil  
[EMAIL PROTECTED] wrote:



Done !
But I have troubles to install Debian I hope I will be able to fix the  
debian

generation for the release... When is it ?? 1st December ??
Phil

Le Samedi 26 Novembre 2005 21:17, Youness Alaoui a écrit :

On Sat, 26 Nov 2005 14:55:23 -0500, Jérôme Gagnon-Voyer

[EMAIL PROTECTED] wrote:
 I think most of the things you said are for the makefile right?

Yeah, I think so..

 Le 05-11-26 à 14:46, Youness Alaoui a écrit :
 ok, here's the things I still think needs to be corrected before
 the release (minor things)... these things are what I noticed after
 extracting the deb file (make deb  dpkg -x -d dpkg  
amsn_0.95) :
 * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn- 
remote-

 CLI not just /usr/bin/amsn
 * there is a ~/msn/sndplay file that should be removed (Jerome ?)

 You can remove it with  the makefile for Win and Linux but not yet
 from aMSN. This thing is used in only one place...alarm.tcl
Before,
 it was used to play sound everywhere in aMSN. But now I use  
quicktime

 for sound EXCEPT in alarm.tcl...why? This alarm.tcl file is such a
 mess, one day I took a full hour to try to figure out how to change
 things and..it's too hard!! I'll probably do it one day but  
man...who

 coded that?? LOL!!

lol.. yeah, the alarm code was the first thing Burger coded (he didn't
know tcl yet at that time) so that's probably why.. and it's very old  
code

you know!
but I though (and just checked, it's true) that the alarms code was
modified and fixed and that now it uses the default procs from gui.tcl
(play_snack, play_sound, play_loop).. so it should be compatible..
I think all you need to change is the play_loop proc in gui.tcl in  
order
to make it work, assuming that quicktime sound player supports  
looping or

a way to get notified when the movie finishes...
if you want to keep it, please move it to utils/macosx and change it's
reference in here :
[EMAIL PROTECTED]:~/msn$ grep sndplay *
Makefile:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn amsn- 
remote

amsn-remote-CLI amsn.desktop langlist
Makefile.in:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn  
amsn-remote

amsn-remote-CLI amsn.desktop langlist
config.tcl: ::config::setKey soundcommand ./ 
sndplay

\$sound;#Soundplayer for Mac OS 10.3-10.4
config.tcl: ::config::setKey
soundcommand ./sndplay \$sound

 * when we create the deb file, there is a /usr/share/pixmaps/
 msn.png that points to the compile dir where the png file was :
 [EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
 total 0
 lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/
 amsn/amsn*
 [EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
 total 4
 lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png - /home/
 kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png

 you see, the bin points to the correct amsn

Re: [Amsn-devel] Something else?!

Le 05-11-29 à 19:46, Youness Alaoui a écrit :(This might be stupid) I would like to suggest we either fix the problems with skins.. because now, from what I notice, if we change a skin, it doesn't completly change, some keys are not loaded (we should reload default keys before loading the skin)Yes we should. But we said that 6 months ago, and nobody did it. So that's surely not during a feature freeze that we will do it. That's our fault if we didn't do it, if we start with that, there's surely a whole lot of things we should do and we didn't do ;-) I play with skins each week and a lot of mac users are playing with skins on the Mac Forum and skins are one of the few things that I didn't receive any bugs or specific complain :P No it's not perfect but it's not far from great. , some pixmaps are not used... anyways, a few things I'm not sure they are right...Tom did a cleanup of unused pixmaps during the time you didn't read the amsn-commits :P No problem here. I may be the one who doesn't understand that the skin is supposed to be like that, but anyways, I would sugggest that if the fix is easy, then do it, if not, I would have a msg_box say "We suggest you relaunch amsn to view the skin correctly". as I said, it might be stupid... sorry if that's the case.. It's not stupid but like I said, many people plays with skins every week (all kinds of old and new skins) and nobody noticed theses problems with the keys if we switch to a skin that have missing keys. This is a very small issue and the important is that the default skin use all the keys. Unless someone is able to make an easy fix, I would recommend to hold it instead of making a big change, skin system is working without any bug and I think it's fair to keep it like that :P We also have to accept the fact that this release is not perfect as we wanted it but we decided to finally release it even if it's not perfect (but even that, it's a very good stable release, we didn't rush things).

Re: [Amsn-devel] Something else?!

2005-11-29 Thread Youness Alaoui

On Tue, 29 Nov 2005 21:45:53 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:




Le 05-11-29 à 21:34, Youness Alaoui a écrit :


hehe, no I didn't mean that, that would be too much trouble, like I
said, just a little thing to do because now we're in a feature
freeze...
what I meant by some pixmaps are not used was that some pixmaps
would remain from the old skin instead of the skin system using the
new skin's pixmaps...



I don't get that one :P If the skin has the pixmaps, the skin system
takes it, if not, it takes the pixmaps from the default skin. That's
the correct behavior.



ok, that's probably why I said that I may say something stupid :P forget  
about it :)



Anyway, as you said, it's not a big deal to just add a message_box
(but still, it can be feel as a pain for some people to always click
on OK when switching skin, even if they just make a preview of the
skin), I left the decision to others, I'm 50-50 :P


to preview a skin, you enable the preview checkbox... to click ok, is  
not that bad if anyways, you have to restart amsn...

it's a suggestion, maybe other devs' opinions would help us decide...

--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!


Comments on that?

We ship it or not?
Le 05-11-27 à 10:22, Karel Demeyer a écrit :

I didn't follow the activities, so maybe it's already done, please  
don't

shoot me, but I'd like to make sure the inkdraw plugin I made won't be
shipped with 0.95, as the inksending/receiving doesn't work all  
time...

I don't want to be bothered with bugreports about it yet you see ;)

Great work guys!

Karel





On za, 2005-11-26 at 14:46 -0500, Youness Alaoui wrote:

ok, here's the things I still think needs to be corrected before the
release (minor things)... these things are what I noticed after  
extracting

the deb file (make deb  dpkg -x -d dpkg amsn_0.95) :
* I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn- 
remote-CLI

not just /usr/bin/amsn
* there is a ~/msn/sndplay file that should be removed (Jerome ?)
* when we create the deb file, there is a /usr/share/pixmaps/ 
msn.png that

points to the compile dir where the png file was :
[EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
total 0
lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/ 
amsn/amsn*

[EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
total 4
lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png -
/home/kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/ 
msn.png


you see, the bin points to the correct amsn file, but the msn.png  
points
elsewhere .. I think it actually points to the temporary directory  
when

the deb file was created...

* In the lang directory, there are some files that should be  
removed :

LANG-HOWTO
genpage.c
missing.py
addkey.tcl
lang1.tmpl
lang2.tmpl
lang3.tmpl
langchk.sh
sortlang
complete.pl
convert.tcl
genlangfiles.c

and when I say removed, I'm talking about 'not included in the  
package'

only!
* the AppMain.tcl file should be removed when we create a linux/ 
windows

package
* amsn.desktop can be removed from the /usr/share/amsn/ directory...
* the sxml.tcl file is made as executable, we should remove the  
executable

flag...
* These utils/ subdir should be removed, as they are not used yet :
pixmapoption/   pixmapbutton/  pixmapprogbar/
and maybe scalable-bg/ too, we'll need to ask Tom, but from a  
grep, it
seems it's only used in pixmapprogbar and pixmapbutton which are  
removed

anyways...
* the pixmaps in utils/pixmapscroll/horizontal and
utils/pixmapscroll/vertical directories should be made skinable  
(although

it might not be a good time to move all that)
* the webcamsn.tcl file in utils/webcamsn should be removed since  
it was

only used as a test.tcl file...
* the utils/linux/capture/test.tcl file should be removed.
* the libtray.so should have a pkgIndex.tcl file with it and we  
should do
a package require instead of a load... (it might not be a good  
time to do

it also)
* fix the make deb so that it won't need to sign the deb file.. if  
it's
needed to make an official release, then the package will have to  
do that

additional step manually...
I'll remind you of my problem :
dpkg-deb: building package `amsn' in `../ 
amsn_0.95cvs-20051126_i386.deb'.

make[1]: Leaving directory `/home/kakaroto/msn/export'
  dpkg-genchanges -b
dpkg-genchanges: binary-only upload - not including any source code
  signfile amsn_0.95cvs-20051126_i386.changes
gpg: WARNING: unsafe permissions on configuration file
`/home/kakaroto/.gnupg/gpg.conf'
gpg: WARNING: unsafe enclosing directory permissions on  
configuration file

`/home/kakaroto/.gnupg/gpg.conf'
gpg: skipped Phil [EMAIL PROTECTED]: secret  
key not

available
gpg: [stdin]: clearsign failed: secret key not available


The deb file seems to be created and perfectly 'healty', it just  
stays in

the parent directory...

* the control of the debian package might need some thing :
conflicts: ccmsn
depends: tcl8.4 tk8.4 tcltls


* I'd also need someone to do the exact same thing with rpm  
files... I

don't know how it works, but I'll see if I can extract the rpm to a
directory...

* we might need to check for this kind of things also in the src  
package

(cvs export)..

* one last thing... revert back the budy icons... please :(

KaKaRoTo


On Sat, 26 Nov 2005 10:57:31 -0500, Youness Alaoui
[EMAIL PROTECTED] wrote:

humm... well, even daily is ok, but in a digest, will we get the  
diff
too ? yes, and that's the problem, it's a pain in the ass to go  
looking

for the comments individually...
anyways, now, I'm just looking at what CIA-13 has to say on the  
amsn IRC

channel.. it gives me a summary

KaKaRoTo

On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier
[EMAIL PROTECTED] wrote:


I was going to say to go to:
http://lists.sourceforge.net/lists/listinfo/amsn-commits
and set your option to digest, but then realised the digest is  
daily

instead
of weekly.

Lio.

- Original Message -
From: Youness Alaoui

oups.. ok, sorry :)
I don't read the commits because I filter them, get them to another
directory (Opera names that a filter) and mark them as read.. if I
don't,
I'll have too much to look into

Re: [Amsn-devel] Something else?!

Well anyway we already show a message so it's a good thing to show a good message with good instructions to follow. Thanks for your idea, in most of softwares we get a INSTALL file so newbies will have less problem (hopefully...).DONELe 05-11-29 à 23:00, Youness Alaoui a écrit :Hey, the "unable to load TkCximage" message is an incredible problem.. google for "tkcximage", you'll see how many threads there are on that problem, I just added an INSTALL file with basic instructions on how to compile/install amsn... I'd like you guys to review add, add things to it, maybe rephrase some things, whatever, I think it's basic, simple but complete... anyways.. my suggestion would be : should we add after the "unable to load TkCximage" another message that says "Please compile amsn first, instructions on how to compile are located in the file INSTALL".. or something like that... what do you think ?  maybe it's not necessary since we'll ship binary releases... but just an idea...

Re: [Amsn-devel] Something else?!

2005-11-27 Thread Alvaro J. Iradier

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Youness Alaoui wrote:
 * In the lang directory, there are some files that should be removed :
 LANG-HOWTO ---
 genpage.c
 missing.py   
 addkey.tcl
 lang1.tmpl
 lang2.tmpl
 lang3.tmpl
 langchk.sh
 sortlang  ---
 complete.pl
 convert.tcl 
 genlangfiles.c

 and when I say removed, I'm talking about 'not included in the package' 
 only!

Hi, I don't see a problem on keeping the marked ones on the package.
They are small, and they can be useful for the users to learn about
language translation without need to get the CVS package.

Greets.
- --

()
  Alvaro J. Iradier Muro
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDiaACoDlUrRluukQRAh17AKDn01pjHPRq22MYWG9hpgLURD1VRACeJOGT
61Oh+minGsIKh9HeplgMB6E=
=Xze8
-END PGP SIGNATURE-


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-11-27 Thread Sander Hoentjen

On Sat, 2005-11-26 at 23:01 +0100, Le Philousophe - Phil wrote:
 Hi,
 coming back from two days where I was away... and so much reading !! :p
 I have no time today to do that but tomorrow I will make that.
 I am trying to install bochs to let me to have a Debian within my FC4 !!
Use Xen instead ;)



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-11-26 Thread Youness Alaoui

humm... well, even daily is ok, but in a digest, will we get the diff too  
? yes, and that's the problem, it's a pain in the ass to go looking for  
the comments individually...
anyways, now, I'm just looking at what CIA-13 has to say on the amsn IRC  
channel.. it gives me a summary


KaKaRoTo

On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier  
[EMAIL PROTECTED] wrote:



I was going to say to go to:
http://lists.sourceforge.net/lists/listinfo/amsn-commits
and set your option to digest, but then realised the digest is daily  
instead

of weekly.

Lio.

- Original Message -
From: Youness Alaoui

oups.. ok, sorry :)
I don't read the commits because I filter them, get them to another
directory (Opera names that a filter) and mark them as read.. if I don't,
I'll have too much to look into and I don't have time to look at normal
emails, so imagine with the commits...
it would be nice to have a digest of all commits once per week so we can
look at what was done, but only get the message that was sent, not the
diff...
maybe CIA would be a place to look at for this thing, but I don't know if
they have a send me weekly summaries of the activities... I'll have to
look into that.

KaKaRoTo

On Fri, 25 Nov 2005 16:25:21 -0500, Jérôme Gagnon-Voyer
[EMAIL PROTECTED] wrote:


Hey, you should read the amsn-commits list, it was done on 17th
november ;-0

De :   [EMAIL PROTECTED]
Objet : [Amsn-commits] msn autoupdate.tcl,1.32,1.33
Date : 17 novembre 2005 22:07:57 HNE
À :   [EMAIL PROTECTED]

Update of /cvsroot/amsn/msn
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26417

Modified Files:
autoupdate.tcl
Log Message:
Fixed: autoupdate now checks for all 'sections' of release numbers

Index: autoupdate.tcl
===
RCS file: /cvsroot/amsn/msn/autoupdate.tcl,v
retrieving revision 1.32
retrieving revision 1.33
diff -C2 -d -r1.32 -r1.33
*** autoupdate.tcl 17 Sep 2005 16:32:31 - 1.32
--- autoupdate.tcl 18 Nov 2005 03:07:55 - 1.33
***
*** 530,539 
   set yourver [split $version .]

! if { [lindex $lastver 0]  [lindex $yourver 0] } {
! set newer 1
! } else {
! # Major version is at least the same
! if { [lindex $lastver 1]  [lindex $yourver 1] } {
   set newer 1
   }
   }
--- 530,537 
   set yourver [split $version .]

! for {set x 0} {$x[llength $lastver]} {incr x} {
! if {[lindex $lastver $x]  [lindex $yourver $x]} {
   set newer 1
+ break
   }
   }



Le 05-11-25 à 16:12, Youness Alaoui a écrit :



one more TODO item and pretty important :
Make sure the auto-updater recognizes 0.94  0.95  0.95.1  0.95.2
 0.95.10  0.96

KKRT

On Fri, 25 Nov 2005 15:56:18 -0500, Youness Alaoui
[EMAIL PROTECTED] wrote:


Yes, I do agree.. as I said, December 1st, if nothing major
appears, we release 0.95... if we can't fix the bug by december
1st, we'll use the orkaround and that's it...
Harry, maybe you didn't get the latest change because the
anonymous CVS wasn't up to date... JUST IN CASE, I would suggest
you get the latest cvs again and do a `make clean all`... if the
bug still happens, i would really appreciate it if you did like
you did at first : give us the backtrace of the segfault ...
without the backtrace from gdb, we can't find where the new bug
happens...

Thanks,
KaKaRoTo

On Fri, 25 Nov 2005 15:06:19 -0500, Jérôme Gagnon-Voyer
[EMAIL PROTECTED] wrote:


Don't forget we just have to re-enable the check for the PWC driver
at the start of aMSN. That way, the config buttons will just be
disabled so nobody will get a seg fault, that's not a serious bug
for a release because we can prevent the bug from happening (yes
it's
better to fix the bug but at least we can prevent it)
Le 05-11-25 à 14:09, Harry Vennik a écrit :


That is to say, we thought it would be fixed now, but it is not.
At this moment I don't think anyone understands why the change by
Phil didn't
fix it. I tried to find it out this morning, but no success. I will
try again
tomorrow, if I don't get it again, and neither does anyone else,
then I think
we should not have this prevent us from releasing 0.95, even though
I regard
it as quite a serious bug.








---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!

Re: [Amsn-devel] Something else?!

2005-11-26 Thread Youness Alaoui

ok, here's the things I still think needs to be corrected before the  
release (minor things)... these things are what I noticed after extracting  
the deb file (make deb  dpkg -x -d dpkg amsn_0.95) :
* I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn-remote-CLI  
not just /usr/bin/amsn

* there is a ~/msn/sndplay file that should be removed (Jerome ?)
* when we create the deb file, there is a /usr/share/pixmaps/msn.png that  
points to the compile dir where the png file was :

[EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
total 0
lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/amsn/amsn*
[EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
total 4
lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png -  
/home/kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png


you see, the bin points to the correct amsn file, but the msn.png points  
elsewhere .. I think it actually points to the temporary directory when  
the deb file was created...


* In the lang directory, there are some files that should be removed :
LANG-HOWTO
genpage.c
missing.py
addkey.tcl
lang1.tmpl
lang2.tmpl
lang3.tmpl
langchk.sh
sortlang
complete.pl
convert.tcl
genlangfiles.c

and when I say removed, I'm talking about 'not included in the package'  
only!
* the AppMain.tcl file should be removed when we create a linux/windows  
package

* amsn.desktop can be removed from the /usr/share/amsn/ directory...
* the sxml.tcl file is made as executable, we should remove the executable  
flag...

* These utils/ subdir should be removed, as they are not used yet :
pixmapoption/   pixmapbutton/  pixmapprogbar/
and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep, it  
seems it's only used in pixmapprogbar and pixmapbutton which are removed  
anyways...
* the pixmaps in utils/pixmapscroll/horizontal and  
utils/pixmapscroll/vertical directories should be made skinable (although  
it might not be a good time to move all that)
* the webcamsn.tcl file in utils/webcamsn should be removed since it was  
only used as a test.tcl file...

* the utils/linux/capture/test.tcl file should be removed.
* the libtray.so should have a pkgIndex.tcl file with it and we should do  
a package require instead of a load... (it might not be a good time to do  
it also)
* fix the make deb so that it won't need to sign the deb file.. if it's  
needed to make an official release, then the package will have to do that  
additional step manually...

I'll remind you of my problem :
dpkg-deb: building package `amsn' in `../amsn_0.95cvs-20051126_i386.deb'.
make[1]: Leaving directory `/home/kakaroto/msn/export'
 dpkg-genchanges -b
dpkg-genchanges: binary-only upload - not including any source code
 signfile amsn_0.95cvs-20051126_i386.changes
gpg: WARNING: unsafe permissions on configuration file  
`/home/kakaroto/.gnupg/gpg.conf'
gpg: WARNING: unsafe enclosing directory permissions on configuration file  
`/home/kakaroto/.gnupg/gpg.conf'
gpg: skipped Phil [EMAIL PROTECTED]: secret key not  
available

gpg: [stdin]: clearsign failed: secret key not available


The deb file seems to be created and perfectly 'healty', it just stays in  
the parent directory...


* the control of the debian package might need some thing :
conflicts: ccmsn
depends: tcl8.4 tk8.4 tcltls


* I'd also need someone to do the exact same thing with rpm files... I  
don't know how it works, but I'll see if I can extract the rpm to a  
directory...


* we might need to check for this kind of things also in the src package  
(cvs export)..


* one last thing... revert back the budy icons... please :(

KaKaRoTo


On Sat, 26 Nov 2005 10:57:31 -0500, Youness Alaoui  
[EMAIL PROTECTED] wrote:


humm... well, even daily is ok, but in a digest, will we get the diff  
too ? yes, and that's the problem, it's a pain in the ass to go looking  
for the comments individually...
anyways, now, I'm just looking at what CIA-13 has to say on the amsn IRC  
channel.. it gives me a summary


KaKaRoTo

On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier  
[EMAIL PROTECTED] wrote:



I was going to say to go to:
http://lists.sourceforge.net/lists/listinfo/amsn-commits
and set your option to digest, but then realised the digest is daily  
instead

of weekly.

Lio.

- Original Message -
From: Youness Alaoui

oups.. ok, sorry :)
I don't read the commits because I filter them, get them to another
directory (Opera names that a filter) and mark them as read.. if I  
don't,

I'll have too much to look into and I don't have time to look at normal
emails, so imagine with the commits...
it would be nice to have a digest of all commits once per week so we can
look at what was done, but only get the message that was sent, not the
diff...
maybe CIA would be a place to look at for this thing, but I don't know  
if

they have a send me weekly summaries of the activities... I'll have to
look into that.

KaKaRoTo

On Fri, 25 Nov 2005 16:25:21 -0500, Jérôme Gagnon-Voyer

Re: [Amsn-devel] Something else?!

2005-11-26 Thread Jérôme Gagnon-Voyer

I think most of the things you said are for the makefile right? Le 05-11-26 à 14:46, Youness Alaoui a écrit :ok, here's the things I still think needs to be corrected before the release (minor things)... these things are what I noticed after extracting the deb file (make deb  dpkg -x -d dpkg amsn_0.95) : * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn-remote-CLI not just /usr/bin/amsn * there is a ~/msn/sndplay file that should be removed (Jerome ?)You can remove it with  the makefile for Win and Linux but not yet from aMSN. This thing is used in only one place...alarm.tcl   Before, it was used to play sound everywhere in aMSN. But now I use quicktime for sound EXCEPT in alarm.tcl...why? This alarm.tcl file is such a mess, one day I took a full hour to try to figure out how to change things and..it's too hard!! I'll probably do it one day but man...who coded that?? LOL!! * when we create the deb file, there is a /usr/share/pixmaps/msn.png that points to the compile dir where the png file was : [EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l total 0 lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/amsn/amsn* [EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/ total 4 lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png - /home/kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png  you see, the bin points to the correct amsn file, but the msn.png points elsewhere .. I think it actually points to the temporary directory when the deb file was created...  * In the lang directory, there are some files that should be removed : LANG-HOWTO genpage.c missing.py addkey.tcl lang1.tmpl lang2.tmpl lang3.tmpl langchk.sh sortlang complete.pl convert.tcl genlangfiles.c  and when I say removed, I'm talking about 'not included in the package' only! * the AppMain.tcl file should be removed when we create a linux/windows packageI confirm * amsn.desktop can be removed from the /usr/share/amsn/ directory... * the sxml.tcl file is made as executable, we should remove the executable flag... * These utils/ subdir should be removed, as they are not used yet : pixmapoption/   pixmapbutton/  pixmapprogbar/ and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep, it seems it's only used in pixmapprogbar and pixmapbutton which are removed anyways... * the pixmaps in utils/pixmapscroll/horizontal and utils/pixmapscroll/vertical directories should be made skinable (although it might not be a good time to move all that) * the webcamsn.tcl file in utils/webcamsn should be removed since it was only used as a test.tcl file...So it's not used anymore? When we ask people to run the test.tcl file, it's not used? * the utils/linux/capture/test.tcl file should be removed. * the libtray.so should have a pkgIndex.tcl file with it and we should do a package require instead of a load... (it might not be a good time to do it also) * fix the make deb so that it won't need to sign the deb file.. if it's needed to make an official release, then the package will have to do that additional step manually... I'll remind you of my problem : dpkg-deb: building package `amsn' in `../amsn_0.95cvs-20051126_i386.deb'. make[1]: Leaving directory `/home/kakaroto/msn/export'  dpkg-genchanges -b dpkg-genchanges: binary-only upload - not including any source code  signfile amsn_0.95cvs-20051126_i386.changes gpg: WARNING: unsafe permissions on configuration file `/home/kakaroto/.gnupg/gpg.conf' gpg: WARNING: unsafe enclosing directory permissions on configuration file `/home/kakaroto/.gnupg/gpg.conf' gpg: skipped "Phil [EMAIL PROTECTED]": secret key not available gpg: [stdin]: clearsign failed: secret key not available   The deb file seems to be created and perfectly 'healty', it just stays in the parent directory...  * the control of the debian package might need some thing : conflicts: ccmsn depends: tcl8.4 tk8.4 tcltls   * I'd also need someone to do the exact same thing with rpm files... I don't know how it works, but I'll see if I can extract the rpm to a directory...  * we might need to check for this kind of things also in the src package (cvs export)..  * one last thing... revert back the budy icons... please :( hehe

Re: [Amsn-devel] Something else?!

2005-11-26 Thread Youness Alaoui

On Sat, 26 Nov 2005 14:55:23 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



I think most of the things you said are for the makefile right?


Yeah, I think so..


Le 05-11-26 à 14:46, Youness Alaoui a écrit :


ok, here's the things I still think needs to be corrected before
the release (minor things)... these things are what I noticed after
extracting the deb file (make deb  dpkg -x -d dpkg amsn_0.95) :
* I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn-remote-
CLI not just /usr/bin/amsn
* there is a ~/msn/sndplay file that should be removed (Jerome ?)

You can remove it with  the makefile for Win and Linux but not yet
from aMSN. This thing is used in only one place...alarm.tcl   Before,
it was used to play sound everywhere in aMSN. But now I use quicktime
for sound EXCEPT in alarm.tcl...why? This alarm.tcl file is such a
mess, one day I took a full hour to try to figure out how to change
things and..it's too hard!! I'll probably do it one day but man...who
coded that?? LOL!!


lol.. yeah, the alarm code was the first thing Burger coded (he didn't  
know tcl yet at that time) so that's probably why.. and it's very old code  
you know!
but I though (and just checked, it's true) that the alarms code was  
modified and fixed and that now it uses the default procs from gui.tcl  
(play_snack, play_sound, play_loop).. so it should be compatible..
I think all you need to change is the play_loop proc in gui.tcl in order  
to make it work, assuming that quicktime sound player supports looping or  
a way to get notified when the movie finishes...
if you want to keep it, please move it to utils/macosx and change it's  
reference in here :

[EMAIL PROTECTED]:~/msn$ grep sndplay *
Makefile:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn amsn-remote  
amsn-remote-CLI amsn.desktop langlist
Makefile.in:FILES_TO_INSTALL := *.tcl hotmlog.htm sndplay amsn amsn-remote  
amsn-remote-CLI amsn.desktop langlist
config.tcl: ::config::setKey soundcommand ./sndplay  
\$sound;#Soundplayer for Mac OS 10.3-10.4
config.tcl: ::config::setKey  
soundcommand ./sndplay \$sound




* when we create the deb file, there is a /usr/share/pixmaps/
msn.png that points to the compile dir where the png file was :
[EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
total 0
lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/
amsn/amsn*
[EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
total 4
lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png - /home/
kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png

you see, the bin points to the correct amsn file, but the msn.png
points elsewhere .. I think it actually points to the temporary
directory when the deb file was created...

* In the lang directory, there are some files that should be removed :
LANG-HOWTO
genpage.c
missing.py
addkey.tcl
lang1.tmpl
lang2.tmpl
lang3.tmpl
langchk.sh
sortlang
complete.pl
convert.tcl
genlangfiles.c

and when I say removed, I'm talking about 'not included in the
package' only!
* the AppMain.tcl file should be removed when we create a linux/
windows package

I confirm

* amsn.desktop can be removed from the /usr/share/amsn/ directory...
* the sxml.tcl file is made as executable, we should remove the
executable flag...
* These utils/ subdir should be removed, as they are not used yet :
pixmapoption/   pixmapbutton/  pixmapprogbar/
and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep,
it seems it's only used in pixmapprogbar and pixmapbutton which are
removed anyways...
* the pixmaps in utils/pixmapscroll/horizontal and utils/
pixmapscroll/vertical directories should be made skinable (although
it might not be a good time to move all that)
* the webcamsn.tcl file in utils/webcamsn should be removed since
it was only used as a test.tcl file...

So it's not used anymore? When we ask people to run the test.tcl
file, it's not used?


well.. we shouldn't ask people to do it... we won't say go find a  
test.tcl file in the directory /usr/share/amsn/utils/linux/capture .. if  
you have it installed there... and even if, we can't say ok, thx, I fixed  
it, update and recompile... those people will have a release, it  
shouldn't contain any test files or temp files...
also, we never need to test the webcamsn stuff anymore.. and concerning  
the capture extension, we won't say try test.tcl, we'll say open the  
menu.. and click on webcam configuration setup item to get the same  
functionality as the test... (the webcam wizard code is almost a copy  
paste of the test.tcl code)



* the utils/linux/capture/test.tcl file should be removed.
* the libtray.so should have a pkgIndex.tcl file with it and we
should do a package require instead of a load... (it might not be a
good time to do it also)
* fix the make deb so that it won't need to sign the deb file.. if
it's needed to make an official release, then the package will have
to do that additional

Re: [Amsn-devel] Something else?!

2005-11-26 Thread Le Philousophe - Phil

Hi,
coming back from two days where I was away... and so much reading !! :p
I have no time today to do that but tomorrow I will make that.
I am trying to install bochs to let me to have a Debian within my FC4 !!
I will be able to test all we need !!
Phil
P.S. The maintner of debian package gave me its version of control file so 
there is a thing about ccmsn (not conflicts but replaces or sth like that).

Le Samedi 26 Novembre 2005 20:46, Youness Alaoui a écrit :
 ok, here's the things I still think needs to be corrected before the
 release (minor things)... these things are what I noticed after extracting
 the deb file (make deb  dpkg -x -d dpkg amsn_0.95) :
 * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn-remote-CLI
 not just /usr/bin/amsn
 * there is a ~/msn/sndplay file that should be removed (Jerome ?)
 * when we create the deb file, there is a /usr/share/pixmaps/msn.png that
 points to the compile dir where the png file was :
 [EMAIL PROTECTED]:~/msn/export/pkg/usr$ ls bin/ -l
 total 0
 lrwxrwxrwx  1 kakaroto kakaroto 18 Nov 26 14:14 amsn - ../share/amsn/amsn*
 [EMAIL PROTECTED]:~/msn/export/pkg/usr/share$ ls -l pixmaps/
 total 4
 lrwxrwxrwx  1 kakaroto kakaroto 72 Nov 26 14:14 msn.png -
 /home/kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/msn.png

 you see, the bin points to the correct amsn file, but the msn.png points
 elsewhere .. I think it actually points to the temporary directory when
 the deb file was created...

 * In the lang directory, there are some files that should be removed :
 LANG-HOWTO
 genpage.c
 missing.py
 addkey.tcl
 lang1.tmpl
 lang2.tmpl
 lang3.tmpl
 langchk.sh
 sortlang
 complete.pl
 convert.tcl
 genlangfiles.c

 and when I say removed, I'm talking about 'not included in the package'
 only!
 * the AppMain.tcl file should be removed when we create a linux/windows
 package
 * amsn.desktop can be removed from the /usr/share/amsn/ directory...
 * the sxml.tcl file is made as executable, we should remove the executable
 flag...
 * These utils/ subdir should be removed, as they are not used yet :
 pixmapoption/   pixmapbutton/  pixmapprogbar/
 and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep, it
 seems it's only used in pixmapprogbar and pixmapbutton which are removed
 anyways...
 * the pixmaps in utils/pixmapscroll/horizontal and
 utils/pixmapscroll/vertical directories should be made skinable (although
 it might not be a good time to move all that)
 * the webcamsn.tcl file in utils/webcamsn should be removed since it was
 only used as a test.tcl file...
 * the utils/linux/capture/test.tcl file should be removed.
 * the libtray.so should have a pkgIndex.tcl file with it and we should do
 a package require instead of a load... (it might not be a good time to do
 it also)
 * fix the make deb so that it won't need to sign the deb file.. if it's
 needed to make an official release, then the package will have to do that
 additional step manually...
 I'll remind you of my problem :
 dpkg-deb: building package `amsn' in `../amsn_0.95cvs-20051126_i386.deb'.
 make[1]: Leaving directory `/home/kakaroto/msn/export'
   dpkg-genchanges -b
 dpkg-genchanges: binary-only upload - not including any source code
   signfile amsn_0.95cvs-20051126_i386.changes
 gpg: WARNING: unsafe permissions on configuration file
 `/home/kakaroto/.gnupg/gpg.conf'
 gpg: WARNING: unsafe enclosing directory permissions on configuration file
 `/home/kakaroto/.gnupg/gpg.conf'
 gpg: skipped Phil [EMAIL PROTECTED]: secret key not
 available
 gpg: [stdin]: clearsign failed: secret key not available


 The deb file seems to be created and perfectly 'healty', it just stays in
 the parent directory...

 * the control of the debian package might need some thing :
 conflicts: ccmsn
 depends: tcl8.4 tk8.4 tcltls


 * I'd also need someone to do the exact same thing with rpm files... I
 don't know how it works, but I'll see if I can extract the rpm to a
 directory...

 * we might need to check for this kind of things also in the src package
 (cvs export)..

 * one last thing... revert back the budy icons... please :(

 KaKaRoTo


 On Sat, 26 Nov 2005 10:57:31 -0500, Youness Alaoui

 [EMAIL PROTECTED] wrote:
  humm... well, even daily is ok, but in a digest, will we get the diff
  too ? yes, and that's the problem, it's a pain in the ass to go looking
  for the comments individually...
  anyways, now, I'm just looking at what CIA-13 has to say on the amsn IRC
  channel.. it gives me a summary
 
  KaKaRoTo
 
  On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier
 
  [EMAIL PROTECTED] wrote:
  I was going to say to go to:
  http://lists.sourceforge.net/lists/listinfo/amsn-commits
  and set your option to digest, but then realised the digest is daily
  instead
  of weekly.
 
  Lio.
 
  - Original Message -
  From: Youness Alaoui
 
  oups.. ok, sorry :)
  I don't read the commits because I filter them, get them to another
  directory (Opera names that a filter) and mark them as

Re: [Amsn-devel] Something else?!


hello?!
Le 05-11-24 à 17:25, Jérôme Gagnon-Voyer a écrit :

So...is there something else before the release? We have a basic- 
but fonctionnal-webcam wizard (to change device, choose options,  
see if we are firewalled), the segfault bug is fixed with PWC, the  
bugreport is in place and is working well...there's not a lot of  
bugs on the tracker (just strange bugs with snit or things like  
that), we did a cleanup on CVS tree...


So...I think this version is ready.


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  
SPLUNK!

http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-11-25 Thread Youness Alaoui

Sorry, I was about to answer right now, I was searching for the correct  
thread...
well, I don't think there's something else besides that the pwc driver  
still doesn't work, from what Harry said, the fix didn't fix it, it still  
seg faults... so we'll wait for this to be fixed...
in the meantime, I suggest intensive testing, and going through the list  
of bugs just to make sure it's fixed...
Aprat from that, I would like to suggest a full feature freeze (only bug  
correction) until december 1st.. that would give us 1 week to make sure  
everything is ok and to avoid any oups, we forgot to do this before  
releasing...
so everyone, this is a big annoucement : CVS source of december 1st will  
be the 0.95 release!!! wouhouuu!! ok.. this means that the 0.95 release  
won't occur before at least september 15th.. you ask why ? it's because we  
will take the december 1st CVS, do an export on it, we'll get our 0.95  
release, then we'll have to create all the packages, once the packages are  
created, there is the whole todo list for a release that we need to finish  
(changing the amsn.sf.net/amsn_latest page being the last one to do)..  
we'll have to upload the files to the SF release system (all packages at  
once), integrate the new website, make sure it works and no 404 errors,  
once everything is set up (which would take 1 to 2 weeks.. maybe less, who  
knows), THEN we'll change the amsn_latest page and do all the  
annoucements, at that point, 0.95 will be RELEASED!


My Thanks goes to everyone here (also users who contributed) for their  
hard work.


KaKaRoTo

On Fri, 25 Nov 2005 13:47:53 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



hello?!
Le 05-11-24 à 17:25, Jérôme Gagnon-Voyer a écrit :

So...is there something else before the release? We have a basic-but  
fonctionnal-webcam wizard (to change device, choose options, see if we  
are firewalled), the segfault bug is fixed with PWC, the bugreport is  
in place and is working well...there's not a lot of bugs on the tracker  
(just strange bugs with snit or things like that), we did a cleanup on  
CVS tree...


So...I think this version is ready.


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Le 05-11-25 à 14:27, Youness Alaoui a écrit :Sorry, I was about to answer right now, I was searching for the correct thread... well, I don't think there's something else besides that the pwc driver still doesn't work, from what Harry said, the fix didn't fix it, it still seg faults... so we'll wait for this to be fixed... in the meantime, I suggest intensive testing, and going through the list of bugs just to make sure it's fixed...I checked for the last week and except for the listdevice bug, it should be good. Aprat from that, I would like to suggest a full feature freeze (only bug correction) until december 1st.. that would give us 1 week to make sure everything is ok and to avoid any "oups, we forgot to do this before releasing"... so everyone, this is a big annoucement : CVS source of december 1st will be the 0.95 release!!! wouhouuu!! ok.. this means that the 0.95 release won't occur before at least DECEMBERr 15th.. you ask why ? it's because we will take the december 1st CVS, do an export on it, we'll get our 0.95 release, then we'll have to create all the packages, once the packages are created, there is the whole todo list for a release that we need to finish (changing the amsn.sf.net/amsn_latest page being the last one to do).. we'll have to upload the files to the SF release system (all packages at once), integrate the new website, make sure it works and no 404 errors, once everything is set up (which would take 1 to 2 weeks.. maybe less, who knows), THEN we'll change the amsn_latest page and do all the annoucements, at that point, 0.95 will be RELEASED! Well you're the maintener, so you decide the date ;-) Just to say that I'm ready ASAP, more we delay, more the exams are coming, and my time is limited by the exams. So if you decide you have some free hours before 1st december, let me know. The sooner is the better.

Re: [Amsn-devel] Something else?!

2005-11-25 Thread Harry Vennik

Op donderdag 24 november 2005 23:25, schreef Jérôme Gagnon-Voyer:
 So...is there something else before the release? We have a basic-but
 fonctionnal-webcam wizard (to change device, choose options, see if
 we are firewalled), the segfault bug is fixed with PWC,
That is to say, we thought it would be fixed now, but it is not.
At this moment I don't think anyone understands why the change by Phil didn't 
fix it. I tried to find it out this morning, but no success. I will try again 
tomorrow, if I don't get it again, and neither does anyone else, then I think 
we should not have this prevent us from releasing 0.95, even though I regard 
it as quite a serious bug.

 the bugreport is in place and is working well...there's not a lot of bugs on
 the tracker (just strange bugs with snit or things like that), we did a
 cleanup on CVS tree...

 So...I think this version is ready.
At least it gets real close by now.



 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through log
 files for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
 http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

Don't forget we just have to re-enable the check for the PWC driver at the start of aMSN. That way, the config buttons will just be disabled so nobody will get a seg fault, that's not a "serious bug" for a release because we can prevent the bug from happening (yes it's better to fix the bug but at least we can prevent it)Le 05-11-25 à 14:09, Harry Vennik a écrit :That is to say, we thought it would be fixed now, but it is not. At this moment I don't think anyone understands why the change by Phil didn't  fix it. I tried to find it out this morning, but no success. I will try again  tomorrow, if I don't get it again, and neither does anyone else, then I think  we should not have this prevent us from releasing 0.95, even though I regard  it as quite a serious bug.

Re: [Amsn-devel] Something else?!

2005-11-25 Thread Youness Alaoui


ll

On Fri, 25 Nov 2005 15:13:10 -0500, Rafael Rodríguez  
[EMAIL PROTECTED] wrote:



hello! :)

how u doing?

El Viernes, 25 de Noviembre de 2005 19:47, Jérôme Gagnon-Voyer escribió:

hello?!

Le 05-11-24 à 17:25, Jérôme Gagnon-Voyer a écrit :
 So...is there something else before the release? We have a basic-
 but fonctionnal-webcam wizard (to change device, choose options,
 see if we are firewalled), the segfault bug is fixed with PWC, the
 bugreport is in place and is working well...there's not a lot of
 bugs on the tracker (just strange bugs with snit or things like
 that), we did a cleanup on CVS tree...

 So...I think this version is ready.


 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through
 log files
 for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD
 SPLUNK!
 http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
 ___
 Amsn-devel mailing list
 Amsn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amsn-devel

---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems?  Stop!  Download the new AJAX search engine that  
makes

searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=Click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel




--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!

2005-11-25 Thread Youness Alaoui

Yes, I do agree.. as I said, December 1st, if nothing major appears, we  
release 0.95... if we can't fix the bug by december 1st, we'll use the  
orkaround and that's it...
Harry, maybe you didn't get the latest change because the anonymous CVS  
wasn't up to date... JUST IN CASE, I would suggest you get the latest cvs  
again and do a `make clean all`... if the bug still happens, i would  
really appreciate it if you did like you did at first : give us the  
backtrace of the segfault ...

without the backtrace from gdb, we can't find where the new bug happens...

Thanks,
KaKaRoTo

On Fri, 25 Nov 2005 15:06:19 -0500, Jérôme Gagnon-Voyer  
[EMAIL PROTECTED] wrote:



Don't forget we just have to re-enable the check for the PWC driver
at the start of aMSN. That way, the config buttons will just be
disabled so nobody will get a seg fault, that's not a serious bug
for a release because we can prevent the bug from happening (yes it's
better to fix the bug but at least we can prevent it)
Le 05-11-25 à 14:09, Harry Vennik a écrit :


That is to say, we thought it would be fixed now, but it is not.
At this moment I don't think anyone understands why the change by
Phil didn't
fix it. I tried to find it out this morning, but no success. I will
try again
tomorrow, if I don't get it again, and neither does anyone else,
then I think
we should not have this prevent us from releasing 0.95, even though
I regard
it as quite a serious bug.






--
KaKaRoTo


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Re: [Amsn-devel] Something else?!