[ANN] Sense - call for collaboration

Hi All,

I would like to share with you a side project I've working on for the last
couple of weeks - a chrome extension that offers a JSON friendly developers
interface to ElasticSearch. It is based on the wonderful JavaScript based
code editor Ace (http://ace.ajax.org/) and offers features like syntax
highlighting, autocomplete and error highlighting. You can see screenshots
on https://github.com/bleskes/sense#screenshots (or get it on http://bit.ly/12rQHgb
and give it a spin) .

Most of Sense's smartness comes from a knowledge base which tells it of
ElasticSearch's endpoints and what JSON structure they expect. As you can
imagine it takes a quite a bit of effort to complete it. Until now I've
working on it on my own and I now feel it has come to a point where more
hands can be very useful.

If you'd like to help and learn lots about what ElasticSearch's API looks
like (after all, we need to go through all the endpoints ;)) shoot me an
e-mail, or better yet - a pull request on github.

Any other feedback is, of course, always welcome.

Cheers,
Boaz

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Boaz - the Sense plugin is awesome!

good work

clint

On Tue, Mar 5, 2013 at 9:44 PM, Boaz Leskes b.leskes@gmail.com wrote:

Hi All,

I would like to share with you a side project I've working on for the last
couple of weeks - a chrome extension that offers a JSON friendly developers
interface to ElasticSearch. It is based on the wonderful JavaScript based
code editor Ace (http://ace.ajax.org/) and offers features like syntax
highlighting, autocomplete and error highlighting. You can see screenshots
on https://github.com/bleskes/sense#screenshots (or get it on
http://bit.ly/12rQHgb and give it a spin) .

Most of Sense's smartness comes from a knowledge base which tells it of
ElasticSearch's endpoints and what JSON structure they expect. As you can
imagine it takes a quite a bit of effort to complete it. Until now I've
working on it on my own and I now feel it has come to a point where more
hands can be very useful.

If you'd like to help and learn lots about what ElasticSearch's API looks
like (after all, we need to go through all the endpoints ;)) shoot me an
e-mail, or better yet - a pull request on github.

Any other feedback is, of course, always welcome.

Cheers,
Boaz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Boaz, thanks for this great tool

Any chance you'll enable cookies use for it?
https://developer.chrome.com/extensions/cookies.html

This will help with using it against a secured web proxy.

Thanks!

On Tue, Mar 5, 2013 at 10:44 PM, Boaz Leskes b.leskes@gmail.com wrote:

Hi All,

I would like to share with you a side project I've working on for the last
couple of weeks - a chrome extension that offers a JSON friendly developers
interface to ElasticSearch. It is based on the wonderful JavaScript based
code editor Ace (http://ace.ajax.org/) and offers features like syntax
highlighting, autocomplete and error highlighting. You can see screenshots
on https://github.com/bleskes/sense#screenshots (or get it on
http://bit.ly/12rQHgb and give it a spin) .

Most of Sense's smartness comes from a knowledge base which tells it of
ElasticSearch's endpoints and what JSON structure they expect. As you can
imagine it takes a quite a bit of effort to complete it. Until now I've
working on it on my own and I now feel it has come to a point where more
hands can be very useful.

If you'd like to help and learn lots about what ElasticSearch's API looks
like (after all, we need to go through all the endpoints ;)) shoot me an
e-mail, or better yet - a pull request on github.

Any other feedback is, of course, always welcome.

Cheers,
Boaz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Itamar,

No problem. If you can make the change, check that it actually do work for
you and issue a pull request I'll accept it and make a quick minor release.

Cheers,
Boaz

On Mon, Apr 22, 2013 at 6:09 PM, Itamar Syn-Hershko itamar@code972.comwrote:

Hi Boaz, thanks for this great tool

Any chance you'll enable cookies use for it?
https://developer.chrome.com/extensions/cookies.html

This will help with using it against a secured web proxy.

Thanks!

On Tue, Mar 5, 2013 at 10:44 PM, Boaz Leskes b.leskes@gmail.com wrote:

Hi All,

I would like to share with you a side project I've working on for the
last couple of weeks - a chrome extension that offers a JSON friendly
developers interface to ElasticSearch. It is based on the wonderful
JavaScript based code editor Ace (http://ace.ajax.org/) and offers
features like syntax highlighting, autocomplete and error highlighting. You
can see screenshots on https://github.com/bleskes/sense#screenshots (or
get it on http://bit.ly/12rQHgb and give it a spin) .

Most of Sense's smartness comes from a knowledge base which tells it of
ElasticSearch's endpoints and what JSON structure they expect. As you can
imagine it takes a quite a bit of effort to complete it. Until now I've
working on it on my own and I now feel it has come to a point where more
hands can be very useful.

If you'd like to help and learn lots about what ElasticSearch's API looks
like (after all, we need to go through all the endpoints ;)) shoot me an
e-mail, or better yet - a pull request on github.

Any other feedback is, of course, always welcome.

Cheers,
Boaz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/2Mcc_xlev_o/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.