Miranda NG:About: Difference between revisions

From Miranda NG
Jump to navigation Jump to search
(Start to translate)
(MRA is deprecated)
(33 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Languages/About}}
<languages/>
<translate>
<!--T:1-->
'''Miranda NG''' (Next Generation) is a successor of a popular multi-protocol instant messaging client for Windows – Miranda IM.
'''Miranda NG''' (Next Generation) is a successor of a popular multi-protocol instant messaging client for Windows – Miranda IM.


== Protocol Support ==
<!--T:2-->
* {{Plugin/en|AIM}} (AOL Instant Messenger)
Miranda NG is distributed under [[License|GNU General Public License]].
* {{Plugin/en|EmLanProto|Em-LAN}}
</translate>
* {{Plugin/en|Facebook}}
* {{Plugin/en|GG|Gadu-Gadu}}
* {{Plugin/en|ICQ}}
* {{Plugin/en|IRC}} (Internet Relay Chat)
* {{Plugin/en|Jabber}}
* {{Plugin/en|MRA}} (Mail.ru Agent)
* {{Plugin/en|MSN}}
* {{Plugin/en|Omegle}}
* {{Plugin/en|Tlen}}
* {{Plugin/en|Twitter}}
* {{Plugin/en|XFire}}
* {{Plugin/en|Yahoo}}


== Supported Operating Systems ==
__TOC__
Windows 2000 / 2003 / XP / Vista / 7 / 8


== History ==
<translate>
There was
== Protocol support == <!--T:3-->
In the spring of 2012 the development of Miranda IM came into a stalemate:
</translate>
{{Plugins|form=links|type=protocol
|d_EmLanProto = (E-mage LAN)
|d_GG = (Gadu-Gadu)
|d_IRC = (Internet Relay Chat)
|d_Jabber = (XMPP)
}}


# Принятая (и по сегодняшний день) модель разработки Миранды оказалась полностью нежизнеспособной по следующим причинам:
<translate>
#* Изменениям в ядре требовалось порядка полутора лет, чтобы быть подхваченными разработчиками плагинов и быть, наконец-то, доведенными до конечных пользователей. В результате возникающие задержки получались огромными.
== Supported operating systems == <!--T:4-->
#* Исходный код плагинов был раскидан по десяткам репозиториев, а для многих плагинов (актуальный) исходный код был вообще недоступен. Это ограничивало или вообще делало невозможным аудит кода плагинов со стороны участником команды. Соответственно, код некоторых плагинов содержит нерабочий, неэффективный или откровенно ошибочный код, и никто не может на это повлиять.
</translate>
#* Существовал огромный воз проблем с совместимостью между различными версиями ядра Миранды и даже между версиями отдельных плагинов. Особенно это касалось поддержки Unicode, которая в Miranda IM так и не доведена до конца.
Windows 2003 / XP SP3 / Vista / 7 / 8 / 10.
# Сложился четко созревший конфликт между двумя оставшимися на тот момент активными разработчиками Миранды: {{Developer|ghazan|Георгием Хазаном}} (ghazan) и {{Developer|borkra|Борисом Красновским}} (borkra), последней каплей которого стал откат Борисом фикса для совершенной им ошибки под тем предлогом, что в комментарии к коммиту был употреблено английское причастие ''borkred'', изобретенное для сломанных им частей Миранды одним из участников проекта (не Георгием).


В результате всего этого в начале апреля 2012 тогдашний куратор ядра Miranda IM Георгий Хазан принял решение покинуть проект, несмотря на наличие множества очевидных направлений развития Миранды. Однако, в процессе переговоров между разными сторонами было принято решение организовать новый проект, под руководством ghazan.
<translate>
== History == <!--T:5-->


15 мая 2012 года исходный код ядра Миранды был залит в отдельный репозиторий, и в него потом было добавлено больше сотни плагинов. Плагины для портирования выбирались по принципу частоты использования и популярности на сайте [http://miranda-vi.org www.miranda-vi.org]. Однозначно исключались плагины, для которых не существовало актуального исходного кода. В последующем в исходные тексты было внесено более полутора тысяч изменений, после чего 30 августа 2012 года был выпущен первый релиз Miranda NG.
<!--T:6-->
In spring 2012 the development of Miranda IM reached a deadlock.
# The existing (up to the present) model of Miranda development proved to be totally unsustainable for the following reasons:
#* It usually took over a year for changes in the core to be taken up by the plugin developers and to be finally brought to end users.
#* Plugins' source code was scattered about dozens of repositories, many plugins had no current source code available. Thus, code monitoring by the team was limited, if not to say impossible. As a result some plugins contained unusable, inefficient or buggy code, and no one could fix it.
#* There were lots of compatibility issues between different versions of Miranda core or even between versions of some plugins. This was especially true for implementation of Unicode support which hadn't been finished in Miranda IM.
# There was a conflict between {{Developer|George Hazan}} (ghazan) and {{Developer|Boris Krasnovskiy}} (borkra), the most active Miranda developers at the time. When Boris reverted a fix for his error because the commentary to commit contained the term ''borkred'' – which had been invented by one of the coders to denote Miranda parts broken by Boris – that was the last straw for George.


Сейчас (осень 2012 года) в проекте зарегистрированы 15 человек, из них минимум половина активно участвуют в разработке.
<!--T:7-->
In April 2012, George Hazan decided to leave Miranda IM project despite many obvious directions for Miranda development. However, during the negotiations between the various parties it was decided to found a new project led by George.


== Design principles ==
<!--T:8-->
* В проект входит не только ядро, но и вообще все плагины, которые могут быть использованы. Это открывает возможность любому члену команды проверить (и при необходимости исправить) код любого плагина.
On May 15, 2012 the source code of Miranda core was uploaded to a separate repository and later over a hundred plugins were added. Plugins to port were chosen on the basis of usage frequency and popularity on <tvar|miranda-vi.org>[http://miranda-vi.org www.miranda-vi.org]</>. Plugins without actual source code have been left out. After that the source code has undergone more than a thousand changes and the first stable build of Miranda NG was released on August 30, 2012.
* Каждая конкретная версия Miranda NG совместима только сама с собой (т. е. гарантируется, что все плагины в одной сборке совместимы друг с другом, но две соседние сборки могут быть полностью несовместимы). Это полностью решает все проблемы с совместимостью разных версий, позволяет избавиться от громоздкого кода во многих местах ядра и открывает широчайший простор для глобальной оптимизации как ядра Миранды, так и соответствующих плагинов.
* Прекращается поддержка версий ANSI, как полностью морально устаревших. Единственным поддерживаемым компилятором на момент написания статьи является Visual Studio 2010. Возможно, после выхода релиза VS2012, ее поддержка также будет включена в проект.
* Все члены команды имеют разный доступ: кто-то может исправлять только код плагинов, кто-то работает в трекере и вики, кто-то может исправлять любой код.


== Miranda NG advantages ==
<!--T:9-->
* Подключение и отключение плагинов «на лету», без перезапуска программы;
By autumn 2012 fifteen members joined the project, at least half of them are actively involved in the development.
* Повышена скорость запуска и работы программы;
* Значительно уменьшено потребление ресурсов системы (GDI и оперативной памяти), в т. ч. за счет вынесения неиспользуемых кусков ядра в отдельные модули (папка <tt>Core</tt>).
* Все плагины находятся в одном репозитории, при изменениях в ядре необходимые правки вносятся сразу, без ожидания реакции разработчиков, которая может длиться месяцами у Miranda IM.
* Проведена достаточно большая работа по унификации — многое из того, что каждый плагин реализовывал самостоятельно, было перенесено в ядро.
* Избавление от старых «костылей» и багов, повышающее общую стабильность программы.
* Возвращение в разработку Miranda NG кодеров, покинувших или бросивших по тем или иным причинам разработку плагинов под Miranda IM.


== Major features and differences from Miranda IM ==
== Project principles == <!--T:10-->
* В связи с серьезными изменениями в ядре программы, Miranda NG стала несовместима с плагинами от Miranda IM.
</translate>
* Стандартные модули ядра Miranda NG вынесены в папку <tt>Core</tt> в корне программы. Эти модули не загружаются в память при наличии их «замен» и автоматически подгружаются, если «замена» была отключена. В результате экономится память и уменьшено время загрузки программы. (Miranda IM держит в памяти ненужные модули даже при наличии их альтернатив.)
* Отказ от ANSI, ядро и все плагины полностью поддерживают Unicode.
* Вместо нескольких тулбаров, реализуемых в каждом плагине контакт-листа по-своему, приведен в порядок и доработан плагин {{Plugin/en|TopToolBar}}.
* Dbtool стал плагином. Теперь проверка и сжатие базы данных убрано в сам драйвер базы (в Miranda IM для каждого формата необходимо писать собственный dbtool). Таким образом, {{Plugin/en|DbChecker}} и {{Plugin/en|Import}} теперь только запускают соответствующий драйвер, и больше нет необходимости под каждый драйвер иметь свою «родную» утилиту.
* {{Plugin/en|PluginUpdater}} — «синхронизатор» плагинов с официальным репозиторием.
* Функционал плагина {{Plugin/en|ExtraIcons}} перенесён в ядро.


== Also ==
* <translate><!--T:11--> The project includes the core and all the plugins, so that any member of the team can check (and fix if necessary) the code of any plugin.</translate>
* [[Help|Friendly asked questions and help]]
* <translate><!--T:12--> Every next Miranda NG version is compatible only with itself (i. e., all plugins of the same build are compatible with each other while two adjacent builds can be completely incompatible). This makes it possible to get rid of bulky code in many parts of Miranda core and offers great opportunity for global optimization of both the core and the plugins.</translate>
* <translate><!--T:13--> ANSI is not supported anymore. Compiling with Visual Studio 2015 and 2017 is supported.</translate>
* <translate><!--T:14--> All the team members have different access rights: some can commit to any code, some can commit only to the plugins' code, some are engaged in the bugtracker and wiki.</translate>


== External links ==
<translate>
* [http://bugs.miranda-ng.org/roadmap Miranda NG Roadmap]
== Miranda NG advantages == <!--T:15-->
</translate>
 
* <translate><!--T:16--> Plugins can be loaded/unloaded dynamically ("on the fly") without having to restart the program.</translate>
* <translate><!--T:17--> The speed of program startup and operation was increased.</translate>
* <translate><!--T:18--> The consumption of system resources (GDI and RAM) was significantly reduced. This was achieved through extracting unused parts of the core to separate modules (those were placed into Core folder).</translate>
* <translate><!--T:19--> All plugins are gathered in a single repository, any changes required are applied to them immediately without waiting for the plugin developers' response (which could take months for Miranda IM).</translate>
* <translate><!--T:20--> A great deal of work on unification was done – lots of features implemented in several plugins independently were moved to the core.</translate>
* <translate><!--T:21--> Getting rid of old bugs and "crutches" improves the overall stability of the program.</translate>
* <translate><!--T:22--> Some coders who abandoned the development of Miranda IM plugins for various reasons now return to Miranda NG development.</translate>
 
<translate>
== Features and differences from Miranda IM == <!--T:34-->
</translate>
 
* <translate><!--T:23--> Due to major changes in the core, Miranda NG is not compatible with plugins for Miranda IM.</translate>
* <translate><!--T:24--> The [[Core and basic plugins#Core|standard Miranda NG core modules]] were extracted to Core folder in the root of the program. These modules are not loaded into memory if their "substitutes" are found in Plugins folder. Also, they are automatically loaded when the "substitutes" are being disabled. It saves memory and reduces the load time of the program. (Miranda IM keeps in memory unnecessary modules together with their "substitutes".)</translate>
* <translate><!--T:25--> ANSI is no longer supported. The core and all the plugins support Unicode completely.</translate>
* <translate><!--T:26--> The multiple toolbars implemented in each contact list plugin in their own way were replaced with {{Plugin|TopToolBar}} plugin which had undergone great changes.</translate>
* <translate><!--T:27--> Now database checking and compression are performed by database drivers. (Miranda IM has to have a special dbtool for each database format.) Thus, {{Plugin|DbChecker}} and {{Plugin|Import}} plugins just run the appropriate driver and there is no need to have a special tool for each driver.</translate>
* <translate><!--T:28--> There is {{Plugin|PluginUpdater}} – plugin to keep your Miranda NG up-to-date.</translate>
* <translate><!--T:29--> {{Plugin|ExtraIcons}} plugin was moved into the core.</translate>
 
<translate>
== See also == <!--T:30-->
 
<!--T:31-->
* [[Changelog|Miranda NG changelog]]
* [[Miranda NG:General disclaimer|Miranda NG contributors]]
* [[FAQ|Frequently Asked Questions]]
 
== External links == <!--T:32-->
</translate>
 
* [https://github.com/miranda-ng/miranda-ng/milestones <translate><!--T:33--> Miranda NG Roadmap</translate>]
 
[[Category:Main pages{{#translation:}}|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

Revision as of 22:50, 28 November 2018

Miranda NG (Next Generation) is a successor of a popular multi-protocol instant messaging client for Windows – Miranda IM.

Miranda NG is distributed under GNU General Public License.

Protocol support

  • GG (Gadu-Gadu)
  • IRC (Internet Relay Chat)

Supported operating systems

Windows 2003 / XP SP3 / Vista / 7 / 8 / 10.

History

In spring 2012 the development of Miranda IM reached a deadlock.

  1. The existing (up to the present) model of Miranda development proved to be totally unsustainable for the following reasons:
    • It usually took over a year for changes in the core to be taken up by the plugin developers and to be finally brought to end users.
    • Plugins' source code was scattered about dozens of repositories, many plugins had no current source code available. Thus, code monitoring by the team was limited, if not to say impossible. As a result some plugins contained unusable, inefficient or buggy code, and no one could fix it.
    • There were lots of compatibility issues between different versions of Miranda core or even between versions of some plugins. This was especially true for implementation of Unicode support which hadn't been finished in Miranda IM.
  2. There was a conflict between George Hazan (ghazan) and Boris Krasnovskiy (borkra), the most active Miranda developers at the time. When Boris reverted a fix for his error because the commentary to commit contained the term borkred – which had been invented by one of the coders to denote Miranda parts broken by Boris – that was the last straw for George.

In April 2012, George Hazan decided to leave Miranda IM project despite many obvious directions for Miranda development. However, during the negotiations between the various parties it was decided to found a new project led by George.

On May 15, 2012 the source code of Miranda core was uploaded to a separate repository and later over a hundred plugins were added. Plugins to port were chosen on the basis of usage frequency and popularity on www.miranda-vi.org. Plugins without actual source code have been left out. After that the source code has undergone more than a thousand changes and the first stable build of Miranda NG was released on August 30, 2012.

By autumn 2012 fifteen members joined the project, at least half of them are actively involved in the development.

Project principles

  • The project includes the core and all the plugins, so that any member of the team can check (and fix if necessary) the code of any plugin.
  • Every next Miranda NG version is compatible only with itself (i. e., all plugins of the same build are compatible with each other while two adjacent builds can be completely incompatible). This makes it possible to get rid of bulky code in many parts of Miranda core and offers great opportunity for global optimization of both the core and the plugins.
  • ANSI is not supported anymore. Compiling with Visual Studio 2015 and 2017 is supported.
  • All the team members have different access rights: some can commit to any code, some can commit only to the plugins' code, some are engaged in the bugtracker and wiki.

Miranda NG advantages

  • Plugins can be loaded/unloaded dynamically ("on the fly") without having to restart the program.
  • The speed of program startup and operation was increased.
  • The consumption of system resources (GDI and RAM) was significantly reduced. This was achieved through extracting unused parts of the core to separate modules (those were placed into Core folder).
  • All plugins are gathered in a single repository, any changes required are applied to them immediately without waiting for the plugin developers' response (which could take months for Miranda IM).
  • A great deal of work on unification was done – lots of features implemented in several plugins independently were moved to the core.
  • Getting rid of old bugs and "crutches" improves the overall stability of the program.
  • Some coders who abandoned the development of Miranda IM plugins for various reasons now return to Miranda NG development.

Features and differences from Miranda IM

  • Due to major changes in the core, Miranda NG is not compatible with plugins for Miranda IM.
  • The standard Miranda NG core modules were extracted to Core folder in the root of the program. These modules are not loaded into memory if their "substitutes" are found in Plugins folder. Also, they are automatically loaded when the "substitutes" are being disabled. It saves memory and reduces the load time of the program. (Miranda IM keeps in memory unnecessary modules together with their "substitutes".)
  • ANSI is no longer supported. The core and all the plugins support Unicode completely.
  • The multiple toolbars implemented in each contact list plugin in their own way were replaced with TopToolBar plugin which had undergone great changes.
  • Now database checking and compression are performed by database drivers. (Miranda IM has to have a special dbtool for each database format.) Thus, DbChecker and Import plugins just run the appropriate driver and there is no need to have a special tool for each driver.
  • There is PluginUpdater – plugin to keep your Miranda NG up-to-date.
  • ExtraIcons plugin was moved into the core.

See also

External links