wydiwys FAQ

• It doesn't work! (uhhh ... what doesn't work???)

• The keyboard buttons don't work while presenting. wydiwys is still being developed. It probably doesn't work on all browsers, and may never work on the really old ones with inadequate Javascript support. The wydiwys.js javascript module is what interprets the keypresses and navigates to the next page. Your presentation may have been prepared with an older version of wydiwys.js, so try replacing it with the latest one on this website.

• My wireless presenter doesn't work. wydiwys ought to work with any wireless presenter, but it has only been tested with a SIIG CE-WR0012-S1 and a Targus AMP16US presenter. These both make codes 33 for BACK, 34 for FORWARD, and 66 for ENTER (which is the white square/black square on the front of the Targus, and the white screen/black screen on the right of the SIIG). Other codes are easily added to wydiwys, and you can find out what they are with this tool ( click on all the "suppress handling" checkboxes) . Note that some of the buttons on these presenters emit multiple codes and have toggle modes - a keypress alternates between one set of multiple codes and another. BTW, make sure your presenter is turned on and the USB plug is plugged in and the battery is fresh. Duh.

• wydiwys can't make a presentation output directory. You may already have a directory with the same name. Delete or rename it. wydiwys is expressly designed to NOT write over an old presentation. You should also make sure you have the permissions to create the output directory.

• Is there a Windows version? No. Windows doesn't have hard links. If you want to port it, be my guest, but you should use a Linux or BSD or Solaris or Mac system instead.

• Where's the GIT repository? Soon, soon.

• I would like feature X. Start coding.

• The design file syntax sucks. Yes indeedy. If somebody wants to come up with (and justify) a better syntax, make a wiki page and propose it (and defend it). Then start coding.

• Is there a mailing list? No. Start one if you wish, and add a link on this wiki (and change this FAQ entry).

• Whats planned next for wydiwys? Text-only slides. These will be synthesized as HTML slides without images, and will probably heavily borrow code from Eric Wilhelm's Text::Slidez. These will be somewhat browser dependent, which breaks the wydiwys model, but they will be useful for quick hacks.

• I don't like white on dark blue Nav/Text slides. The appearance is controlled by the html template file and the style.css file that it calls. You can change the style.css file and change the appearance of all the slides that use it.

• Why doesn't wydiwys have its own website? Because I'm working on Server Sky, and wydiwys is a tool I made for doing that. If you want to set up a wydiwys page on Sourceforge or Freshmeat, be my guest. If you want to take over the wydiwys project, bless you. If you want to work on Server Sky, outstanding!!!

• I have a different question. Find the answer, and add it here.

• Meta-Answer: I wrote the first version of WYDIWYS because I needed it. I am sharing it with the world, under GPL2. That does not mean I am obligated to support your use of it. If you don't like the way it works, fix it. If you can't program, learn. If you can't learn, you shouldn't be making slide presentations. Go away.