Closed Bug 114242 Opened 23 years ago Closed 14 years ago

[RFE] several separate bookmarks lists

Categories

(SeaMonkey :: Bookmarks & History, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mac.bjarnedm, Unassigned)

References

Details

I would like to see the ability to manage several separate lists of bookmarks.

I justify this in the following need for at least three separate lists:
1) a systemwide list managed by the super-user
2) a bookmarks list for the workgroup / project one is working on
3) a personal bookmarks list

you might also want more than one of 2) if you are involved in more than one project
reporter: is there any difference between this request and bug 104184?
  "[RFE] UI for bookmark file location preference"
Alfonso: Not the same thing at all :-)

bug #104184 deals with the location of a *single* bookmarks file that might be
implictly shared between NS4 and Mozilla.

I'm proposing bookmark files that in
case 1) are explicitly shared by all users on a computer/network and only
administered by a super-user
case 2) are explicitly shared by all members of a group/project and administered
by this
case 3) private bookmarks administered only by the owner of the profile

futhermore, my proposal includes the ability to have several bookmark files
loaded concurrently -- you might liken it to the abilty to have several email
accounts or newsgroup accounts concurrently. In fact, I think an interface along
the lines of the Mail/News administration would be appropiate.
Summary: several separate bookmarks lists → [RFE] several separate bookmarks lists
Bjarne: 
104184 isn't really about sharing the bookmarks between NS4 and Moz (see the
dupped bug 107130), it's just to be able to select where do you want to store
your bookmarks. This way you can keep one file with (case a), other with (case
b) etc...

I agree that 104184 doesn't deal with the ability to load various files at the
same time, from my point of view this is possibly bug 72413 "permit remote
HTTP/FTP URLS for bookmarks datasources", as long as it also allows to load the
files from the local network.
hmmmmm ...

I guess I'm going for the whole package:
-- any number of bookmark files
-- stored anywhere : local computer , LAN , WAN , web , ...
-- using any protocol : file , ftp , http , ldap , acap , ...

with shared bookmark files you will - of course - have the same problems as you
have when updating databases : concurrency, read/write access etc.

I think my FRE might be considered a super-set of all the previous mentioned
RFEs :-)
->default assignee.
Assignee: pchen → ben
Status: UNCONFIRMED → NEW
Status: NEW → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
*** Bug 147537 has been marked as a duplicate of this bug. ***
*** Bug 176360 has been marked as a duplicate of this bug. ***
*** Bug 231149 has been marked as a duplicate of this bug. ***
In schools and businesses, it would be very handy to be able to set up a 2nd
common bookmarks file that either appears above personal bookmarks, or is merged
with personal bookmarks.  This 2nd bookmark file could (probably should) be
read-only from browser.  (ie: Removing or editing bookmarks from the common file
will result only in non-persistent changes in memory, but will not be written
back to the file.)

A nice set of prefs to go along with this would be something like:
 browser.bookmarks.common.file
 browser.bookmarks.common.from_url  (allow retrieving from a web site)
 browser.bookmarks.common.mergetype (1=merged, 2=above, 3=below)
    (how common bookmarks are merged with user pref bookmarks)

Unfortunately this doesn't sound like something trivial.  It would, however, be
a big help to schools and businesses deploying Mozilla/Firebird extensively.
Product: Browser → Seamonkey
Assignee: bugs → nobody
Status: ASSIGNED → NEW
QA Contact: claudius → bookmarks
Target Milestone: Future → ---
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.