I had a quick conversation with Derek over IM. We're in the process of putting together an outline and schedule for docs.
I'll put together a new post as soon as I can (hoping tonight). On Sep 15, 4:44 pm, David Pollak <[EMAIL PROTECTED]> wrote: > Derek, > > We'd love to have you help out. Perhaps Tyler can jump in here.... > > Thanks, > > David > > Derek Chen-Becker wrote: > > Amazing how far it's come since 0.1 last year. Once you and Marius are > > done cleaning things up maybe I can help with the Scaladocs a little. > > I know there's also quite a bit of catch-up on the Wiki to be done as > > well. In particular, updating the LiftTags, Cheat Sheet (maybe should > > be broken into chapters) and the howtos would be nice to make sure > > we're not duplicating things as well as providing coherent > > documentation for people who want to use it. As much as I love having > > a Wiki so that things can evolve quickly, I think it's important to > > have a polished set of core documentation that the rest of the Wiki > > can reference. > > > Derek > > > On Mon, Sep 15, 2008 at 2:27 PM, David Pollak <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > Derek Chen-Becker wrote: > >> So will that be a 1.0 or 0.10 release at that point? Just curious :) > > Once we get the API situation sorted out, we'll release 0.10. The > > next release will be RC1 about a month later. Then we'll go > > through RC cycles until we're happy with Lift, the ScalaDocs, the > > online documentation, the installer, etc. > > >> Derek > > >> On Mon, Sep 15, 2008 at 2:21 PM, David Pollak > >> <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> wrote: > > >> On Mon, Sep 8, 2008 at 11:23 PM, Jorge Ortiz > >> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > >> The Lift APIs are undergoing some short-term trauma in > >> expectation of > >> long-term stability and backwards compatibility after the > >> 1.0 release. > > >> The Lift APIs were fairly stable from 0.5-0.9. Marius and I > >> have been going through and cleaning, scrubbing and polishing > >> the APIs. Please expect them to stabilize by the end of October. > > >> Thanks, > > >> David > > >> On Mon, Sep 8, 2008 at 10:23 PM, Alan M > >> <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> wrote: > > >> > Thanks a lot, that clears things up considerably. Now > >> my only concern > >> > is how much stuff has changed so quickly.. But such is > >> life on the > >> > edge eh? > > >> > As for the other stuff, that probably belongs in > >> another thread.. my > >> > bad in mixing.. > > >> > Alan > > >> > On Sep 5, 2:51 pm, "David Pollak" > >> <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> > >> > wrote: > >> >> On Fri, Sep 5, 2008 at 2:23 PM, Alan M > >> <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> wrote: > > >> >> > As far as I can tell the example doesn't compile > >> with any version of > >> >> > Lift. ResponseIt is gone in .10 and > >> SimpleController exists only in . > >> >> > 10. > > >> >> ResponseIt is now LiftResponse > > >> >> Here's a pretty simple set of REST services: > > >> >> object RestAPI extends XMLApiHelper { > >> >> val logger: Logger = Logger.getLogger("us.esme.api") > > >> >> def dispatch: LiftRules.DispatchPf = { > >> >> case RequestState("api" :: "get_msgs" :: Nil, "", > >> GetRequest) => getMsgs > >> >> } > > >> >> def getMsgs(): LiftResponse = { > >> >> val r: Can[NodeSeq] = > >> >> for (user <- calcUser ?~ "User not found"; > >> >> val lst = > >> Mailbox.mostRecentMessagesFor(user.id <http://user.id>, 40)) > >> >> yield lst.flatMap{ case (msg, why) => > >> msg.toXml % why.attr} > > >> >> r > >> >> } > > >> >> } > > >> >> > So I'm trying to create a basic web service based on > >> the example, any > >> >> > advice on how to proceed? What is the replacement > >> for ResponseIt or > >> >> > what should I use instead of SimpleController? > > >> >> > To be honest I'm having a hell of a time so far. It > >> seems that Lift > >> >> > is very much tailored towards standard webapps with > >> templated pages > >> >> > and O/R mapped data from databases, etc... > > >> >> Lift does REST and web services in a very simple way. > >> It's simpler than any > >> >> framework I've used. > > >> >> Lift also does standard XHTML, Ajax, and Comet in very > >> simple, manageable > >> >> ways. > > >> >> > But in my case, I'm getting > >> >> > my data from other sources and in particular I'm > >> getting my user > >> >> > authentication and authorization data from an > >> unusual source. So it's > >> >> > been particularly hard for me to know when I should > >> use the standard > >> >> > Lift stuff and when I should/can go it on my own. > >> Which may explain > >> >> > why I'm so highly interested in > >> using/referencing/blatantly copying > >> >> > the Web Service example on the wiki. > > >> >> > Also, just an observation, it seems that Lift is > >> trying to be like > >> >> > Rails.. IE handle every layer by itself. > > >> >> It has solutions for most layers because in my > >> experience, most of the other > >> >> solutions don't meet my needs. Most of the > >> Java-derived stuff is amazingly > >> >> heavy weight and requires too much hidden state, XML > >> files, etc. I've tried > >> >> to make Lift as much as possible oriented to the > >> strengths of Scala and to > >> >> getting common things done simply, easily, and securely. > > >> >> > I'm not sure that's a good > >> >> > thing.. such as it's own O/R tools, > > >> >> You're seeing on another thread just how hard it is to > >> use JPA. I don't > >> >> know if that's JPA, JPA with Scala or what, but it's > >> not as easy as Lift's > >> >> OR mapper and Lift's OR mapper comes with a lot of > >> side benefits as it's > >> >> integrated into common REST and HTML tasks. Also, > >> Lift's OR Mapper is > >> >> optional. If you want to use JPA, go right ahead. > > >> >> > it's own authentication stuff, > > >> >> Which is optional... except how many web apps don't > >> have authentication? > >> >> So, you can roll your own or use the Lift stuff. Your > >> choice. > > >> >> > it's own templating (well wicket modified/adapted) > > >> >> It's Wicket inspired, not adapted and there are very > >> compelling reasons for > >> >> Lift's templating engine. Please read the View > > >> First<http://liftweb.net/index.php/Lift_View_First>document. > >> Lift is > >> >> not front-controller. > > >> >> > etc.. Correct me > >> >> > if I'm wrong. Anyway.. it's early days yet.. maybe > >> they'll split off. > > >> >> There are half a dozen Lift sub-packages and there > >> will be more divisions of > >> >> Lift. But at the end of the day, Lift gives me most > >> of the common things I > >> >> do when I build web apps. Why shouldn't a web > >> framework do this? > > >> >> Thanks, > > >> >> David > > >> >> > Alan > > >> >> -- > >> >> Lift, the simply functional web > >> frameworkhttp://liftweb.net<http://liftweb.net> > >> >> Collaborative Task Managementhttp://much4.us > >> <http://much4.us> > >> >> Follow me:http://twitter.com/dpp > >> >> Git some:http://github.com/dpp > > >> -- > >> Lift, the simply functional web frameworkhttp://liftweb.net > >> Collaborative Task Managementhttp://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 -~----------~----~----~----~------~----~------~--~---
