Closed Bug 94787 Opened 22 years ago Closed 11 years ago

Alphabetical Order for Profiles


(Toolkit :: Startup and Profile System, enhancement)

Not set





(Reporter: raccettura, Assigned: raccettura)



(3 obsolete files)

Could profiles maybe be listed in alphabetical order rather than the order in
which they were created?  That would be great for when you have a lot of
profiles... and considering how Netscape Comm. and most other programs list
information (including the component portion of buzilla) alphabetical order just
makes more sence and feels better.
This is probably a legitimate RFE, and there's no obvious duplicate in this component 

In truth, in the Profile Manager dialog, the profile names are topped by a column header, 
"Available Profiles," which appears similar to that used in list views under Classic in Mail/
News, for example. Such column headers usually are clickable to sort by their type. So, if 
we don't provide this "clickable" sort functionality, the default sort order of these profiles 
should be by that described in the header, and in this case that is profile name.

So, to state it succinctly, the profiles should be listed in alphabetical order, and the list 
should resort when a change is made to the list.

Marking enhancement, though, as the current functionality does work.
Severity: trivial → enhancement
Ever confirmed: true
Is there a timeframe for completion of this?  Maybe 9.5?  I don't think it is
that much work is it?
Target Milestone: --- → Future
Anyone?  I guess no chance on 1.3a... but perhaps for 1.3b?

Would be nice.

With lots of profiles, would look neater if it were all in alphabetical order.
Can we hvae this added to the list of bugs for Firebird 1.0?

I think it would be a good way to polish it up (as small as it is).  With large
lists, it can be a bit annoying.
Taking, I have a patch
Assignee: bugs → robert
Attached patch Patch v1 (obsolete) — Splinter Review
My first attempt at writing a patch.

Please don't hurt me.  I'm a nice guy.	Really!  :-)
Attached patch Patch v1.0001 (obsolete) — Splinter Review
Deleted a return for no good reason, contributors.
Attachment #138833 - Attachment is obsolete: true
Attached patch Patch v1.0002 (obsolete) — Splinter Review
I suck, I'm used to tabbing.
Attachment #138836 - Attachment is obsolete: true
Comment on attachment 138838 [details] [diff] [review]
Patch v1.0002

Suggesions for sr?
Attachment #138838 - Flags: review?(
Attachment #138838 - Flags: review?( → review?(dean_tessman)
Comment on attachment 138838 [details] [diff] [review]
Patch v1.0002

> function loadElements()
> {
>   try {
>+    var ProfileArray = new Array()
>     var profileRoot = Registry.getKey(Registry.Common, "Profiles");
>     var regEnum = Registry.enumerateSubtrees( profileRoot );
>@@ -170,15 +172,18 @@
>         break;
>       var migrated = Registry.getString( node.key, "migrated" );
>-      AddItem( "profiles", new Profile(, migrated ) );
>+      ProfileArray[ProfileArray.length] = new Array(,migrated);

Why do you create two Arrays?  Also, you need a space between the comma and
"migrated" to be consistent with the surrounding code.
Attachment #138838 - Flags: review?(dean_tessman) → review-
Comment on attachment 138838 [details] [diff] [review]
Patch v1.0002

This bug still exists ;-)  me kind of forgot. 

Going to update sometime... I could do better than this.
Attachment #138838 - Attachment is obsolete: true
Product: Browser → Seamonkey
See bug 193755.  
Are you still working on this ?
Component: Startup & Profiles → Startup and Profile System
Product: SeaMonkey → Toolkit
QA Contact: agracebush → startup
Target Milestone: Future → ---
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.