Page 1 of 1
3.0 Plans October 10, 2009
#1
Posted 10 October 2009 - 07:42 PM
2.1 isn't even out yet and I'm already planning ahead for 3.0!
The version number will shoot all the way up to 3.0 because it is going to be a massive update. Here are some of the planned updates:
1. Running inside Messenger, no more extra process using added resources
2. Interface to edit WLM UIB which will allow people to edit the WLM UI easily (especially addon developers)
3. Migration of main engine to C# language
4. Migration of hook engine to C# language (it's currently C++)
5. Make the project open source (under GPL licence) to encourage other developers to give input and provide code/fix bugs
6. No more proxy connection system. Instead there will be an internal Winsock/WinHttp hooks (no more Firewall issues!)
7. Upgrade to use .Net 3.0 Framework
8. Make the UI in WPF
These are just some of the ideas that I'm planning for version 3.0. Of course it's a BIG project, so during the development stage there will be updates to 2.1.
Also, with the intoduction of Windows Live Messenger 2009 the user interface changed from an XML system to a (much faster) binary system (you can think of it as 'compiled' XML). This disabled almost everyone from editing the WLM interface because it became far too difficult. As 3.0 will have a UIB editor for plugin developers (and myself) I will release an open source UIB resource editor so things like A-Patch can become useful again (if it were to use the code/libraries I provice).
The version number will shoot all the way up to 3.0 because it is going to be a massive update. Here are some of the planned updates:
1. Running inside Messenger, no more extra process using added resources
2. Interface to edit WLM UIB which will allow people to edit the WLM UI easily (especially addon developers)
3. Migration of main engine to C# language
4. Migration of hook engine to C# language (it's currently C++)
5. Make the project open source (under GPL licence) to encourage other developers to give input and provide code/fix bugs
6. No more proxy connection system. Instead there will be an internal Winsock/WinHttp hooks (no more Firewall issues!)
7. Upgrade to use .Net 3.0 Framework
8. Make the UI in WPF
These are just some of the ideas that I'm planning for version 3.0. Of course it's a BIG project, so during the development stage there will be updates to 2.1.
Also, with the intoduction of Windows Live Messenger 2009 the user interface changed from an XML system to a (much faster) binary system (you can think of it as 'compiled' XML). This disabled almost everyone from editing the WLM interface because it became far too difficult. As 3.0 will have a UIB editor for plugin developers (and myself) I will release an open source UIB resource editor so things like A-Patch can become useful again (if it were to use the code/libraries I provice).
#14
Posted 14 October 2009 - 09:13 PM
Matt, on 10 October 2009 - 10:42 AM, said:
1. Running inside Messenger, no more extra process using added resources
6. No more proxy connection system. Instead there will be an internal Winsock/WinHttp hooks (no more Firewall issues!)
6. No more proxy connection system. Instead there will be an internal Winsock/WinHttp hooks (no more Firewall issues!)
These ideas will increase the number of MD users for sure
Matt, on 10 October 2009 - 10:42 AM, said:
2. Interface to edit WLM UIB which will allow people to edit the WLM UI easily (especially addon developers)
Also, with the intoduction of Windows Live Messenger 2009 the user interface changed from an XML system to a (much faster) binary system (you can think of it as 'compiled' XML). This disabled almost everyone from editing the WLM interface because it became far too difficult. As 3.0 will have a UIB editor for plugin developers (and myself) I will release an open source UIB resource editor so things like A-Patch can become useful again (if it were to use the code/libraries I provice).
Also, with the intoduction of Windows Live Messenger 2009 the user interface changed from an XML system to a (much faster) binary system (you can think of it as 'compiled' XML). This disabled almost everyone from editing the WLM interface because it became far too difficult. As 3.0 will have a UIB editor for plugin developers (and myself) I will release an open source UIB resource editor so things like A-Patch can become useful again (if it were to use the code/libraries I provice).
I think this is the feature you should focuse on now, because modifing the UI is the base to reintroduce old MD options that many users miss.
In particular, looking at the feedback on the public discussion forum, it's evident that the new MD bar is not very appreciated (by the ones who don't use FB or simply use a skin): so, IMHO reintroducing a MD button like the Plus! Live one trough a specific option should be the first thing to do for the next version!
Page 1 of 1

Sign In
Register
Help



MultiQuote