Initial foray into indexing into lucene, using a projection to talk to
Clucene - using utf8 to transmit the data to native side

Helps if we pass in the indexing callback to the prelude script

spaces/tabs

per project vim.custom instead

Got rid of the indexing natives, index requests actually mean pushing to a stream which we'll be able to subscribe to

update notes

So I could use a projection to push state into my native handler, seems legit

Showing how we might push from a projection into an indexing subsystem

Time to start playing with Clucene

Don't check in the clucene stuff

Ensure we can build against CLucene, in situ anyway

Will use a class to hold the engine state, seems legit

Pulled in jsoncpp and made sure I can use it from our code

this sort of thing, stringly typed nightmare

Manage index writers in a map

Pass in the logger to the lucene engine

Basic data being chucked into lucene, expensive, and not actually storing "real" data, just entries

Sod this, adding a one-way utf8 marshaller for ease

Updated handler to take utf8 via the new marshalling code

Integrate with clucene's document and fields, re-use the flag values

Removed accidental file

Non sigsegging indexing code that takes in options from JS about how to index each field, needs an API to support that on JS side of course