Internet Explorer 9, developer preview -- speed, graphics and HTML5 demos within originally appeared on Download Squad on Tue, 16 Mar 2010 12:12:00 EST. Please see our terms for use of feeds.

Rey Bango (Ajaxian and now Microsoft employee) will do a post that rounds up the news from MIX today where the IE9 team shared a first preview release of IE9 that comes with new features from HTML5+ (video, SVG, CSS3, addEventListener, JavaScript compilation spread across multicore, and more). All of this is hardware accelerated. Yum. Missing was news on canvas and I didn't see deets on CSS transforms and the like (which would be awesome with hardware acceleration too).

John Resig just got on stage to talk about the collaboration between jQuery and Microsoft and how Microsoft is now contribution resources and code. For example, templates (all on GitHub which gives you:

•  
• <script type="text/javascript">
•  
•     var product = { name: "Laptop", price: 788.67 };
•  
•     $(showProduct);
•  
•     function showProduct() {
•         $("#results").html( tmpl("productTemplate", product) );
•     }
•  
•     function formatPrice(price) {
•         return "$" + price;
•     }
•    
• </script>
•  
• <script type="text/html" id="productTemplate">
•     Product Name: <%= name %>
•     <br />
•     Product Price: <%= formatPrice(price) %>
• </script>
•  
• <div id="results"></div>
•  

More later....

Filed under: Microsoft, Browsers

• Speed -- faster, generally (waiting on details).
• Standards -- CSS3 support, higher Acid3 score, 55/100 currently. (Acid4 will be released soon no doubt...)
• JavaScript -- new engine, faster, uses multiple cores! Codenamed 'Chakra' (sounds a bit like Carakan...)
• Interface -- the interface looks significantly different. Very minimal? (this is a developer build, though, so who knows)

Internet Explorer 9 details emerge at MIX10, tech demo downloadable now originally appeared on Download Squad on Tue, 16 Mar 2010 12:00:00 EST. Please see our terms for use of feeds.

Microsoft today released the Windows Internet Explorer Platform Preview to the public. The release is meant to demonstrate the capabilities of Internet Explorer 9 to Web developers while at the same time providing feedback to the IE9 team. Microsoft says it is committed to updating the Platform Preview to keep a more effective rhythm for discussion, and it will be updated every eight weeks or so. Microsoft will share feedback with standards-setting bodies in addition to using it for internal development.

The Platform Preview is a minimal wrapper: it's not a full-fledged browser. It has no tabs. It has no address bar. It has no back button. So what is included? Everything that Web developers need to see: the rendering engine, of course, as well as the new JavaScript engine, hardware acceleration features, and the developer tools. The IE9 team told Ars that each update will use one of the latest internal engineering builds, at which point the feedback loop will start again.

Read the comments on this post

Twitter founder Evan Williams was widely expected to announce an advertising platform at the SXSW conference yesterday, but while he announced something with dozens of major media partners, it wasn’t an ad platform — it was something called @anywhere. And what is @anywhere? Good question. In fact, that’s just one of the many good questions that attendees hoped in vain would be asked by Umair Haque of Harvard Business Review, whose interviewing skills received less than critical acclaim during and after the keynote.

The official Twitter blog entry about the launch of @anywhere isn’t much help when it comes to answering the question of what the new service is — or at least it’s not as much help as you might expect it to be, what with this being one of the most hotly-awaited SXSW keynotes in recent memory. The blog post describes the service as recreating the kind of ‘open, engaging interactions” between users that Twitter provides, but integrating that into any web site through Javascript, and thus “providing a new layer of value for visitors without sending them to Twitter.com.”

And that’s pretty much it. No descriptions of what this might involve, no screenshots of what it might look like (although the Los Angeles Times seems to have whipped up its own), just some logos of partners like eBay and Yahoo and Digg. The way Twitter has described it, @anywhere will allow readers of articles at the New York Times and other sites to click and follow writers directly from their bylines, and — judging by what Evan Williams told Anil Dash on Twitter — will also let them click and see information about popular Twitter users who are mentioned on a participating site, by way of a popup window triggered by mousing over a link, similar to the hover popups at Twitter.com.

So then @anywhere is popup windows? Not exactly the earth-shattering announcement everyone seemed to be hoping for. As Liz has pointed out, these types of features — following someone from a page, posting something to Twitter directly from a site, etc. — are already widely available through a number of services and features built into sites (such as the New York Times). There has been some speculation that @anywhere will also be a competitor for Facebook Connect, allowing users to log in with their Twitter credentials (also something that many sites already do) and then incorporate their behavior on the site into their Twitter stream somehow.

• Twitter CEO Ev Williams: Further @Anywhere Details at Chirp Conference Tech Insider
• SXSW: Twitter to Launch @Anywhere, Fails to Live Up to SXSW Hype Tech Insider
• Ning’s CEO Shuffle: Gina Bianchini Steps Down Tech Insider
• Google Buzz: Should You Cross the Streams? Tech Insider

It’s worth noting, however, that neither the Twitter blog post nor Evan Williams’ keynote suggested anything like the kind of features that Facebook Connect provides by being integrated into sites such as The Huffington Post — although Williams told Om on Twitter that more details would be coming at the company’s upcoming Chirp conference. Hopefully those details will flesh out a service that provides some real bang for Twitter, because so far @anywhere seems like a bit of a whimper.

For the GigaOM network’s complete SXSW coverage, check out this round-up.

Related content from GigaOM Pro (sub req’d):

Why NewNet Companies Must Shoulder More Responsibility

Post and thumbnail photos courtesy of Flickr user b_heyer

Twitter, web sitenize veya blogunuza, birkaç satırlık JavaScript kodunu kopyalayıp yapıştırmak suretiyle, Twitter.com'un sunduÄŸu birçok iÅŸlevsel/fonksiyonel özelliÄŸi kolayca entegre edebilmenizi saÄŸlayacak olan yeni platformu/projesi @anywhere'i duyurdu.



Twiter, bu yeni platformu/projesi/özelliÄŸi/ ile Web sitesi sahiplerinin, çok daha fazla uzmanlık ve uÄŸraşı isteyen Twitter API ile uÄŸraÅŸmadan, web sitelerini Twitter ile entegre edebilmelerini ve bu entegrasyonla;
web sayfasında Twitter adresi bulunan birisini ziyaretçiler takip etmek istediklerinde; herhangi bir linke tıklayıp Twitter.com'a gitmeye gerek duymadan, sanki Twitter.com'daymış gibi, açılan küçük bir pencere yardımıyla, takip etmeye baÅŸlayabilmelerini saÄŸlayacak türden birçok özelliÄŸi, kendi web sitelerinde kullanabilmelerine olanak tanımakta.

devamını oku »

ilgili yazılar

• Facebook Sayfanızı Involver Ä°le ZenginleÅŸtirin! (6)
• Get Satisfaction, Facebook Sayfanızda! (1)
• Facebook'ta Müzik Dinlemek Ä°çin: Muziic (6)
• Facebook'un Önerisi: PromoQube! (0)
• "KeÅŸke Bir Mikro Blog Servisim Olsaydı!" Diyenl... (3)
• HootSuite'ten iPhone Ä°çin Twitter Uygulaması! (0)
• Beslemelerinizi Feedburner'dan Tweetleyin! (5)
• Facebook'tan Tweetleme, Eli Kulağında! (0)
• Web Sitesini SosyalleÅŸtirmeyene Kız Vermiyorlar! (5)
• Glydo'dan Ä°ÅŸe Yarar Öneriler! (1)

bu yazı algoz tarafından bildirgec.org adresli sitede yayımlanmak üzere yazılmıştır. kaynak gösterilmeksizin kopyalanamaz.

etiketler: uygulama, platform, bonus, twitter, sosyal medya, web 3, social media, anywhere, mikro bildiri, web os, bonuslu bildiri

The Chromium folk have posted about JavaScript conformance as they release a test runner for Sputnik, that allows you to easily run the complete test suite from within your browser:

Sputnik touches all aspects of the JavaScript language defined in the 3rd edition of the ECMA-262 spec. In many ways it can be seen as a continuation of and a complement to existing browser conformance testing tools, such as the Acid3 test. While we are always focused on improving speed, Sputnik is not about testing how fast your browser executes JavaScript, but rather whether it does so correctly.

Since we released the Sputnik tests as an open source project, the most requested feature has been the ability to run the tests in a browser, and we are excited to launch that functionality today. The new test runner lets you run the tests from a single URL and quickly see the results in your browser. This makes it easier both for users to see how well their browser conforms to the JavaScript spec, as well as for browser makers to find bugs and incompatibilities.

You can also use Sputnik to compare browser conformance.

The dart board shows relative conformance based on the number of tests that hit or miss. Of course, in the real world, all tests are not equal. This has been an issue with Acid tests. The race to 100 is socially interesting, but if you miss a few core tests that could be worse than meeting 10 corner cases in SVG :)

Twitter CEO Evan Williams just announced at SXSW that his company is taking another step to integrate with the rest of the web with a new platform called @anywhere. Operators of third-party websites will be able to plug in @anywhere to integrate some basic Twitter functionality without requiring their users to navigate away from a page.

When you visit a website that supports @anywhere, you’ll be able to follow any Twitter account associated with that site without navigating away to the profile at Twitter.com. The Twitter blog suggests that the platform will let you follow a participating journalist from his or her byline. It also suggests that you’ll be able to tweet about a YouTube video without interrupting it.

More @anywhere features are planned; Twitter says the above-mentioned items are are “just the beginning.” Integrating with the rest of the web is a wise move. Facebook’s Facebook Connect platform is dominating right now, and while Twitter has a similar login platform, it’s lost its head start when it comes to openness and integration.

The person or organization behind a website can drop some JavaScript in the website to integrate with @anywhere, so there won’t be any arcane Application Programming Interface (API) to learn and implement. Initial partners will include Amazon, AdAge, Bing, Citysearch, Digg, eBay, The Huffington Post, Meebo, MSNBC.com, The New York Times, Salesforce.com, Yahoo, and — as mentioned above — YouTube. Twitter hasn’t said when those sites will begin using @anywhere.

Future announcements regarding the platform will come from the @anywhere Twitter account — you get one guess as to what the username is. Platform/API guru Ryan Sarver promised “lots more details” at the Chirp Twitter developer conference this April 14 and 15.

Tags: at-anywhere, ev, evan williams, sxsw, sxsw-2010, trending, twitter

Watching Twitter CEO Ev Williams on stage at South by Southwest Interactive is a reminder that it’s still a work in progress—and watching people trying to cram into the overflow keynote was a reminder of just how much is expected. Ditto watching the steady stream leave as the interview by Umair Haque continued. The big news is the official announcement of @anywhere, a new Twitter platform that will let companies like Amazon (NSDQ: AMZN) and the New York Times feed Twitter results directly from their own sites, or, as Williams puts it, ‘giving people value with as little effort as possible.” Twitter becomes part of any site, not a destination, with a few lines of javascript. But what does it mean in terms of money? Advertising? Nothing that concrete out of this session. More to come.

During his keynote at SXSW this afternoon (live blog here), Twitter CEO Evan Williams just announced a new “At Anywhere” platform, which allows websites to more deeply integrate the service into their sites. The idea is to offer a more seamless experience to Twitter users navigating third party sites like the Huffington Post and the New York Times, giving them Twitter content without forcing them to jump off the page they’re currently viewing. The details on the new platform are still scant, but this is Twitter’s answer to Facebook Connect, which we reported on back in January.

Among the features:

• When you browse a site that uses @anywhere, people and brands that have Twitter accounts will be highlighted with a hyperlink. Mousing over that hyperlink will show a small box (a “hovercard”) containing their Twitter information, including their most recent tweet (in effect it means you don’t have to click over to Twitter’s homepage to see their Twitter profile)
• Publishers will be able to more deeply integrate their own Twitter profiles, making them easier for their readers to ‘follow’ them
• Sites will be able to implement @anywhere with a few lines of Javascript.
• The new platform is launching with a number of major sites and services, including the New York Times, Huffington Post, Meebo, Amazon, Yahoo, Bing, and eBay.

It looks like the platform may eventually be hosted at Twitter.com/anywhere, which currently features a placeholder Twitter account that tweeted “Stay Tuned”. Update This may actually be a Twitter account related to the platform — it just tweeted “If you’re a javascript guru and want to help us build @anywhere and work with publishers @jointheflock”.

From the Twitter blog:

We’ve developed a new set of frameworks for adding this Twitter experience anywhere on the web. Soon, sites many of us visit every day will be able to recreate these open, engaging interactions providing a new layer of value for visitors without sending them to Twitter.com. Our open technology platform is well known and Twitter APIs are already widely implemented but this is a different approach because we’ve created something incredibly simple. Rather than implementing APIs, site owners need only drop in a few lines of javascript. This new set of frameworks is called @anywhere.

When we’re ready to launch, initial participating sites will include Amazon, AdAge, Bing, Citysearch, Digg, eBay, The Huffington Post, Meebo, MSNBC.com, The New York Times, Salesforce.com, Yahoo!, and YouTube. Imagine being able to follow a New York Times journalist directly from her byline, tweet about a video without leaving YouTube, and discover new Twitter accounts while visiting the Yahoo! home page—and that’s just the beginning. Twitter has proven to be compelling in a variety of ways. With @anywhere, web site owners and operators will be able to offer visitors more value with less heavy lifting.

Vous connaissez tous Google maps et les applications qui peuvent en découler sur SPIP ?

Mais savez-vous qu'il existe une ribambelle d'API Google applicables à SPIP.

Procédons par étapes

• Les Google Maps
• Les Graphes ( camemberts, courbes, histogrammes, gauges)
• Les geo maps
• Les gadgets

Elles présentent souvent un aspect ludique dans un site internet et bien pratique pour géolocaliser un lieu ou pour proposer un itinéraire. L'API Google Maps est connu sous trois versions : V1, V2 (la plus utilisée) et enfin la V3 en cours de développement et qui ne nécessitera plus de clé.

Le plugin SPIP le plus connu étant GIS Escoitar

Il est bien entendu possible de faire des tas d'autres choses avec Google Maps et SPIP comme ces exemples :

Lieux intéressants

Itinéraires

Ou encore des Street Views

Accompagné d'un fichier xml, il est également possible de faire passer des tas d'informations dans les markers, les positionner, ajouter des images, du son, etc.. Couplé avec un fichier kml, on peut créer des zones de couleurs, des tracés, des cercles, des polylignes etc..

Un autre API bien pratique est celui qui permet de faire des graphes dynamiques comme celui-ci :

Camembert. Cliquez un peu partout pour voir des effets intéressants. Dans cette exemple on affiche la popularité relative et absolue des dix derniers articles déposés sur le site. Il n'est pas necessaire d'avoir de grandes connaissances en javascript pour obtenir ces jolis graphiques.

Un Histogramme : exemple

Le principe est le même que pour le camembert

D'autres exemples ( certains étant des gadgets pas toujours très utiles ) Sur la page des API's Google

Cedric Dugas feels so passionate about fixed positioning in WebKit that he created A Better Mobile Web to talk about it:

The Problem

It is impossible to have an element fixed in CSS on the page in the mobile Webkit browser. When you are surfing the web on your phone, webkit opens the page completely and acts as a viewport.

“Imagine a book in front of you. Take a piece of paper, cut a 320*416 square in it, and lay it over the book. To read the book, move the paper around and position the hole over the words you want to see.” -Richard Herrera

Why it is important

To create better mobile applications and websites, we need fixed positionning to give the user better tools to browse the web on handled devices. Like a real mobile app, we could have a fixed toolbar when scrolling on a site, it is critical to not take the user in hostage in very long list or on long content pages. This is something we can’t really emulate in javascript as mobile devices are not really powerful.

The solution

The Webkit team could give us a proprietary CSS property that would overwrite the viewport behavior, and this is the proposition here. Give us a CSS property like position: -webkit-viewport-fixed that we can apply on a div so it can be fixed to the viewport.

That is one feature request, but surely there we can add to that? The broad domain of “abettermobileweb.com” deserves more!

What would you like to see for mobile specifically that isn’t covered in the current Web and device API standard work?

Voici une idée plutôt séduisante pour proposer plusieurs URLs dans un seul lien.

Pluralink permet effectivement de proposer plusieurs URLs accessibles à travers un seul lien dans le corps d'un texte, et ce via l'ajout d'un petit code en javascript.

C'est typiquement le genre de scripts qui peuvent permettre d'apporter des petits plus et de se différencier des autres blogs lors de la création d'un thème Wordpress.

=> Lire la suite!

Ben Cherry has a really nice detailed analysis of the module pattern.

He starts with the simple pattern that Crock-y documented back in the day..... and then goes on to discuss augmentation (loose and strict) and then deeper into some cool patterns:

Cloning and Inheritance

•  
• var MODULE_TWO = (function (old) {
•     var my = {},
•         key;
•      
•     for (key in old) {
•         if (old.hasOwnProperty(key)) {
•             my[key] = old[key];
•         }
•     }
•      
•     var super_moduleMethod = old.moduleMethod;
•     my.moduleMethod = function () {
•         // override method on the clone, access to super through super_moduleMethod
•     };
•      
•     return my;
• }(MODULE));
•  

This pattern is perhaps the least flexible option. It does allow some neat compositions, but that comes at the expense of flexibility. As I've written it, properties which are objects or functions will not be duplicated, they will exist as one object with two references. Changing one will change the other. This could be fixed for objects with a recursive cloning process, but probably cannot be fixed for functions, except perhaps with eval. Nevertheless, I've included it for completeness.

Cross-File Private State

One severe limitation of splitting a module across multiple files is that each file maintains its own private state, and does not get access to the private state of the other files. This can be fixed. Here is an example of a loosely augmented module that will maintain private state across all augmentations:

•  
• var MODULE = (function (my) {
•     var _private = my._private = my._private || {},
•         _seal = my._seal = my._seal || function () {
•             delete my._private;
•             delete my._seal;
•             delete my._unseal;
•         },
•         _unseal = my._unseal = my._unseal || function () {
•             my._private = _private;
•             my._seal = _seal;
•             my._unseal = _unseal;
•         };
•      
•     // permanent access to _private, _seal, and _unseal
•      
•     return my;
• }(MODULE || {}));
•  

Any file can set properties on their local variable _private, and it will be immediately available to the others. Once this module has loaded completely, the application should call MODULE._seal(), which will prevent external access to the internal _private. If this module were to be augmented again, further in the application's lifetime, one of the internal methods, in any file, can call _unseal() before loading the new file, and call _seal() again after it has been executed.

This pattern occurred to me today while I was at work, I have not seen this elsewhere. I think this is a very useful pattern, and would have been worth writing about all on its own.

Sub-modules

Our final advanced pattern is actually the simplest. There are many good cases for creating sub-modules. It is just like creating regular modules:

•  
• MODULE.sub = (function ()) {
•     var my = {};
•     // ...
•      
•     return my;
• }());
•  

While this may have been obvious, I thought it worth including. Sub-modules have all the advanced capabilities of normal modules, including augmentation and private state.

Nice work Ben!