Please also see: http://groups.google.com/group/liftweb/msg/1f156eeec71da397?hl=en
On Tue, May 12, 2009 at 11:52 AM, Timothy Perrett <timo...@getintheloop.eu>wrote: > > > Awesome - im working on something now... My day did not go to plan so it > dropped off the list unfortunately. I should be able to blag some work time > tomorrow to get this done. > > Cheers, Tim > > On 12/05/2009 19:46, "marius d." <marius.dan...@gmail.com> wrote: > > > > > Thanks for clarifications. The very point for this component diagram > > is to highlight the building blocks of Lift. Nothing more. How these > > components interact is a different story that based on my experience > > can not really be expressed by a component diagram. The "LiftCore" > > term from the diagram and "Lift-Core" from the source is an > > unfortunate naming collision. I'm really sorry that this caused > > confusion. > > > > If you are interested in the Request processing life-cycle (narrative > > not visual) you can find this in the LiftBook in the Advanced > > chapter. > > > > I'm also looking forward to see whatever Tim comes up with ! > > > > Br's, > > Marius > > > > On May 12, 8:53 pm, "Charles F. Munat" <c...@munat.com> wrote: > >> Marius, > >> > >> I think that there's some confusion about what I am looking for vs. what > >> my questions were about the component diagram. These are two separate > >> issues. > >> > >> Re the component diagram, I am just trying to make sense of it. Mostly I > >> was confused (and I think others might be as well) because you refer to > >> a Lift Core in the diagram, and then there is what appears to be a > >> lift-core module in the source code, but that module appears to be empty > >> and/or wrap up things that are represented separately from the Lift Core > >> in your diagram. > >> > >> Now that I understand that the Lift Core in the diagram bears no > >> relation to "lift-core" in the source code, much of my confusion has > >> disappeared. It's an unfortunate overlap though. > >> > >> Re the component diagram, I am still not very clear what Lift Core > >> constitutes or really how all these parts interact, but maybe I'm just > >> not good with component diagrams. Probably the latter, as I can't > >> remember ever seeing one that I thought provided much help. > >> > >> The flow chart I'd like to see is a completely different issue. Tim > >> asked what I was looking for and I said that what I'd really like to see > >> is a diagram that explained the Lift request/response cycle, preferably > >> as a flow chart. I know that this would be big and complex, but it would > >> be extremely helpful to me. > >> > >> It has been a goal of mine for some time to create such a chart as I > >> learn the Lift request/response cycle. I'm just now finally getting to > >> that point in my learning as I read the advanced chapters of your book. > >> > >> I think that Tim might be putting together a basic chart. If he does, > >> I'm hoping to fill it in with details as I learn more. Ideally, I'd love > >> a wall poster with the full Lift request/response cycle and detailed > >> explanations on it so I could refer to it when I'm coding. Could also be > >> useful on the wiki. > >> > >> I hope this clarifies the situation. Sorry for the confusion. > >> > >> Chas. > >> > >> marius d. wrote: > >>> Charles, > >> > >>> The diagram for the lift book is a component level diagram showing the > >>> most relevant pieces of lift. Component diagram reveal very little > >>> information about the actual interactions. The Lift-Core in the > >>> diagram you posted is essentially the Lift's "engine", the logic > >>> behind processing Lift requests and mainly it's about LiftServlet and > >>> LiftSession classes. Maybe what you're looking for is some sequence > >>> diagrams? LiftBook discusses the request processing life-cycle in the > >>> Advanced chapter but we didn't put diagrams there due to complexity > >>> and space rationales. > >> > >>> I wonder what does not make sense in the diagram you posted? ... given > >>> the fact that this is a component level diagram and not a sequence/ > >>> flow one. > >> > >>> Br's, > >>> Marius > >> > >>> On May 12, 11:22 am, "Charles F. Munat" <c...@munat.com> wrote: > >>>> Oh, that's easy. I don't get anything. The entire pipeline is a > mystery > >>>> to me. > >> > >>>> What I'd like to make is a complete (large) flow chart that shows what > >>>> happens to the request at every step of the way until it is returned > to > >>>> the browser as a response. Considering the number of possible decision > >>>> points, I think it would be a big chart. But even just a simplified > one > >>>> would help. > >> > >>>> The smart folks on the committers list here understand these things so > >>>> well that they answer in shorthand, assuming that I (or others) > >>>> understand all sorts of things that I have no clue about. That usually > >>>> means that I have to take half an hour to think through an answer step > >>>> by step, looking things up. > >> > >>>> I'm interested to see anything you come up with. Your online tutorials > >>>> have been surprisingly easy for the lay person to understand. I think > >>>> you have a knack for this. > >> > >>>> Meanwhile, I'll keep banging away at Chatper 7 when I can get free > from > >>>> all this other stuff (I'm as far behind as David is, I think). > >> > >>>> I don't normally use IM, but if you email a time, I'll make myself > >>>> available. I'll have to try to remember my username... > >> > >>>> Chas. > >> > >>>> Timothy Perrett wrote: > >> > >>>>> I have some time this week - mind if I have a go? Touch base with me > >>>>> offline > >>>>> and we'll exchange IM's... Id like to understand what exactly you > don't > >>>>> get > >>>>> in order to best explain / diagram it. > >>>>> Cheers, Tim > >>>>> On 12/05/2009 00:47, "David Pollak" <feeder.of.the.be...@gmail.com> > wrote: > >>>>>> On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat <c...@munat.com> > wrote: > >>>>>>> Yeah. I'm hoping that David comes up with something to show how he > views > >>>>>>> Lift. Then again, I am reminded of the scene in Being John > Malkovich > >>>>>>> where Malkovich follows the tunnel into his own subconscious mind. > Being > >>>>>>> David Pollak? This could be scary... > >>>>>> Run away!!!! > >>>>>> And I don't think I'll have time to come up with something... I'm > >>>>>> super-behind > >>>>>> in all things work right now. :-( > > > > > > > > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
