Waves Roadmap

If you have any ideas for enhancements you’d like to see, post them to the support group, and we’ll see if we can’t include them into the roadmap.

Version 0.8

Template Engines

• Haml and Sass
• Tenjin

Web Servers

• Support for other rack handlers in config
• Server config parameter: server :mongrel

Caching

• Better caching support

Controller Mixins

• Treat default controller impl as mixin. Ex: PrettyUrlController

Enhanced request mapping syntax

• Use actual lambdas and Proc#|. Ex:

with( resource ) do
  controller { ... } | view { |x| ... }
end

Filebase Support

• Default model adapter for Filebase.

Sample App

• Add login / session example.

Use Facets Libraries

• English: inflector
• Stick: for units (bytes, mbytes, etc.)

URI-based Filters

Right now you can only apply filters based on the path.

Version 0.9+

Magic Templates

• Port DrySQL code to build reflection layer
• Schema repository (generated or otherwise)
• Build “naked” HTML templates based on schema
• “Ext”ize magic templates

Testing Support

• Favor a testing framework? Which one?
• Best way to handle mock data sets?

Form Helpers

• Include basic set in default application?

Integration Tasks

• Next version of Sequel fixes primary key problem
• Next version of Rack fixes problem with Lint, plus app.new

Sessions

• Session storage: database and in-memory
• “Flash” session variable?

Undo / Redo Support

Inspired by Pascal’s Rails plugin. The idea would be to introduce a simple controller-DSL for defining actions and then their undo / redo actions. A variety of helpers would be made available for common scenarios, such as database updates to make it easier to implement.

mod_waves Apache Module

Inspired by another idea of Pascal’s, to take advantage of Waves’ thread-safety and code-reloading to create a PHP-like (or Tomcat-like) ability to drop an app into an apache directory and automatically load it. Development could proceed as in PHP or Tomcat (the Tomcat model requiring an explicit reload, but also being a little easier to implement with minimal blocking …).