Hi Florian, That could confusing for the first time.
I think interpreter binding UX have more improvements we need to make. For example, changing order of selected interpreter does not mean anything but only for the first one. In this case it's better to have 'radio' button or something similar, to select the default. Also i've seen some user who uses the zeppelin for the first time, they didn't noticed that press 'Save' button of interpreter binding menu, before start. Thanks Florian for valuable feedback. Best, moon On Mon, Dec 7, 2015 at 10:00 PM Florian Leitner < florian.leit...@seleritycorp.com> wrote: > Hi, > > First of all, thanks to all developers behind this open source project and > their hard work and blood and sweat! > > It might be worth reporting this minor, but anoying "negative first UX" > issue I just had when running Zeppelin and the tutorial for the very first > time. > > After opening the Tutorial notebook, the first-time user is presented with > the following text: > > Bind interpreter for this note. Click to Bind/Unbind interpreter. Drag and >> drop to reorder interpreters. >> The first interpreter on the list becomes default. To create/remove >> interpreters, go to Interpreter menu. > > > Plus a list of possible interpreters all in blue with Spark shown as the > first option. I kind of naturally deduced that I was being asked to click > on the Spark interpreter, as to select it; Then I clicked save. Oh my was I > wrong... > > Next, I (thought I) ran the download of the archive, which seemed a tad > fast :-), but there was no error/problem. It only appeared weird to me that > the output should be code itself. But whatever, I moved on to the graph > displays. Everything works nicely, you play around with the dials and stuff > starts happening (So cool coming from Jupyter, btw!). At some point I > clicked "Run" on one of the displays...: > > sql interpreter not found > > > Uh-oh. Luckily, someone else already had that problem and had asked for a > solution on Stack Overflow, with one guy answering (explaining how to > re-activate the Spark interpreter...), although he did not get the "correct > answer hook". > > While I am sure this is something every user of Zeppelin will get used to > pretty fast, it is a frustrating first user experience. Either explain in > the interpreter configuration box what the color-codes mean (blue=active > interpreter, white=inactive interpret) or, better, use an UI with semantics > that are less ambiguous. > > For your consideration... Other than that minor hick-up, Zeppelin looks > like a great product, thanks! Looking forward to using it! > > Regards, > Florian >
