yogsottot / organize-search-engines Goto Github PK

customize toolbar breaks ose

the generation of favicons for "open in tabs" seems broken

we shouldn't save the rdf directly, but copy the data over to a temporary
rdf data source and save that.
This makes sure, that relicts of engines that are in no folders go away.

[deleted issue]

sometimes engines disappear, because they are in no folder, but are still
installed and somewhere in the rdf...

Minefield/Gran Paradiso offers the possibility to add multiple search bars.
We should modify those as well.

we don't know how long rdf will be supported and rdf code constantly crashes...

This would break compatibility with Firefox 2 (no sqlite templates there),
so no hurry here.

removing engines doesn't persist over restarts

What steps will reproduce the problem?
1. open the manager
2. rename it
3. drag & drop it somewhere else

What do you expect to happen? What do you see instead?
the engine has its old name.

removing folders doesn't work

improve sort stuff

Some user said, that Newsfox breaks the folders. Need to investigate that.

the search history could only show those terms that were used with the
engine currently selected. I don't think I really want this, but I'll file
this issue, so I can finally get rid of my old todo list.

[optionally] select the search engine of the current page automatically

the selected engine isn't highlighted in bold anymore in Firefox 3. (Only
the folder it is in.)

Structure__Item::modified with values 0,1 and 2 is really ugly. This should
get a better fix, with it's own flag or some detection whether the item is
in RDF.

copy n paste would be nice, as another way to move engines across folders
not involving the mouse

when an engines is updated, it's name is reset to the default and therefore
it's also moved back to the root folder. We should change it back to what
the user wanted.

What steps will reproduce the problem?
1.
2.
3.

What do you expect to happen? What do you see instead?


Please provide any additional information below.

What steps will reproduce the problem?
1. Create a new profile and start firefox with it
2. Install Organize Search Engines 1.5 RC1 and restart
3. Drag a selection text to the search engine button, then to an engine
menuitem other than the current engine and drop

What do you expect to happen? What do you see instead?
Firefox should start a search with the selected engine, but it starts a
search with the current engine

What version of the product are you using? On what operating system and
Firefox version?
Windows XP SP2, Firefox 3.0.8, Organize Search Engines 1.5 RC1

What other add-ons are you using?
None

crash on cancel when there's an empty folder

dragging text over the search bar should open it to allow selecting a
engine to search the text

when an engine is added, and the rdf is saved, reloaded, or a template is
rebuilt, Firefox crashes.

export/import stuff

What steps will reproduce the problem?
1.
2.
3.

What do you expect to happen? What do you see instead?


Please provide any additional information below.

What steps will reproduce the problem?
1.
2.
3.

What do you expect to happen? What do you see instead?


Please provide any additional information below.

allow the user to select an engine's folder during its install

.

What steps will reproduce the problem?
1. Create a new profile and start firefox with it
2. Install Organize Search Engines 1.5 RC1, SearchWP 2.4b1 and restart
3. Drag a selection text to the search engine button

What do you expect to happen? What do you see instead?
The engine selection popup should open, but it does not appear.

What version of the product are you using? On what operating system and
Firefox version?
Windows XP SP2, Firefox 3.0.8, Organize Search Engines 1.5 RC1

What other add-ons are you using?
SearchWP 2.4b1

a workaround wouldn't hurt...

the manage window should have buttons, menus and all.

Specifically needed (sorted by importance):
 * a "move" button, so dnd isn't the only way to move an engine into
another folder. This is a major accessibility flaw currently.
  * the menus will also be there primarily for accessibility reasons, e.g.
sorting is only available through mouse clicks
  * This will allow me to also remove the css making the buttons focus-able.
  * Move the restore default button, get more link and show suggestions
checkbox to the menu.
  * ...

What steps will reproduce the problem?
1.
2.
3.

What do you expect to happen? What do you see instead?


Please provide any additional information below.

seems like the keywords are never saved...

I have written an userChrome.js script to archive:
1. Left click on an engine menuitem would change to the engine and do search;
2. Ctrl + Left click on an engine menuitem would do search and keep the
menu open

But with OSE "Open All in Tabs" items, OSE always closes the engine popup
immediately. This happens with both OSE 1.4 and OSE 1.5 RC1. Would you
kindly to provide a fix? I could send you my script if needed.

'nuff said

Search on Tabs is said to be incompatible. Will need to check that...

the engine manager needs a "properties" button... until now we used the
properties icon for keywords. I think we're running out of icons.

just fixed...
reporter: anandi at
https://addons.mozilla.org/de/firefox/discussions/comments.php?DiscussionID=941

the fix also replaces the awful way for supporting customize toolbar with a
nice DOMNodeInserted listener :)

Some properties dialog would be nice...

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.

support for second search most likely needs an update

renaming default engines doesn't work in Firefox 3 yet.

renaming didn't work completely (e.g. the engine was offered to be
installed a 2nd time on a page with a <link> to it) until I reimplemented
it with that *big* hack into the search service...

add separators before instead of after an item - that's how the bookmarks
manager works

What steps will reproduce the problem?
1. create a folder
2. move one or more engines into this folder
3. press ok
4. reopen the engine manager
5. move the engines out of the folder
6. delete the folder
7. press ok
8. open up the error console, notice the exceptions there
9. open the engines popup, notice that the icon is missing from the engines
that /were/ in the folder
10. restart Firefox, find the engines removed

allow engines (and folders) to be in more than only one folder.

that'll be pretty damn hard, but it'll be worth it!

See also:
http://maltekraus.de/blog/firefox/organize-search-engines/mehrfach-auswahl-von-s
uchmaschinen-teil-2-43.html
http://maltekraus.de/blog/firefox/organize-search-engines/mehrfach-auswahl-von-s
uchmaschinen-fragen-ueber-fragen-27.html

with "intelligent" search plugins, their'd be a automatic detection which
engine to use based on the search terms.

For example, when a number is typed in, Bugzilla is searched. Search terms
ending with "\.js$", "\.cpp$" and so on would be sent to mxr.

This is kind of like search keywords, but automatic based on the content.

This would be rather complicated to implement, performance might suck with
many engines or bad regular expressions. And finally, most engines could
not be detected without re-introducing keywords. So it's questionable
whether this is really worth it.

allow the user to set background colors for engines...

probably hard to get with different themes

try to be compatible to as many extensions as possible... there's already
compatibility for searchOnTab, 2ndSearch and an "API" to make things easier
for other extensions.