Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
video:player_loc
or video:content_loc
. In the case of an mRSS feed, these equivalent tags are media:player
or media:content
, respectively. We need this information to verify that there is actually a live video on your landing page and to extract metadata and signals from the video bytes for ranking. If one of these tags is not included we will not be able to verify the video and your Sitemap/mRSS feed will not be crawled. To reduce confusion, here is some more detail about these elements.video:player_loc
or content video:content_loc
location is required. However, we strongly suggest you provide both, as they each serve distinct purposes: player location is primarily used to help verify that a video exists on the page, and content location helps us extract more signals and metadata to accurately rank your videos. URL extensions at a glance:
Sitemap: mRSS: Contents: <loc> <link> The playpage URL <video:player_loc> <media:player> (url attribute) The SWF URL <video:content_loc> <media:content> (url attribute) The FLV or other raw video URL
NOTE: All URLs should be unique (every URL in your entire Video Sitemap and mRSS feed should be unique)
Friends, This is a secret tool to hide your content from strangers. It protect your content without loss any data. You can convert text,HTML,JavaScript etc, in to Un escape format. Also you can decode your content with this tool. Just paste your Text,HTML,JavaScript on first box then hit Encode button. Your text will encode like %3C%73%63%72%69%70%74% format. You can decode it easily, Just copy this encoded code second box. then hit on Decode button. Are you happy now enjoy…..
{2. In the Chrome manifest, we specified the relevant file types to which the service applies. In our case, that's most file types, as seen below. Specialized services may just want certain types, such as images for Picasa.
"name”: "Box Uploader",
...
"file_browser_handlers": [
{
"id”: "upload",
"default_title": "Save to Gallery", // What the button will display
"file_filters": [
]
}
],
"file_browser_handlers": [3. With some JavaScript code connecting to the file browser handler, we set up a way to upload files through Box’s Quick Importer.
{
"id": "upload",
"default_title": "Save to Box",
"file_filters": [
"filesystem:*.*"
]
}
],
var fm = new FileManager();That's actually all there was to the integration.
fm.uploadServer = 'https://www.box.net/<...>';
if (bgPage && bgPage.filesToUpload.length) {
var entry;
while(entry = bgPage.filesToUpload.pop()) {
entry.file(function(file) {
fm.uploadFile(file);
});
}
}
JavaScript libraries let developers do more with less code. But JavaScript libraries need to work on a variety of browsers, so using them often means shipping even more code. If JQuery has code to support XMLHttpRequest over ActiveX on an older browser like IE6 then you end up shipping that code even if your application doesn't support IE6. Not only that, but you ship that code to the other 90% of newer browsers that don't need it.
This problem is only going to get worse. Browsers are rushing to implement HTML5 and EcmaScript5 features like JSON.parse that used to be provided only in library code, but libraries will likely have to keep that code for years if not decades to support older browsers.
Lots of compilers (incl. (JSMin, Dojo, YUI, Closure, Caja) remove unnecessary code from JavaScript to make the code you ship smaller. They seem like a natural place to address this problems. Optimization is just taking into account the context that code is going to run in to improve it; giving compilers information about browsers will help them avoid shipping code to support marginal browsers to modern browsers.
The JavaScript Knowledge Base (JSKB) on browserscope.org seeks to systematically capture this information in a way that compilers can use.
It collects facts about browsers using JavaScript snippet. The JavaScript code (!!window.JSON && typeof window.JSON.stringify === 'function') is true if JSON is defined. JSKB knows that this is true for Firefox 3.5 but not Netscape 2.0.
Caja Web Tools includes a code optimizer that uses these facts. If it sees code like
if (typeof JSON.stringify !== 'function') { /* lots of code */ }
it knows that the body will never be executed on Firefox 3.5, and can optimize it out. The key here is that the developer writes feature tests, not version tests, and as browsers roll out new features, JSKB captures that information, letting compilers produce smaller code for that browser.
The Caja team just released Caja Web Tools, which already uses JSKB to optimize code. We hope that other JavaScript compilers will adopt these techniques. If you're working on a JavaScript optimizer, take a look at our JSON APIs to get an idea of what the JSKB contains.
If you're writing JavaScript library code or application code then the JSKB documentation can suggest good feature tests. And the examples in the Caja Web Tools testbed are good starting places.
Update: The described product or service is no longer available. More information.
http://www.metrokitchen.com/nice-404-page
"If you're looking for an item that's no longer stocked (as I was), this makes it really easy to find an alternative."-Riona, domestigeek
http://www.comedycentral.com/another-404
"Blame the robot monkeys"-Reid, tells really bad jokes
http://www.splicemusic.com/and-another
"Boost your 'Time on site' metrics with a 404 page like this."-Susan, dabbler in music and Analytics
http://www.treachery.net/wow-more-404s
"It's not reassuring, but it's definitive."-Jonathan, has trained actual spiders to build websites, ants handle the 404s
http://www.apple.com/iPhone4g
"Good with respect to usability."
http://thcnet.net/lost-in-a-forest
"At least there's a mailbox."-JohnMu, adventurous
http://lookitsme.co.uk/404
"It's pretty cute. :)"-Jessica, likes cute things
http://www.orangecoat.com/a-404-page.html
"Flow charts rule."-Sahala, internet traveller
http://icanhascheezburger.com/iz-404-page
"I can has useful links and even e-mail address for questions! But they could have added 'OH NOES! IZ MISSING PAGE! MAYBE TIPO OR BROKN LINKZ?' so folks'd know what's up."-Adam, lindy hop geek
The Googleplex is really buzzing this week with people furiously preparing for Google I/O! As with any conference, there are physical limits on how many people can participate, so we’re striving to make the Google I/O Extended events around the world more interactive than just simple viewing parties. Yesterday, we got to share the details of the Develop For Good hackathon contest sponsored by Google.org in conjunction with Google I/O Extended.
But this certainly isn’t the first time Google.org has engaged with developers to help make our planet a better place. In fact, many Googlers recently participated in Random Hacks of Kindness Global, a twice-annual event where developers in 21+ cities around the world spark new ideas for making the world a better place through innovation and technology. Among the many projects, one team in San Francisco worked on an algorithm for scanning textbooks and processing mathematical formulae in an accessible way for users with vision impairment. Take some time this weekend to read the recaps and get inspired!
The Chinese space program may also make this an inspiring weekend when they attempt the country’s first manned docking mission, designated Shenzhou 9, and take off for the Tiangong 1 space laboratory on Saturday. The attempt becomes even more inspiring since the three-person crew will include the first female Chinese astronaut. We wish them godspeed.
Meanwhile, scientists at NASA in the United States are awaiting the arrival of a new Mars rover which will search for signs of life in a new way. The rover, named Curiosity, is scheduled to land on the red planet in August, well ahead of any humans who might one day be en route. Who can imagine what it might find there?