Changes:

• FIX: Setup files were not anymore compatible with latest WiX 3 beta
• FIX: Router failing opening users and filters configuration in Windows
• FIX: Mysql missing crypt is replaced with DES_crypt from OpenSSL in Windows
• NEW: Compressed stream support via zlib
• NEW: Keep server.pem on upgrades
• NEW: Using SubWCRev from TortoiseSVN for version files generation (instead of xsltproc)
• NEW: All configuration files are now generated on build by Perl from generic distribution ones
• NEW: Using udns library for Windows builds too (resolver component was removed)
• UPDATE: Synced config.h with the one from generic builds

All changes are visible as SVN revisions 644-688 in the repository.

Please note new build prerequisites such as udns, zlib, Perl and TortoiseSVN for manual builds.

After few months spent with Apple’s Monaco font, unfortunately not in Monaco, and few hours of fighting with FontForge I have finally made up great bitmap 9×18 font for my terminal.

(Using new Fixed font with 18pt size with vertical spacing set to 0.80, no antialiasing)

Here is my story… First I have used famous Monaco Apple font, which was doing really great. However I have noticed that while on normal ANSI session of mc (Midnight Commander) Monaco’s box drawing is OK, while on UTF mc (ncurses) are using UNICODE box drawing characters (0×2500) which look awful with Monaco, the reason is that vertical box lines are not continuos divided by line spacing.

Since anyway I don’t use antialiasing in the terminal, I have started looking for perfect bitmap console font that contains maximum number of UNICODE ranges (including my Polish characters), and I have found great X11 font package by Markus Kuhn at http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html

I have used FontForge (from MacPorts) to produce following dfonts below.

Download

• FixedMedium.dfont 2008-06-20, 312 KB, Fixed medium bitmap font sizes: 13, 14, 15, 18
• FixedBold.dfont 2008-06-20, 64 KB, Fixed bold bitmap font sizes: 13, 14, 15, 18

License

You are free to use, distribute or modify fonts provided here. I disclaim any warranties with regard to this font. This work is derieved from UCS fonts available from Markus Kuhn at: http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html

Important

In order to have continuos vertical line drawing with this Fixed font you need to reduce vertical line spacing to ~0.80 (as for 18pt size) in Terminl.app font settings.

Fortunately Adium, the great Mac OS X IM client, made me remember, as it was regularly complaining about inability to make a connection to my company XMPP server running jabberd2 Windows version of mine. Also Tomasz Sterna, current maintainer of jabberd2, pointed me some win32 bugfixes hanging on mailing list. So there’s an interest in what I’m doing here! It is alive! Alive!

Going back to the subject, I’ve sat myself for a few (or little more) hours back to Windows and Visual Studio, made latest trunk compile properly in Visual Studio 2005 and finally killed all those annoying bugs that made jabberd2 win32 so unstable. So here it is, you can find brand new build.. working with Adium, and the others I hope. Still you need to remember to install VS2005 and OpenSSL runtimes before running my installer or it gonna fail. I hope I can make it somehow better soon, like having some message popping up about those runtime libraries in the installer.

Also as a side-effect of my work there are Visual Studio 2005 compatible versions of libgsasl and libidn there in the downloads, so hope I did something good for the community and I can sleep well now. Good night.

Now it is fixed in both SVN and downloads of jabberd2 win32. Sorry for the problem, now I hope you can enjoy at last jabberd2 for Windows installer.

It is not yet super-perfect, however it respects upgrades, also it will NOT overwrite your existing jabberd2 configuration nor database files.

Installer running on fresh jabberd2 free system will ask for XMPP domain during setup process and install running jabberd2 configuration using SQLite backend for authentication and storage with registration enabled. After installation remember you need to restart jabber2comp service every time you change comp.xml file (where comp may be s2s, c2s, router, resolver or sm).

Running installer over existing jabberd2 installation will result only with upgrading binary files and writing new *.dist.xml files next to existing *.xml ones.

Have fun with jabberd2! Don’t forget to install Visual C++ 2005 Runtime Libraries prior running the setup.

Several users already confirmed running jabberd2 on Windows server platform with success (I am running it also at my company). And now mu-conference component will be nice addendum to this light XMPP server suite, as together with jabberd2 all takes ~6MB on the disk with no extra software required!

P.S. Windows MSI installer is also on the way. Soon jabberd2 XMPP server installation will be even easier.

During development of those few patches I’ve learnt some few new things about way we make icons displayed next to menu items I want to share with you…

How to get icons in context menus

Methods described here are related to shell context menu extension, however they can be used in any Windows application.

hbmp(Un)checked method

Initially both Tortoises were filling hbmpUnchecked & hbmpChecked fields of MENUITEMINFO that is passed to InsertMenuItem with HBITMAP created from icon to get icons on menu item. This solution works on all Windows since 95. However the strong limitation is that HBITMAP must be SM_CXMENUCHECK x SM_CYMENUCHECK (usually 12 x 12). So if you are using 16 x 16 icon, the icon gets squished and looks awfully. The function used to convert icon to bitmap is:

HBITMAP CShellExt::IconToBitmap(std::string sIcon)
{
	RECT rect;

	rect.right = ::GetSystemMetrics(SM_CXMENUCHECK);
	rect.bottom = ::GetSystemMetrics(SM_CYMENUCHECK);

	rect.left = rect.top  = 0;

	HICON hIcon = (HICON)LoadImageA(g_hInstance, sIcon.c_str(), IMAGE_ICON, rect.right, rect.bottom, LR_DEFAULTCOLOR);
	if (!hIcon)
		return NULL;

	HWND desktop = ::GetDesktopWindow();
	if (desktop == NULL)
	{
		DestroyIcon(hIcon);
		return NULL;
	}

	HDC screen_dev = ::GetDC(desktop);
	if (screen_dev == NULL)
	{
		DestroyIcon(hIcon);
		return NULL;
	}

	// Create a compatible DC
	HDC dst_hdc = ::CreateCompatibleDC(screen_dev);
	if (dst_hdc == NULL)
	{
		DestroyIcon(hIcon);
		::ReleaseDC(desktop, screen_dev);
		return NULL;
	}

	// Create a new bitmap of icon size
	HBITMAP bmp = ::CreateCompatibleBitmap(screen_dev, rect.right, rect.bottom);
	if (bmp == NULL)
	{
		DestroyIcon(hIcon);
		::DeleteDC(dst_hdc);
		::ReleaseDC(desktop, screen_dev);
		return NULL;
	}

	// Select it into the compatible DC
	HBITMAP old_dst_bmp = (HBITMAP)::SelectObject(dst_hdc, bmp);
	if (old_dst_bmp == NULL)
	{
		DestroyIcon(hIcon);
		return NULL;
	}

	// Fill the background of the compatible DC with the given colour
	::SetBkColor(dst_hdc, RGB(255, 255, 255));
	::ExtTextOut(dst_hdc, 0, 0, ETO_OPAQUE, &rect, NULL, 0, NULL);

	// Draw the icon into the compatible DC
	::DrawIconEx(dst_hdc, 0, 0, hIcon, rect.right, rect.bottom, 0, NULL, DI_NORMAL);

	// Restore settings
	::SelectObject(dst_hdc, old_dst_bmp);
	::DeleteDC(dst_hdc);
	::ReleaseDC(desktop, screen_dev);
	DestroyIcon(hIcon);
	return bmp;
}

Ownerdraw method

Tortoise SVN was using also owner draw method. I won’t describe here details of this method. This relays on MENUITEMINFO fType flag set to MFT_OWNERDRAW. Shell extension in HandleMenuMsg2 callback should handle WM_MEASUREITEM and WM_DRAWITEM. This method is generally OK, however it has several flaws:

1. We need to measure & draw menu in all stated ourselves, which makes us write plenty of code.
2. Ownerdraw menus are not respecting visual styles of Windows XP or Vista. We would need to use uxtheme functions to somehow handle rendering of menu parts on those systems.
3. We need to keep exta context information for each menu item with text, icon handle, etc.
4. Keyboard shortcuts doesn’t work automatically, we must handle WM_MENUCHAR to make them work.

HBMMENU_CALLBACK method

Since Windows 98 MENUITEMINFO has extra field hbmpItem. This field can be used for setting the HBITMAP with bitmap that is displayed next to the menu item. hbmpItem can be set also to HBMMENU_CALLBACK which will make menu item work like owner-draw, but WM_MEASUREITEM & WM_DRAWITEM just need to handle icon drawing, rest will be done by Windows. This method is easiest to implement and so it is used inside many application, I just name on I use or develop: wxWidgets SDK, Miranda IM. We just need to initialize menu item like that:

MENUITEMINFO menuiteminfo;
ZeroMemory(&menuiteminfo, sizeof(menuiteminfo));
menuiteminfo.cbSize = sizeof(menuiteminfo);
menuiteminfo.fMask = MIIM_FTYPE | MIIM_ID | MIIM_SUBMENU | MIIM_DATA | MIIM_BITMAP | MIIM_STRING;
menuiteminfo.fType = MFT_STRING;
menuiteminfo.dwTypeData = lpszMenuTitle;
menuiteminfo.cch = _tcslen(lpszMenuTitle);
menuiteminfo.hbmpItem = HBMMENU_CALLBACK;
menuiteminfo.wID = id;

Rest is done in WM_MEASUREITEM where we need to just make sure we have space for 16 x 16 image using:

	case WM_MEASUREITEM:
		{
			MEASUREITEMSTRUCT* lpmis = (MEASUREITEMSTRUCT*)lParam;
			if (lpmis==NULL)
				break;
			lpmis->itemWidth += 2;
			if (lpmis->itemHeight < 16)
				lpmis->itemHeight = 16;
			*pResult = TRUE;
		}
		break;

Then to draw an icon we need to handle WM_DRAWITEM, but just drawing the icon, nothing else:

	case WM_DRAWITEM:
		{
			LPCTSTR resource;
			DRAWITEMSTRUCT* lpdis = (DRAWITEMSTRUCT*)lParam;
			if ((lpdis==NULL)||(lpdis->CtlType != ODT_MENU))
				return S_OK; // not for a menu
			resource = GetMenuIconResourceID(lpdis->itemID);
			if (resource == NULL)
				return S_OK;
			HICON hIcon = (HICON)LoadImage(g_hResInst, resource, IMAGE_ICON, 16, 16, LR_DEFAULTCOLOR);
			if (hIcon == NULL)
				return S_OK;
			DrawIconEx(lpdis->hDC,
				lpdis->rcItem.left - 16,
				lpdis->rcItem.top + (lpdis->rcItem.bottom - lpdis->rcItem.top - 16) / 2,
				hIcon, 16, 16,
				0, NULL, DI_NORMAL);
			DestroyIcon(hIcon);
			*pResult = TRUE;
		}
		break;

Simple ? Yes it is. However there are some issues with this method as well:

1. When this method is used on Windows 2000 shell extension window background popup menu, then shell.dll is removing text from the menu, so we see just icons.

   This is obviously a bug of Windows 2000 shell.dll, because MSDN documentation states this shall work regardless of the sittuation, but we need to somehow get over it. Surprisingly it does work fine when we right-click on explorer item (file or folder). The easiest solution is using hbmp(Un)checked method when uFlags == 0 of QueryContextMenu, which indicated we clicked the background, so we fall back to most primitive method, but at least we got text and “some” icons in the menu.

   Note: This bug only appears in Windows 2000 explorer’s background menu of shell extension, so in every other situation as standalone program menus HBMMENU_CALLBACK method can be used without any problem. So you may not care about it unless you are shell extension developer.

2. Vista is removing menu theme when some menu item has hbmpItem set to HBMMENU_CALLBACK, so we will have nice icons and nice menu, but if we want to have nice icons with 100% themed menu on Vista we need to use last method…

Vista PARGB32 hbmpItem bitmap method

Vista strongly relays on 32-bit pre-multiplied alpha RGB bitmaps for rendering its interface. In Vista hbmpItem can be set to PARGB32 HBITMAP and this bitmap will be nicely displayed by Vista together with theming as you can see on the screenshot at right. I got know of this possibility reading nice article Vista Style Menus, Part 1 - Adding icons to standard menus at ShellRevealed blog.

The most important question is how to we get our icon (regardless it is 32-bit with alpha, or 256-color with mask) converted to PARGB32 HBITMAP. Windows API doesn’t give such possibility straight of the box. Article from ShellRevealed proposes WIC (Windows Imaging Component) which is cool & quite simple for conversion or Vista’s GDI method, but those require Vista SDK, which may be annoying for those using Visual Studio’s out of the box.

As an alternative to that I’ve used Gdiplus which is present on most of the systems since Windows 2000, and most shipped with Visual Studios Platforms SDKs. This method is also much simpler than WIC or GDI method from described article. My PARGB32 function is as follows:

HBITMAP CShellExt::IconToBitmapPARGB32(std::string sIcon)
{
	std::map<UINT, HBITMAP>::iterator bitmap_it = bitmaps.lower_bound(uIcon);
	if (!m_gdipToken)
		return NULL;
	HICON hIcon = (HICON)LoadImageA(g_hResInst, sIcon.c_str(), IMAGE_ICON, 16, 16, LR_DEFAULTCOLOR);
	if (!hIcon)
		return NULL;
	Bitmap icon(hIcon);
	Bitmap bmp(16, 16, PixelFormat32bppPARGB);
	Graphics g(&bmp);
	g.DrawImage(&icon, 0, 0, 16, 16);

	HBITMAP hBmp = NULL;
	bmp.GetHBITMAP(Color(255, 0, 0, 0), &hBmp);

	return hBmp;
}

So in this case instead menuiteminfo.hbmpItem = HBMMENU_CALLBACK we do menuiteminfo.hbmpItem = IconToBitmapPARGB32(lpszIconResourceID). We shouldn’t forget of initializing Gdiplus library with GdiplusStartup(&m_gdipToken, &gdiplusStartupInput, NULL) in program/DLL initialization code and shutting it down after all with GdiplusShutdown(m_gdipToken).

Since we are going to use Gdiplus only on Vista, we may use Gdiplus.dll as delayed load DLL, so it won’t be loaded on older systems using previous methods, saving us some memory. Simple enough ?

Testing Windows version number with GetVersionEx and combining this method for Vista with HBMENU_CALLBACK method for Windows XP and older systems (with hbmp(Un)checked fallback on explorer extension on Windows 2000 if needed) is my opinion best method of having nice menus in all modern Windows systems. This is also current display method of Tortoise CVS & Tortoise SVN latest development versions. If you need full code to browse you may want look into Tortoise SVN SVN trunk files: src\TortoiseShell\ContextMenu.cpp, src\TortoiseShell\ShellExt.cpp and src\TortoiseShell\ShellExt.h.

How to fix that ?

It is possible to fix that with any good Resource Editor. Follow the recipe to get rid of popping up JavaScript error:

1. Close all Internet Explorer windows.
2. Locate and extract IE Dev Toolbar JavaScript source using any resource editor. Open C:\Program Files\Microsoft\Internet Explorer Developer Toolbar\IEDevToolbar.dll and extract resource TXT/235/1033 (type/resource ID/resource language). I used Resource Extractor extension of Total Commander. Alternatively you can use XN Resource Editor. I didn’t use Resource Hacker for this because it was saving the resource as hex-dump rather than binary file.
3. Modify extracted JavaScript source 235.bin using any text editor. Locate function:

   function ParseDoc(doc)
       {
           var aRules = GatherRulesFromDoc(doc);
           collSelectors = parser.Parse(aRules);
   
           // Set quirks mode if necessary
           if("BackCompat" == doc.compatMode)
           {
               for(var i = 0; i < collSelectors.Count; i++)
               {
                   collSelectors.item(i).SetQuirksMode(true);
               }
           }
   
       }

   Change red marked line into:

                   try { collSelectors.item(i).SetQuirksMode(true); } catch(e) {}

4. Save back the resource file 235.bin into TXT/235/1033 of IEDevToolbar.dll. I used “replace” function of Resource Hacker.

Now you should have fixed IEDevToolbar.dll, that is not raising any errors anymore.

Note

Please don’t ask me about any binaries as it is against EULA of IE Dev Toolbar.

I hope this will help to popularize XMPP somehow. I presume that free 3MB setup will be something that everyone can try installing at their office next to MS Exchange server, at least just to put e-mail/XMPP instead of just e-mail in the footer We just need to make Jabber trendy.. heh ?