[SCM] WebKit Debian packaging branch, debian/unstable, updated. debian/1.1.15-1-40151-g37bb677
sullivan
sullivan at 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Sat Sep 26 05:52:58 UTC 2009
The following commit has been merged in the debian/unstable branch:
commit 4343655b01c9ea7a702b7b9bdeed455af9a2bf59
Author: sullivan <sullivan at 268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Date: Tue Dec 11 01:00:21 2001 +0000
* WebView.subproj/WKWebController.h:
* WebView.subproj/WKWebDataSource.h:
* WebView.subproj/WKWebView.h:
Fixed some typos and misspellings.
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@485 268f45cc-cd09-0410-ab3c-d52691b4dbfc
diff --git a/WebKit/ChangeLog b/WebKit/ChangeLog
index e03a4e2..88d180a 100644
--- a/WebKit/ChangeLog
+++ b/WebKit/ChangeLog
@@ -1,3 +1,11 @@
+2001-12-10 John Sullivan <sullivan at apple.com>
+
+ * WebView.subproj/WKWebController.h:
+ * WebView.subproj/WKWebDataSource.h:
+ * WebView.subproj/WKWebView.h:
+
+ Fixed some typos and misspellings.
+
2001-12-07 Richard Williamson <richwill at richwill.com>
* WebView.subproj/NSWebPageDataSource.h:
diff --git a/WebKit/ChangeLog-2002-12-03 b/WebKit/ChangeLog-2002-12-03
index e03a4e2..88d180a 100644
--- a/WebKit/ChangeLog-2002-12-03
+++ b/WebKit/ChangeLog-2002-12-03
@@ -1,3 +1,11 @@
+2001-12-10 John Sullivan <sullivan at apple.com>
+
+ * WebView.subproj/WKWebController.h:
+ * WebView.subproj/WKWebDataSource.h:
+ * WebView.subproj/WKWebView.h:
+
+ Fixed some typos and misspellings.
+
2001-12-07 Richard Williamson <richwill at richwill.com>
* WebView.subproj/NSWebPageDataSource.h:
diff --git a/WebKit/WebView.subproj/IFWebController.h b/WebKit/WebView.subproj/IFWebController.h
index d57639d..9525f73 100644
--- a/WebKit/WebView.subproj/IFWebController.h
+++ b/WebKit/WebView.subproj/IFWebController.h
@@ -32,18 +32,18 @@
/*
*/
@protocol WKCredentialsHandler
-// Ken will come up with a proposal for this. We decided not have a generic API,
+// Ken will come up with a proposal for this. We decided not to have a generic API,
// rather we'll have an API that explicitly knows about the authentication
// attributes needed.
// Client should use this API to collect information necessary to authenticate,
// usually by putting up a dialog.
-// Do we provide a default dialog.
+// Do we provide a default dialog?
@end
/*
Implementors of this protocol will receive messages indicating
- data as it arrive.
+ data as it arrives.
This method will be called even if the data source
is initialized with something other than a URL.
@@ -51,10 +51,10 @@
@protocol WKLoadHandler
/*
- A new chunk of data has been received. This could be partial load
+ A new chunk of data has been received. This could be a partial load
of a url. It may be useful to do incremental layout, although
typically for non-base URLs this should be done after a URL (i.e. image)
- has been completed downloaded.
+ has been completely downloaded.
*/
- (void)receivedDataForLocation: (WKLoadProgress *)progress;
diff --git a/WebKit/WebView.subproj/IFWebDataSource.h b/WebKit/WebView.subproj/IFWebDataSource.h
index 190fab9..42c6bff 100644
--- a/WebKit/WebView.subproj/IFWebDataSource.h
+++ b/WebKit/WebView.subproj/IFWebDataSource.h
@@ -20,8 +20,8 @@
[dataSource setFrameSetHandler: (WKFrameSetHandler *)myManager];
[dataSource setScriptContextHandler: (WKScriptContextHandler *)myContext];
- [dataSource setLoadHandler: (WKLoadHandler *)loadHandler];
- [dataSource setCredentialsHandler: (WKCredentialsHandler *)credentialsHandler];
+ [dataSource setLoadHandler: (WKLoadHandler *)myLoadHandler];
+ [dataSource setCredentialsHandler: (WKCredentialsHandler *)myCredentialsHandler];
...
or
...
@@ -41,8 +41,8 @@
}
-// Can these init methods return nil? i.e. if URL is invalid, or should they
-// throw expections?
+// Can these init methods return nil? e.g. if URL is invalid, or should they
+// throw exceptions?
- initWithURL: (NSURL *)url;
- initWithData: (NSData *)data;
- initWithString: (NSString *)string;
@@ -60,7 +60,7 @@
// Start actually getting (if initialized with a URL) and parsing data.
- (void)startLoading;
-// Cancel and pending loads.
+// Cancel any pending loads.
- (BOOL)stopLoading;
// Get DOM access to the document.
@@ -76,7 +76,7 @@
// should this be handled by the view?
- (WKDOMNode *)activeNode;
-// URL reference point, these should problably not be public for 1.0.
+// URL reference point, these should probably not be public for 1.0.
- setBase: (NSURL *)url;
- (NSURL *)base;
- setBaseTarget: (NSURL *)url;
@@ -109,7 +109,7 @@
#endif
- executeScript: (NSString *)string;
-// Same as above expect uses the node as 'this' value
+// Same as above except uses the node as 'this' value
- executeScript: (NSString *)string withNode: (WKDOMNode *)node;
// This API reflects the KDE API, but is it sufficient?
@@ -122,13 +122,13 @@
// that this means WebCore, specifically KWQ, also doesn't have dependencies on the AppKit.
- (NSImage *)icon;
-// Is page secure, i.e. https, ftps
-// Should this perhap be on the URL?
+// Is page secure, e.g. https, ftps
+// Should this perhaps be on the URL?
// This would the be implemented like this
// return [[self url] isSecure];
- (BOOL)isPageSecure;
-// ---------------------- Convience methods ----------------------
+// ---------------------- Convenience methods ----------------------
- (NSString *)pageTitle;
// ---------------------------------------------------------------
@@ -162,7 +162,7 @@
/*
- The class provide a cover for URL based preference items.
+ This class provides a cover for URL-based preference items.
*/
@interface WKPreferences
+ getPreferencesForURL: (NSURL *)url;
diff --git a/WebKit/WebView.subproj/IFWebView.h b/WebKit/WebView.subproj/IFWebView.h
index 84abe65..e15db15 100644
--- a/WebKit/WebView.subproj/IFWebView.h
+++ b/WebKit/WebView.subproj/IFWebView.h
@@ -11,7 +11,7 @@
#ifdef READY_FOR_PRIMETIME
/*
- Typical usage of an WKWebView.
+ Typical usage of a WKWebView.
NSURL *url = [NSURL URLWithString: @"http://www.apple.com"];
...
@@ -33,12 +33,12 @@
What is the behaviour of the view after it has been initialized and -startLoading is called?
- 1. When the data source is set during (i.e. -setDataSource:) -locationWillChange will be sent
- to the view's controller. It may veto by returning NO. Note that if the convience initializers
+ 1. When the data source is set (i.e. -setDataSource:) -locationWillChange will be sent
+ to the view's controller. It may veto by returning NO. Note that if the convenience initializers
are used no controller will have been set, and thus no chance to veto will be provided.
- 2. The view will do nothing until receipt of it's first -receivedDataForURL: message
- from it's data source. Thus the view will not change it's content before users have
+ 2. The view will do nothing until receipt of its first -receivedDataForURL: message
+ from its data source. Thus the view will not change its content before users have
a chance to cancel slow URLs.
During this time, if -stopLoading is called on the data source, loading will
@@ -49,8 +49,8 @@
Controllers should initiate progress indicators at this point (how?).
- 3. After receipt of it first -receivedDataForURL: it will clear it's contents
- and perform it's first layout. At this point a loadingStarted message will
+ 3. After receipt of it first -receivedDataForURL: it will clear its contents
+ and perform its first layout. At this point a loadingStarted message will
be sent to the client.
4. Upon every subsequent receipts of -finishedReceivingDataForURL: messages it
diff --git a/WebKit/WebView.subproj/WKWebController.h b/WebKit/WebView.subproj/WKWebController.h
index d57639d..9525f73 100644
--- a/WebKit/WebView.subproj/WKWebController.h
+++ b/WebKit/WebView.subproj/WKWebController.h
@@ -32,18 +32,18 @@
/*
*/
@protocol WKCredentialsHandler
-// Ken will come up with a proposal for this. We decided not have a generic API,
+// Ken will come up with a proposal for this. We decided not to have a generic API,
// rather we'll have an API that explicitly knows about the authentication
// attributes needed.
// Client should use this API to collect information necessary to authenticate,
// usually by putting up a dialog.
-// Do we provide a default dialog.
+// Do we provide a default dialog?
@end
/*
Implementors of this protocol will receive messages indicating
- data as it arrive.
+ data as it arrives.
This method will be called even if the data source
is initialized with something other than a URL.
@@ -51,10 +51,10 @@
@protocol WKLoadHandler
/*
- A new chunk of data has been received. This could be partial load
+ A new chunk of data has been received. This could be a partial load
of a url. It may be useful to do incremental layout, although
typically for non-base URLs this should be done after a URL (i.e. image)
- has been completed downloaded.
+ has been completely downloaded.
*/
- (void)receivedDataForLocation: (WKLoadProgress *)progress;
diff --git a/WebKit/WebView.subproj/WKWebDataSource.h b/WebKit/WebView.subproj/WKWebDataSource.h
index 190fab9..42c6bff 100644
--- a/WebKit/WebView.subproj/WKWebDataSource.h
+++ b/WebKit/WebView.subproj/WKWebDataSource.h
@@ -20,8 +20,8 @@
[dataSource setFrameSetHandler: (WKFrameSetHandler *)myManager];
[dataSource setScriptContextHandler: (WKScriptContextHandler *)myContext];
- [dataSource setLoadHandler: (WKLoadHandler *)loadHandler];
- [dataSource setCredentialsHandler: (WKCredentialsHandler *)credentialsHandler];
+ [dataSource setLoadHandler: (WKLoadHandler *)myLoadHandler];
+ [dataSource setCredentialsHandler: (WKCredentialsHandler *)myCredentialsHandler];
...
or
...
@@ -41,8 +41,8 @@
}
-// Can these init methods return nil? i.e. if URL is invalid, or should they
-// throw expections?
+// Can these init methods return nil? e.g. if URL is invalid, or should they
+// throw exceptions?
- initWithURL: (NSURL *)url;
- initWithData: (NSData *)data;
- initWithString: (NSString *)string;
@@ -60,7 +60,7 @@
// Start actually getting (if initialized with a URL) and parsing data.
- (void)startLoading;
-// Cancel and pending loads.
+// Cancel any pending loads.
- (BOOL)stopLoading;
// Get DOM access to the document.
@@ -76,7 +76,7 @@
// should this be handled by the view?
- (WKDOMNode *)activeNode;
-// URL reference point, these should problably not be public for 1.0.
+// URL reference point, these should probably not be public for 1.0.
- setBase: (NSURL *)url;
- (NSURL *)base;
- setBaseTarget: (NSURL *)url;
@@ -109,7 +109,7 @@
#endif
- executeScript: (NSString *)string;
-// Same as above expect uses the node as 'this' value
+// Same as above except uses the node as 'this' value
- executeScript: (NSString *)string withNode: (WKDOMNode *)node;
// This API reflects the KDE API, but is it sufficient?
@@ -122,13 +122,13 @@
// that this means WebCore, specifically KWQ, also doesn't have dependencies on the AppKit.
- (NSImage *)icon;
-// Is page secure, i.e. https, ftps
-// Should this perhap be on the URL?
+// Is page secure, e.g. https, ftps
+// Should this perhaps be on the URL?
// This would the be implemented like this
// return [[self url] isSecure];
- (BOOL)isPageSecure;
-// ---------------------- Convience methods ----------------------
+// ---------------------- Convenience methods ----------------------
- (NSString *)pageTitle;
// ---------------------------------------------------------------
@@ -162,7 +162,7 @@
/*
- The class provide a cover for URL based preference items.
+ This class provides a cover for URL-based preference items.
*/
@interface WKPreferences
+ getPreferencesForURL: (NSURL *)url;
diff --git a/WebKit/WebView.subproj/WKWebView.h b/WebKit/WebView.subproj/WKWebView.h
index 84abe65..e15db15 100644
--- a/WebKit/WebView.subproj/WKWebView.h
+++ b/WebKit/WebView.subproj/WKWebView.h
@@ -11,7 +11,7 @@
#ifdef READY_FOR_PRIMETIME
/*
- Typical usage of an WKWebView.
+ Typical usage of a WKWebView.
NSURL *url = [NSURL URLWithString: @"http://www.apple.com"];
...
@@ -33,12 +33,12 @@
What is the behaviour of the view after it has been initialized and -startLoading is called?
- 1. When the data source is set during (i.e. -setDataSource:) -locationWillChange will be sent
- to the view's controller. It may veto by returning NO. Note that if the convience initializers
+ 1. When the data source is set (i.e. -setDataSource:) -locationWillChange will be sent
+ to the view's controller. It may veto by returning NO. Note that if the convenience initializers
are used no controller will have been set, and thus no chance to veto will be provided.
- 2. The view will do nothing until receipt of it's first -receivedDataForURL: message
- from it's data source. Thus the view will not change it's content before users have
+ 2. The view will do nothing until receipt of its first -receivedDataForURL: message
+ from its data source. Thus the view will not change its content before users have
a chance to cancel slow URLs.
During this time, if -stopLoading is called on the data source, loading will
@@ -49,8 +49,8 @@
Controllers should initiate progress indicators at this point (how?).
- 3. After receipt of it first -receivedDataForURL: it will clear it's contents
- and perform it's first layout. At this point a loadingStarted message will
+ 3. After receipt of it first -receivedDataForURL: it will clear its contents
+ and perform its first layout. At this point a loadingStarted message will
be sent to the client.
4. Upon every subsequent receipts of -finishedReceivingDataForURL: messages it
diff --git a/WebKit/WebView.subproj/WebController.h b/WebKit/WebView.subproj/WebController.h
index d57639d..9525f73 100644
--- a/WebKit/WebView.subproj/WebController.h
+++ b/WebKit/WebView.subproj/WebController.h
@@ -32,18 +32,18 @@
/*
*/
@protocol WKCredentialsHandler
-// Ken will come up with a proposal for this. We decided not have a generic API,
+// Ken will come up with a proposal for this. We decided not to have a generic API,
// rather we'll have an API that explicitly knows about the authentication
// attributes needed.
// Client should use this API to collect information necessary to authenticate,
// usually by putting up a dialog.
-// Do we provide a default dialog.
+// Do we provide a default dialog?
@end
/*
Implementors of this protocol will receive messages indicating
- data as it arrive.
+ data as it arrives.
This method will be called even if the data source
is initialized with something other than a URL.
@@ -51,10 +51,10 @@
@protocol WKLoadHandler
/*
- A new chunk of data has been received. This could be partial load
+ A new chunk of data has been received. This could be a partial load
of a url. It may be useful to do incremental layout, although
typically for non-base URLs this should be done after a URL (i.e. image)
- has been completed downloaded.
+ has been completely downloaded.
*/
- (void)receivedDataForLocation: (WKLoadProgress *)progress;
diff --git a/WebKit/WebView.subproj/WebDataSource.h b/WebKit/WebView.subproj/WebDataSource.h
index 190fab9..42c6bff 100644
--- a/WebKit/WebView.subproj/WebDataSource.h
+++ b/WebKit/WebView.subproj/WebDataSource.h
@@ -20,8 +20,8 @@
[dataSource setFrameSetHandler: (WKFrameSetHandler *)myManager];
[dataSource setScriptContextHandler: (WKScriptContextHandler *)myContext];
- [dataSource setLoadHandler: (WKLoadHandler *)loadHandler];
- [dataSource setCredentialsHandler: (WKCredentialsHandler *)credentialsHandler];
+ [dataSource setLoadHandler: (WKLoadHandler *)myLoadHandler];
+ [dataSource setCredentialsHandler: (WKCredentialsHandler *)myCredentialsHandler];
...
or
...
@@ -41,8 +41,8 @@
}
-// Can these init methods return nil? i.e. if URL is invalid, or should they
-// throw expections?
+// Can these init methods return nil? e.g. if URL is invalid, or should they
+// throw exceptions?
- initWithURL: (NSURL *)url;
- initWithData: (NSData *)data;
- initWithString: (NSString *)string;
@@ -60,7 +60,7 @@
// Start actually getting (if initialized with a URL) and parsing data.
- (void)startLoading;
-// Cancel and pending loads.
+// Cancel any pending loads.
- (BOOL)stopLoading;
// Get DOM access to the document.
@@ -76,7 +76,7 @@
// should this be handled by the view?
- (WKDOMNode *)activeNode;
-// URL reference point, these should problably not be public for 1.0.
+// URL reference point, these should probably not be public for 1.0.
- setBase: (NSURL *)url;
- (NSURL *)base;
- setBaseTarget: (NSURL *)url;
@@ -109,7 +109,7 @@
#endif
- executeScript: (NSString *)string;
-// Same as above expect uses the node as 'this' value
+// Same as above except uses the node as 'this' value
- executeScript: (NSString *)string withNode: (WKDOMNode *)node;
// This API reflects the KDE API, but is it sufficient?
@@ -122,13 +122,13 @@
// that this means WebCore, specifically KWQ, also doesn't have dependencies on the AppKit.
- (NSImage *)icon;
-// Is page secure, i.e. https, ftps
-// Should this perhap be on the URL?
+// Is page secure, e.g. https, ftps
+// Should this perhaps be on the URL?
// This would the be implemented like this
// return [[self url] isSecure];
- (BOOL)isPageSecure;
-// ---------------------- Convience methods ----------------------
+// ---------------------- Convenience methods ----------------------
- (NSString *)pageTitle;
// ---------------------------------------------------------------
@@ -162,7 +162,7 @@
/*
- The class provide a cover for URL based preference items.
+ This class provides a cover for URL-based preference items.
*/
@interface WKPreferences
+ getPreferencesForURL: (NSURL *)url;
diff --git a/WebKit/WebView.subproj/WebFrameView.h b/WebKit/WebView.subproj/WebFrameView.h
index 84abe65..e15db15 100644
--- a/WebKit/WebView.subproj/WebFrameView.h
+++ b/WebKit/WebView.subproj/WebFrameView.h
@@ -11,7 +11,7 @@
#ifdef READY_FOR_PRIMETIME
/*
- Typical usage of an WKWebView.
+ Typical usage of a WKWebView.
NSURL *url = [NSURL URLWithString: @"http://www.apple.com"];
...
@@ -33,12 +33,12 @@
What is the behaviour of the view after it has been initialized and -startLoading is called?
- 1. When the data source is set during (i.e. -setDataSource:) -locationWillChange will be sent
- to the view's controller. It may veto by returning NO. Note that if the convience initializers
+ 1. When the data source is set (i.e. -setDataSource:) -locationWillChange will be sent
+ to the view's controller. It may veto by returning NO. Note that if the convenience initializers
are used no controller will have been set, and thus no chance to veto will be provided.
- 2. The view will do nothing until receipt of it's first -receivedDataForURL: message
- from it's data source. Thus the view will not change it's content before users have
+ 2. The view will do nothing until receipt of its first -receivedDataForURL: message
+ from its data source. Thus the view will not change its content before users have
a chance to cancel slow URLs.
During this time, if -stopLoading is called on the data source, loading will
@@ -49,8 +49,8 @@
Controllers should initiate progress indicators at this point (how?).
- 3. After receipt of it first -receivedDataForURL: it will clear it's contents
- and perform it's first layout. At this point a loadingStarted message will
+ 3. After receipt of it first -receivedDataForURL: it will clear its contents
+ and perform its first layout. At this point a loadingStarted message will
be sent to the client.
4. Upon every subsequent receipts of -finishedReceivingDataForURL: messages it
diff --git a/WebKit/WebView.subproj/WebView.h b/WebKit/WebView.subproj/WebView.h
index d57639d..9525f73 100644
--- a/WebKit/WebView.subproj/WebView.h
+++ b/WebKit/WebView.subproj/WebView.h
@@ -32,18 +32,18 @@
/*
*/
@protocol WKCredentialsHandler
-// Ken will come up with a proposal for this. We decided not have a generic API,
+// Ken will come up with a proposal for this. We decided not to have a generic API,
// rather we'll have an API that explicitly knows about the authentication
// attributes needed.
// Client should use this API to collect information necessary to authenticate,
// usually by putting up a dialog.
-// Do we provide a default dialog.
+// Do we provide a default dialog?
@end
/*
Implementors of this protocol will receive messages indicating
- data as it arrive.
+ data as it arrives.
This method will be called even if the data source
is initialized with something other than a URL.
@@ -51,10 +51,10 @@
@protocol WKLoadHandler
/*
- A new chunk of data has been received. This could be partial load
+ A new chunk of data has been received. This could be a partial load
of a url. It may be useful to do incremental layout, although
typically for non-base URLs this should be done after a URL (i.e. image)
- has been completed downloaded.
+ has been completely downloaded.
*/
- (void)receivedDataForLocation: (WKLoadProgress *)progress;
--
WebKit Debian packaging
More information about the Pkg-webkit-commits
mailing list