Having gone through Rails, the Google App Engine with Django, and web2py over the last four years, I have seen it all as far as learning new frameworks goes, and I have posted a few ideas on that subject both here and on the book group.
For those of us spoiled by the wealth of learning material on Rails, and to a lesser degree Django and web2py, all I can say is: 'Lift is a new framework, and a sophisticated one at that, which uses a new language derived from a convoluted one, and is at a relatively early stage of development, so therefore the designers are forging ahead to completion of the foundation, and thus there are few who can devote the time to creating the documentation we newcomers need.' My post on the book group defined the three classes of useful documents to be the Guidebook, the Encyclopedia, and the Cookbook. My role for the wiki is to hold Cookbook recipes which answer the most common 'how to' questions we encounter when building a website. In my personal learning quest, I am extending the 'ToDo' app by adding pieces of functionality, like many-to-many tagging, date manipulation, deletion, an admin interface, etc. As I come across solutions or questions, I post those on the group in order to help others and to get improvements and refinements from the members. David is right... Lift and Scala together are taking web applications to a whole new level of performance, so naturally it will take a little time to make things happen. By the way, today my copies of David's and Martin's Scala books arrived, and I urge all to purchase them yourselves! On Jun 1, 3:35 pm, "Charles F. Munat" <c...@munat.com> wrote: > Hi, Xavi, > > One of my tasks is to come up with a good organization for the wiki and > a site map, as well as a list of things we'd like to add to it. > Unfortunately, with the coming Scala/Liftoff and OSB conferences, I've > been swamped with other things. But I am working on it, albeit slowly. > If you have any specific recommendations, please post them. > > Thanks! > > Chas. > > Xavi Ramirez wrote: > > Hello, > > > I'm a bit confused about the future of the lift wiki. What's the end > > goal? In an ideal world is it supposed to be the main repository of > > lift knowledge, or just another documentation source? > > > I personally feel that having one repository of knowledge is much more > > noob friendly. Currently new members have to navigate through started > > guides, books, e-mail threads, scala docs, and personal blogs to find > > relative information. Though the get started guided and book provide > > a good introduction, it's hard to progress from novice to intermediate > > with these fragmented resources. > > > Thanks, > > Xavi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
