Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Loading...
Seo Master present to you: This post is part of the Who's @ Google I/O, a series of blog posts that give a closer look at developers who'll be speaking or demoing at Google I/O. Today's post is a guest post written by Dion Almaer of Mozilla's Bespin project

It feels good to be posting on the Google Code blog again. Since moving down the road from Google to Mozilla I have been busy working with my partner in crime, Ben Galbraith, in a new Developer Tools Lab.

The first product of our new team's endeavors was an experiment code named the Bespin project. Ben and I have been talking about the great things that you can do on the Web platform for quite some years. We feel like there is a big sea change happening right now as the various browsers kick into a new gear with fantastic features. The core runtimes on the Web (the browsers) are getting serious horse power. With technologies such as Web Workers, Canvas, advanced caching (application cache), local storage, native video / audio, and screaming fast JavaScript VMs, we feel that a new world of possibilities is going to hit the Web.

It wasn't too long ago that we saw this before, when Ajax hit the Internet and we went from simple applications to richer ones such as Google Maps and Gmail.

We wanted to test out this theory, so we set about creating a new age application that uses the great new technologies stated earlier. Since we are a developer tools lab, would it not make sense for this experiment to be a developer tool? And, what is the grand daddy of all developer tools? The coding environment that developers use to build applications. How "meta" :)

Being Mozilla, we released a very early version of Bespin that is 100% open source, so the community could form. It has been a fantastic ride even in the short opening months. The editor is fully Web based, and "by the Web, on the Web." Being a former Emacs Lisp hacker, I have known how powerful it is to have an environment that you can change for your own work flow, using a language that you know and love. Why shouldn't today's world of Web developers be able to have a great tool that they can change using Web technology? Yet another reason for Bespin.

We have just released version 0.2 of Bespin, and it has features such as version control built in, rich syntax highlighting, real-time code analysis, a command line that that you can create your own commands for, and a fancy dashboard. We are proud of where we are in short order, but there is much to be done. In the lab we have collaboration support in place and will be deploying soon. We are incredibly excited about some exciting use cases. Wouldn't it be interesting if:
  • You could "follow" a developer and see how he codes? I would love to follow Brendan Eich, the creator of JavaScript, as he hacks on TraceMonkey!
  • You could do a live code review with someone, and both edit the code in place, a la SubEthaEdit or Google Docs?
  • Have a chat session that associates itself with the code files, so you can go back and see the conversations around a bit of code?
  • You were told that someone else is editing in the same file so you can quickly commit the code so they have to do the merge :P
  • You could search and subscribe to others commands, which will then be automatically updated for you
  • And much much more, as you can see on our Roadmap
To see more about Bespin, check out our video, or visit our community home:

.

This is the first of many tools that will come out of our lab. It is important to note that these tools are for the Open Web as a whole. Just because we are at Mozilla doesn't mean that we only care about Firefox, far from it. Bespin itself runs on multiple bleeding edge browsers!

I am very excited to have been asked back to Google I/O (May 27-28) to speak not only about Bespin, but about the Open Web platform itself. I can't wait to share more of our community's work pushing the Open Web forward, and would love feedback on our projects and what you really need from us as developers. Hope to see you in May!

By Dion Almaer, Developer Tools Lab at Mozilla2013, By: Seo Master

seo Bespin: an experiment in giving developers a productive and fun environment on the Open Web 2013

Seo Master present to you:
Blogger Navigation Bar

In every blog there is a blogger default navigation bar (nav bar) of the above style. This nav bar make your blog look less professional. These navigation bars can be removed using a simple CSS one line code.

Also read: Remove Subscribe to: Posts (Atom) Link on Blogger

Removing Blogger Deafult Nav Bar


Apply these steps to remove the Blogger Navigation bar / Blogger Nav Bar.
Steps:

  • Log-in to your blog
  • Template >> HTML >> Proceed
  • Search For this code  ]]></b:skin>   (tip: Use CTRL+F)
  • Now Just above/before  ]]></b:skin>   insert following code

#navbar-iframe,#navbar { display: none !important; }

Save your template and view your blog. Blogger Navigation Bar will no longer be there.
2013, By: Seo Master

seo How to remove Blogger Navigation Bar? 2013

Seo Master present to you:

Cross-posted from the Google Checkout Blog

By Amit Fulay, Product Manager and Mikhail Seregine, Software Engineer

Today at Google I/O, we launched the developer API of Google In-App Payments for the web. In-App Payments enables any web application to receive payments from users and keep them engaged in your application. It is available to all US developers in sandbox today and will be followed by a consumer launch and an international rollout over the summer.

The team started building Google In-App Payments soon after Jambool was acquired by Google in August 2010. This project brought Social Gold technology and expertise and combined it with Google scale. For the payments platform that we’re announcing today, the theme is simplicity:

The simple API makes integration fast so you can start getting paid sooner. Implementing In-App Payments requires only two API calls: one to initiate the payment, and one to accept the notification when a payment is made.

The simple user experience will let your users pay without leaving the app or entering billing details. Users who have previously completed a purchase on Google Checkout, Android Market, Google eBookstore, YouTube Movies and more can use that same account to pay for items in your app in minimal steps. Fast payments that keep users in your game or site can boost customer conversion rates, increasing your revenue.

The simple pricing model is a flat payment processing fee of 5%. It’s 5% whether you distribute your app yourself or via the Chrome Web Store. There are no fixed purchase fees, setup costs, or monthly minimums.

The JavaScript version of the In-App Payments API is available to developers today. A Flash version of the API will be available in the coming weeks.

We invite you to sign up, start integrating your apps and send us feedback. Let’s work together to delight consumers this summer with amazing web apps, monetized effectively, all in the app.
2013, By: Seo Master

seo Making money with Google In-App Payments for the Web 2013

Powered by Blogger.
Design by Dev Nasser