organize-search-engines
organize-search-engines copied to clipboard
Published
20 hours ago •
Baton34
Baton34
rewrite engine manager
There's already a rudimentary and buggy API in the component. The manage
window should just be a consumer of it instead of modifying the low-level RDF.
Problem here is that we don't want to work with a 'live' tree but only
apply the changes when hitting the 'Ok' button.
In the end, we should move the managing code to its own component with its
own interface that can be told, which datasource to use. Than, we can do
our modifications and tell the service to adopt the changes only when the
user clicks Ok.
Original issue reported on code.google.com by [email protected] on 25 Apr 2007 at 3:31
Original comment by [email protected] on 13 Jul 2007 at 1:47
- Added labels: Blocks-2
- Removed labels: Blocks2
blocks issue 23
Original comment by [email protected] on 19 Aug 2007 at 5:14
- Added labels: Blocks-23
use the standard google code feature to express dependencies
Original comment by [email protected] on 9 Feb 2009 at 10:51
- Added labels: Component-Component, Component-Engine-Manager
- Removed labels: Blocks-2, Blocks-23, Component-Logic
when rewriting the engine manager, I'll have to take those experiments for
selecting
multiple engines at once into account.
Original comment by [email protected] on 12 May 2009 at 5:35
- Changed title: rewrite engine manager
(raising priority)
Original comment by [email protected] on 12 May 2009 at 5:36
- Added labels: Priority-High
- Removed labels: Priority-Low