Edit: I just learned that dotcloud supports Opa! So I've pushed OpaDo and you can see a demo here http://opado-tristan.sloughter.dotcloud.com/

I wanted something quick and simple to do in Opa to give it a try so I decided to implement the TodoMVC example that has been redone in almost all Javascript frameworks, https://github.com/addyosmani/todomvc.

The code can be found on GitHub here: https://github.com/tsloughter/OpaDo

Opa is unique in that it is not only a new language but also a new web server and database. While Opa's page pushes the idea that its for the cloud and its easy distribution, I found the nicest part being the static typing and no need for Javascript.

The functions below handle interactions with the Todo items. It somewhat reminds me of Lift but taken even farther.

/** * {1 User interface} */  
update_counts() =  
  num_done = Dom.length(Dom.select_class("done"))  
  total = Dom.length(Dom.select_class("todo"))  
  do Dom.set_text(#number_done, Int.to_string(num_done))  
  Dom.set_text(#number_left, Int.to_string(total - num_done))  
make_done(id: string) =  
  do if Dom.is_checked(Dom.select_inside(#{id}, Dom.select_raw("input"))) then Dom.add_class(#{id}, "done")  
    Dom.remove_class(#{id}, "done")  
remove_item(id: string) =  
  do Dom.remove(#{id})  
remove_all_done() =  
  do Dom.remove(Dom.select_parent_one(Dom.select_class("done")))  
add_todo(x: string) =  
  id = Random.string(8)  
  li_id = Random.string(8)  
  line = <li id={ li_id }><div class="todo" id={ id }> <div class="display"> <input class="check" type="checkbox" onclick={_ -> make_done(id) } /> <div class="todo_content">{ x }</div> <span class="todo_destroy" onclick={_ -> remove_item(li_id) }></span> </div> <div class="edit"> <input class="todo-input" type="text" value="" /> </div> </div></li>  
  do Dom.transform([#todo_list +<- line ])  
  do Dom.scroll_to_bottom(#todo_list)  
  do Dom.set_value(#new_todo, "")  

It is unique in combining the HTML into the language itself. Some have argued against this but when it works well it makes perfect sense. I don't want to have to convert a designers HTML into some other representation! And being able to have type checked dynamic functionality within the HTML is a boon. Even with just this simple program, I found the usefulness of the type checker outstanding.

Next we have the main outline of the page and the entry part for the program.

start() =  
  <div id="todoapp"> <div class="title"> <h1>Todos</h1> </div>  
    <div class="content"> <div id=#create_todo> <input id=#new_todo placeholder="What needs to be done?" type="text" onnewline={_ -> add_todo(Dom.get_value(#new_todo)) } /> </div>  
      <div id=#todos> <ul id=#todo_list></ul> </div>  
      <div id="todo_stats"> <span class="todo_count"> <span id=#number_left class="number">0</span> <span class="word">items</span> left. </span> <span class="todo_clear"> <a href="#" onclick={_ -> remove_all_done() }> Clear <span id=#number_done class="number-done">0</span> completed <span class="word-done">items</span> </a> </span> </div>  
/** * {1 Application} */  
/** * Main entry point. */  
server = Server.one_page_bundle("Todo",  
       ["resources/todos.css"], start)

It won't be able to replace my use of Erlang for the backend and Coffeescript for the frontend, but it looks very promising.

I'll be extending this example to include persistence, sessions and users and will add posts as I complete those.