Closed Bug 223169 Opened 21 years ago Closed 14 years ago

RFE: about:profile

Categories

(SeaMonkey :: Startup & Profiles, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: raccettura, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

Mozilla should support an "about:profiles".

It should contain the following:

Profile Name
Profile Location
Profile Size (MB)
Email Addresses
  Size of Each Address's Mailbox (MB)
# Of Bookmarks
Link to Bookmarks HTML File
Cashe Size (MB)
Address Book Size
Link to about:config (since most will want to get there anyway)


Would be nice to have a place where I could get good stats on my profile.  How
many would like to know how many MB's their profile takes up?  Not easy
(especially on windows) to remember:
C:\Documents and Settings\Robert Accettura\Application
Data\Mozilla\Profiles\Robert J. Accettura\6d5cbxc0.slt and check.

Would be nice if Mozilla could tell me more statistical information.


Ultimately.  Would be nice if Mozilla would let me see if it's on a server
(roaming profile) or local, ability to cap the profile size (good for network
admin's), even move or backup the profile to a remote location through such an
interface.

Out of sight for the casual user.  Available for power users.  

Reproducible: Always

Steps to Reproduce:
Confirming.  Still don't see this anywhere.
Status: UNCONFIRMED → NEW
Ever confirmed: true
similar to bug 171997; which one should we keep?

also, bug 241595 and bug 241597 should be marked as duplicates of one of these;
*** Bug 171997 has been marked as a duplicate of this bug. ***
*** Bug 241597 has been marked as a duplicate of this bug. ***
*** Bug 241595 has been marked as a duplicate of this bug. ***
I've been looking at the code to see if there's anything I can do towards
submitting a patch for this, but I had a question.

Is this something that could be done with XUL? As in, are there already values
that one could drop into an XUL file and have it show up, or would it be better
off being solved by some actual code, like how about:cache is generated?
most of this should be possible using xul and js, but you'd certainly have to 
write js code to do the work, the answers to these questions aren't available 
for free.
Product: Browser → Seamonkey
I think the minimum (or initial) requirement should be to have the current profile's location displayed. The actual code for that is as easy as this:
Components.classes["@mozilla.org/file/directory_service;1"].getService(Components.interfaces.nsIProperties).get("ProfD",Components.interfaces.nsIFile).path

The benefit for the average user is that it makes helping those people easier. You could just tell them "go to about:profile[s] and you will know where to find your profile." Knowing the location is key to fixing certain problems (lock files, file permissions, corrupted files, backup) and it's currently difficult to obtain that information (for an average user).

Calculating the overall size of the profile shouldn't be too hard either. Everything else, especially showing information about other profiles, is nice to have from my point of view.
IMHO, If anything, this should be integrated into about:support or it should be WONTFIX (add-on fodder).
(In reply to comment #10)
> IMHO, If anything, this should be integrated into about:support or it should be
> WONTFIX (add-on fodder).

The main part requested here, showing the profile location, is already part of about:support (Tools/Troubleshooting Information) which will be available in SeaMonkey 2.1. As I said, the rest is nice to have, so I agree with you, let's close this (WFM, WONTFIX, whatever).

Note that bug 548041 (about:support for Thunderbird) will probably add some things we will likely want to port to our about:support as well (I think we currently use Toolkit's as-is), but that'll be in another bug then.
resolving per comment #11, thanks for the input!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.