(I answered Mirko's mail, scroll down)
Added:
- Check whether a newly created profile's config.xml exists (someone
copied the directory but didn't add it to profiles)
0.98 TODO:
- Add missing pixmaps to minimal skin and make sure tab flickering is
visible
- Fix MSNP2P stuff that broke with WLM 2009
- Option to integrate webcam in the chatwindow (needed for maemo)
- Finish VoIP UI
- Small annoyance: when a CW gets opened because they nudge you, you don't
see their DP
- Apply patch from PEACEYALL's thread
- N810: Bind menu button to show right click menu
- Check whether a newly created profile's config.xml exists (someone
copied the directory but didn't add it to profiles)
Square87's stuff
- then i have to test somethings on CW
- and i want to draw ListChoose in canvas (actually i am using
rendercontact and it takes 6 seconds to show about 500 contacts)
On Wed, 28 Jan 2009, Mirko Hansen wrote:
1. Concerning the portability of profiles: If you copy the directory of
a profile to the amsn home directory and forget to insert the new
profile into the profiles file, the config.xml of the new profile gets
overwritten when you enter the address manually. It shouldn't be a big
thing to check if the directory and the config.xml already exist and
then only insert them in the profiles and not overwrite the settings.
I'll have a look at it the next days if I have some free minutes.
That's a good point, yes. Adding it to the TODO.
2. Proposal concerning the auto update function: Shouldn't we extend the
auto update to be able to update files of the core? (Not for major
releases, only for minor updates!) I think it would be a good thing as
there are many protocol changes recently and it would help to fix minor
bugs a lot faster because we are able to spread single core files
instead of having to create a complete release that takes a lot of time.
What do you think?
It's a good thought in theory, but in fact there might be many more
changes reflected to other files as well. For example, imagine adding an
extra argument to a proc on protocol.tcl and the respective change on
gui.tcl regarding the way it's called. Then we distribute protocol.tcl
because of a later protocol change and suddenly the "stable" revision
bugs. We'd need to distribute the patch instead, or think of a smarter way
to do it.
It's a good idea however, and if someone can think of a better way to do
it, it would be nice to include it in 0.98.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
