Closed
Bug 349523
Opened 18 years ago
Closed 17 years ago
Generate bookmarks.html, default_places.html from properties
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla3 alpha4
People
(Reporter: Pike, Assigned: Pike)
References
Details
Attachments
(1 file, 6 obsolete files)
6.26 KB,
patch
|
asaf
:
review+
|
Details | Diff | Splinter Review |
Now that bug 348165 made the links in bookmarks.html strict and only dependent on locale, we can generate that file via a simple set of strings, just like default_places. This is going to cut down the amount of fileformats just as well as the numerous ways to break those files. And it going to make review of those files a lot easier, too.
Comment 1•18 years ago
|
||
I believe default_places.html should be going away on the trunk.
Assignee | ||
Comment 2•18 years ago
|
||
Seth, I actually filed this bug already, axel@pike.org is just another me.
Comment 3•17 years ago
|
||
Comment 4•17 years ago
|
||
Attachment #260552 -
Attachment is obsolete: true
Attachment #260613 -
Flags: review?(sspitzer)
Comment 5•17 years ago
|
||
latest patch adds favicons, and removes the default_places.html file.
Updated•17 years ago
|
Attachment #260613 -
Flags: review?(l10n)
Assignee | ||
Comment 6•17 years ago
|
||
Comment on attachment 260613 [details] [diff] [review] fix v1 >Index: browser/locales/en-US/chrome/browser/places/places.properties >=================================================================== >RCS file: /cvsroot/mozilla/browser/locales/en-US/chrome/browser/places/places.properties,v >retrieving revision 1.18 >diff -u -8 -p -r1.18 places.properties >--- browser/locales/en-US/chrome/browser/places/places.properties 13 Mar 2007 01:21:32 -0000 1.18 >+++ browser/locales/en-US/chrome/browser/places/places.properties 4 Apr 2007 17:30:32 -0000 >@@ -62,8 +62,27 @@ tabs.openWarningTitle=Confirm open > tabs.openWarningMultipleBranded=You are about to open %S tabs. This might slow down %S while the pages are loading. Are you sure you want to continue? > tabs.openButtonMultiple=Open tabs > tabs.openWarningPromptMeBranded=Warn me when opening multiple tabs might slow down %S > > status_foldercount = %S object(s) > > SelectImport=Import Bookmarks File > EnterExport=Export Bookmarks File >+ >+PlacesRootTitle=Bookmarks and History >+ >+PlacesHistoryQueryURI=place:&beginTime=-2592000000000&beginTimeRef=1&endTime=7200000000&endTimeRef=2&sort=4&type=1 >+PlacesHistoryQueryTitle=History >+PlacesHistoryQueryDescription=Shows all browsing history >+ >+PlacesBookmarksRootTitle=Bookmarks >+PlacesBookmarksRootDescription=Add bookmarks to this folder to see them displayed on the Bookmarks Menu >+PlacesBookmarksRootIconURI=chrome://browser/skin/places/bookmarksMenu.png >+ >+PlacesBookmarksToolbarTitle=Bookmarks Toolbar Folder >+PlacesBookmarksToolbarDescription=Add bookmarks to this folder to see them displayed on the Bookmarks Toolbar >+PlacesBookmarksToolbarIconURI=chrome://browser/skin/places/bookmarksToolbar.png >+ >+PlacesFeedsQueryURI=place:&annotation=livemark%2FfeedURI >+PlacesFeedsQueryIconURI=chrome://browser/skin/places/livemarkItem.png >+PlacesFeedsQueryTitle=Subscriptions >+PlacesFeedsQueryDescription=Shows all Subscribed Feeds Most of these shouldn't be in locales/en-US, like, the URIs definitely not, both the icon and query urls. How many of the titles are we using right now, and how many of those are waiting for the rewrite of the manager?
Attachment #260613 -
Flags: review?(l10n) → review-
Comment 7•17 years ago
|
||
(In reply to comment #6) > > Most of these shouldn't be in locales/en-US, like, the URIs definitely not, > both the icon and query urls. i moved all of the new properties into chrome and out of locale. > > How many of the titles are we using right now, and how many of those are > waiting for the rewrite of the manager? > don't know, because the manager requirements for fx3 are not solid, so i've removed them from locale for now.
Attachment #260613 -
Attachment is obsolete: true
Attachment #260723 -
Flags: review?(l10n)
Attachment #260613 -
Flags: review?(sspitzer)
Assignee | ||
Comment 8•17 years ago
|
||
Comment on attachment 260723 [details] [diff] [review] fix v2 - fixes axel's comments r=me. Could you add a comment to places.properties that only the title strings should move over to locales/en-US? If you want to keep the query and icon urls in a properties files, you could split the l10n and functionality part already, that's up to you. Thanks for getting me on the hook here.
Attachment #260723 -
Flags: review?(l10n) → review+
Comment 9•17 years ago
|
||
Comment on attachment 260723 [details] [diff] [review] fix v2 - fixes axel's comments r=sspitzer
Attachment #260723 -
Flags: review+
Comment 10•17 years ago
|
||
note to dietrich: I'm very excited that we have: PlacesHistoryQueryURI=place:&beginTime=-2592000000000&beginTimeRef=1&endTime=7200000000&endTimeRef=2&sort=4&type=1 If you lxr in our code, we use that same value in several places: /browser/components/places/content/controller.js, line 46 -- const ORGANIZER_ROOT_HISTORY_UNSORTED = "place:&beginTime=-2592000000000&beginTimeRef=1&endTime=7200000000&endTimeRef=2&type=1" /browser/components/places/content/history-panel.xul, line 122 -- place="place:&beginTime=-2592000000000&beginTimeRef=1&endTime=7200000000&endTimeRef=2&type=1" Can you log a spin off bug about fixing our code to use the property? note, we also use something similar, but slightly different, here: /browser/base/content/browser-menubar.inc, line 334 -- place="place:&beginTime=-2592000000000&beginTimeRef=1&endTime=7200000000&endTimeRef=2&type=0&sort=4&maxResults=10"> For future extension developers, having one place to get PlacesHistoryQueryURI, instead of following our copy-and-paste approach, would be good.
Updated•17 years ago
|
Status: NEW → ASSIGNED
Comment 11•17 years ago
|
||
mano pointed out that the subscriptions folder is obsolete. this patch doesn't create the folder. it does leave the un-localized properties there in case we use it during upcoming manager changes. we can remove it later if necessary.
Attachment #260723 -
Attachment is obsolete: true
Attachment #261161 -
Flags: review?(mano)
Comment 12•17 years ago
|
||
per mano, the history query is unnecessary as well. leaving in the strings for now, just not creating the bookmark when initializing the datastore. we can remove the strings if necessary when we move them to locale.
Attachment #261161 -
Attachment is obsolete: true
Attachment #261271 -
Flags: review?
Attachment #261161 -
Flags: review?(mano)
Updated•17 years ago
|
Attachment #261271 -
Flags: review? → review?(mano)
Comment 13•17 years ago
|
||
Comment on attachment 261271 [details] [diff] [review] fix v4 >Index: browser/components/places/content/places.properties >=================================================================== So this should probably go to toolkit/ >+// nsNavBookmarks::InitDefaults >+// >+// Initializes default bookmarks and containers. >+// Pulls from places.propertes for l10n. >+// Replaces the old default_places.html file. >+nsresult >+nsNavBookmarks::InitDefaults() >+{ >+ // give bookmarks root folder a title "Bookmarks" >+ nsXPIDLString bookmarksTitle, bookmarksIcon; >+ nsresult rv = mBundle->GetStringFromName(NS_LITERAL_STRING("PlacesBookmarksRootTitle").get(), getter_Copies(bookmarksTitle)); please try to keep code lines not that long (in browser/ I would mumble something about 80 character). >+// BookmarkContentSink::SetItemFavicon >+// >+// This sets the given favicon URI for the given folder. It is used to >+// initialize the favicons for the bookmarks menu and toolbar. We don't >+// actually set any data here because we assume the URI is a chrome: URI. >+// These do not have to contain any data for them to work. >+ >+nsresult >+nsNavBookmarks::SetItemFavicon(PRInt64 aId, const nsAString& aFavicon, >+ PRBool aIsFolder) >+{ >+ nsFaviconService* faviconService = nsFaviconService::GetFaviconService(); >+ NS_ENSURE_TRUE(faviconService, NS_ERROR_OUT_OF_MEMORY); >+ >+ nsresult rv; >+ nsCOMPtr<nsIURI> itemURI; >+ if (aIsFolder) { >+ rv = GetFolderURI(aId, getter_AddRefs(itemURI)); >+ NS_ENSURE_SUCCESS(rv, rv); >+ } >+ else { >+ rv = GetItemURI(aId, getter_AddRefs(itemURI)); Hrm, we don't set favicons on bookmark items directly (the bookmarked uri is annotated). I would rather though stop setting these icons at all for now.
Attachment #261271 -
Flags: review?(mano) → review-
Comment 14•17 years ago
|
||
addresses mano's comments. xpcshell didn't like the properties file in a places/content subdir, so i put it in the global content.
Attachment #261271 -
Attachment is obsolete: true
Attachment #261410 -
Flags: review?(mano)
Comment 15•17 years ago
|
||
Attachment #261410 -
Attachment is obsolete: true
Attachment #261412 -
Flags: review?(mano)
Attachment #261410 -
Flags: review?(mano)
Comment 16•17 years ago
|
||
Comment on attachment 261412 [details] [diff] [review] fix v6 - w/ string file in the right place r=mano.
Attachment #261412 -
Flags: review?(mano) → review+
Updated•17 years ago
|
Flags: in-testsuite?
Target Milestone: Firefox 3 alpha1 → Firefox 3 alpha4
Comment 17•17 years ago
|
||
RCS file: /cvsroot/mozilla/toolkit/components/places/jar.mn,v done Checking in toolkit/components/places/jar.mn; /cvsroot/mozilla/toolkit/components/places/jar.mn,v <-- jar.mn initial revision: 1.1 done RCS file: /cvsroot/mozilla/toolkit/components/places/content/places.properties,v done Checking in toolkit/components/places/content/places.properties; /cvsroot/mozilla/toolkit/components/places/content/places.properties,v <-- places.properties initial revision: 1.1 done Checking in toolkit/components/places/src/nsNavBookmarks.cpp; /cvsroot/mozilla/toolkit/components/places/src/nsNavBookmarks.cpp,v <-- nsNavBookmarks.cpp new revision: 1.80; previous revision: 1.79 done Checking in toolkit/components/places/src/nsNavBookmarks.h; /cvsroot/mozilla/toolkit/components/places/src/nsNavBookmarks.h,v <-- nsNavBookmarks.h new revision: 1.37; previous revision: 1.36 done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Flags: in-testsuite?
Updated•6 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
Updated•5 years ago
|
Target Milestone: Firefox 3 alpha4 → mozilla3 alpha4
You need to log in
before you can comment on or make changes to this bug.
Description
•