Closed Bug 105535 Opened 24 years ago Closed 15 years ago

RFE: smart widgets

Categories

(SeaMonkey :: Composer, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: sujay, Assigned: glazou)

Details

(Whiteboard: composer++)

need Netscape information/widgets i.e. stockquotes, weather, maps and directions.
bulk move to Future...sorry for the spam
Target Milestone: --- → Future
Ah, I was wondering how long it would be until Netscape tried to make money out of Composer! Ideally this would be done with an open architecture so that the user could download new widgets as XPIs. For example, Google could provide a Google search widget or CNN could provide a news headlines widget. Netscape could maintain a directory of widgets similar to the My Sidebar Directory. Am I being too optomistic here?
Status: NEW → ASSIGNED
Ariana--is there any interesting in adding this type of functionality to Composer in the next release cycle?
This is an interesting idea.... I'd like to see us offer a stronger core product and then add these neat features in. Please mark for future and we can discuss when we might get programming buy-off on it :)
reassign to new placeholder
Assignee: syd → composer
Status: ASSIGNED → NEW
Yep. I am working on it. Taking
Assignee: composer → glazman
Severity: normal → enhancement
Summary: RFE: add Netscape info/widgets → RFE: smart widgets
Whiteboard: composer++
Target Milestone: Future → mozilla1.6alpha
Product: Browser → Seamonkey
QA Contact: sujay → composer
Target Milestone: mozilla1.6alpha → ---
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
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
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: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.