Closed Bug 580812 Opened 14 years ago Closed 14 years ago

Allow multiple SDK versions

Categories

(Mozilla Labs Graveyard :: FlightDeck, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: zalun, Unassigned)

Details

update the SDK to current version (0.6) while continuing to support existing version (0.5 on official builder site)
There are several issues to consider in terms of the user experience:

1. the version of the core library a new addon should use;
2. the version of the core library an existing addon should use;
3. how to enable a user to change the version of the core library to use for a given addon.

Regarding the first two issues, new addons should use the latest available version of the core library, while existing addons should use whatever version of the library they were using when they were created or last edited, i.e. they shouldn't automatically be changed to use a major new version of the core library when it becomes available.

As for changing the version of the core library to use, my initial thinking for the user experience here is to add a drop-down menu of versions to the entry in the list of libraries and allow the user to select another version from the drop-down menu, i.e. something like this:

  +------------------------------+
  | [ICON] Libraries (1)       V |
  +------------------------------+
                 +---------+
   Core Library  | 0.6 | v |
                 +---------+
                 | 0.6     |
                 | 0.5     |
                 +---------+
In the 1.0a3 development plan, Piotr notes: "This is big: update itself, create database representation, make people be able to choose which SDK their add-on will use to create XPI."
Agreed on the representation, the steps to achieve this goal: 

* make the database model which will reflect position of the jetpack SDK in the file system
* create a shell script to download desired version number into the right directory
* create new Library version with all modules created from files
* make it possible to switch the documentation to old version, by default read documentation from the current SDK version
* add ability to switch SDK which will be used to create XPI
No longer blocks: 578542
http://github.com/zalun/FlightDeck/tree/bug-580812-multiple_SDK
working on http://flightdeck.zalewa.info/
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.