It took me a long time to "get" lift. For about a year I looked at examples from time to time and tried out some basic stuff, but it just didn't click. I found the structure to be too messy. I still do actually. It seems that the documentation is also not well structured enough for getting started and I had to look at examples and Lift's source to understand how things work (thanks for putting sources in the Maven repo BTW, I wish everyone would do that).
After experimenting with Lift for about two days I think I get the basic idea and I've come to a better understanding about lift's structure by looking at the sources, I can now ignore the parts I don't like (Mapper being one, I use JPA instead) and use the parts that I do. The way the X(HT)ML processing, type-safe JavaScript/jQuery, Ajax and Comet work is just brilliant! PS. I'm working (on my spare time for now) on an Ajax & Comet heavy application that will hopefully also have a lot of runtime customization ability through OSGi. I haven't gotten to the OSGi part yet, because there's the hurdle of OSGifying all the jars I use and I want to get a good understanding of Lift before I start making things dynamic. But do you have any recommendations for OSGi framework/web container combinations to use with Lift? I have tried SpringSource dmServer (with the SpringSource tooling), but I don't like it much... Maybe plain Equinox + Jetty with the ScalaModules library would be a good combo? -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
