Basically, all it does is check the TO line and the CC line to see if there are multiple recipients. If there are, it prompts the user if they would like to reply all, if they say no, it removes everyone except the first email address in the TO field.

Here’s a link to the .msi file (zipped) for your viewing pleasure. Also, this does not require .net 4.0 framework. It works fine on 3.5 sp1 (which should be included in Windows 7.
This is also for Office 32-bit. But will work on Windows 7 x86 and x64 installs… as long as office is 32 bit.

Download the Zip containing the .msi here:
Reply All Outlook Add-In

Code is below:


using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Xml.Linq;
using Outlook = Microsoft.Office.Interop.Outlook;
using Office = Microsoft.Office.Core;
using System.Windows.Forms;

}
}


It works in the latests versions of Chrome and Firefox or any browser that supports WebGL.

This will disable the highlight color (which by default seems to be darker) on the iPhone and other webkit based browsers.

I recently re-jailbroke my iPhone to be able to use the awesome winterboard theme Typophone 4 and David Ashman’s incredibly useful Lockinfo.

I ended up creating 2 winterboard mods, one for Typophone, which includes weather, and one for Lockinfo, which just changes the status bar icon for silent mode.

Download the Typophone 4 modded theme on Cydia under Typophone Weather.
Source on github (I will be updating the source only from now on)
Downloads

Download the Lockinfo mod on Cydia under Lockinfo Native Status Icons
Source on github (I will be updating the source only from now on)
Downloads

Go here for more screenshots.

Please note that as of right now, you cannot use a custom background. I am working on finding a solution for this, but in order to hide the slider, I need to make the background black.

If you are not seeing the weather, make sure you’ve deselected the stock Typophone theme and selected Typophone Weahter.

**** UPDATE ****
I added icons for SMS, vMail, eMail, and Missed Calls.

PLEASE USE VERSION 1.6 OR ABOVE.
This will add application support. More info here.

First, what is livestats? It’s the end point of this Peepcode tutorial video.

Second, why the completely convoluted setup? If you watch the tutorial (it’s only $9 and I highly recommend it), you’ll see that they set up their Faye/Node server on port 8000. I want my setup to work on port 80 so that most firewalls won’t block access to it (including mine at the office). I also have a bunch of other websites running on port 80 (including the geoip site). I need to be able to split up access to each of these based on host names in the request headers (ergo, livestats.gmtaz.com takes you to my node.js app and geopip.gmtaz.com takes you to my geoip app – both of which are running on port 80).

Ah, so what to do, what to do…

First step was to get Node.js running. It works on linux so I had to get a linux distro, hopefully Ubuntu or something similar (ended up going with Mint), and some kind of virtualization software to run it (VirtualBox). Both of these products are free.

Actually, now that I think about it, all the software I used is free. Awesome.

Step 1.A: Get Node.js installed.
Step 1.B: Get nginx installed. “sudo apt install nginx”.

Ok, easy enough. Next step is to complete the tutorial and get the node.js app running. Go do it.

…a few hours later…

So now, you should have your node app running on localhost:8000 without issue. Great! Wait, not great. I(you) want to access the node app on port 80. Ok, well, let’s configure nginx to proxy over port 80 to port 8000.

default.conf

server {
listen 80;
server_name example.com *.example.com localhost;

}


proxy.conf

proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 10m;
client_body_buffer_size 128k;
proxy_connect_timeout 6000;
proxy_send_timeout 6000;
proxy_read_timeout 6000;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
send_timeout 6000;
proxy_buffering off;
proxy_next_upstream error;


Check out the nginx wiki for some good tutorials and sample code.

Now, when I go to http://localhost:80, nginx loads my node app which is running on port 8000.
You can configure multiple server objects in the config. Took me a few minutes to figure that out. This means you can have multiple name based proxies.

Ok, this is great. Now I point my home firewall to forward port 80 to my virtual server’s IP (which should be bridged to your network, not NAT *muy importante*). This allows me to go to my public ip and get routed to my virtual server. Just make sure that in the nginx config you are specifying the server name as the public IP or the DNS friendly name instead of example.com.

This is where the trickiness comes into play. I need a geoip server. I can get one running on apache and php. I used the pure PHP module, but feel free to use the module for Apache. This brings me to my my Apache config. *Awesome segway, I know*

I have apache listening to port 80, which means it can’t be running on the linux VM (you can only bind a port to an app once). Installing Apache 2.2.16 on the host machine (running Windows 7) was my next step. What about IIS? Well, I could use my IIS setup on Windows 7 too but I initially used Apache for my proxy server. Yeah, yeah, now I’m doing a double proxy. Totally unnecessary, but you’ll see why I did it in a minute. Anywho, I have my Apache config set up to run multiple virtual hosts. One vhost proxies out my http request to my IIS server, which then serves up the site in IIS. The other vhost serves up the geoip app.

Another thing to be aware of is that I needed 2 different versions of PHP installed on my computer because Apache 2.2.16 requires a different version (VC9) than my IIS setup (VC6). Also, IIS is configured to hit sql and mysql servers for different websites that I have running, and I was getting errors in php5ts.dll when enabling those modules in PHP 5.3.3 on Windows.

Quick summary of the situation so far:

Windows 7 (HOST):
Apache 2.2.16 with PHP 5.3.3 VC9
– Apache is set up to proxy requests based on host names to IIS or to geoIP.
– In case I decide to turn off the virtual machine, I still want to be able to host all my other websites.
IIS 7.5 with PHP 5.3.3 VC6 (PORT 8000)
– IIS is serving up a few other website that are developed in ASP.net C# and PHP (This is why I need IIS )

Linux Mint (VM)
Nginx
– Proxy server for node.js running on port 8000 (in case I want to run multiple node apps – each one must be on a different port, which is why I need the proxy).
Node.js
– Hosting the livestats app on port 8000.

Got that? Ok. The next part stumped me for most of the day. My node.js via proxy worked fine in Firefox, but not in Chrome. WTF?? Let me rephrase. Chrome worked when going to the direct IP and port of the node server which means that the proxy was causing problems. I’ll save everyone a lot of time by saying this: websockets via proxy don’t seem to work too well.
Basically, Faye was detecting that the Chrome browser can use websockets and was attempting to create the connection using that (websockets). Firefox was using the long-polling method. How did I figure this out? Long story but it had something to do with looking at the Faye object in Chrome inspector and seeing that it was rocking the websocket, then looking at the same Faye message object in Firebug and seeing that it was using long-polling. Ok, I guess it wasn’t that long of a story…

So now I know that Faye, Node, websockets and proxies don’t mix all too well. Turns out there was a simple solution. Force Faye to use long-polling! What do you mean “it’s not an option”?

Check out Faye-node.js in the tutorial code. In there you’ll see an array for CONNECTION_TYPES. Just replace “websocket” with “long-polling”. Amazingly enough, this works.

So now you should have a pretty complicated network of proxies and web servers running but everything should be working fine! Magic? Nay. Just a lot of tinkering and coffee.

Things that made development and testing easier:

1. Running the node.js dev server so that it automatically restarts when a file is changed
2. Installing Dropbox on all servers and running the node site from the application folder within Dropbox
3. Firebug and Chrome’s Inspector
4. Espresso on the mac for editing the app within the Dropbox folder
5. VirtualBox and Linux Mint

These things made it incredibly easy to make changes and verify their functionality with a simple refresh.

EDITORS NOTE: Since writing this, I realized that for some reason the proxy isn’t working all that well in nginx for me ATM. I’m using apache to proxy to nginx for now and not really using nginx at all. The nginx proxy from vm to host works fine, but the proxy from nginx to node doesn’t work…

Something to do tomorrow. PEACE!

EDITORS NOTE 2: I figured out the proxy thing. Now I’m just using nginx for proxy services. Turns out I had statically set livestats.gmtaz.com in my hosts file on windows to 127.0.0.1. Forgot about that. Yay for testing!

1. It’s Free
2. I can post to multiple services with one push: Facebook, Tumblr, Twitter. I use twitter and facebook quite a bit these days and being able to post to everything at once is a HUGE time saver.
3. Easy mobile posting. I have the iPhone Tumblr app. It makes posting beyond simple. I know that there’s one for wordpress, but before Tumblr, I would have to post to facebook, post to twitter, and post to wordpress (if I even wanted to go through the trouble because, let’s face it, the wordpress iPhone app kind of sucks).
4. Integration with Flicker. I could post photos to Flickr and have them automatically appear in my Tumblr feed. Slick.
5. Custom Themes and super easy to customize any theme you have selected.
6. You can allow others to post to your Tumblr roll (after queuing and approving)
7. Super easy analytics integration. Got your own google analytics account? Just edit your theme and put the GA script in there. Done.
8. Automatically import your WordPress RSS feed (or any other RSS feed) into your Tumblr roll.
9. Custom Domain (i.e. log.gmtaz.com or whateveryouwanthere.tumblr.com)
10. Optimized mobile theme (optional but enabled by default). It’s clean and it’s easy. No setup required.
11. BONUS: Built in SEO

I have to say, I really love Tumblr.

Just a quick FYI.

****EDIT****
Actually, now that I think of it – I might move www.gmtaz.com over to tech.gmtaz.com and log.gmtaz.com over to www.gmtaz.com. I feel as though tech.gmtaz.com is going to go by the way side as I don’t really have that much time to put into writing out longer posts. We will see…

I’ll see if I can figure out a way to post images.

I ran with it and came up with what you see below. I’m including the PSD in case you want to change the colors. All you have to do is change the gradient layer style and you’re set.

I’m including a 1920×1200 wallpaper png, an iPhone wallpaper png, and the original PSD in this post.
Let me know what you think and enjoy!

1920×1200
iPhone 3

Here’s an example of what you can do in 2 seconds with the PSD. HDR effects and all…

1920×1200
1440×900