Download links:

• Google Chrome Portable Stable (3.0.195.33)
• Google Chrome Portable Beta (4.0.249.30)
• Google Chrome Portable Dev (4.0.266.0)
• One Number (1.1.0.6)

Of note is that with this release, the Google Chrome Extension Gallery will now work with Beta and Dev builds.  Have fun, and be sure to try One Number!

Google Chrome Portable Changelog:

• Updated Dev to 4.0.266.0 and Beta to 4.0.249.30. Google Chrome Extension gallery is live!
• Installer now shows the version of Chrome being downloaded.
• Updated the sample INI with some new notes.
• msvcr100.dll beta 2 is no longer required by the NSIS plugin. 200kb has been shaved off the launcher.
• Changes to Portable Passwords to improve security and prevent possible vulnerabilities. If you were previously using Portable Passwords you will need to import your passwords to Chrome before updating, see the sample INI for notes on how to keep your saved passwords.
• Fixed bug in NSIS plugin where memory was freed twice (oops).
• Added EncryptPortablePasswords switch to INI, so you can choose to store saved passwords in plaintext. This may be useful if you already use an encryption solution such as TrueCrupt to protect your PortableApps and have no need for additional protection. This is also removes the need for a master password.
• Installer window no longer shows. DialogEx is used instead for the master password prompt.
• Tidied up some things in the launcher code (all language strings are in the appropriate NSH now).
• Updated to PA.c Installer 1.0.1.

One Number Changelog:

• Hopefully fixed Google App Domain support for GMail, added for GWave. Still “Not tested” quality, please give feedback.
• Already read messages will no longer be shown in Google Voice preview.
• GMail and Google Voice options to check for unread messages in all folders/labels, not just the Inbox.
• You can now hide individual services’ unread counts from the main toolbar button.
• Fixed bug where services could stop updating.

Take a look.

Bonus for reading more:  My TODO list:

- Google Apps Domain for Wave: https://wave.google..com/a/<yourdomain.com>/

- Check official GVoice Notifier extension to see how it behaves and compare with mine.

- Option to check all messages, not just inbox? (GMail, GVoice, GWave)

- 27487 – XHR never finishes on 401.  Doesn’t seem possible to fix, it acts like it’s still loading until it times out.

- 27637 – no favicon for my option page

http://www.mzzt.net/tf2/

One of these days I’ll style it.

If they can skew the truth, so can I! Except mine will be more accurate and not as skewed. Still fun to do a LITTLE skewing though.

				Comments
Security				Firefox and Chrome both use Google’s excellent and proven Anti-Phishing and Anti-Malware lists which are continually updated. They have had this technology for longer than IE has. Furthermore, IE’s continued use of the long-proven vulnerable ActiveX technology makes it a danger to use.
Privacy				Firefox and Chrome both include private browsing modes which make sure no trace is left on the user’s system. Furthermore, their lack of ties to a specific host OS, like IE has, allow users to take their favorite browser with them on a thumb drive whenever they use a public computer, further ensuring the privacy of their browsing history and accounts.
Ease of Use				Supporting the latest web standards ensures that the browsing experience is universal regardless of which standards-compliant browser you use. Google Chrome’s slimmed down UI makes using the web simple, easy and fun, while Firefox’s high customization makes it easy to have YOUR web, YOUR way. Oh, and tried to use IE8 on Linux, MacOSX, or Windows 2000? Nope. Firefox runs on all of those. A pre-alpha version of Chrome is available for Linux and OSX.
Web Standards				IE8 is only JUST implementing CSS2.1, something other browsers have done long ago. They are already movong on to CSS3! IE8′s Compatibility View is a step backwards, ensuring devs do not need to change their websites to adhere to standards if they are only concerned with IE; just tell users to click the button instead! Firefox and Chrome continue to improve their performance and compatibility, and both score highly on web benchmarks and compatibility tests such as Acid3. Internet Explorer has yet to break 20% in Acid3, which most other browsers are near or at 100%!
Developer Tools				Firefox has a myriad of useful tools available as extensions, such as Firebug and DOM Inspector. Chrome has tools to allow you to debug scripts, view the DOM tree, and even see how long each resource on your page takes to download and render. As for profiling, the JavaScript engines used in both browsers are significantly faster… but Chrome has a script profiler anyway in the dev branch. And with Firefox extensions I can safely say it probably has one too.
Reliability				Firefox does not yet have tab-process support, but it is stable enough not to need it for the time being, in my personal experience. Chrome has crash recovery as well as tab isolation. It’s possible the IE team didn’t notice because Chrome doesn’t crash very often, thanks to tab isolation!
Customization				Customizability [sic] is not a word. Firefox has addons that can do anything you could want it to do. IE8 has… toolbars. Chrome already has better support for extensions than IE8 and that support is not yet ready for the public eye.
Compatibility				IE has traditionally broken web standards more than any other browser. We have already established that it is not compatible with those web standards. Being compatible with proprietary standards YOU invented is EASY. It should also be mentioned that IE’s compatibility with ActiveX comes at the price of security and privacy.
Manageability				The majority of desktop users are not concerned about Group Policy settings, even if they know what it means. Nevertheless, Firefox and Chrome both properly handle downloaded files, marking them as “untrustworthy” in Windows. Firefox also respects a limited number of applicable group policy settings for Internet Explorer. But ultimately if a group policy setting has to be enforced at the application level instead of the system level, a clever user will always find an application to work around it.
Performance				Chrome is built for speed, and nothing can come close. Except maybe Safari 4. Firefox is also quite speedy, so it gets an honorable mention. Both browsers have newly designed JavaScript engines tuned for speed. IE8 is still using an outdated engine that is not. Oh they tried, but they didn’t use native code compiling like Chrome and Firefox are.

Mine is here.  The biggest change is I’ve gone for the look of the new Windows 7 Content view for files and folders … I like it very much.

In addition I have removed most of the excess whitespace, added hover effects, and added tooltip info to images.  In addition there are custom icons for some different filetypes, and it’s easy to change those.

There are also a couple interesting statistics at the bottom.

Download the source here (requires 7zip or a tool that can extract .7z files to use).

Shockingly IE8RC1 renders it correctly without requiring any hacks.  I did not test it with IE7 (I’m scared to, given the semi-hackish way I got the folder/file lists working without tables).  The latest versions of Gecko, Webkit, and Opera all handle it fine… and of course Gecko and Webkit get fancy rounded borders too.

For the future I might add some javascript in to allow for custom sorting and maybe different views for files/folders… who knows.  But that would require coding a lot of the template over in JavaScript.