We need to document the design of turbo mode, not just the implicit one used for the current implmeentation, but the design we need, the one that will correctly implement the functional spec (bug 108797).

p1/moz097, blocks 108795, depends on 108797

Bill Law posted my spec at http://www.mozilla.org/xpapps/MachVPlan/Turbo_Mode_Plan.html

design spec here: http://mozilla.org/projects/ui/communicator/framework/quicklaunch/

reopening. we now have two specs, which is one too many, and one of them is out of date. We need to update the currently posted QuickLaunch UI design spec, resolve the open issues, and pass a review before we can consider this bug closed.

I have update the spec at http://www.mozilla.org/xpapps/MachVPlan/Turbo_Mode_Plan.html

mass-reassigning pchen QuickLaunch bugs to blaker

Quicklaunch needs to be part of a seperate process so that it doesn't get destroyed when Mozilla crashes.

The new spec can currently be found at http://www.damowmow.com/temp/quicklaunch.html. It will be available at http://www.mozilla.org/xpapps/QuickLaunch/ once mozilla.org starts working again. The old spec can still be found at http://www.mozilla.org/xpapps/MachVPlan/Turbo_Mode_Plan.html.

New spec is at http://www.mozilla.org/xpapps/QuickLaunch/ - I think this can be marked fixed? (law has reviewed it)

verified, and well done too, thank you!

Is quicklaunch going to be attempted on other oses?

I don't know. Got an itch?

Not enough of one :-/