Closed
Bug 319491
Opened 20 years ago
Closed 20 years ago
Reset Camino does not clear top 10 list in bookmarks
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino1.0
People
(Reporter: bugzilla-graveyard, Assigned: bugzilla-graveyard)
Details
(Keywords: fixed1.8, polish)
Attachments
(1 file, 2 obsolete files)
|
6.29 KB,
patch
|
Details | Diff | Splinter Review |
Separate issue from bug 300408, which is for UI.
"Reset Camino" should nuke the top 10 group in the Bookmarks Manager. Right now, it doesn't, and as the top 10 group is our default Dock menu source, it's causing confusion when users reset Camino and find their old bookmarks still in the Dock menu.
| Assignee | ||
Comment 1•20 years ago
|
||
Nominating to block 1.0. Patch will be forthcoming.
cl
Status: NEW → ASSIGNED
Flags: camino1.0?
| Assignee | ||
Comment 2•20 years ago
|
||
OK, what seems like the most logical behaviour here:
a) reset all bookmark visit counts to 0 (in the absence of wiping out bookmarks entirely, which I assume we avoid in Reset Camino for a reason)
b) reset the counts of the top 10 items to 0, forcing a rebuild of the top 10 group (which will leave the *next* 10 bookmarks as the new top 10, potentially alleviating user confusion not at all)
c) something else entirely
I prefer option (a) -- this is "reset", after all.
Josh's bug 257281 comment 15 said we should leave bookmarks alone, but I disagree. I'm with Mike's bug 257281 comment 16 -- if we leave bookmarks alone entirely, we end up with issues like the confusion demonstrated by the filing of bug 319476.
CCing Simon, Josh, and Smokey for further discussion.
cl
Comment 3•20 years ago
|
||
(In reply to comment #2)
> OK, what seems like the most logical behaviour here:
>
> a) reset all bookmark visit counts to 0 (in the absence of wiping out bookmarks
> entirely, which I assume we avoid in Reset Camino for a reason)
Yes, if we choose to do anything. I guess visit counts reaveal browsing behavior, so should be cleared by Reset.
> b) reset the counts of the top 10 items to 0, forcing a rebuild of the top 10
> group (which will leave the *next* 10 bookmarks as the new top 10, potentially
> alleviating user confusion not at all)
No, very confusing.
| Assignee | ||
Comment 4•20 years ago
|
||
Clear all bookmarks visit counts when resetting Camino, per discussions on IRC, as well as Stuart's comment on MZ.
Fixes an NSArray in KindaSmartFolderManager.mm to use NSEnumerator instead, too, per Simon's request.
Attachment #205279 -
Flags: review?(sfraser_bugs)
Comment 5•20 years ago
|
||
Last visit is history information as well, and should also be cleared--whatever "cleared" means, since I'm guessing a nil date will cause issues. Maybe setting the date to the epoch and special casing the display of that value in the info window?
Comment 6•20 years ago
|
||
Comment on attachment 205279 [details] [diff] [review]
clear all visit counts when resetting
>Index: KindaSmartFolderManager.mm
>===================================================================
>+ NSEnumerator* bookmarksEnum = [[[BookmarkManager sharedBookmarkManager] rootBookmarks];
This should have given you a build warning, and thrown an exception at runtime. Did you test it? ;)
>Index: MainController.mm
>
>+ // re-set all bookmarks visit counts to zero
>+ NSEnumerator* bookmarksEnum = [[[BookmarkManager sharedBookmarkManager] rootBookmarks];
>+ BookmarkItem* curItem;
>+ while ((curItem = [bookmarksEnum nextObject]))
>+ {
>+ [curItem setNumberOfVisits:0];
>+ }
Please move this to a method on the bookmark manager. (clearVisitCounts or something).
Attachment #205279 -
Flags: review?(sfraser_bugs) → review-
| Assignee | ||
Comment 7•20 years ago
|
||
Contains part of the fix for bug 254313 as both modify BookmarkManager.mm and I couldn't figure out a clean way to split the patches into two diffs without pulling fresh source between diffs.
cl
Attachment #205279 -
Attachment is obsolete: true
Attachment #205364 -
Flags: review?(sfraser_bugs)
(In reply to comment #5)
> Last visit is history information as well, and should also be cleared--whatever
> "cleared" means, since I'm guessing a nil date will cause issues. Maybe
> setting the date to the epoch and special casing the display of that value in
> the info window?
Now bug 319649.
Comment 9•20 years ago
|
||
Comment on attachment 205364 [details] [diff] [review]
fixes silly mistake and moves clearAllVisits to Bookmark Manager
>Index: BookmarkManager.h
>===================================================================
> - (void)writeSafariFile:(NSString *)pathToFile;
>
>+// Clear visit counts
>+-(void)clearAllVisits;
Please follow the spacing of the methods above.
>Index: KindaSmartFolderManager.mm
>===================================================================
>+ NSEnumerator* bookmarksEnum = [[BookmarkManager sharedBookmarkManager] rootBookmarks];
This still ain't gonna compile without warnings, or even run properly. You need:
NSEnumerator* bookmarksEnum = [[[BookmarkManager sharedBookmarkManager] rootBookmarks] objectEnumerator];
>+ BookmarkItem* curItem;
>+ while ((curItem = [bookmarksEnum nextObject]))
>+ {
>+ [self checkForNewTop10:curItem];
Not your code, but -checkForNewTop10 looks for the item in the array twice (up to 2 * 10 comparisons), then compares with the array items (10 comparisons), then does a bunch of work to possibly insert. This could be made much more efficient.
>Index: BookmarkManager.mm
>===================================================================
>+//
>+// -clearAllVisits:
>+//
>+// resets all bookmarks visit counts to zero as part of Reset Camino
>+//
>+
>+-(void)clearAllVisits
>+{
>+ NSEnumerator* bookmarksEnum = (BookmarkManager*)[self rootBookmarks];
>+ BookmarkItem* curItem;
>+ while (curItem = [bookmarksEnum nextObject])
>+ {
>+ if ([curItem isKindOfClass:[Bookmark class]]) {
>+ [(Bookmark*)curItem setNumberOfVisits:0];
>+ }
Bad spacing here (and we tend not to use {} for 1-liners).
Attachment #205364 -
Flags: review?(sfraser_bugs) → review-
| Assignee | ||
Comment 10•20 years ago
|
||
KindaSmartFolderManager.mm dropped entirely, so Simon can do some reworking of the file.
cl
Attachment #205364 -
Attachment is obsolete: true
Attachment #205499 -
Flags: review?(sfraser_bugs)
Updated•20 years ago
|
Flags: camino1.0? → camino1.0+
Comment 11•20 years ago
|
||
Fixed.
Updated•20 years ago
|
Attachment #205499 -
Flags: review?(sfraser_bugs)
You need to log in
before you can comment on or make changes to this bug.
Description
•