Hi, Here's one alternative. Please check https://www.zeppelinhub.com/viewer/notebooks/aHR0cHM6Ly9yYXcuZ2l0aHVidXNlcmNvbnRlbnQuY29tL0xlZW1vb25zb28vemVwcGVsaW4tZXhhbXBsZXMvbWFzdGVyLzJCNDRRNVU3VC9ub3RlLmpzb24 (Calendar on viewer looks little bit broken, but it'll have no problem on your Zeppelin instance)
If you want to know more about how it works, see http://zeppelin.incubator.apache.org/docs/0.5.5-incubating/displaysystem/angular.html . Hope this helps. Thanks, moon On Sat, Nov 21, 2015 at 8:15 AM Mark Luk <m...@juicero.com> wrote: > According to the specs, we have 2 types of form creation - text field, and > a dropdown box > > > http://zeppelin-project.org/docs/zeppelincontext.html > > > Text field > > /* Create text input form */z.input("formName") > > > > Dropdown box > > /* Create select form */z.select("formName", Seq(("option1", > "option1DisplayName"), > ("option2", "option2DisplayName"))) > > > Is there a way to have Zeppelin get input from a calendar widget instead? > > if not, what do people recommend as the next best thing? > > I could have something else host the calendar widget (maybe django, or > servlet). and when people click on the date in the calendar, it'd link it > to the zeppelin paragraph. and somehow get the date as a parameter to the > paragraph python code? does that sound like a good idea? > > >