WebKit:Alpha - Revision history

Admin at 20:59, 2 May 2012

2012-05-02T20:59:33Z

Sardisson: {{draft}}

2012-05-02T04:01:04Z

Sardisson: more wordsmithing

2012-05-02T03:46:57Z

more wordsmithing

Sardisson: /* Overview */ wordsmithing

2012-05-02T03:45:27Z

Overview: wordsmithing

Sardisson: add an overview that describes the areas where there are abstractions and where there are comingled bits

2012-05-02T03:42:32Z

add an overview that describes the areas where there are abstractions and where there are comingled bits

Sardisson: /* 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

2012-05-02T03:29:57Z

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

Sardisson: caps

2012-05-02T03:23:38Z

caps

Sardisson: /* Steps to Alpha */ detection is really the only part of opensearch that depends on Gecko/non-Camino code

2012-05-02T03:22:54Z

Steps to Alpha: detection is really the only part of opensearch that depends on Gecko/non-Camino code

Sardisson: /* Steps to Alpha */ clarify preferences

2012-05-02T03:22:05Z

Steps to Alpha: clarify preferences

Sardisson: updated pass by someone with a better grasp of current code structure ;-)

2012-05-02T03:21:38Z

updated pass by someone with a better grasp of current code structure ;-)

← Older revision		Revision as of 20:59, 2 May 2012
Line 1:		Line 1:
		+	<small>↩ [[WebKit:Home_Page\|WebKit]]</small>
		+
	{{draft}}		{{draft}}
	== Overview ==		== Overview ==

← Older revision		Revision as of 04:01, 2 May 2012
Line 1:		Line 1:
		+	{{draft}}
	== Overview ==		== Overview ==
	Although much of Camino’s UI code is self-contained and abstracted from the underlying rendering engine, there are certain areas where the abstraction is incomplete or impossible (for instance, MainController and PreferenceManager both contain startup code that’s tied to Gecko’s startup and preferences APIs, as well as startup and general app-control code that’s independent of rendering engine). There may also be areas where the UI code may depend on the structure of the current abstraction code, which may have to change to account for differences between the Gecko and WebKit APIs.		Although much of Camino’s UI code is self-contained and abstracted from the underlying rendering engine, there are certain areas where the abstraction is incomplete or impossible (for instance, MainController and PreferenceManager both contain startup code that’s tied to Gecko’s startup and preferences APIs, as well as startup and general app-control code that’s independent of rendering engine). There may also be areas where the UI code may depend on the structure of the current abstraction code, which may have to change to account for differences between the Gecko and WebKit APIs.

@@ Line 6: / Line 6: @@
 == Alpha ==
-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.
+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.
@@ Line 24: / Line 24: @@
 "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 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.)

@@ Line 1: / Line 1: @@
 == Overview ==
-Although much of Camino’s UI code is self-contained and abstracted from the underlying rendering engine, there are certain areas where the abstraction is incomplete or impossible (for instance, MainController and PreferenceManager both contain startup code that’s tied to Gecko, as well as startup and general app-control code that’s independent of rendering engine).  There may also be areas where the UI code may depend on the structure of the current abstraction code, which may have to change to account for differences between the Gecko and WebKit APIs.
+Although much of Camino’s UI code is self-contained and abstracted from the underlying rendering engine, there are certain areas where the abstraction is incomplete or impossible (for instance, MainController and PreferenceManager both contain startup code that’s tied to Gecko’s startup and preferences APIs, as well as startup and general app-control code that’s independent of rendering engine).  There may also be areas where the UI code may depend on the structure of the current abstraction code, which may have to change to account for differences between the Gecko and WebKit APIs.
 As a result, we expect much of the UI code will be reuseable, but may still need small changes.  The backend code/abstraction layer (much of which is contained in src/embedding, but some of which is in MainController, PreferenceManager, HistoryDataSource, and some of the classes in src/browser) will need to be rewritten in the whole or in part.

← Older revision		Revision as of 03:42, 2 May 2012
Line 1:		Line 1:
−	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.	+	== Overview ==
		+	Although much of Camino’s UI code is self-contained and abstracted from the underlying rendering engine, there are certain areas where the abstraction is incomplete or impossible (for instance, MainController and PreferenceManager both contain startup code that’s tied to Gecko, as well as startup and general app-control code that’s independent of rendering engine). There may also be areas where the UI code may depend on the structure of the current abstraction code, which may have to change to account for differences between the Gecko and WebKit APIs.
		+
		+	As a result, we expect much of the UI code will be reuseable, but may still need small changes. The backend code/abstraction layer (much of which is contained in src/embedding, but some of which is in MainController, PreferenceManager, HistoryDataSource, and some of the classes in src/browser) will need to be rewritten in the whole or in part.
		+
		+	== Alpha ==
		+
		+	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.		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.

@@ Line 5: / Line 5: @@
 == Steps to Alpha ==
 # Disable (likely comment out) all Camino code except the minimum needed.
 # 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.

@@ Line 8: / Line 8: @@
 # Bootstrapped, dead-simple, pre-alpha browser with no features and no Camino look and feel, but built on top of some Camino code.
 # 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.
+#* If volunteer wishes to hook up search bar, it is likely not hard to do here, without the OpenSearch detection feature.
 # Hook up basic history system using WebKit-provided interface.
 # Hook up bookmark system using Camino method (unless we devise a new method).