Jetpack/FAQ: Difference between revisions

Jump to navigation Jump to search

Jetpack/FAQ (view source)

Revision as of 21:05, 15 February 2012

315 bytes removed ,  15 February 2012
→‎General
Line 30: Line 30:


Developers and users alike also will not have to worry about add-on compatibility with new versions of Firefox.  
Developers and users alike also will not have to worry about add-on compatibility with new versions of Firefox.  
Finally, add-ons built with these tools will soon load in separate processes, so slow-running add-ons won't slow down Firefox itself.


'''Can I do everything with the Add-on SDK and Add-on Builder Beta that I could with a XUL-based add-on? Should I rewrite my XUL-based add-on now? '''  
'''Can I do everything with the Add-on SDK and Add-on Builder Beta that I could with a XUL-based add-on? Should I rewrite my XUL-based add-on now? '''  
Line 45: Line 43:
Add-on Builder and the Add-on SDK are aimed primarily at Web developers who wish to write add-ons but are unfamiliar with the traditional XUL-based approach. So it supports a set of easy-to-use high level JavaScript APIs which address the most common use cases encountered by add-on developers. Using only the high level APIs, you can't do everything a XUL-based add-on can do.  
Add-on Builder and the Add-on SDK are aimed primarily at Web developers who wish to write add-ons but are unfamiliar with the traditional XUL-based approach. So it supports a set of easy-to-use high level JavaScript APIs which address the most common use cases encountered by add-on developers. Using only the high level APIs, you can't do everything a XUL-based add-on can do.  


After shipping version 1.0 of the Add-on SDK and the Add-on Builder Beta, one of our top priorities is to help developers migrate from XUL-based add-ons to Builder/SDK based add-ons, so implementing advanced add-ons will become much easier.  
However, we're adding to the set of high level APIs, to make it easier to write advanced add-ons using the SDK and Builder.  


So if you're a XUL add-on developer, an early adopter, and are willing to participate in the development process, then now is a great time to try out the Add-on SDK and Add-on Builder and help us figure out the right set of features to enable you to make the transition.  
So if you're a XUL add-on developer, an early adopter, and are willing to participate in the development process, then now is a great time to try out the Add-on SDK and Add-on Builder and help us figure out the right set of features to enable you to make the transition.  
Line 55: Line 53:
'''What are the system requirements for the Add-on Builder Beta? '''  
'''What are the system requirements for the Add-on Builder Beta? '''  


You need Firefox version 4 or later, and an Internet connection.  
You need a current version of Firefox, and an Internet connection.  


'''What are the system requirements for the Add-on SDK? '''  
'''What are the system requirements for the Add-on SDK? '''  


You need [http://python.org/ Python 2.5, 2.6, or 2.7], and Firefox version 4 or later.  
You need [http://python.org/ Python 2.5, 2.6, or 2.7], and a current version of Firefox.


If you're running Windows, [https://wiki.mozilla.org/MozillaBuild MozillaBuild], while not mandatory, will install the correct version of Python and the MSYS package, which will make it easier to work with the SDK.  
If you're running Windows, [https://wiki.mozilla.org/MozillaBuild MozillaBuild], while not mandatory, will install the correct version of Python and the MSYS package, which will make it easier to work with the SDK.  
Line 65: Line 63:
'''Will the Add-on SDK be fully integrated into Firefox? '''  
'''Will the Add-on SDK be fully integrated into Firefox? '''  


The Add-on SDK is a separate product from Firefox, and there are no plans to integrate its functionality directly into Firefox. However, the Add-on Builder, Add-on SDK and Firefox teams work closely to ensure Firefox provides a great set of extension capabilities for SDK APIs to expose to add-on developers.  
The Add-on SDK is currently a separate product from Firefox. But we are investigating ways in which the SDK could be integrated into Firefox.


'''Do users need to download or install anything to use Add-on SDK and Add-on Builder based add-ons? '''  
'''Do users need to download or install anything to use Add-on SDK and Add-on Builder based add-ons? '''  
Line 80: Line 78:


The Jetpack team's current focus is creating the best possible experience for developers of desktop Firefox add-ons. We are well aware, however, of the importance of mobile Firefox to Mozilla and its users, and we plan to prioritize mobile Firefox add-on development in a future release of the Add-on SDK and Add-on Builder.  
The Jetpack team's current focus is creating the best possible experience for developers of desktop Firefox add-ons. We are well aware, however, of the importance of mobile Firefox to Mozilla and its users, and we plan to prioritize mobile Firefox add-on development in a future release of the Add-on SDK and Add-on Builder.  
In version 1.5 the SDK started to offer experimental support for the native version of Firefox Mobile.


'''What is Jetpack? '''  
'''What is Jetpack? '''  
Line 87: Line 87:
'''I have a Google Chrome plugin/Safari add-on. Will it work as a Firefox add-on? '''  
'''I have a Google Chrome plugin/Safari add-on. Will it work as a Firefox add-on? '''  


You will need to do some porting, but the changes should be relatively straightforward. David Morgan has written an extension for Chrome and Firefox that shares much of the code: http://code.google.com/p/scry/.  
You will need to do some porting, but the changes should be relatively straightforward. David Morgan has written an extension for Chrome and Firefox that shares much of the code: http://code.google.com/p/scry/.


== Programming  ==
== Programming  ==
Wbamberg
canmove, Confirmed users
737

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/397837"

Navigation menu