====== TODO ======

Close-range targets:
  * Allow developer to configure locales supported by the web application - DONE
  * Change configuration file settings.properties back to PHP-based code - DONE
  * StringUtils have to comply with security requirements as stated - DONE
  * Write code for view redirection - DONE
  * Further clarify and separate object responsibilities ((That's internal to Mivec - no changes required even if Mivec evolves))
  * Complete XML-based action-to-view mapping configuration - DONE((Implementation using PHP DOMXML extension and [[http://www.engageinteractive.com/domit|DOMIT! DOMXML library]] had been completed))
  * Complete PHP code-based action-to-view mapping configuration - DONE
  * Security flaws exploiting and fixing
  * PHP 5 compatibility - I'm not sure if my codes are compatible, as I'm still using PHP 4 for development
  * Validation error messages on Actions should allow internationalization too - DONE

Long-range targets:
  * Make XML-based action-to-view mapping configuration "compile" a PHP code-based configuration to prevent overhead on parsing XML
  * Write code for securing the application in unified way with pluggable authentication modules - this was implemented during a recent freelance project. Coming soon...
  * Improve compatibility with IIS ((Again, this was from the freelance project described above.))
  * Make a docbook manual for offline viewing

By the time all long-range targets are completed, Mivec Framework should be marked as 1.0 final.