Possible WLCP Enhancements?

calkins
June 02, 2009, 12:18 PM posted in General Discussion

Hi Andrew & Jon,

I'm wondering if the following could be incorporated into the next WLCP version.  These are pretty minor, and just wishful thinking, so if it's not possible (or requires too much work) it's no big deal.  The latest version is nearly perfect.

Audio "Repeat" Button?

This version has completely changed the way I study lessons on Cpod.  I used to listen to the Lesson mp3 and Audio Review in iTunes.  Now I listen to everything (including vocab. and expansion sentences) in the XML file.

One thing I miss is being able to set the Audio Review and Lesson mp3 on repeat.  Not sure if it's feasible, but is there anyway to add a "repeat" button next to the mp3 players?

 

 

 

 

 

 

Using Chinese Pera-kun?

I have a feeling this isn't possible, but is there anyway that the characters (for the vocab. and sentences) could allow the use of Pera-kun?

I know it's possible to use the "tooltips" toggle to get popup information, but I absolutely love the "annotations (with pinyin)" toggle.  Having the pinyin with literal translation is priceless.  But I would also like to use pera-kun at the same time.

I've noticed that Pera-kun works with the expansion sentences headings...

 

 

 

 

 

 

...but I have a feeling that XHTML Ruby prevents Pera-kun from working on the other characters.


Again, just wishful thinking.  I can't say enough about this program and am always thankful for the work you guys put into it!

Profile picture
andrew_c
June 02, 2009, 06:10 PM

Hi Brent,

I'm not working on WLCP anymore. I still use WLCP generated documents every single day, but no longer have the time or motivation to make further contributions.

Regarding the second suggestion, have you tried it with HanziBar?  I still use the old stylesheet from last October and HanziBar provides pop-ups just fine.  Also, I could be wrong, but I thought that Jon used an alternative technique, not XHTML Ruby, in the latest style sheet to do those annotations, something else other than XHTML Ruby might be the issue.