TODO

• If someone starts Whippet inside a wp-content, but that wp-content is inside a WordPress install, should Whippet start it as a standalone folder or an ordinary install? Or, perhaps, ask?
  • One option: start as root if there's no whippet-wp-config, or standalone if there is.
• Windows support. For this to work minimally, and within a command prompt, we would need:
  • A batch file to start Whippet
  • To disable or replace all the functionality that uses Linux commands (wget, grep, etc)
  • To test and make sure PHP functions like popen work properly under Windows
  • Most Windows users would probably prefer a GUI environment and an installer that packages PHP
• SQLite support for dev work, and/or ability to magically restore and use an sqldump
• Show output as plugins being loaded (I think this might be impossible to do robustly)
• Remove all the echo calls from whippet.php and use whippet::message instead
• Refactor whippet.php, moving some stuff into other files where that's sensible (eg options parsing/help/checking), making it OO (and DRYer), and paying particular attention to all the filenames and paths that are floating around. The file was tiny to begin with, but is now rather large and unwieldy.
• We should check that grep is available before attempting to run it to gather callback data
• Before trying to get a WordPress, check that wget, tar, etc, actually exist so whippet can moan more meaningfully if they don't.
• Multisite support needs more testing, and only currently works for folder-based sites.
• Test with complicated plugins like BuddyPress