[Lift] Re: a plea for documentation
Hi, Actually my mind keeps flipping between SEAM and Liftweb, for months. Today my feeling is I should focus on the JPA for my project in Java using seam generate, then to take the JPA across to the Liftweb environment and to program my website in Liftweb. Since my database is big, nearly 100 tables in mysql. Of course torn between doing it completely in SEAM or using JPA/Liftweb. The great thing about Liftweb is the community is going good now - and I guess my quesitons will get answered, also I would tend to contribute back to the community. As opposed to completely doing it in SEAM, sure there's documentation, but I wouldn't be contributing back. Also I like Scala and I like where Liftweb is going. Anyway, just thoughts, Philip On Nov 30, 4:34 pm, philip [EMAIL PROTECTED] wrote: Hi, I also agree with David that I'm very excited to use Lift and have great enthusiasm about it, and I play around with it now and then, but I'm reluctant to use it on my big project until my understanding is at a point of strong confidence. So like a weight lifter, I'm in training. When I compare it to SEAM, SEAM is also complex but there is so much documentation I won't get stuck so I'm willing to use it on the big project. Thanks, Philip On Nov 27, 10:15 am, David Stein [EMAIL PROTECTED] wrote: On Wed, Nov 26, 2008 at 3:10 PM, David Pollak [EMAIL PROTECTED] wrote: If you've been following the threads then you've seen that I'm devoting the next 4 months to Lift 1.0 and documentation. What more do you want? What are you planning to contribute to the process other than complaining that it's somehow not enough? Oops. My apologies for being so irritable. Funny, my girlfriend has also been complaining about me this week, so maybe I'm just oblivious to how I come across! I definitely didn't mean to imply that we need more from the committers, per se, but I might suggest that a highly effective use of their time would be to document the API before writing books, which could take months. Documenting the API is probably 15 hours tops, and with 6-12 committers it's not a lot overall. With the API documented, many of us bewildered folks on the sidelines could step up and write tutorials and sample projects. I have a little egg on my face because I don't think I gave a thorough read-through of the book. I started looking at a few chapters a while ago, but they were more outlines at the time. Somehow I missed the chapters which are actually pretty comprehensive, like the one on JPA. Very much looking forward to this! Sorry again, and please ignore me as necessary, DS --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: a plea for documentation
http://github.com/tjweir/liftbook/tree/master See earlier posts for details. Derek On Sun, Nov 30, 2008 at 7:33 PM, Oscar Picasso [EMAIL PROTECTED]wrote: Which book are you talking about? I didn't know that they were already chapters of a lift book we could read. On Wed, Nov 26, 2008 at 9:15 PM, David Stein [EMAIL PROTECTED] wrote: I started looking at a few chapters a while ago, but they were more outlines at the time. Somehow I missed the chapters which are actually pretty comprehensive, like the one on JPA. Very much looking forward to this! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: a plea for documentation
Hi, I also agree with David that I'm very excited to use Lift and have great enthusiasm about it, and I play around with it now and then, but I'm reluctant to use it on my big project until my understanding is at a point of strong confidence. So like a weight lifter, I'm in training. When I compare it to SEAM, SEAM is also complex but there is so much documentation I won't get stuck so I'm willing to use it on the big project. Thanks, Philip On Nov 27, 10:15 am, David Stein [EMAIL PROTECTED] wrote: On Wed, Nov 26, 2008 at 3:10 PM, David Pollak [EMAIL PROTECTED] wrote: If you've been following the threads then you've seen that I'm devoting the next 4 months to Lift 1.0 and documentation. What more do you want? What are you planning to contribute to the process other than complaining that it's somehow not enough? Oops. My apologies for being so irritable. Funny, my girlfriend has also been complaining about me this week, so maybe I'm just oblivious to how I come across! I definitely didn't mean to imply that we need more from the committers, per se, but I might suggest that a highly effective use of their time would be to document the API before writing books, which could take months. Documenting the API is probably 15 hours tops, and with 6-12 committers it's not a lot overall. With the API documented, many of us bewildered folks on the sidelines could step up and write tutorials and sample projects. I have a little egg on my face because I don't think I gave a thorough read-through of the book. I started looking at a few chapters a while ago, but they were more outlines at the time. Somehow I missed the chapters which are actually pretty comprehensive, like the one on JPA. Very much looking forward to this! Sorry again, and please ignore me as necessary, DS --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: a plea for documentation
Which book are you talking about? I didn't know that they were already chapters of a lift book we could read. On Wed, Nov 26, 2008 at 9:15 PM, David Stein [EMAIL PROTECTED] wrote: I started looking at a few chapters a while ago, but they were more outlines at the time. Somehow I missed the chapters which are actually pretty comprehensive, like the one on JPA. Very much looking forward to this! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: a plea for documentation
On Wed, Nov 26, 2008 at 11:22 AM, David Pollak [EMAIL PROTECTED] wrote: David, We are actively working on documentation. Please see a number of recent posts on the subject. David Yes, I've been following those posts. Having a couple of books out will be great. Books take time to write though, certainly much more time than it takes to update the Scaladocs. What do you guys, the committers, think about putting your book efforts on hold until the API is documented? At the very least, I'd encourage you guys to not submit code from now on which isn't documented. It's just too much work to go back later and add it, as we all know from our own experiences no doubt. DS --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
