Chapter 3 of Lift in Action is interesting because it reveals the elegance and simplicity of Lift's View-Snippet-Model and templating system, actually showing how one would approach a workflow, from View First design and designer deliverables to template nesting and menu building, and from application requirements to business object modeling. In the midst of all this, the active record-like Mapper "ORM" is presented in quite useful fashion. You can find the code (in my repo, which is fully compatible with Lift 2.5 and sbt 0.12) here (at Tag "chapter03"): https://github.com/victorkane/LiftInActionAuctionApp/tree/chapter03
For development, it is quite common to use the built in H2 database engine, and this is no exception. So while it's very cool I don't have to start installing "stacks" of base software just to run the code, how do I get to visualize the database, as I would with, say, Phpmyadmin for MySql? The Lift community continues to impress in this case by conveniently documenting two ways:
Here's what I did to get the Lift in Action tutorial auction application dev'ed up and running with Lift 2.5 and sbt 0.12.1:
[Edit: Since I started on this over the last couple of days, my work has been made considerably easier by the timely publication of Instant Lift Web Applications by Torsten Uhlmann. Congratulations on this up-to-date and pithy masterpiece! In any case I want to persevere on this front too.]
Why not indeed! Considering that I spent many years working with the Spring framework (plain old Java objects) on desktop apps years ago, as a lightweight alternative to Enterprise Java, things might start looking quite powerful and familiar, and yet streamlined and better. Things might calm down a little and I might get a productive, solid environment to rock on!
So I'm documenting how I got up and running now with the latest versions of Lift and the Scala IDE for Eclipse, etc., on a souped up MacBook Air, it's pretty sui generis but it might help someone, certainly myself if I come back to things after a stint at something else.
The task on Pivotal Tracker (love using it) says "Learn CoffeeScript". The project this chore forms a part of is really important to me, and while several important projects I am working on still deserve to be based on Drupal, others deserve a new kind of architecture, something wildly new and at the same time something going back to my roots (learning C with Kernighan and Ritchie's The C Programming Language enthralled with the hiding of detail overload prevalent in the Z80 and 8086 assembler languages I had been using) in the eighties (Turbo C...).