+1 sounds great to me ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message----- From: Daniel Gruno <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Sunday, March 15, 2015 at 9:56 AM To: "[email protected]" <[email protected]> Subject: Re: An idea for an interactive UI for Steve board votes > > >On 2015-03-15 17:39, Mattmann, Chris A (3980) wrote: >> Daniel, +1, to write the REST API in Python! :) >> >> I am +1 to your UI in its current form and when you >> are ready and have some volunteer cycles, and if you >> want to collaborate would love to on the REST API. >Great! I'm positive we could have something done before the 2016 election >:) >I only implemented this in perl because I would really love to see this >being an option at the upcoming elections (should be ready to just >implement and work with, but of course that's entirely up to the Steve >Project), in the long run, a system that relies slightly less on a ton >of regex and more on serialized data would clearly be something I'd >prefer. > >I'll get started on some design ideas for the REST stuff from a client >perspective soonish. >Maybe an UI for creating the elections as well? :) Can't be too difficult! > >create: web UI -> REST -> JSON-> ballot object on server >see ballot: ballot object on server -> JSON -> REST -> election ballot >in browser >vote: form data -> REST -> vote file on server > >or something like that... > >With regards, >Daniel. >> Cheers, >> Chris >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Chief Architect >> Instrument Software and Science Data Systems Section (398) >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 168-519, Mailstop: 168-527 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Associate Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> >> >> >> >> -----Original Message----- >> From: Daniel Gruno <[email protected]> >> Reply-To: "[email protected]" <[email protected]> >> Date: Sunday, March 15, 2015 at 9:16 AM >> To: "[email protected]" <[email protected]> >> Subject: Re: An idea for an interactive UI for Steve board votes >> >>> Hi Chris, >>> I would love for this to pull data from a REST API, it would mean less >>> tinkering with the perl stuff ;) >>> What I have done for now, as I'd love for this to be something we can >>> try out soon, is just modify the perl script (see patch in previous >>> email) to add a stv_form_interactive function that spits out the same >>> page as the example, but with real data. >>> it gets called by passing "?interactive=true" to the usual vote URL. If >>> present, interactive mode kicks in, if not, it's the old version. >>> >>> I definitely think the REST API is the way forward (if possible, i >>>would >>> love to rewrite in Python ;) ), and in the long run, that's what I'll >>> aim for. Makes it easier to define candidates, and a heck of a lot >>> easier to import statements from them when we get so far, but for now >>>in >>> the short run, I've just modded the perl script. >>> >>> With regards, >>> Daniel. >>> >>> On 2015-03-15 17:08, Mattmann, Chris A (3980) wrote: >>>> Daniel I poked around on this and you have a wow+awesome+woot from >>>> me. I love the new UI. My only legitimate concern is the mapping of >>>> this to backend REST services - does your program call the backend >>>> Python/Perl Steve code directly? >>>> >>>> If so, do you have any thoughts on these REST services I put up >>>> on the Steve wiki? >>>> >>>> http://wiki.apache.org/Steve/SteveRESTAPI >>>> >>>> >>>> Cheers, >>>> Chris >>>> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> Chris Mattmann, Ph.D. >>>> Chief Architect >>>> Instrument Software and Science Data Systems Section (398) >>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>> Office: 168-519, Mailstop: 168-527 >>>> Email: [email protected] >>>> WWW: http://sunset.usc.edu/~mattmann/ >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> Adjunct Associate Professor, Computer Science Department >>>> University of Southern California, Los Angeles, CA 90089 USA >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> >>>> >>>> >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: Daniel Gruno <[email protected]> >>>> Reply-To: "[email protected]" <[email protected]> >>>> Date: Sunday, March 15, 2015 at 9:01 AM >>>> To: "[email protected]" <[email protected]> >>>> Subject: An idea for an interactive UI for Steve board votes >>>> >>>>> (sent from wrong address at first, here goes...) >>>>> >>>>> HI folks, >>>>> I've been wondering for some time if it wasn't possible to make board >>>>> voting a bit less stressful. >>>>> As it is right now, you have to mentally keep a note of letters and >>>>> their corresponding names and how that all adds up to a weird string >>>>> you >>>>> are typing into a text field - it can get a bit confusing, especially >>>>> when you suddenly change your mind and want to rearrange things. >>>>> >>>>> So I came up with an interactive UI for managing those sort of votes, >>>>> where you can drag'n'drop candidates onto a ballot (as many as you >>>>> like, >>>>> of course) and then rearrange that ballot as you see fit with your >>>>> mouse. Not only will i display the candidates in a more friendly >>>>> manner, >>>>> it will also conform to the old Steve methods and generate an STV >>>>> string >>>>> for voting. I've been working with Jim to get some extra features >>>>>into >>>>> it, and it's starting to look real nice. >>>>> >>>>> You can see a demo with fake names at http://asfcloud.com/steve.html >>>>> I have a patch for the perl script so that everything - sans the >>>>> statement data - will work out of the box. >>>>> >>>>> To get to the point; Is this something we would want to implement, >>>>> maybe >>>>> showcase at the next annual meeting? The feedback I've gotten has >>>>>been >>>>> ranging from "I like it" to "wow, that's awesome", so I think we >>>>>could >>>>> really help some folks if we could get this implemented. >>>>> >>>>> It's tested and should work with the latest versions of FireFox, >>>>> Chrome, >>>>> Internet Explorer, Safari, Opera etc (anything that will do HTML5). >>>>> You can see a patch to cast-vote.pl at >>>>>https://paste.apache.org/p/n1IU >>>>> although it will also require the support files (JS, CSS, PNGs) to >>>>>work >>>>> properly. >>>>> >>>>> Thoughts? Comments? Flames? >>>>> >>>>> With regards, >>>>> Daniel. >
