JSAV version 0.2.0 released

4 replies [Last post]
shaffer
shaffer's picture
Offline
White BeltYellow BeltGreen BeltRed BeltBlack Belt
Joined: 2009-05-28
Posts:
Points: 2009

We have just released JSAV Version 0.2.0 to SourceForge. Hopefully later this evening I will also update the OpenAlgoViz@SourceForge website to include information about the OpenDSA project and provide distribution via a .zip file for those who prefer that to SVN/CVS.

 

Release 0.2.0 includes the following:

  • Support for bars and numbers as alternative look-and-feel for the array layout, (instead of boxes around array items)
  • Optimizations/refactoring of the slideshow state mechanism
  • CSS style reset for consistency across browsers
  • Slideshow counter
  • Ability to invoke a parameterized version of an AV
  • OEmbed support (initial version)
  • Options panel (for things like animation speed, bars vs. array layout) (initial version)
  • Shellsort AV
  • Ability to invoke another web page (e.g., "help" files)
  • Title screen for a slideshow
  • Release Bonus: Draft layout of Shellsort Proficiency Exercise
  • Bug fix: Disabling controls during animation
  • Bug fix: No double-printing of first slide of slideshow

naps
Offline
White BeltYellow BeltGreen BeltRed Belt
Joined: 2009-06-11
Posts:
Points: 65
Re: JSAV version 0.2.0 released

In the slideshow for ShellSort posted at algoviz.org/OpenDSA/AeBook/Shellsort.php, the mechanism for going through all the sldes is to click through them one slide at a time.   I fear this could become annoying for a reader in a situation, like the ShellSort storyboard, where there are 123 slides in the slide show — 1 for each data exchange.   It would be nice if a reader who was reaching a point of understanding each step had a slider bar of some sort to go through a sub-sequence of the slides at a high rate of speed.  In other words, when the slides are becoming too granular for the reader, provide some GUI component to move thorugh a series of slides rapidly. 

shaffer
shaffer's picture
Offline
White BeltYellow BeltGreen BeltRed BeltBlack Belt
Joined: 2009-05-28
Posts:
Points: 2009
Re: JSAV version 0.2.0 released

Hopefully the eventual Pseudocode support will allow users to condense slides as they contract sections of the pseudocode. But this would make a nice, simple alternative for developers who do not wish to add in pseudocode for their AV. It would also help during debugging to be able to skip a bunch of slides!! It could be implemented as an alternative display option for the existing slide counter.

 

ville
ville's picture
Offline
White BeltYellow BeltGreen BeltRed BeltBlack Belt
Joined: 2009-05-28
Posts:
Points: 559
Re: JSAV version 0.2.0 released

Yes, a way to jump ahead in the animation would be useful. Like Cliff said, in debugging it’s annoying to step through all the previous steps.  But does a slider solve this problem for students? It does not give an indication what they are jumping into anyway, as I’m thinking most of the students aren’t familiar with the structure of the slideshow beforehand. Could a "table of contents" of certain important (author specified) points in the slideshow be a better/alternative solusion? And clicking in the toc would take the student to that step in the animation.

Ville Karavirta, Aalto University, http://villekaravirta.com/

shaffer
shaffer's picture
Offline
White BeltYellow BeltGreen BeltRed BeltBlack Belt
Joined: 2009-05-28
Posts:
Points: 2009
Re: JSAV version 0.2.0 released

I think that a slider would be helpful, and easy. Both easy to implement and easy to use (the developer merely changes a parameter in the deflnition of the slideshow counter widget). While a TOC might be better, it is likely to be substantially more difficult to both implement and use (by AV developers). My big concern would be if the slider were to be put off in favor of eventually doing the TOC. Even if both features were available, I can see a developer choosing the slider.

 

We might want to start keeping a list of proposed features, with some sort of priorities.  We do have the bug tracker that to some extent gets used to request features. And we also have the road map. But that is at a rather high level. I don’t think we have a comprehensive list of features that might get included (or at least considered).