Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under browser...

Kaum habe ich (Erik sei dank) Zugang zur schönen neuen Google-Wave-Welt erhalten, musste ich mich gleich nach einem Client dafür umschauen. Und bin mit Waveboard  fündig geworden.

Im Prinzip ist das Programm nichts anderes als ein spezialisierter Browser für Google Wave. Also nichts, was ich nicht auch mit Fluid oder Prism hätte selbst basteln können. Jedenfalls entlastet es meinen Arbeitsbrowser von der Darstellung des doch relativ aufwändigen Wave-Frontends. Und es erspart mir - allein wegen Wave - mit meinem Browser permanent bei Google eingeloggt zu sein und damit alle Suchaktivitäten getrackt zu bekommen...

Drei kleine Dinge sind mit dem Selbstbau mittels Fluid nicht zu bewerkstelligen: Waveboard findet mit einem Icon Platz in der Menüleiste und zeigt an, wenn eine Wave geändert wurde. Darüber informiert es auch mittels Growl. Und in den Menüs bietet es (natürlich mit Tastaturkürzeln versehen) die wichtigsten Befehle zum Bearbeiten der Waves.

Ob und wozu Google Wave etwas taugt, kann ich aktuell noch nicht sagen. Die ersten Test-Waves haben mich noch ziemlich verwirrt. Aber dank dieser Doku hege ich die Hoffnung, bald den Durchblick zu gewinnen.

Systemvoraussetzungen: OS X 10.5 (universal)
Download: Waveboard 0.11 (iPhone Version ebenfalls vorhanden)
Lizenz: Freeware (PRO-Version für 9,- Euro)

Falls ich übrigens doch nicht der letzte war, der noch keine Einladung bekommen hatte: ich hätte jetzt auch ein paar zu vergeben... Kurzer Kommentar reicht. Update: sorry, alle Einladungen sind raus.

Filed under: browser



Site Specific Browsers (SSBs) provide a great solution for your WebApp woes. Using Fluid, you can create SSBs to run each of your favorite WebApps as a separate Cocoa desktop application. Fluid gives any WebApp a home on your Mac OS X desktop complete with Dock icon, standard menu bar, logical separation from your other web browsing activity, and many, many other goodies.
Small OS X window titled 'Fluid' with label 'Convert to Desktop Application', two text fields labeled 'URL' and 'Name' and 'Create' button. The 'URL' text field value is 'facebook.com' and the 'Name' text field value is 'Facebook'.

Fluid includes Tabbed Browsing, built-in Userscripting (aka Greasemonkey), URL pattern matching for browsing whitelists and blacklists, bookmarks, auto-software updates via the Sparkle Update framework, custom SSB icons, a JavaScript API for showing Dock badges, Growl notifications, and Dock menu items, and more.

The Fluid Thumbnail Plug-in allows you to browse the web with CoverFlow or iPhoto-like thumbnail previews for links on the current page. Watch the screencast in the sidebar on the right to see the Thumbnail Plug-in in action. How does the Thumbnail Plug-in know how to find the links on the current page from which to make the thumbnails? Simple... Use CSS selectors to select links or images for a given URL pattern (like *google.com*). Add CoverFlow support for your own site with a simple CSS selector!

http://www.fluidapp.com/

Filed under: browser

joe says...

"Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. (...) Google Chrome OS is being created for people who spend most of their time on the web, and is being designed to power computers ranging from small netbooks to full-size desktop systems."

This will basically make the desktop obsolete. Sounds great.

Filed under: browser

mlevit says...

Last week, Microsoft showed off some browser technology that could help Internet Explorer leapfrog the competition. But if Mozilla succeeds in its hope, Microsoft could be playing catch-up instead.

The technology in question is hardware-accelerated graphics and text using interfaces called Direct2D and DirectWrite that provide an easy way to use graphics cards' computing power. They're built into Windows 7, and Microsoft is bringing them to Windows Vista but not Windows XP.

The performance boost from Direct2D and DirectWrite was the centerpiece of Microsoft's demonstration of Internet Explorer 9 goodies shown last week. Online maps flashed on the screen quickly and tracked mouse movements responsively; text was clearer and changed sizes more gracefully.

But the day of Microsoft's demo, Mozilla evangelist Chris Blizzard had this to tweet: "Interesting that we're doing Direct2D support in Firefox as well--I'll bet we'll ship it first."

There's work to back up his rhetoric. On Sunday, Bas Schouten, the programmer who's been leading the work for Mozilla, posted a prototype of Firefox using the Direct2D and DirectWrite.

Amazing read and fantastic news for us all. While Google tries to speed up webpage load times with a new HTTP protocol layer Microsoft and Mozilla try to speed up the browsers by utilising the computers GPU for graphics rendering.

It makes perfect sense. Why use a CPU to render graphics when the computers graphics card can do a much better job? Thanks to Windows 7 and soon Vista browsers will be able to utilise Direct2D and DirectWrite to render webpages.

It looks like a very promising upcoming technology that will speed up most webpages by around two-fold. Let's just hope Mozilla can release this technology by Firefox 4.0.

Check out Bas Schouten's website benchmarks of Direct2D vs GDI (last link in the quoted section above).

Thanks

Filed under: browser

chrisrutz says...

Filed under: Browser

HikiCulture says...

I decided to look through various Mozilla Firefox themes today since I've not changed my theme for over a month now. After doing a little bit of searching, I decided to make the theme Black Stratini my new default Firefox theme.

The light-colored original version of the Stratini theme is nice as well, but I went with the dark version of it since it goes nicely with my customized dark Windows XP theme.

Damn, is it ever nice!

Filed under: Browser

MhdBadi says...


I just can't accept the idea of having an operating system with only Chrome browser. But I'll try it soon.

Filed under: Browser

For all of you who are visually oriented, look at this tab bar with multiple tabs.

Remember what the one you want now looks like, but not its name?

See the handle bars in the middle? Pull them down.

And now you can see all the tabbed sites. You can close with the same handlebars.

Neat, eh?
Joan Vinall-Cox, PhD
JNthWEB Consulting - http://jnthweb.ca/
Social Media & Learning
http://joanvinallcox.wordpress.com/my-e-portfolio/

Filed under: browser

aulia says...

It's finally out. Camino 2.0 has tab overview which is like Exposé but for browser tabs, it warns you of phishing sites and sites with malware, you can rearrange the tabs, has growl support, has pop-up and flash blockers, and it also supports Keychain.

It's my preferred browser after Safari.

Download Camino 2 here

Filed under: browser

mlevit says...

All advanced Firefox users out there know that there will be a time when some add-ons no longer works with the new version of Firefox you have just upgraded too.

Thankfully there is a quick and simple solution to this problem provided by Mozilla without the need to hack your Firefox's internals. Mozilla has an add-on titled Add-on Compatibility Reporter 0.3 which disables Firefox's compatibility checking and allows all incompatible add-ons to run.

But it not only does that it also allows you to send Mozilla reports on whether the add-ons which have been marked incompatible still work or have stopped working with the new version of Firefox.

After installing the Add-on Compatibility Reporter, your incompatible extensions will become enabled for you to test whether they still work with the version of Firefox or Thunderbird that you're using. If you notice that one of your add-ons doesn't seem to be working the same way it did in previous versions of the application, just open the Add-ons Manager and click Compatibility next to that add-on to send a report to Mozilla.

Even if your add-ons all work fine, if they're marked incompatible, please let us know that they work fine by submitting a success report so we can encourage the add-on developer to update their compatibility information.

We'll collect all of the reports and let add-on developers know what users are having problems with, or if their add-ons seem to work just fine in future versions of the product.

If you encounter problems and want to disable your incompatible add-ons again, uninstalling the Add-on Compatibility Reporter should revert to your previous compatibility checking settings.

via addons.mozilla.org

Thanks

     

Filed under: browser