Meh, I don't mind sayin' it there b0mmel, but there is no longer any reason to use the major clients. Technology and the user have moved forward since the days of AOHell.
![gtk pidgin download gtk pidgin download](https://www.kongtechnology.com/images/pidgin.gif)
Having said that, honestly, there is no more need for these branded, ad- and bloatware-laden crappy messengers when one simple one will allow me to communicate with just about everyone. Since I don't care for it anyway, psh.Īnd why would I use a multi-messenger website for IMing, when I have a perfectly good client? That supports all major protocols? This is akin to saying "I want an alternative messenger, but I don't." What?! Pick one. And about the only thing I don't get with Pidgin is video. I mean, my God, MSN AOL and Yahoo messengers are freakin HUGE! And please don't tell me that the ads are necessary, because if I can use Pidgin that has no ads, well then. I'm going to have to reference b0mmel's statement from below, just to provide a opposing opinion for those who may care for it: the purpose of alternative messengers, not to point out the obvious, is to provide a user withĢ) a method by which to connect to multiple chat protocols should one wish andģ) a lightweight client without all the bloatware.
Gtk pidgin download install#
Its helpful to have a start menu entry too.Reliable, extensible, good-looking, no ads, all major protocols, small install and fast. I then was able to compile an msi with GTK included, so it can be deployed on the network as required Start Menu Once I downloaded the GTK zip, I extracted the files into pidgin-2.10.7\GTK then re-ran heat and the changes I made to the generated file. The first msi I compiled did not include GTK, which is available with pidgin on sourceforce. Pidgin needs GTK+ in order to run, which isn't supplied with the normal downloads. All rights reserved.Ĭopyright (C) Outercurve Foundation. Like I said in my introduction, once a wxs file is configured, then all that needs to be done is run candle and light: >candle pidgin-2.10.7.wxs This needs a product feature title setting Compiling I did a global find / replace of SourceDir\ to the location on my local disk This needs Product name, manufacturer and version setting to relevant valuesįor the parent directory which it creates for all the components, I changed this to be the install directory, and then wrapped the components in a tag: This produces a wxs file with all the files in the directory specified, but needs some details updating: heat dir "pidgin-2.10.7/" -template product -gg -suid -sfrag
![gtk pidgin download gtk pidgin download](https://2.bp.blogspot.com/-8WYDr_-gg5Q/Uzc4Fz-qKtI/AAAAAAAAAqs/QmgADTAcYIY/s1600/pidgin-tabbed-chat.png)
To save generating by hand all the config required to install files from a directory, there is a tool supplied with wix called heat.
Gtk pidgin download zip#
The other option is to take the pidgin-win32-bin zip file, and install all the files within this archive.Īs, Pidgin has about 700 fiiles in the archive, I initially looked at this option, until I saw suggestions of how this was bad practice to install an exe, then run it. The first is using a precompiled exe installer, and copying to the target machine, then executing silently. There are 2 options for deploying pidgin. A real tutorial is available here on .hu Deployment Options The wixobj file then needs to be compiled using light, hopefully producing a nice shiney msi file. This is then parsed using the candle program. Put some xml together in a wxs file, detailing the files to be installed, source and destination locatons. Wix is an opensource microsoft tool for creating msi files. Currently, there are no official pidgin msi files, but it is my preferred client. We already deploy updates for flash, adobe reader, java etc via msi files. A jabber service has been set up, but a client still needed to be deployed to all the end users. With its shutdown forthcoming, alternatives were needed. The main office IM tool is currently msn messenger.