Well, this is an apt discussion at this point in time I feel. One of
the weakness of the Lift Project is really the sparse documentation,
as well as the rapid cycle of development obsoleting virtually many of
the slightly older code out there.
I don't mind contributing my time improving the
Well for the current information the places to go are
http://scala-tools.org/mvnsites-snapshots/liftweb/index.html and
http://wiki.github.com/dpp/liftweb if that will help you.
On Dec 21, 7:47 pm, johncch john...@gmail.com wrote:
Well, this is an apt discussion at this point in time I feel. One
1.0 is the last official release that was not a milestone or snapshot
- thus, they are the primary api docs right now until we release 2.0
(that is, what was being called 1.1 is being renamed to 2.0). API docs
are a process issue, and handled as part of our build process - they
will always live
Hi Tim,
Thanks for your reply.
1.0 is the last official release that was not a milestone or snapshot
- thus, they are the primary api docs right now until we release 2.0
(that is, what was being called 1.1 is being renamed to 2.0). API docs
are a process issue, and handled as part of our
To give the benefit of doubt to people who use Lift knowing that is
closed to commiting they may think the same about the documentation. I
have added a bit but I've more thrown up a few pages and figured
someone with more knowledge would flesh them out.
On Dec 20, 8:47 pm, Timothy Perrett
I really don't think thats the issue - Lift is not closed to committing... if
that were the case, David would never have recruited us onto the team ;-)
95% of all OSS projects i've ever come across have the same policy when it
comes to wikis etc... they are organic, community driven beasts.
Why not improve the existing wiki on github?
Or fork the book and make improvements that way?
I'm not opposed to additional resources, but why create another place
where docs may or not be out of date?
I think that Lift is still at the point where one location of docs is
better.
My opinion.
Definitely! I would like one location for everything, but I believe that
the current situation is not like that.
- there two API docs 1.0 and 1.1, the latter is hard to find
- there's liftweb.net (a little bit out-dated)
- there's the Wiki
- there's David's Blog (that has some unique
Why not help make the wiki the one location?
On Dec 19, 8:16 am, Hannes hannes.flo...@gmx.li wrote:
Definitely! I would like one location for everything, but I believe that
the current situation is not like that.
- there two API docs 1.0 and 1.1, the latter is hard to find
- there's
+1 for the wiki site being the official Lift documentation place. I'm
not sure if github should be the wiki container ... IMHO the
official Lift website should be.
Br's,
Marius
On Dec 19, 3:39 pm, TylerWeir tyler.w...@gmail.com wrote:
Why not help make the wiki the one location?
On Dec 19,
My suggestion is to get Programming in Scala, it explains the basics
more than the others. Davids book and the rest are great but written
for existing programmers. I also am learning not being a coder for
years so I know how you feel.
On Dec 16, 3:05 am, Daniel who.reads.th...@gmail.com wrote:
And from there, my suggestion would be to experiment with existing sample
Lift applications such as those in http://github.com/dpp/lift-samples to get
the feel for Lift from working code.
alex
On Tue, Dec 15, 2009 at 12:49 PM, Randinn rand...@gmail.com wrote:
My suggestion is to get
I also suggest possibly looking at http://www.scala-lang.org/node/104
and http://www.naildrivin5.com/scalatour might help a bit.
Also working on the tuts at http://www.simplyscala.com/ are nice as
you can see them in action.
On Dec 16, 3:05 am, Daniel who.reads.th...@gmail.com wrote:
Hey,
I'm
I'm sorry I didn't reply to this earlier. Yes, I am looking for docs
so I can keep my newbie questions to a minimum. I know I can ask
anything here but I'd rather see you all moving Lift forward then
dealing with my simplistic questions.
On Dec 8, 10:50 am, Timothy Perrett timo...@getintheloop.eu
Something like This Week in Lift master would help.
http://suitmymind.com/blog/2009/01/22/this-week-in-edge-cappuccino/
On Dec 7, 5:55 am, Timothy Perrett timo...@getintheloop.eu wrote:
Randinn,
This is already slated for 1.1/2.0 release... dont worry we are getting to it
:-)
Cheers, Tim
Great! Thank you for the heads-up.
On Dec 7, 9:55 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Randinn,
This is already slated for 1.1/2.0 release... dont worry we are getting to it
:-)
Cheers, Tim
On 7 Dec 2009, at 08:09, Randinn wrote:
I am writing here to get a dialog going
A pretty good idea, a commiter makes a change or adds a feature then
post about it on a blog, that would make it easier for people to go
through and later on to be able to update the documentation.
On Dec 7, 10:53 pm, TylerWeir tyler.w...@gmail.com wrote:
Something like This Week in Lift master
You are aware that our maven site automatically generates a list of
changes in a given version? If any commiters adds something then they
updates the changes.xml for just this reason.
Take a look at that and see if it is the kind of thing you would like?
I'm not saying it's everything you
On Wed, May 13, 2009 at 1:36 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
I'm still working on S.scala documentation. I've put some examples in, but
they feel really contrived. Does someone have some real-world use cases for
highLevelSessionDispatch and/or sessionRewriter?
I used each
Cool, I hadn't thought of that. Also, any objections to rearranging some of
the code while I'm updating docs? There are two S.loc methods that are far
apart in the file, for instance.
Derek
On Wed, May 13, 2009 at 2:40 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, May 13,
On Wed, May 13, 2009 at 2:00 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
Cool, I hadn't thought of that. Also, any objections to rearranging some of
the code while I'm updating docs? There are two S.loc methods that are far
apart in the file, for instance.
Have a field day!
Derek
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
Rob Dickens wrote:
Maybe good documentation starts with good documentation of the source
code itself. How many people really understand what even the
initialisation stuff does, I wonder; complicated and undocumented
enough for me to give up, anyway (which is saying something).
Rob,
Do
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
24 matches
Mail list logo
