Include version information when opening help pages.

When opening links to poedit.net in the browser, append ?fromVersion=xxx
to the URL so that version-specific help can be displayed when
appropriate.
Move File->Catalogs manager to the bottom.

Top slots of the menu should be used for standard file operations such as New.
Remove the option to open catalogs manager on startup.

The manager is pretty much on life support by now.  And it will be more
useful to show a welcome screen on startup.
AttentionBar: don't use ShowWithEffect even on Windows.

The animation is flickering, with the window behind it not updated, not
very nice in 2013.
AttentionBar: only hide the message after action.

First perform the action (e.g.  show properties), then hide the message.
Useful for reference while performing the corrective action.
Disable PoeditArtProvider on OS X.

It wasn't used anyway, accidentally, and the builtin one did the right
thing, picking files from Resources.  Unlike the builtin one, this
wasn't even Retina ready.
Defer creation of content controls until actually loading a file.

Don't create all the splitters, lists and text controls in PoeditFrame
constructor.  Instead, leave the content area empty until some content -
a PO file - is loaded.

This will make it easier to swap content depending on file type (e.g.
making POT viewing read-only) as well as allowing showing some welcome
screen content when the window is empty.
Add a simple welcome screen.

Include buttons for opening or creating translations.
Merge branch 'welcome-screen'
Larger, more sensible, default window size.
Don't reset team metadata when creating from POT.

Even though the GNU project uses per-language teams, others use a single
team contact for all translators.  Don't remove the entries, let the
user do it if they so desire.
Use mkdtemp() on OS X.

This was accidentally lost when converting the build system to use Xcode projects.
Add and use LanguageDialog.

Add a dialog for picking the language - just a simple window with
LanguageCtrl inside it.  Use it when creating a new file from POT,
instead of showing the full properties dialog.
Split PoeditFrame::OnNew() into NewFromScratch() and NewFromPOT().

They didn't share any common code anymore after 272faa4.
Ensure correct content view when creating new file.

Consequently, don't crash because the list is null.
Don't manually add default xgettext keywords.

There's no point, modern xgettext versions have good builtin lists.
Don't require immediate saving when creating a file from POT.

Change the workflow to be more in line in what is usually done in
document-based apps: don't immediately save the file and let the user do
it.  To accomplish this, introduce the concept of a file with assigned
filename, but not existing on the disk yet.  If that happens (such as
after creating a file from a POT), ask for filename confirmation when
saving.

Choose appropriate file for the new translation: use lang code for the
name and save directory as the POT file.

Don't do this for completely new catalogs (from sources) yet, because
the whole thing is more complicated there.
Note files as recent when saving too.

Otherwise newly created files wouldn't appear in Open Recent.
Allow creating translation from PO files, not just POTs.

Threat them as POTs, though: manually clear all the translations.  This
is relatively common thing to do, especially when the developer is not
familiar with gettext and doesn't use POTs or has them out of date.  So
why not make it a bit easier.
Less overwhelming new file workflow.

Previously, File->New was the workflow for setting up scan from sources
and it involved, *immediately* doing the following: 1.  save the file,
2.  setup al properties, 3.  setup sources scanning.  Without any
explanation or any reference material.

Replace this with - hopefully - something friendlier: create a new,
unsaved, empty document and explain why it's empty and what it means.
Offer a link to the manual and explain the two typical actions for
filling in the entries: update from POT or from sources.  Make sure
sources extraction requires file saving (for proper reference to the
path).