Ctrl+enter in the webadmin data browser

[Aseem Kishore]

(Sorry, we've just this week updated from 1.6 to 1.8, so all this feedback is probably way late. Apologies!)

It's interesting that this new webadmin optimizes for multi-line input rather than single-line ones. Did you guys consider going more of a Facebook style, where enter still submits by default, but shift+enter adds a newline?

Alternately, if you want to stick to optimizing for multi-line input, will you guys consider supporting cmd+enter too? Ctrl+enter is really cumbersome on Macs. =)

Thanks for the consideration!

Aseem

[Javier de la Rosa]

On Tue, Oct 23, 2012 at 5:15 PM, Aseem Kishore <aseem....@gmail.com> wrote:
> but shift+enter adds a newline?

+1.


--
Javier de la Rosa
http://versae.es

[Mattias Persson]

It could even be an option to the right of the input field, containing "Facebook-style" and "I-don't-know-what-to-call-ctrl-ENTER-style", and perhaps remembered by the browser.

2012/10/23 Javier de la Rosa <ver...@gmail.com>

--

--
Mattias Persson, [mat...@neotechnology.com]
Hacker, Neo Technology
www.neotechnology.com

[Peter Neubauer]

Yes,
that sounds like a good thing. Wanna make an issue on this?

Cheers,

/peter neubauer

G: neubauer.peter
S: peter.neubauer
P: +46 704 106975
L: http://www.linkedin.com/in/neubauer
T: @peterneubauer

Neo4j 1.8 GA - http://www.dzone.com/links/neo4j_18_release_fluent_graph_literacy.html

> --
>
>

[Aseem Kishore]

Done: https://github.com/neo4j/community/issues/949

--

[Jacob Hansson]

Would y'all prefer FB-style, or just adding command+enter as an extra sequence?

Part of the reasoning behind making it CTRL+ENTER is that cypher is now mutating, and we thought it would be less likely that you end up firing off a half-baked mutating query by mistake if the execute sequence is a two-key thing.

/jake

[Aseem Kishore]

I personally would prefer FB-style, because the primary Data Browser use case for me is by far looking up nodes and relationships -- one-line inputs. For mutable Cypher, I go to the console tab -- which optimizes for multiple lines of input.

(But on that note, how come two newlines doesn't finish an input there anymore? The semi-colon is less of a big deal, so just wondering.)

Aseem

--
 
 

[Michael Hunger]

I would make the input field in the data browser reject mutating queries, much to dangerous there.

And then go with the approach that wes used in the console:

- submit on enter

- automatically reformat queries as they are entered into multiline thingies

- optionally additional lines with shift-enter

- the big run button there is just for android phones which don't generated return-keys on submit

see http://console.neo4j.org

Michael

--