opening a bug to "formalise" this feature.
setting milestone and nominating as beta1 candidate
Status: NEW → ASSIGNED
Target Milestone: M14
PDT needs more info on exactly what this it...Advanced Search?
Whiteboard: [NEED INFO]
This is the bug Ben created to track implementation of the multiple search engine UI which includes the Advanced Tab and the multiple search engine results. Having the Advanced Tab is a beta1 requirement because it is also the chief discoverable way we offer choice, a high priority to reviewers and press and something that Netcenter is selling to partners as we speak. Note this is only UI in the Sidebar and search results in the content window - we have cut the additional Search Dialog window from beta1.
Whiteboard: [NEED INFO]
renaming summary to "advanced search functionality" so we can distinguish this bug from the other search bugs.
Summary: search functionality → advanced search functionality
search ( full details here: http://client/seamonkey/navigator/search-steps.htm ) is something XPApps would like implemented in basic form for beta as one showcase feature for our app. Basically we want to: - display results in the sidebar - display results in an advanced listing in the content area (see doc) - allow choice of more than one search engine in categories (back end work already hooked up, remaining work needing to be done on UI)
Putting on the PDT- radar for beta1. As long as we can offer choice in the preferences were ok for beta1.
Clearing PDT- for re-consideration. Please come and talk to me about this before you mark it PDT- again.
Re-summarizing bug. This isn't advanced -- it IS the search feature for beta 1.
Summary: advanced search functionality → Search functionality
Spoke with don. Putting on the PDT- radar for beta.
This is bogus, and needs to be PDT+. The "choice" comes from supporting multiple search engines which includes aggregated search results. If you don't have support for multiple engines, you don't get any choice... meaning that all we'll be able to do it go to Netcenter for searchs. It ALSO means a LOT of work would have to be done to pull out all the search support that has already gone into the builds, which makes no sense either. Removing PDT- from status area; please re-consider AGAIN and if you don't come up with PDT+, come talk to me.
Do we have any contractual obligations with third-party search engines in this area?
Note: bug # 26334 (which is marked PDT+ for beta1!) depends on this search functionality for search categories and multiple engine support.
This has to do with multiple search engines. Not a must have for beta1. Putting on PDT- radar for beta1. 26334 set to PDT-. michaell will go see rjc for marketing explanation :-)
Back in... Putting on PDT+ radar for beta1
Whiteboard: [PDT-] → [PDT+]
Priority: P3 → P1
We need a landing date planned for this. Please add the date to the status whiteboard. Thanks, Jim
more tweaks checked in as per german/usability request. Keeping this bug open to track further requirements. removing beta1 and PDT+ status though as all other chagnes are not required until after beta1
Target Milestone: M14 → M15
Move to M16 ... Ben, are you done tracking this sucker yet?
Target Milestone: M15 → M16
Move to M20 as a meta tracking bug.
Target Milestone: M16 → M20
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
yeah i guess we have 'search functionality' :-), marking VERIFIED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.