Difference between revisions of "WebKit:Alpha"

From Camino Wiki
Jump to navigation Jump to search
m (caps)
(→‎Steps to Alpha: maybe use dummy files for dead-simple bootstrap, so there's a minimum browser with minimum code to show us what we need, then merge)
Line 5: Line 5:
 
== Steps to Alpha ==
 
== Steps to Alpha ==
 
# Disable (likely comment out) all Camino code except the minimum needed.
 
# Disable (likely comment out) all Camino code except the minimum needed.
 +
#* It might be more expedient to create a series of temporary dummy files to bootstrap the dead-simple browser so that we know the structure required for a WebKit browser; then begin merging that code into existing Camino code (e.g., DummyMainController)
 
# Replace or modify src/embedding (as well as startup-related code in MainController and PreferenceManager)  to use WebKit.
 
# Replace or modify src/embedding (as well as startup-related code in MainController and PreferenceManager)  to use WebKit.
 
# Bootstrapped, dead-simple, pre-alpha browser with no features and no Camino look and feel, but built on top of some Camino code.
 
# Bootstrapped, dead-simple, pre-alpha browser with no features and no Camino look and feel, but built on top of some Camino code.

Revision as of 20:29, 1 May 2012

Camino 3's alpha phase will start with the most basic of alphas, delivered when we can ship Camino that: browses the web, has tabs, has bookmarks (the current bookmark manager UI may not be 100% functional), interfaces with history (autocomplete hopefully, but likely doesn't have a history manager), and has Camino icons in the toolbar.

The location bar will not need to be finished or include feed or security information to start. The location bar will likely be basic and may only pull from bookmarks (i.e., not include the entire algorithm we now use), though could pull from history as well. The search bar will not need to exist yet.

Steps to Alpha

  1. Disable (likely comment out) all Camino code except the minimum needed.
    • It might be more expedient to create a series of temporary dummy files to bootstrap the dead-simple browser so that we know the structure required for a WebKit browser; then begin merging that code into existing Camino code (e.g., DummyMainController)
  2. Replace or modify src/embedding (as well as startup-related code in MainController and PreferenceManager) to use WebKit.
  3. Bootstrapped, dead-simple, pre-alpha browser with no features and no Camino look and feel, but built on top of some Camino code.
  4. Hook up basic UI (back, forward, reload, stop, location bar).
    • If volunteer wishes to hook up search bar, it is likely not hard to do here, without the OpenSearch detection feature.
  5. Hook up basic history system using WebKit-provided interface.
  6. Hook up bookmark system using Camino method (unless we devise a new method).
  7. Hook up autocomplete in location bar using history and bookmarks (or just bookmarks for now).
  8. Hook up tabs system, possibly with a max tab limit to start.

"Basic" things likely missing:

  • No import of old Camino data as of yet.
  • No use of Keychain as of yet, unless it's given for free by WebKit.
  • No bookmark bar.
  • Possibly/likely no status bar.
  • Limited preferences UI (no cookies, pop-ups, certificates, etc.)