Facebook tricks, Windows trick, Google trick, Internet hacking, Ethical Hacking, gmail tricks, Technological news, Software Crack, Mobile Tricks, Blogging Trick, ebay Trick, Computer program, LAN hacking, WAN hacking, cookies stealing, Email Tracing
Friday, March 2, 2012
Firefox's Jetpack extensions reach mobile browsing
Firefox's Jetpack extensions reach mobile browsing | Deep Tech - CNET News CNET News @import "http://i.i.com.com/cnwk.1d/Ads/common/css/SponsoredTextLink/sponsoredTextLink.live.css"; Manage Packages With UPS My Choice Home Reviews Cell Phones Camcorders Digital Cameras Laptops TVs Car Tech Forums Appliances Cell Phone Accessories Components Desktops E-book Readers Games and Gear GPS Hard Drives & Storage Headphones Home Audio Home Video Internet Access Monitors MP3 Players Networking and Wi-Fi Peripherals Printers Software Tablets Web Hosting You are here: News Latest News Mobile Startups Cutting Edge Media Security Business Tech Health Tech Crave Apple Microsoft Politics & Law Gaming & Culture Blogs Video Photos RSS Download Windows Software Mac Software Mobile Apps Web Apps The Download Blog CNET TV How To Computers Home Theater Smartphones Tablets Web Marketplace Log In | Join Log In Join CNET Sign in with My profile Log out .mad_center {text-align:center;} .mad_center div, .mad_center table, .mad_center iframe, .mad_center a img {margin-left: auto; margin-right: auto;} CNET News Deep Tech Firefox's Jetpack extensions reach mobile browsing by Stephen Shankland February 22, 2012 8:40 AM PST Follow @stshank
Mozilla has begun adding mobile device support to its newer extensions framework--but it's also change Jetpack's direction and breaking earlier extensions' compatibility.
(Credit:Mozilla)
Not long after Mozilla brought its browser toAndroid, the organization has adapted its Jepack tools for building browser add-ons for mobile use, too.
"Now you can start developing add-ons for the mobile version ofFirefox," said Mozilla's Dave Mason in a mailing list message yesterday about the latest Jetpack, formally called the Add-on SDK version 1.5. "For this initial release we have the page-mod API working so that you can, among other things, create add-ons that will display mobile-friendly versions of Web sites that do not have that option."
The mobile market is very important, given the tremendous growth in browsing from mobile phones andtablets, but Mozilla is having a tough time getting a foothold. The non-profit organization is effectively shut off from Windows Mobile and iOS, and Google just released a beta version of its Chrome for Android.
But Mozilla is working hard on its Android browser--and building a browser-based mobile OS called Boot to Gecko (B2G) that it plans to showcase next week at Mobile World Congress. All this work is central to Mozilla's hope to break the ecosystem locks in the mobile market that make it difficult for programmers and device owners to switch from one group of technologies to another.
Related storiesDoes your browser feed the cookie monster--or starve it?Mozilla contemplates nuking McAfeeComing in 2012: Firefox for Windows 8's MetroMozilla's plan for 2012: Break the ecosystem lock
Jetpack lets people expand Firefox's abilities through use of extensions built with Web programming technologies such as HTML, JavaScript, and CSS. Jetpack lives alongside Firefox's earlier add-ons that use the more powerful but complicated XUL technology.
Part of the promise of Jetpack is that Firefox updates shouldn't break add-on compatbility as often as with traditional XUL add-ons, because Mozilla aims to keep the Jetpack interfaces stable across.
However, Mason also said one aspect of Jetpack is changing, so Jetpack add-ons will need to be rebuilt for Firefox 11:
In Firefox 11 (currently the Firefox beta release) we removed the nsIDOMNSElement, which is heavily used in the SDK. We've updated the SDK to handle this change, but this means that add-ons built with earlier versions of the SDK will not work with Firefox 11.So if you have add-ons built with earlier versions of the SDK, you'll need to repack them using this version of the SDK.
At the same time, Mozilla is easing some of the pains of traditional add-ons. It's now possible for some add-ons to be installed or updated without requiring a browser restart, and Mozilla is marking add-ons as compatible by default with future versions of Firefox since most of them don't actually break with Firefox updates.
Mozilla is making deeper changes to Jetpack, too, according to a recently posted Jetpack 2012 road map.
A problem led to the changes: Mozilla had geared Jetpack for two audiences that it now believes aren't actually likely to use it.
The first of those are programmers looking to develop sophisticated extensions, but Mozilla now believes they're more likely to make full-on Web apps. The second are those who want to use the Greasemonkey technology to modify Web pages as they load, but Jetpack is too heavy and complicated for them, Mozilla believes.
The new road map said this about the change:
With shallow-integrators having better options coming in the form of apps, and the Jetpack project never really satisfying the Greasemonkey-scripters properly, we are proposing that we now turn our focus to the "Deep-Integrators."
Deep-integrators are the backbone of Firefox's add-on community. They are the developers who have made Firefox unique among browsers. While the SDK is still useful to them in its current state, we can make it an excellent toolset for them that offers a better platform than the traditional tools have.
The spotlight of this change will be "chrome mods," the ability to change the browser's user interface. (Chrome here refers to the frame around the Web pages in a browser, not to Google's browser.)
"With a new focus on deep integrators we want to investigate what kinds of modifications we can allow SDK developers to make to the desktop UI [user interface]," Mozilla's chrome-mods wiki page states. "Chrome mods should allow the developer to easily alter Firefox chrome in a manner that is very similar to page-mods with the exception that the chrome being altered must first be properly identified before the developer can alter that element."
No comments:
Post a Comment