I've pushed an update to Chrome Dev and posted it to the Chrome Portable homepage. As this isn't a supported release really (it's dev branch so basically pre-alpha level software), it doesn't warrant a homepage announcement. However, I have it in the updater so anyone running Chrome Dev and the latest Platform beta will see the update and have it installed.
I was wondering if anyone had thoughts on any other ways to approach this. Of course, Chrome Dev is a special outlier case, so it doesn't really apply to much else.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Chrome dev is Solid as Titanium,
I use it as my Default and only browser,
I have a feed notifier extension, so if you release a line "Chrome 466.0 released" into the feed it would be nice.
Sometimes making love is just not enough, you have to step it up!
Chrome 6.0.472.0 dev released, just copy it to the chrom-bin and update the package portable.
Please provide an additional feed for beta/dev releases.
Thanks.
Sometimes making love is just not enough, you have to step it up!
As already stated, we don't do feeds for dev releases. Important betas go out on the main feed. This is a dev release, not intended for daily use. And it is supported as such, meaning we don't rush releases out and won't do all of them.
Like I said, the choice is either we only do dev releases when we do stable and announce them as a footnote. Or we do that and any in between just get pushed out in the updater and posted to the page. It is not an app people use every day so it will not be announced via our RSS feed. And it's kinda silly to create an RSS feed *just* for Google Chrome Portable Dev (we do no other dev versions but Firefox Portable nightly... and that's automated so it needs no updates/announcements).
Sometimes, the impossible can become possible, if you're awesome!
John,
First of all, I really like and appreciate your personal investment of time in the constant evolution and development of the Portable Apps website and applications. I would never have the patience to either do the work, or put up with the impatience of your addictive customers (of which I'me one!). My hat is off to you......Thanks for what you do!!!!
Some thoughts on Google Chrome: I've used Google Chrome Dev. as my default web- browser for over 6 months, and prefer it over anything else. Currently I'm using version 6.0.472.0 on my HP Laptop with Windows 7 HP (64-bit) and 4GB of DDR3. Chrome flies. I used to use the portable version but it seemed to crash my Laptop version when I update the nightly version on my USB flash drive. If I could figure out how to use the most recent Dev. version on both my Laptop & my Flash Drive......I would do it in a minute.
Since I've been using the Chrome Dev. versions, I NEVER have Google extentions crash or fail to work when I do updates. That is definetly NOT
the case with nightly builds of Mozilla Minefield, or the new version of Firefox 4.0 beta 1 Portable. Mozilla Addons seem to need quite a bit of time catching up to the evolution of the browser, while Google Chrome Extensions appear to evolve with the updating of the browser itself.
Last observation: I love your products since they allow me to use Public computers in Government libraries but many of them seem to have Network Administation Firewalls that won't let me use Google Chromium because of proxy restrictions. They don't seem to block Portable Firefox and that is the only reason I use it on Public Libraries......I would prefer to use the most recent developer version of Google Chrome.
Just some thoughts.....I wonder if anyone else shares them.
Clean Shave
CleanShave
I know. And it turns out there are more users of the Dev release than expected (a couple thousand). So we'll be making an effort to get them out. But even so, they'll be outdated often as Dev releases come out weekly. See here for more:
https://portableapps.com/node/24275#comment-154748
Also, you can't connect elsewhere because Chrome doesn't have proxy settings. It uses IE's components for that.
Sometimes, the impossible can become possible, if you're awesome!