Hi guys, is there a chance to get any further info on this?

Hi there,

 

Is there a way to develop a custom index manager, in order to use

another index engine (e.g. Windows Desktop Search or Google Desktop)

as a backend?

 

I'm asking this because I would like to concentrate my query in a

single search engine. This way, it doesn't matter whether I'm

searching from inside Omea or from the desktop, I would find the same

results. Moreover, Omea-only items (like feeds) could be indexed in a

way that if a desktop-originated query returned an item from Omea, a

specially-crafted URL would open the correct item in Omea.

 

Although I consider Omea an outstanding application, it is not always

convenient to have to open its GUI to search for something when I can

do the same from my taskbar. Besides, Windows Desktop Search and

Google Desktop have lots of file filters, much more than Omea offers

right now. Therefore, why can't I leverage those powerful tools in

order to create an awesome productivity tool?

 

I'm glad you could answer, Michael.

As far as I understand, you've set two independent tasks:

1. let Omea index resources not covered in current list.

 

Yes, that's it. This is the one of the issues, however not the most important

to me.

2. let outside environment index Omea resources.

 

This is the key point to me. I'd like to be able to completely replace the

current indexing engine by a custom made, in order to redirect it to a third-party

desktop search engine (like Google's). I believe the easiest way to achieve

this would be to replace, via OpenAPI, the current Index Manager by another

which implements all of the required interfaces. I think that could not impact

adversely in Omea's architecture, perhaps all it takes is refactoring to

use an interface instead of a concrete class (just a guess).

While the first task can be solved in Omea (with more or less

efforts), and there are several existing patterns which can be applied

to different resources depending on their nature, second task is

questionable since it has no interface for exporting resources "on

demand" (only "Export Resources list" into XML facility which is to

appear in 2.1.5).

Actually I don't want a "export on demand" feature, for that would duplicate

the indexed content. I want to replace the current indexing engine.

I can even help you with delivering Omea-oriented

protocol URL for its resources,

That would be great! Any notifying protocol - TCP/IP, DDE or similar would

do the trick, I think.

Best regards,

    Igor

Dear Igor Abade,

I> That would be great! Any notifying protocol - TCP/IP, DDE or similar

I> would do the trick, I think.

Anyway this will be after the 2.2 release, not earlier. We just need to fulfill

our promises, and help people with serious problems... Let's return to this

issue afterwards, when we will start planning new version.

best wishes,

Michael Gerasimov,

JetBrains Omea Developer