pidgin/nest
Rename GTK+ to GTK, as upstream has done.
+++ b/hugo/content/development/design-guidelines.md Tue Jun 25 22:54:54 2019 -0400
@@ -30,13 +30,13 @@
+In plain language, this means that the protocol-specific code goes in the protocol plugin (*prpl*), and that libpurple exists, and is cleanly separated from the user interface. There are practical implications to this. While all of our code depends on glib, only the Pidgin specific parts depend on GTK.
To implement, for example, file transfer; there are 3 steps. First, the protocol(s) have to support it. By themselves, however, the protocols can do nothing. So the "core," libpurple, has to support it also (the second step).
We do not want massive amounts of very similar code in libpurple, so the implementation of file transfer at the libpurple level has to abstract away from how individual protocols handle it, so as to be able to use the same calls from all file transfer supporting protocols.
+Last, but not least, before the user can actually send or receive a file, the UI (Pidgin, Finch, or Adium) must support it. These interfaces know nothing about the protocol, and have only limited contact with the core. This helps to enforce the desire for uniformity explained above. It also makes it easier for the only sort of duplication we encourage: many interfaces. The core implementation cannot assume too much about what the UI will do, because the GTK UI (Pidgin) might need to handle a file transfer somewhat differently than the ncurses-based UI (Finch).
Patches that violate this layering will be rejected. In practice, this means that there is more work involved to introduce a new class of functionality, say file transfer, white-boarding, voice, or video. On the other hand, it means less work to implement any given class of functionality for a new protocol or for a new UI.
@@ -46,4 +46,4 @@
+Pidgin and libpurple are single threaded. That means that the network code runs in the same process as the user interface. Network code must be non-blocking, otherwise the UI will be unresponsive. Code should be event-driven. Long running tasks should be asynchronous. File descriptors that need to be watched for changes should be added to the event loop.
+++ b/hugo/content/development/version-control.md Tue Jun 25 22:54:54 2019 -0400
@@ -17,6 +17,6 @@
The default branch has moved libgnt out to its own repository at [bitbucket.org/pidgin/libgnt](https://bitbucket.org/pidgin/libgnt) to make it more accessible to other developers. The intent here is to have it be a separate package on all distributions to make it more accessible to users as well as developers. This will help on distributions such as Slackware that enforce rules of one distribution package per source package.
+Pidgin 3 also depends on [bitbucket.org/pidgin/talkatu](https://bitbucket.org/pidgin/talkatu) for reusable [GTK](https://www.gtk.org) widgets that are geared towards messaging clients.
Purple 3 has adopted [gplugin](https://bitbucket.org/gplugin/gplugin), which is a library that handles plugins in multiple langauages leveraging [gobject-introspection](https://gi.readthedocs.io/en/latest/). It currently supports C/C++, Python, and Lua plugins, with more languages planned for the future.
+++ b/hugo/content/drafts/download.md Tue Jun 25 22:54:54 2019 -0400
@@ -19,9 +19,9 @@
[](http://sourceforge.net/projects/pidgin/files/Pidgin/2.13.0/pidgin-2.13.0.exe/download?accel_key=62%3Aa4c0d8b6-1952-11e9-abae-525400fc71c5&click_id=a4c154bc-1952-11e9-abae-525400fc71c5&source=accel)
+This version of Pidgin downloads an appropriate version of GTK. GTK is now installed locally for Pidgin, and not system-wide, thus Pidgin will not interfere with other GTK apps on your system.
+If you would like to have GTK included in the installer, we have an [offline installer](http://sourceforge.net/projects/pidgin/files/Pidgin/2.13.0/pidgin-2.13.0-offline.exe/download) that bundles everything except spell-checking dictionaries.
@@ -79,4 +79,4 @@
+++ b/hugo/content/drafts/release-process.md Tue Jun 25 22:54:54 2019 -0400
@@ -63,7 +63,7 @@
1. `make distcheck` - Standard automake target. Builds and verifies tarballs. If "distcheck" fails and you're sure the failure is innocuous then you can use `make dist`, instead.
+ 1. If there's a new GTK Bundle, upload the zip file to [Sourceforge](https://sourceforge.net/projects/pidgin/files/Pidgin/) and make sure that the `BUNDLE_SHA1SUM` in `pidgin/win32/nsis/generate_gtk_zip.sh` is correct (this should have been checked before `make release`).
+++ b/hugo/content/gsoc/ideas.md Tue Jun 25 22:54:54 2019 -0400
@@ -35,7 +35,7 @@
+We are replacing as many parts of libpurple and Pidgin with modern library-provided functionality as feasible for 3.0. For example, we have ripped out our custom DNS infrastructure and replaced it with GIO DNS that did not exist when our infrastructure was written. There's still a lot left to do here. For example, we do not use the GTK icon infrastructure everywhere. Talk to Michael McConville about some things he identified during his 2015 Maintenance Hero project.
+++ b/hugo/content/help/windows.md Tue Jun 25 22:54:54 2019 -0400
@@ -21,11 +21,11 @@
+The installer will, if necessary, download and install the GTK runtime, which is needed for Pidgin to run. If you need to use a proxy server to connect to the Internet, it is possible that the Pidgin installer will not be able to reach the resources it needs. The installer automatically checks for proxies configured in Internet Options. If you know the proxy settings, you can configure them by opening Internet Options directly from Control Panel, or by opening Internet Explorer and selecting Tools > Internet Options > Connections > LAN Settings.