Thanks, Jim. Will do. Chas.
Jim Lloyd wrote: > Chas, > > This is my first post to this group. I'm a friend of David's who has > been meaning to learn Scala and Lift for months based on David's praise > for Scala and his obvious joy in working on Lift. I finally found some > time to dive into Scala and I love it. I'm now trying to find time to > dive into Lift, and I too am wishing for more documentation. This means > that I probably won't be able to answer any of your questions, but that > I will be keenly interested in anything you produce, including all of > your questions, whether they get quick answers or not. I recommend that > you post your questions to this list. It might be worthwhile to identify > your questions with some prefix in the subject like "DocQ: ...", but I > think it better that you don't fragment the list. > > Jim > > On Sun, Aug 31, 2008 at 9:09 PM, Charles F. Munat <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > OK, I have an idea and I think I've narrowed it down to something I can > fit into my schedule. I'll work on it and hopefully will have something > in the next week or so. > > Chas. > > Charles F. Munat wrote: > > Actually, after reviewing my schedule and reconsidering the amount of > > time required, I'm probably biting off more than I can chew. Also, I > > understand that you're hard at work on a manual. Any idea when > and how > > that will be available? > > > > Chas. > > > > David Pollak wrote: > >> Charles, > >> > >> I am unclear what you are asking for. The Lift list is open to > all for > >> posting. If you've got questions, by all means, post them. > There are > >> lots of folks who are helpful and knowledgeable on the list. > >> > >> One of the reasons that the Lift list and the Lift community are > >> populated with such awesome and helpful people is the attitude > and tone > >> on the list and in the community. We are here to welcome folks > into the > >> community, help them understand, and build excellent things. > >> > >> As you produce stuff and contribute to the Lift community, I > expect that > >> you'll get increasingly positive responses to your work and your > questions. > >> > >> Thanks, > >> > >> David > >> > >> On Sat, Aug 30, 2008 at 3:39 PM, Charles F. Munat > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > >> > >> > >> Lift desperately needs better documentation prior to the > release of > >> version 1.0. Despite the efforts of many to create > documentation, there > >> is still no clear path to Lift adoption for the majority of web > >> developers out there. At least, none that I can find. > >> > >> I am willing to write Lift documentation, but I don't > understand Lift > >> well enough to do so. I am also unwilling to waste hours > searching for > >> answers to questions -- that is simply not a worthwhile use > of my time. > >> > >> I am willing to devote an hour a day for the month of > September to > >> getting a good start on a non-wiki documentation site. What > I need is > >> permission to post questions to the mailing list. > >> > >> The reason I need permission is because when I have a > question, I want > >> to be able to post it and get a rapid reply. I do not have > several hours > >> to spend on each question searching through the wiki, the > mailing list, > >> and the example code trying to figure out if it has been > answered > >> before. That is not an efficient use of my time, and I have > very little > >> time. > >> > >> This may result in a lot of traffic to the list. I'll have a > lot of > >> questions. So I suggest the creation of a separate > "documentation" > >> mailing list. And if some of the best coders for Lift were > on that list > >> and agreed to try to respond quickly, then I can learn Lift > quickly (a > >> benefit to me) and I can write the documentation quickly (a > benefit to > >> the community and new users). Win-win. > >> > >> I am even willing to give my phone number to select members > of the > >> community so that they can call me with answers to questions > if that's > >> faster than writing an email. This is about getting > documentation done, > >> quickly and accurately. The "if you build it, documentation > will come" > >> method does not work in real life. > >> > >> It would also be nice if folks on the list would read the > documentation > >> and send corrections, suggestions, comments, etc. to me > (maybe via the > >> documentation mailing list). > >> > >> I've been out of the loop for a couple of months, so maybe > some of this > >> already exists. If so, please enlighten me. > >> > >> Does the Lift community think this would be valuable? I can > tell you now > >> that barring some sort of effort along these lines, it is > not looking > >> like I will ever have the time to make Lift my primary > development > >> method, and that would be a shame. And if I'm having that > problem, I > >> suspect that many others are as well. Great documentation = > rapid > >> adoption. Poor documentation = possibly, consignment to the > great heap > >> of good ideas that failed. > >> > >> Feedback? > >> > >> Charles F. Munat > >> Seattle > >> > >> > >> > >> > >> > >> -- > >> Lift, the simply functional web framework http://liftweb.net > >> Collaborative Task Management http://much4.us > >> Follow me: http://twitter.com/dpp > >> Git some: http://github.com/dpp > >> > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
