--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
You can also checkout my book here (chapter 1 is free):
http://manning.com/perrett/
</shameless_self_plug>
Cheers, Tim
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
Cheers, Tim
The Exploring lift book (below) is a great reference for first steps
on any feature, but gets in to code pretty fast, which sounds like it
may not be what you're looking for.
Paul
> To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
The book is split up into 3 sections:
1. introduction
2. tutorial application
3. In depth reference
The chapters you have likely read so far are from section 1. So, to that end, hang in there, it will get more in depth as the chapters progress. Its important to start easy so that everyone can follow along and has the same base.
Cheers, Tim
I didn't mean to slight the book at all :-)
Quite the contrary, I thought the background quite a good intro for a
newbie. As I only have the MEAP so far (chapters 1-5) I can only
comment on that, but what I have seems to be a higher text-to-code
ratio than the Exploring Lift book. The later however is currently the
first place I go to look for detailed information on a feature when
I'm ready for it. Partly because it has clickable links from the TOC
and the manning book does not.
Paul
No offence taken - its all a work in progress as far as im concerned :-)
Generally speaking I expect there to be a lot more text than code. As its an "in action" book, I like to take the time to explain everything fully and in enough detail that someone new to Lift will get what is being discussed. Subsequently, LiA is going to be a much, much bigger book than TDGL in terms of pages. Moreover, the way I speak is generally the way I write so tends to be a slightly more verbose vernacular :-)
If you have additional feedback, such as the ToC thing (that should be an easy fix for manning) please raise it in the author forum and we will try to do something about it.
Cheers, Tim