That is a typo. The Nil on the end shouldn't be there. Then the "::" operator should work correctly. I'll update the book.
Derek On Sun, Mar 8, 2009 at 6:21 PM, James Matlik <[email protected]> wrote: > Hello Derek, > > I fully understand having a day job and prioritizing side projects > accordingly. I also appreciate the work you, Marius and Tyler have done > with the book. I have found it very helpful in my playing over the weekend. > > It looks like there are two versions of the getting started doc available. > The version on the liftweb.net home page is the newer, updated version > while an older version is available on the wiki main page. > > Also, I've found a few typos (I think) in the Exploring Lift book. I am > not overly familiar with git, so it is very possible I've pulled an older > version of that as well. I got there, again, via the link on the wiki main > page. Using git-show, it looks like the last commit was: > > Author: Derek Chen-Becker <[email protected]> > Date: Fri Mar 6 16:13:21 2009 -0700 > Minor corrections and formatting on Actors section. > > I believe the typo is in listing 6.36, shown below. > > val menus = ... Menu(Loc(...)) :: Transaction.menus :: Nil > LiftRules.setSiteMap(SiteMap(menus : _*)) > > This should be using the ::: operator instead of :: because the CRUDify > menus are returned as Lists. Using the :: would assign a List[Product] > instead of the required Seq[Menu]. > > It would be nice if there were some more detail surrounding the CRUDify > feature, particularly in relation to foreign keys. I must have spent 3 > hours trying to figure out how to create a selector box on the edit/create > pages, as well as output human readable output on the display pages. It > required a combination of digging into the lift-webkit source and querying > on google with just the right text. > > Thanks, > James > > On Sun, Mar 8, 2009 at 5:47 PM, Derek Chen-Becker > <[email protected]>wrote: > - Show quoted text - > >> I'm addressing some of your notes/questions below >> >> On Sat, Mar 7, 2009 at 6:18 PM, Matlik <[email protected]> wrote: >> >>> - Simply copying and pasting the commands into the command line can >>> be problematic. For example, when I tried to start the 'todo' >>> tutorial, I ended up with the following. Notice that most of the >>> pasted text has a space between each letter, and the hyphen character >>> is not the ascii '-' but the unicode '-' (appears longer on my >>> system). >>> >> >> That's odd. I just tested the most recent version that's up on the website >> with both Acroread and Evince and both of them copy text fine. The older >> version of the PDF had incorrect fonts set which would have caused the >> problem you're seeing, so could you please make sure that you have the >> latest one? >> >>> >>> >>> - In general, I think it is good practice to have such documentation >>> online in HTML format, particularly the quick-start and entry level >>> docs. >> >> >> I agree. I'll work on putting up both an HTML and PDF version. >> >> >>> >>> >>> - You may want to consider using page space more economically within >>> the PDF doc. There is a lot of dead white space around the text. >>> This can be useful for jotting down notes, but it also requires more >>> paper when printing. Using more of the white space is good for both >>> economical and ecological greenness. Granted, the StartingWithLift.pdf >>> document isn't huge, but every little bit helps. >> >> >> I wonder if this is the same issue with the older PDF, since I >> significantly adjusted margins on the new one. >> >>> >>> 4. Is there some reason why the wiki cannot provide the "In Progress >>> Book" in PDF or HTML format? >> >> >> Yes. I'm having an issue properly exporting PDF and HTML from LyX in an >> automated fashion so we would have to manually build nightlies at this >> point. This is something I've been working on for a while, but please >> understand that setting up this infrastructure is very low on my priority >> list. Tyler, Marius and I have day jobs, do a lot of work on Lift proper, >> and are working hard to get the book ship-shape, so it didn't seem >> unreasonable to have people build it themselves. Stay tuned for more info on >> this front, and I'll put a current PDF on the github site today. >> >> > The long and the short of it is I felt like I needed to dig and jump >> >>> through hoops to get to the best documentation available. All the >>> information is there; it just isn't easily (or obviously) accessible >>> with a few mouse clicks from the liftweb.net home page. I am a >>> persistent guy, but I do like my immediate gratification. >>> >> >> Please let me know if you continue to have issues with the getting started >> docs and I'll work on the rest of the issues I discussed here. >> >> Derek >> >> >> >> > - Show quoted text - > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
