[Amsn-devel] Notification window.
Hi all :) I just want to say that i'll start to work on notification window to allow smileys and colored text in it. Just i did with topCW. If you are not agree or whatever: say it :P I'll update this post. Bye. Square87 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] [Amsn-commits] SF.net SVN: amsn: [9360] trunk/amsn/utils/base64/base64.tcl
Hi Billiob,
Did you report this also to the tcllib maintainers? If not, anyone with
a newer tcllib installation (and all Fedora users) will still have the
bug.
Sander
On Fri, 2008-01-11 at 16:00 -0800, [EMAIL PROTECTED] wrote:
Revision: 9360
http://amsn.svn.sourceforge.net/amsn/?rev=9360view=rev
Author: billiob
Date: 2008-01-11 16:00:22 -0800 (Fri, 11 Jan 2008)
Log Message:
---
fix bug #133
Modified Paths:
--
trunk/amsn/utils/base64/base64.tcl
Modified: trunk/amsn/utils/base64/base64.tcl
===
--- trunk/amsn/utils/base64/base64.tcl2008-01-11 19:09:32 UTC (rev
9359)
+++ trunk/amsn/utils/base64/base64.tcl2008-01-12 00:00:22 UTC (rev
9360)
@@ -280,6 +280,8 @@
binary scan $string c* X
set output
+
+ set nums
foreach x $X {
set bits [lindex $base64 $x]
@@ -298,17 +300,20 @@
# padding characters. If x=={}, we have 12 bits of input
# (enough for 1 8-bit output). If x!={}, we have 18 bits of
# input (enough for 2 8-bit outputs).
-
- foreach {v w z} $nums break
- set a [expr {($v 2) | (($w 0x30) 4)}]
-
- if {$z == {}} {
- append output [binary format c $a ]
- } else {
- set b [expr {(($w 0xF) 4) | (($z 0x3C) 2)}]
- append output [binary format cc $a $b]
- }
- break
+ # if string is just characters nor part of the Base64 alphabet
+ '='
+ # then nums is still .
+ if { $nums != } {
+ foreach {v w z} $nums break
+ set a [expr {($v 2) | (($w 0x30) 4)}]
+
+ if {$z == {}} {
+ append output [binary format c $a ]
+ } else {
+ set b [expr {(($w 0xF) 4) | (($z 0x3C)
2)}]
+ append output [binary format cc $a $b]
+ }
+ break
+ }
} else {
# RFC 2045 says that line breaks and other characters not part
# of the Base64 alphabet must be ignored, and that the decoder
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Amsn-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/amsn-commits
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
[Amsn-devel] Problem with tcllib from ubuntu repos
Hi,
when having installed tlcllib from the ubuntu 7.10 repos, I get this error
on login (trying to login):
11:53:12 -
11:53:12 GOT TCL/TK ERROR : {{The keyset handle mescapec is invalid!}}
Stack:
The keyset handle quot;mescapecquot; is invalid!
while executing
quot;error quot;The keyset handle \quot;$keyset\quot; is
invalid!quot;quot;
(procedure quot;blockquot; line 21)
invoked from within
quot;block $keyset $message 1 0quot;
(quot;ecbquot; arm line 2)
invoked from within
quot;switch -exact -- $mode {
ecb {
return [block $keyset $message 1 0]
}
cbc -
ofb -
cfb {
# Is the initialization/feedback v...quot;
(procedure quot;::des::encryptquot; line 2)
invoked from within
quot;::des::encrypt $key quot;${password}\nquot;quot;
(procedure quot;save_configquot; line 45)
invoked from within
quot;save_configquot;
(quot;usquot; arm line 15)
invoked from within
quot;switch -- [ns cget -stat] {
a {
#Send three first commands at same time, to be faster
if { [::config::getKey protocol] == 15 } {
::MSN::Wr...quot;
(procedure quot;cmsn_authquot; line 6)
invoked from within
quot;cmsn_auth $itemquot;
(quot;USRquot; arm line 2)
invoked from within
quot;switch -- [lindex $item 0] {
MSG {
cmsn_ns_msg $item $message
$message destroy
return 0
}
IPG {
::MSNMobile::MessageReceived quot;$messa...quot;
(procedure quot;cmsn_ns_handlerquot; line 4)
invoked from within
quot;cmsn_ns_handler $command $messagequot;
(quot;defaultquot; arm line 2)
invoked from within
quot;switch -- [lindex $command 0] {
UBM {
$self handleUBM $command $message
}
ADL {
$self handleADL $command
}
ILN {
cm...quot;
(procedure quot;::NS::Snit_methodhandleCommandquot; line 27)
invoked from within
quot;::NS::Snit_methodhandleCommand ::NS ::NS::Snit_inst1 ::ns ::ns {USR 16
OK [EMAIL PROTECTED] 1 0}quot;
(quot;uplevelquot; body line 1)
invoked from within
quot;uplevel 1 $command $argsquot;
invoked from within
quot;$options(-name) handleCommand $commandquot;
(procedure quot;::Connection::Snit_methodreceivedDataquot; line 48)
invoked from within
quot;::Connection::Snit_methodreceivedData ::Connection
::Connection::Snit_inst2 ::NS::Connection1 ::NS::Connection1quot;
(quot;uplevelquot; body line 1)
invoked from within
quot;uplevel 1 $command $argsquot;
invoked from within
quot;::NS::Connection1 receivedDataquot;
(quot;uplevelquot; body line 1)
invoked from within
quot;uplevel 1 $command $argsquot;
invoked from within
quot;ns receivedDataquot;
Code: NONE
11:53:12 -
11:53:12 AMSN version: 0.98b - AMSN date: 01/11/2008 19:07:15
11:53:12 TCL version : 8.4.15 - TK version : 8.4.15
11:53:12 tcl_platform array content : osVersion
2.6.22-14-genericbyteOrder littleEndian threaded 1 machine i686
platform unix os Linux user
scapor wordSize 4
11:53:12 -
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] [Amsn-commits] SF.net SVN: amsn: [9360] trunk/amsn/utils/base64/base64.tcl
On Jan 12, 2008 10:33 AM, Sander Hoentjen [EMAIL PROTECTED] wrote: Hi Billiob, Did you report this also to the tcllib maintainers? If not, anyone with a newer tcllib installation (and all Fedora users) will still have the bug. Sander Done with that bug report : http://sourceforge.net/tracker/index.php?func=detailaid=1869943group_id=12883atid=112883 Greets -- Boris FAURE (aka billiob) mail, jabber, msn : [EMAIL PROTECTED] No trees were killed in the sending of this message. However, a large number of electrons were terribly agitated. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] [Amsn-commits] SF.net SVN: amsn: [9360] trunk/amsn/utils/base64/base64.tcl
In theory, it shouldn't be sent upstream, since it's normal that if you have an invalid string, it should crash and tell you about it. Anyways, I fixed it in my yesterday's last commit (r936x something) i remove the leading '=' that M$ sends us sometimes in the b64 string, this way we don't give the invalid string to the b64 module.. You can read about it in the debian bugzilla at : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451679 KaKaRoTo On Sat, Jan 12, 2008 at 03:08:34PM +0100, Boris Faure (aka billiob) wrote: On Jan 12, 2008 10:33 AM, Sander Hoentjen [EMAIL PROTECTED] wrote: Hi Billiob, Did you report this also to the tcllib maintainers? If not, anyone with a newer tcllib installation (and all Fedora users) will still have the bug. Sander Done with that bug report : http://sourceforge.net/tracker/index.php?func=detailaid=1869943group_id=12883atid=112883 Greets -- Boris FAURE (aka billiob) mail, jabber, msn : [EMAIL PROTECTED] No trees were killed in the sending of this message. However, a large number of electrons were terribly agitated. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Notification window.
I don't agree well.. I don't like the idea because we want to have a bugfix release, and I don't want new features in... The MSNP15 was ok because everything was inside an 'if [config::getKey protocol] == 15' so it wouldn't affect anything else. But now, you're already working on it, and scapor is also doing some new stuff, so we're starting to get some improvements, and maybe that's all because we just released, we're not in a feature freeze, so everyone is happy and active... and I'm happy to see amsn-commits mailing list flooding my inbox, so I don't want to stop anyone from doing what they think should be done... Once we do the bugfix release, we might just apply patches one after the other into the 0_97 branch or something like that and release the version without any of the new 'unstable' functionality and leave the new features for 0.98. KaKaRoTo On Sat, Jan 12, 2008 at 09:20:47AM +, square87 wrote: Hi all :) I just want to say that i'll start to work on notification window to allow smileys and colored text in it. Just i did with topCW. If you are not agree or whatever: say it :P I'll update this post. Bye. Square87 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Notification window.
Why not branch now? Then new features can go to trunk, bug fixes go on the 0.97.1 branch? On 12 Jan 2008, at 20:26, Youness Alaoui wrote: I don't agree well.. I don't like the idea because we want to have a bugfix release, and I don't want new features in... The MSNP15 was ok because everything was inside an 'if [config::getKey protocol] == 15' so it wouldn't affect anything else. But now, you're already working on it, and scapor is also doing some new stuff, so we're starting to get some improvements, and maybe that's all because we just released, we're not in a feature freeze, so everyone is happy and active... and I'm happy to see amsn-commits mailing list flooding my inbox, so I don't want to stop anyone from doing what they think should be done... Once we do the bugfix release, we might just apply patches one after the other into the 0_97 branch or something like that and release the version without any of the new 'unstable' functionality and leave the new features for 0.98. KaKaRoTo On Sat, Jan 12, 2008 at 09:20:47AM +, square87 wrote: Hi all :) I just want to say that i'll start to work on notification window to allow smileys and colored text in it. Just i did with topCW. If you are not agree or whatever: say it :P I'll update this post. Bye. Square87 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Notification window.
Can be done, but we can also do it later... basically, why later.. only because the more I wait, the more chance someone else will do this boring task... lol no seriously, the reason is because if we have two branches now, we'll have to commit in both branches, which is difficult/complicated/blabla (and more of a PITA than difficult).. but in the end, before we release, we will still need to check every commit to make sure that we didn't forget any bugfix, then apply them on the branch (like we did for previous versions but skipped it for 0.97 since we had no new feature and it was a pain to do). so why waste time now, do the branch thing, then spend months developping and double-commiting, and in the end, review each commit and apply missing commits to the branch, while we could just develop normal, and in the end, review each commit and apply bugfix commits to the branch ? that was my idea, I could be wrong, in the end, do whatever you think is best. KaKaRoTo On Sat, Jan 12, 2008 at 08:32:46PM +, Tom Hennigan wrote: Why not branch now? Then new features can go to trunk, bug fixes go on the 0.97.1 branch? On 12 Jan 2008, at 20:26, Youness Alaoui wrote: I don't agree well.. I don't like the idea because we want to have a bugfix release, and I don't want new features in... The MSNP15 was ok because everything was inside an 'if [config::getKey protocol] == 15' so it wouldn't affect anything else. But now, you're already working on it, and scapor is also doing some new stuff, so we're starting to get some improvements, and maybe that's all because we just released, we're not in a feature freeze, so everyone is happy and active... and I'm happy to see amsn-commits mailing list flooding my inbox, so I don't want to stop anyone from doing what they think should be done... Once we do the bugfix release, we might just apply patches one after the other into the 0_97 branch or something like that and release the version without any of the new 'unstable' functionality and leave the new features for 0.98. KaKaRoTo On Sat, Jan 12, 2008 at 09:20:47AM +, square87 wrote: Hi all :) I just want to say that i'll start to work on notification window to allow smileys and colored text in it. Just i did with topCW. If you are not agree or whatever: say it :P I'll update this post. Bye. Square87 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Notification window.
The branch is here We only have to merge changes applied to the trunk to it In fact I hope we will do 0.97.1 without any P15 code ! Phil Youness Alaoui a écrit : Can be done, but we can also do it later... basically, why later.. only because the more I wait, the more chance someone else will do this boring task... lol no seriously, the reason is because if we have two branches now, we'll have to commit in both branches, which is difficult/complicated/blabla (and more of a PITA than difficult).. but in the end, before we release, we will still need to check every commit to make sure that we didn't forget any bugfix, then apply them on the branch (like we did for previous versions but skipped it for 0.97 since we had no new feature and it was a pain to do). so why waste time now, do the branch thing, then spend months developping and double-commiting, and in the end, review each commit and apply missing commits to the branch, while we could just develop normal, and in the end, review each commit and apply bugfix commits to the branch ? that was my idea, I could be wrong, in the end, do whatever you think is best. KaKaRoTo On Sat, Jan 12, 2008 at 08:32:46PM +, Tom Hennigan wrote: Why not branch now? Then new features can go to trunk, bug fixes go on the 0.97.1 branch? On 12 Jan 2008, at 20:26, Youness Alaoui wrote: I don't agree well.. I don't like the idea because we want to have a bugfix release, and I don't want new features in... The MSNP15 was ok because everything was inside an 'if [config::getKey protocol] == 15' so it wouldn't affect anything else. But now, you're already working on it, and scapor is also doing some new stuff, so we're starting to get some improvements, and maybe that's all because we just released, we're not in a feature freeze, so everyone is happy and active... and I'm happy to see amsn-commits mailing list flooding my inbox, so I don't want to stop anyone from doing what they think should be done... Once we do the bugfix release, we might just apply patches one after the other into the 0_97 branch or something like that and release the version without any of the new 'unstable' functionality and leave the new features for 0.98. KaKaRoTo On Sat, Jan 12, 2008 at 09:20:47AM +, square87 wrote: Hi all :) I just want to say that i'll start to work on notification window to allow smileys and colored text in it. Just i did with topCW. If you are not agree or whatever: say it :P I'll update this post. Bye. Square87 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Notification window.
and to also separate their commits, in order words don't do one commit containing multiple things like a bugfix and a feature... make them into 2 commits. On Sun, Jan 13, 2008 at 12:05:01AM +0100, Harry Vennik wrote: I agee to that. As we have to use the 0_97 branch anyway (and we do), why not skip the MSNP15-related commits... That means less work and a better bugfix release! Anyway, everyone should take care to have real descriptive commit messages, it will be easier then to select which commits should be merged into the 0_97 branch. Harry Op 12-jan-2008, om 23:25 heeft Philippe Valembois - Phil het volgende geschreven: The branch is here We only have to merge changes applied to the trunk to it In fact I hope we will do 0.97.1 without any P15 code ! Phil Youness Alaoui a écrit : Can be done, but we can also do it later... basically, why later.. only because the more I wait, the more chance someone else will do this boring task... lol no seriously, the reason is because if we have two branches now, we'll have to commit in both branches, which is difficult/ complicated/blabla (and more of a PITA than difficult).. but in the end, before we release, we will still need to check every commit to make sure that we didn't forget any bugfix, then apply them on the branch (like we did for previous versions but skipped it for 0.97 since we had no new feature and it was a pain to do). so why waste time now, do the branch thing, then spend months developping and double-commiting, and in the end, review each commit and apply missing commits to the branch, while we could just develop normal, and in the end, review each commit and apply bugfix commits to the branch ? that was my idea, I could be wrong, in the end, do whatever you think is best. KaKaRoTo On Sat, Jan 12, 2008 at 08:32:46PM +, Tom Hennigan wrote: Why not branch now? Then new features can go to trunk, bug fixes go on the 0.97.1 branch? On 12 Jan 2008, at 20:26, Youness Alaoui wrote: I don't agree well.. I don't like the idea because we want to have a bugfix release, and I don't want new features in... The MSNP15 was ok because everything was inside an 'if [config::getKey protocol] == 15' so it wouldn't affect anything else. But now, you're already working on it, and scapor is also doing some new stuff, so we're starting to get some improvements, and maybe that's all because we just released, we're not in a feature freeze, so everyone is happy and active... and I'm happy to see amsn-commits mailing list flooding my inbox, so I don't want to stop anyone from doing what they think should be done... Once we do the bugfix release, we might just apply patches one after the other into the 0_97 branch or something like that and release the version without any of the new 'unstable' functionality and leave the new features for 0.98. KaKaRoTo On Sat, Jan 12, 2008 at 09:20:47AM +, square87 wrote: Hi all :) I just want to say that i'll start to work on notification window to allow smileys and colored text in it. Just i did with topCW. If you are not agree or whatever: say it :P I'll update this post. Bye. Square87 -- --- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http:// sf.net/marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel --- -- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ marketplace ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source.
