From: Graham B. <gb...@ta...> - 2004-11-20 03:50:53
|
OK, I have run into an interesting one here. In the latest snapshot, if you try to load the chat window pref pane, it throws an exception "NSUnarchiver: inconsistency between written and read data for object 0xd46b80" when you run it on 10.2, but has no issue on 10.3. The problem is something with the nib, and I suspect it is the webkit portion, but I have no idea what needs to be done to fix the nib. Any ideas? ------------------------------------------------------------------ Graham Booker Texas A&M University gb...@ta... Graduate Student in ELEN ------------------------------------------------------------------ |
From: Jason T. <tow...@ma...> - 2004-11-20 08:02:34
|
On Nov 19, 2004, at 7:49 PM, Graham Booker wrote: > OK, I have run into an interesting one here. In the latest snapshot, > if you try to load the chat window pref pane, it throws an exception > "NSUnarchiver: inconsistency between written and read data for object > 0xd46b80" when you run it on 10.2, but has no issue on 10.3. The > problem is something with the nib, and I suspect it is the webkit > portion, but I have no idea what needs to be done to fix the nib. Any > ideas? Graham, I guess this must have been introduced when I fixed the strangeness in the nib which was almost hiding the scrollbar but not quite. I wonder if we reverted to the old nib version and edited it with 10.2 tools if that would fix things. I see you already checked in a fix which programmatically adds the WebView. -Jason |
From: Graham B. <gb...@ta...> - 2004-11-20 15:22:11
|
Don't worry about it now. I went through, deleted the WebView from the nib, and created a NSTabView instead. Then in the code, I alloc/init a webView and insert it into that tab view. That works on 10.2. When it comes down to it, 10.2 really doesn't like a WebView in the nib. The old WebStyles pref pane would work, but it crashes interface builder. Anyway, I have a system in place that works, so I guess we should just keep it. On Nov 20, 2004, at 2:02 AM, Jason Townsend wrote: > On Nov 19, 2004, at 7:49 PM, Graham Booker wrote: >> OK, I have run into an interesting one here. In the latest snapshot, >> if you try to load the chat window pref pane, it throws an exception >> "NSUnarchiver: inconsistency between written and read data for object >> 0xd46b80" when you run it on 10.2, but has no issue on 10.3. The >> problem is something with the nib, and I suspect it is the webkit >> portion, but I have no idea what needs to be done to fix the nib. >> Any ideas? > > Graham, I guess this must have been introduced when I fixed the > strangeness in the nib which was almost hiding the scrollbar but not > quite. > > I wonder if we reverted to the old nib version and edited it with 10.2 > tools if that would fix things. I see you already checked in a fix > which programmatically adds the WebView. > > -Jason ------------------------------------------------------------------ Graham Booker Texas A&M University gb...@ta... Graduate Student in ELEN ------------------------------------------------------------------ |
From: Alexei S. <isv...@sy...> - 2004-11-21 01:59:59
|
I'm wondering if there's anything in place in Fire to support MSN user Avatars - and if so what needs to be done to activate them. If they're not supported, is anything being done to address this? Thanks. -Myrd |
From: Jason T. <tow...@ma...> - 2004-11-22 00:35:46
|
On Nov 20, 2004, at 5:59 PM, Alexei Svitkine wrote: > I'm wondering if there's anything in place in Fire to support MSN user > Avatars - and if so what needs to be done to activate them. If they're > not supported, is anything being done to address this? Thanks. We don't currently support MSN buddy icons, however we have all the support infrastructure there to add that feature since we support buddy icons on AIM. There's a feature request for this here: [ 832575 ] MSN: Buddy Picture http://sourceforge.net/tracker/index.php? func=detail&aid=832575&group_id=33772&atid=409173 From Mark's last comment in the feature request: Any help that can be offered for this would be most appreciated -- MSN display pictures are dealt with via a different protocol from the standard MSN things. This would be a lot of work to implement. On the plus side, custom emoticons and file transfers behind NAT would be more or less "free" once this is implemented. This is something that I plan to look into in the future. -Jason |
From: Alexei S. <isv...@sy...> - 2004-11-22 23:24:59
|
> We don't currently support MSN buddy icons, however we have all the > support infrastructure there to add that feature since we support > buddy icons on AIM. > > There's a feature request for this here: > > [ 832575 ] MSN: Buddy Picture > http://sourceforge.net/tracker/index.php? > func=detail&aid=832575&group_id=33772&atid=409173 > > From Mark's last comment in the feature request: > > Any help that can be offered for this would be most appreciated -- MSN > display pictures are dealt with via a different protocol from > the standard MSN things. This would be a lot of work to implement. > On the plus side, custom emoticons and file transfers behind NAT would > be more or less "free" once this is implemented. > > This is something that I plan to look into in the future. > > -Jason > One IM client that's also GPL'd that implements this is Miranda IM - http://www.miranda-im.org/. Might be worthwhile to look at their source. IMO this a pretty big feature that Fire lacks. -Myrd |
From: Mark R. <bd...@us...> - 2004-11-23 00:53:12
Attachments:
smime.p7s
|
On Nov 23, 2004, at 12:24 PM, Alexei Svitkine wrote: >> We don't currently support MSN buddy icons, however we have all the >> support infrastructure there to add that feature since we support >> buddy icons on AIM. >> >> There's a feature request for this here: >> >> [ 832575 ] MSN: Buddy Picture >> http://sourceforge.net/tracker/index.php? >> func=detail&aid=832575&group_id=33772&atid=409173 >> >> From Mark's last comment in the feature request: >> >> Any help that can be offered for this would be most appreciated -- >> MSN display pictures are dealt with via a different protocol from >> the standard MSN things. This would be a lot of work to implement. >> On the plus side, custom emoticons and file transfers behind NAT >> would be more or less "free" once this is implemented. >> >> This is something that I plan to look into in the future. >> >> -Jason >> > > One IM client that's also GPL'd that implements this is Miranda IM - > http://www.miranda-im.org/. Might be worthwhile to look at their > source. IMO this a pretty big feature that Fire lacks. From my point of view MSN Avatars are relatively unimportant compared to some of the other issues that need to be resolved. The biggest issue is complete file transfer support, followed by all round stability. Put simply, it's not something that I personally care about, other than from a "it would be nice to support the same features as other clients" point of view. I initially started looking into supporting avatars and the related features (custom emoticons, file transfers when both parties are behind NAT, etc) several months ago. My conclusion was that the way the MSN library Fire uses is structured will make it difficult to add support for these features. I have put in a lot of work since then on refactoring the code to make adding support easier, but due to lack of time I've not started working on these features directly. While other GPL'd clients have support for MSN avatars, they share no MSN-related code with Fire and are typically structured in quite different manners. This means their code isn't easily portable or very useful as a reference. What's it going to take to get this feature implemented? Either someone who knows C++ and Objective-C who is willing to step up and submit patches, copious amounts of spare time on my behalf, or something miraculous to happen that convinces me to add it <wink>. I am more than willing to help out anyone who is interested in working on this feature. I hope this clarifies things a little bit more. Regards, Mark Rowe <http://bdash.net.nz/> |
From: Elektron <ele...@ya...> - 2004-11-24 11:01:43
|
> Any help that can be offered for this would be most appreciated -- MSN > display pictures are dealt with via a different protocol from > the standard MSN things. This would be a lot of work to implement. > On the plus side, custom emoticons and file transfers behind NAT would > be more or less "free" once this is implemented. How about any file transfers in the first place? (the only ones I've seen working are MSN transfers to Trillian users. I haven't tried ICQ or AIM much, though.) - Purr |
From: Mark R. <bd...@us...> - 2004-11-24 23:56:59
Attachments:
smime.p7s
|
On Nov 25, 2004, at 12:01 AM, Elektron wrote: >> Any help that can be offered for this would be most appreciated -- >> MSN display pictures are dealt with via a different protocol from >> the standard MSN things. This would be a lot of work to implement. >> On the plus side, custom emoticons and file transfers behind NAT >> would be more or less "free" once this is implemented. > > How about any file transfers in the first place? (the only ones I've > seen working are MSN transfers to Trillian users. I haven't tried ICQ > or AIM much, though.) From my email in this thread on the 23rd: > From my point of view MSN Avatars are relatively unimportant compared > to some of the other issues that need to be resolved. The biggest > issue is complete file transfer support, followed by all round > stability. Put simply, it's not something that I personally care > about, other than from a "it would be nice to support the same > features as other clients" point of view. Granted, the file transfers in Fire 1.0.x are a bit flakey. Current CVS has much improved file transfer support -- it's a lot less likely to crash when things don't work out. That said, it still only supports the case where the sender is not behind NAT or has port-forwarding of the relevant file transfer ports enabled. As I mentioned above, file transfers are a high priority of me to fix. I've been playing around with a few changes that increase transfer speeds while decreasing CPU usage -- hopefully I'll be able to work out the remaining kinks in the near future. Regards, Mark Rowe |