Save the following code under ~/.vim/syntax/google_gadgets.vim:

" Vim syntax file for Google gadgets module files.
" Maintainer: Guy Rutenberg <http://www.guyrutenberg.com>
" Last Change: 2008 Mar 28
"
 
:syntax clear
 
runtime! syntax/xml.vim
 
unlet b:current_syntax
:syntax include @HTML syntax/html.vim
:syntax region HTMLcode matchgroup=CDATA start=/<Content\s\+type="html"\s*>\_s*<!\[CDATA\[/ end=/\]\]>\_s*<\/Content>/ contains=@HTML
 
syn keyword javaScriptReserved _IG_Prefs getString getInt getBool getArray set setArray dump _IG_FetchContent _IG_FetchXmlContent _IG_FetchFeedAsJSON _IG_RegisterOnloadHandler _gel _gelstn _esc _unesc _trim _uc _min _max _hesc _args _toggle _IG_GetImage _IG_GetCachedUrl
let b:current_syntax = "google_gadgets"

And add the following line to your .vimrc

au BufRead <google_gadgets> runtime! syntax/google_gadgets.vim

The current syntax highlighting will highlight the XML part as XML, and if your gadget contains an HTML part, it will highlight it too (including CSS and JavaScript). I’ve also registered the core JavaScript library of the Google Gadgets API as JavaScript keywords so they will get highlighted too.

The line you added to the .vimrc file will automatically load the syntax highlighting for files of type google_gadgets. While this file type isn’t automatically detected, you can easily set one by typing :set filetype=google_gadget.

Tip: If you want some file to always be detected as google_gadget add the following modeline to it:

<!-- vim: set filetype=google_gadgets : -->

(you got to have modelines enabled for this to work).

Some things are still missing, such as highlighting for all the keywords and methods of the API, and automatic file type detection. I plan to address those issue as time will permit me. If you think I’ve left out some important functionality that should belong with this code, please comment or contact me.

The first step is to install ctags (if you haven’t got it already installed), this provides the tags file, on which the autocompletion is based. ctags is available directly from the package manager of all popular distro’s.

The next step is to install the OmniCppComplete plugin for vim. The plugin uses the ctags‘ generated tags file for the autocompletion. In order for the autocompletion to properly work with classes, you need to create the ~/.ctags file and add some default options. Each option should be listed in a newline. Your ~/.ctags file should look like this:

--c++-kinds=+p
--fields=+iaS
--extra=+q

These options will now be used as default when running ctags.

The next step is to create a tag file for the wxWidgets library. This can be done using the following command:

 ctags -f ~/.vim/wxwidgetstags -R /usr/include/wx-2.8

Don’t forget to replace /usr/include/wx-2.8 with the path to the header files of wxWidgets. This will create the tags file under your ~/.vim directory.

The next step is to tell vim to use this tags file. This is done by adding the following line to your ~/.vimrc:

:set tags+=~/.vim/wxwidgetstags

And now your done. OmniComplete will now work for wxWidgets, listing members and functions for any of the wxWidgets classes.
Remember you can repeat the last two steps for any other libraries you use in order for the OmniComplete to work with them too.

N.B. don’t forget to run ctags -R . in your projects root dir if you want OmniComplete to work for classes you defined.

I ended up writing two macros one for PHP files (but it’s also good for C/C++ etc.) and one for smarty.

:vmap tg di_(<ESC>pa)<ESC>
:vmap ts di{t}<ESC>pa{/t}<ESC>

To use these macros just highlight the string for translation in vim’s visual mode and press tg (or ts), and your string will be wrapped for translation.