Aside: I think the preferred abbreviation for Programming in Scala is PinS, not PiS.
Just fyi, --j On Fri, Apr 3, 2009 at 4:15 PM, Timothy Perrett <[email protected]>wrote: > > > My advice, if your generally / vaugly familiar with Scala from reading PiS > (that truly is a very unfortunate acronym!) just dive into making a lift > app, then go from there. > > One of the best things about Lift is the community - if you have questions, > chances are its either already in the group archive from one of our many > debates, or in the lift book, or if not, just ask on the mailing list and > someone will no doubt help you right quick! > > Good luck! > > Tim > > > On 03/04/2009 23:01, "Charles F. Munat" <[email protected]> wrote: > > > > > I'd suggest that you start working in Lift, then when you encounter > > something that doesn't make sense to you, refer to the PiS book > > (unfortunate acronym). It helps if you have the PDF version because you > > can search. The index is OK, but often insufficient. > > > > This is the approach I used to get started, though eventually I went > > back and read most of the book sequentially (I still have a couple of > > chapters to go). Take a look also at DPP's book and the online Lift > > book, both easily searchable. > > > > If you want to jump ahead in the book, I'd recommend the following: > > > > 15: Case Classes and Pattern Matching > > 16: Working with Lists > > 23: For Expressions Revisited > > > > Lists, for expressions, case classes, and pattern matching are used *all > > over the place* in Lift. You can't be too familiar with these. > > > > Then maybe: > > > > 19: Type Parameterization > > 21: Implicit Conversions and Parameters > > > > You don't need to understand those thoroughly, but having some > > familiarity with them will help with debugging and understanding what > > the heck is going on. > > > > If you have time, you could also read the following to fill in a few > gaps: > > > > 22: Implementing Lists > > 26: Working with XML > > > > And if you're going to use Comet, you should probably read: > > > > 30: Actors and Concurrency > > > > But again, you can dive in and then reference these chapters as > necessary. > > > > Chas. > > > > lmorroni wrote: > >> Hi, > >> I am a Java programmer that is interested in learning Lift. I have > >> just finished the first six chapters of Programming in Scala. I > >> wonder what people's opinions are on how much of this book I need to > >> read before diving into Lift. I attempted to dive into Lift without > >> reading anything on Scala and that worked great until I wanted to > >> start reviewing the Lift libraries :) > >> Maybe there are some chapters in this book that I can skip? I think > >> the book is really well written and I have followed everything so > >> far. I just would rather get rolling on Lift sooner rather than > >> later. > >> Larry > >> > >>> > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
