[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread David Pollak 
Please also see:
http://groups.google.com/group/liftweb/msg/1f156eeec71da397?hl=en

On Tue, May 12, 2009 at 11:52 AM, Timothy Perrett
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."  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"  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"  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 o

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread Timothy Perrett 


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."  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"  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"  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 m

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread marius d. 

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"  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"  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.
> >

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread Charles F. Munat 

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"  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"  wrote:
 On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat  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. :-(
> > 

--~--~-~--~~~---~--~~
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 
liftwe

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread marius d. 

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"  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"  wrote:
>
> >> On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat  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. :-(
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread Timothy Perrett 


Hey Chas,

> 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.

It will be a medium size chart :-) I'll try and bash it out today with a but
of graffle action! Do note however that a diagram about lifts processing
pipeline will be somewhat different to the diagram you previously posted
which details more the package structure of lift.

> 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.

Almost certainly anything you don't understand, or is not clear, just say
and im sure someone will be happy to lay it out for you.

> 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.

Thanks, that's great feedback :-)

Cheers, Tim



--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread Charles F. Munat 

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"  wrote:
> 
>> On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat  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. :-(
> 
> 
> 
> > 

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-12 Thread Charles F. Munat 

A man can dream, can't he?

David Pollak wrote:
> 
> 
> On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat  > 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. :-(
>  
> 
> 
> 
> Chas.
> 
> Timothy Perrett wrote:
>  > Chas - now I see your confusion. One can only imagine by "lift core"
>  > the author of that image means net.liftweb.http...
>  >
>  > Cheers, Tim
>  >
>  > On May 11, 7:28 pm, "Charles F. Munat"  > wrote:
>  >> How would you draw the diagram? Don't be so sure that your learning
>  >> style isn't mirrored by others...
>  >>
>  >> Chas.
>  >>
>  >>
>  >>
>  >> David Pollak wrote:
>  >>> In this case, I don't think lift-core means the same as the
> lift-core
>  >>> package.
>  >>> I'm also not a fan of layer diagrams in general... I think that
> they
>  >>> fail to show the interconnected nature of things... but that's
> just my
>  >>> learning style.
>  >>> On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat
> mailto:c...@munat.com>
>  >>> >> wrote:
>  >>> No complaints here. I'm just confused by the diagram in the
> Lift book.
>  >>> I'm very literal about these things, and this diagram
> doesn't make much
>  >>> sense to me. (Probably, the problem is in my addled brain,
> not the
>  >>> diagram.) I'm trying to figure out if it can be improved
> and, if so,
>  >>> how.
>  >>> Chas.
>  >>> David Pollak wrote:
>  >>>  > A long time ago, I insisted that Lift was everything
> that we had
>  >>> in all
>  >>>  > the Lift packages.  When DavidB split Lift into different
>  >>> packages, he
>  >>>  > called the "whole thing that includes all Lift packages"
> Lift
>  >>> Core.  It
>  >>>  > would probably be better named "Lift Bloat" (this is a
> joke), but
>  >>> it is
>  >>>  > what it is.
>  >>>  > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat
> mailto:c...@munat.com>
>  >>> >
>  >>>  > 
>   >>>  > What exactly is Lift-Core. When I read Chapter 7 of
> the Lift
>  >>> book, it
>  >>>  > says that Lift-Core is
>  >>>  > "The engine of the framework responsible for the
> request/response
>  >>>  > lifecycle, the rendering pipeline, invoking the user's
>  >>> functions, etc.
>  >>>  > We don't directly cover the core in this book because
>  >>> essentially all of
>  >>>  > the functionality that we do cover sits on top of
> the core."
>  >>>  > But when I look in the source code under lift-core,
> there's
>  >>> nothing
>  >>>  > there except a pom.xml file that appears to pull a
> bunch of
>  >>>  > dependencies, namely, lift-util, lift-webkit,
> lift-mapper,
>  >>> lift-machine,
>  >>>  > lift-record, lift-textile, lift-facebook, lift-amqp,
>  >>> lift-xmpp, and
>  >>>  > lift-widgets.
>  >>>  > So does "lift-core" comprise these widgets? Or is
> the lift-core
>  >>>  > something else? (The diagram in the book shows the
> Mapper,
>  >>> for example,
>  >>>  > as being separate from the Core.)
>  >>>  > Thanks for any help.
>  >>>  > Chas.
>  >>>  > --
>  >>>  > Lift, the simply functional web
> frameworkhttp://liftweb.net 
>  >>>  > Beginning
> Scalahttp://www.apress.com/book/view/1430219890
> 
>  >>>  > Follow me:http://twitter.com/dpp
>  >>>  > Git some:http://github.com/dpp
>  >>> --
>  >>> Lift, the simply functional web frameworkhttp://liftweb.net
> 
>  >>> Beginning Scalahttp://www.apress.com/book/view/1430219890
> 
>  >>> Follow me:http://twitter.com/dpp
>  >>> Git some:http://github.com/dpp
>  > >
> 
> 
> 
> 
> 
> -- 
> 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/

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread Timothy Perrett 


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"  wrote:

> On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat  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. :-(



--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread David Pollak 
On Mon, May 11, 2009 at 4:41 PM, Charles F. Munat  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. :-(


>
>
> Chas.
>
> Timothy Perrett wrote:
> > Chas - now I see your confusion. One can only imagine by "lift core"
> > the author of that image means net.liftweb.http...
> >
> > Cheers, Tim
> >
> > On May 11, 7:28 pm, "Charles F. Munat"  wrote:
> >> How would you draw the diagram? Don't be so sure that your learning
> >> style isn't mirrored by others...
> >>
> >> Chas.
> >>
> >>
> >>
> >> David Pollak wrote:
> >>> In this case, I don't think lift-core means the same as the lift-core
> >>> package.
> >>> I'm also not a fan of layer diagrams in general... I think that they
> >>> fail to show the interconnected nature of things... but that's just my
> >>> learning style.
> >>> On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat  >>> > wrote:
> >>> No complaints here. I'm just confused by the diagram in the Lift
> book.
> >>> I'm very literal about these things, and this diagram doesn't make
> much
> >>> sense to me. (Probably, the problem is in my addled brain, not the
> >>> diagram.) I'm trying to figure out if it can be improved and, if
> so,
> >>> how.
> >>> Chas.
> >>> David Pollak wrote:
> >>>  > A long time ago, I insisted that Lift was everything that we had
> >>> in all
> >>>  > the Lift packages.  When DavidB split Lift into different
> >>> packages, he
> >>>  > called the "whole thing that includes all Lift packages" Lift
> >>> Core.  It
> >>>  > would probably be better named "Lift Bloat" (this is a joke),
> but
> >>> it is
> >>>  > what it is.
> >>>  > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat <
> c...@munat.com
> >>> 
> >>>  > >> wrote:
> >>>  > What exactly is Lift-Core. When I read Chapter 7 of the Lift
> >>> book, it
> >>>  > says that Lift-Core is
> >>>  > "The engine of the framework responsible for the
> request/response
> >>>  > lifecycle, the rendering pipeline, invoking the user's
> >>> functions, etc.
> >>>  > We don't directly cover the core in this book because
> >>> essentially all of
> >>>  > the functionality that we do cover sits on top of the core."
> >>>  > But when I look in the source code under lift-core, there's
> >>> nothing
> >>>  > there except a pom.xml file that appears to pull a bunch of
> >>>  > dependencies, namely, lift-util, lift-webkit, lift-mapper,
> >>> lift-machine,
> >>>  > lift-record, lift-textile, lift-facebook, lift-amqp,
> >>> lift-xmpp, and
> >>>  > lift-widgets.
> >>>  > So does "lift-core" comprise these widgets? Or is the
> lift-core
> >>>  > something else? (The diagram in the book shows the Mapper,
> >>> for example,
> >>>  > as being separate from the Core.)
> >>>  > Thanks for any help.
> >>>  > Chas.
> >>>  > --
> >>>  > Lift, the simply functional web frameworkhttp://liftweb.net
> >>>  > Beginning Scalahttp://www.apress.com/book/view/1430219890
> >>>  > Follow me:http://twitter.com/dpp
> >>>  > Git some:http://github.com/dpp
> >>> --
> >>> Lift, the simply functional web frameworkhttp://liftweb.net
> >>> Beginning Scalahttp://www.apress.com/book/view/1430219890
> >>> Follow me:http://twitter.com/dpp
> >>> Git some:http://github.com/dpp
> > >
>
> >
>


-- 
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread Charles F. Munat 

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...

Chas.

Timothy Perrett wrote:
> Chas - now I see your confusion. One can only imagine by "lift core"
> the author of that image means net.liftweb.http...
> 
> Cheers, Tim
> 
> On May 11, 7:28 pm, "Charles F. Munat"  wrote:
>> How would you draw the diagram? Don't be so sure that your learning
>> style isn't mirrored by others...
>>
>> Chas.
>>
>>
>>
>> David Pollak wrote:
>>> In this case, I don't think lift-core means the same as the lift-core
>>> package.
>>> I'm also not a fan of layer diagrams in general... I think that they
>>> fail to show the interconnected nature of things... but that's just my
>>> learning style.
>>> On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat >> > wrote:
>>> No complaints here. I'm just confused by the diagram in the Lift book.
>>> I'm very literal about these things, and this diagram doesn't make much
>>> sense to me. (Probably, the problem is in my addled brain, not the
>>> diagram.) I'm trying to figure out if it can be improved and, if so,
>>> how.
>>> Chas.
>>> David Pollak wrote:
>>>  > A long time ago, I insisted that Lift was everything that we had
>>> in all
>>>  > the Lift packages.  When DavidB split Lift into different
>>> packages, he
>>>  > called the "whole thing that includes all Lift packages" Lift
>>> Core.  It
>>>  > would probably be better named "Lift Bloat" (this is a joke), but
>>> it is
>>>  > what it is.
>>>  > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat >> 
>>>  > >> wrote:
>>>  > What exactly is Lift-Core. When I read Chapter 7 of the Lift
>>> book, it
>>>  > says that Lift-Core is
>>>  > "The engine of the framework responsible for the request/response
>>>  > lifecycle, the rendering pipeline, invoking the user's
>>> functions, etc.
>>>  > We don't directly cover the core in this book because
>>> essentially all of
>>>  > the functionality that we do cover sits on top of the core."
>>>  > But when I look in the source code under lift-core, there's
>>> nothing
>>>  > there except a pom.xml file that appears to pull a bunch of
>>>  > dependencies, namely, lift-util, lift-webkit, lift-mapper,
>>> lift-machine,
>>>  > lift-record, lift-textile, lift-facebook, lift-amqp,
>>> lift-xmpp, and
>>>  > lift-widgets.
>>>  > So does "lift-core" comprise these widgets? Or is the lift-core
>>>  > something else? (The diagram in the book shows the Mapper,
>>> for example,
>>>  > as being separate from the Core.)
>>>  > Thanks for any help.
>>>  > Chas.
>>>  > --
>>>  > Lift, the simply functional web frameworkhttp://liftweb.net
>>>  > Beginning Scalahttp://www.apress.com/book/view/1430219890
>>>  > Follow me:http://twitter.com/dpp
>>>  > Git some:http://github.com/dpp
>>> --
>>> Lift, the simply functional web frameworkhttp://liftweb.net
>>> Beginning Scalahttp://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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread Timothy Perrett 

Chas - now I see your confusion. One can only imagine by "lift core"
the author of that image means net.liftweb.http...

Cheers, Tim

On May 11, 7:28 pm, "Charles F. Munat"  wrote:
> How would you draw the diagram? Don't be so sure that your learning
> style isn't mirrored by others...
>
> Chas.
>
>
>
> David Pollak wrote:
> > In this case, I don't think lift-core means the same as the lift-core
> > package.
>
> > I'm also not a fan of layer diagrams in general... I think that they
> > fail to show the interconnected nature of things... but that's just my
> > learning style.
>
> > On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat  > > wrote:
>
> >     No complaints here. I'm just confused by the diagram in the Lift book.
> >     I'm very literal about these things, and this diagram doesn't make much
> >     sense to me. (Probably, the problem is in my addled brain, not the
> >     diagram.) I'm trying to figure out if it can be improved and, if so,
> >     how.
>
> >     Chas.
>
> >     David Pollak wrote:
> >      > A long time ago, I insisted that Lift was everything that we had
> >     in all
> >      > the Lift packages.  When DavidB split Lift into different
> >     packages, he
> >      > called the "whole thing that includes all Lift packages" Lift
> >     Core.  It
> >      > would probably be better named "Lift Bloat" (this is a joke), but
> >     it is
> >      > what it is.
>
> >      > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat  >     
> >      > >> wrote:
>
> >      >     What exactly is Lift-Core. When I read Chapter 7 of the Lift
> >     book, it
> >      >     says that Lift-Core is
>
> >      >     "The engine of the framework responsible for the request/response
> >      >     lifecycle, the rendering pipeline, invoking the user's
> >     functions, etc.
> >      >     We don't directly cover the core in this book because
> >     essentially all of
> >      >     the functionality that we do cover sits on top of the core."
>
> >      >     But when I look in the source code under lift-core, there's
> >     nothing
> >      >     there except a pom.xml file that appears to pull a bunch of
> >      >     dependencies, namely, lift-util, lift-webkit, lift-mapper,
> >     lift-machine,
> >      >     lift-record, lift-textile, lift-facebook, lift-amqp,
> >     lift-xmpp, and
> >      >     lift-widgets.
>
> >      >     So does "lift-core" comprise these widgets? Or is the lift-core
> >      >     something else? (The diagram in the book shows the Mapper,
> >     for example,
> >      >     as being separate from the Core.)
>
> >      >     Thanks for any help.
>
> >      >     Chas.
>
> >      > --
> >      > Lift, the simply functional web frameworkhttp://liftweb.net
> >      > Beginning Scalahttp://www.apress.com/book/view/1430219890
> >      > Follow me:http://twitter.com/dpp
> >      > Git some:http://github.com/dpp
>
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread Charles F. Munat 

How would you draw the diagram? Don't be so sure that your learning 
style isn't mirrored by others...

Chas.

David Pollak wrote:
> In this case, I don't think lift-core means the same as the lift-core 
> package.
> 
> I'm also not a fan of layer diagrams in general... I think that they 
> fail to show the interconnected nature of things... but that's just my 
> learning style.
> 
> On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat  > wrote:
> 
> No complaints here. I'm just confused by the diagram in the Lift book.
> I'm very literal about these things, and this diagram doesn't make much
> sense to me. (Probably, the problem is in my addled brain, not the
> diagram.) I'm trying to figure out if it can be improved and, if so,
> how.
> 
> 
> 
> Chas.
> 
> David Pollak wrote:
>  > A long time ago, I insisted that Lift was everything that we had
> in all
>  > the Lift packages.  When DavidB split Lift into different
> packages, he
>  > called the "whole thing that includes all Lift packages" Lift
> Core.  It
>  > would probably be better named "Lift Bloat" (this is a joke), but
> it is
>  > what it is.
>  >
>  > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat  
>  > >> wrote:
>  >
>  >
>  > What exactly is Lift-Core. When I read Chapter 7 of the Lift
> book, it
>  > says that Lift-Core is
>  >
>  > "The engine of the framework responsible for the request/response
>  > lifecycle, the rendering pipeline, invoking the user's
> functions, etc.
>  > We don't directly cover the core in this book because
> essentially all of
>  > the functionality that we do cover sits on top of the core."
>  >
>  > But when I look in the source code under lift-core, there's
> nothing
>  > there except a pom.xml file that appears to pull a bunch of
>  > dependencies, namely, lift-util, lift-webkit, lift-mapper,
> lift-machine,
>  > lift-record, lift-textile, lift-facebook, lift-amqp,
> lift-xmpp, and
>  > lift-widgets.
>  >
>  > So does "lift-core" comprise these widgets? Or is the lift-core
>  > something else? (The diagram in the book shows the Mapper,
> for example,
>  > as being separate from the Core.)
>  >
>  > Thanks for any help.
>  >
>  > Chas.
>  >
>  >
>  >
>  >
>  >
>  > --
>  > 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
>  >
>  > >
> 
> 
> 
> 
> 
> -- 
> 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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread David Bernard 
See
http://groups.google.com/group/liftweb/browse_thread/thread/957d5c8942b70a19/6fc14f442224626a

the name "lift-core" was keep for backward compatibility and to avoid
existing user to replace "lift-core" by lift-full or the exact list of
need-jar in pom.xml.

/davidB

On Mon, May 11, 2009 at 16:10, David Pollak
wrote:

> In this case, I don't think lift-core means the same as the lift-core
> package.
> I'm also not a fan of layer diagrams in general... I think that they fail
> to show the interconnected nature of things... but that's just my learning
> style.
>
>
> On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat  wrote:
>
>> No complaints here. I'm just confused by the diagram in the Lift book.
>> I'm very literal about these things, and this diagram doesn't make much
>> sense to me. (Probably, the problem is in my addled brain, not the
>> diagram.) I'm trying to figure out if it can be improved and, if so, how.
>>
>>
>>
>> Chas.
>>
>> David Pollak wrote:
>> > A long time ago, I insisted that Lift was everything that we had in all
>> > the Lift packages.  When DavidB split Lift into different packages, he
>> > called the "whole thing that includes all Lift packages" Lift Core.  It
>> > would probably be better named "Lift Bloat" (this is a joke), but it is
>> > what it is.
>> >
>> > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat > > > wrote:
>> >
>> >
>> > What exactly is Lift-Core. When I read Chapter 7 of the Lift book,
>> it
>> > says that Lift-Core is
>> >
>> > "The engine of the framework responsible for the request/response
>> > lifecycle, the rendering pipeline, invoking the user's functions,
>> etc.
>> > We don't directly cover the core in this book because essentially
>> all of
>> > the functionality that we do cover sits on top of the core."
>> >
>> > But when I look in the source code under lift-core, there's nothing
>> > there except a pom.xml file that appears to pull a bunch of
>> > dependencies, namely, lift-util, lift-webkit, lift-mapper,
>> lift-machine,
>> > lift-record, lift-textile, lift-facebook, lift-amqp, lift-xmpp, and
>> > lift-widgets.
>> >
>> > So does "lift-core" comprise these widgets? Or is the lift-core
>> > something else? (The diagram in the book shows the Mapper, for
>> example,
>> > as being separate from the Core.)
>> >
>> > Thanks for any help.
>> >
>> > Chas.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > 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
>> >
>> > >
>>
>>
>>
>
>
> --
> 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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-11 Thread David Pollak 
In this case, I don't think lift-core means the same as the lift-core
package.
I'm also not a fan of layer diagrams in general... I think that they fail to
show the interconnected nature of things... but that's just my learning
style.

On Sun, May 10, 2009 at 11:03 AM, Charles F. Munat  wrote:

> No complaints here. I'm just confused by the diagram in the Lift book.
> I'm very literal about these things, and this diagram doesn't make much
> sense to me. (Probably, the problem is in my addled brain, not the
> diagram.) I'm trying to figure out if it can be improved and, if so, how.
>
>
>
> Chas.
>
> David Pollak wrote:
> > A long time ago, I insisted that Lift was everything that we had in all
> > the Lift packages.  When DavidB split Lift into different packages, he
> > called the "whole thing that includes all Lift packages" Lift Core.  It
> > would probably be better named "Lift Bloat" (this is a joke), but it is
> > what it is.
> >
> > On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat  > > wrote:
> >
> >
> > What exactly is Lift-Core. When I read Chapter 7 of the Lift book, it
> > says that Lift-Core is
> >
> > "The engine of the framework responsible for the request/response
> > lifecycle, the rendering pipeline, invoking the user's functions,
> etc.
> > We don't directly cover the core in this book because essentially all
> of
> > the functionality that we do cover sits on top of the core."
> >
> > But when I look in the source code under lift-core, there's nothing
> > there except a pom.xml file that appears to pull a bunch of
> > dependencies, namely, lift-util, lift-webkit, lift-mapper,
> lift-machine,
> > lift-record, lift-textile, lift-facebook, lift-amqp, lift-xmpp, and
> > lift-widgets.
> >
> > So does "lift-core" comprise these widgets? Or is the lift-core
> > something else? (The diagram in the book shows the Mapper, for
> example,
> > as being separate from the Core.)
> >
> > Thanks for any help.
> >
> > Chas.
> >
> >
> >
> >
> >
> > --
> > 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
> >
> > >
>
> >
>


-- 
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-10 Thread Charles F. Munat 

So really there is no lift core, it's just a combination of other modules?

Chas.

Timothy Perrett wrote:
> You would use lift core if you wanted to include all this jars in your  
> project. It in itself does not "do" anything and it's just a pom module.
> 
> Does that help?
> 
> Cheers, Tim
> 
> Sent from my iPhone
> 
> On 10 May 2009, at 07:49, "Charles F. Munat"  wrote:
> 
>> What exactly is Lift-Core. When I read Chapter 7 of the Lift book, it
>> says that Lift-Core is
>>
>> "The engine of the framework responsible for the request/response
>> lifecycle, the rendering pipeline, invoking the user's functions, etc.
>> We don't directly cover the core in this book because essentially  
>> all of
>> the functionality that we do cover sits on top of the core."
>>
>> But when I look in the source code under lift-core, there's nothing
>> there except a pom.xml file that appears to pull a bunch of
>> dependencies, namely, lift-util, lift-webkit, lift-mapper, lift- 
>> machine,
>> lift-record, lift-textile, lift-facebook, lift-amqp, lift-xmpp, and
>> lift-widgets.
>>
>> So does "lift-core" comprise these widgets? Or is the lift-core
>> something else? (The diagram in the book shows the Mapper, for  
>> example,
>> as being separate from the Core.)
>>
>> Thanks for any help.
>>
>> Chas.
>>
> 
> > 

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-10 Thread Heiko Seeberger 
Lift Bloat: LOL!!!

2009/5/10 David Pollak 

> A long time ago, I insisted that Lift was everything that we had in all the
> Lift packages.  When DavidB split Lift into different packages, he called
> the "whole thing that includes all Lift packages" Lift Core.  It would
> probably be better named "Lift Bloat" (this is a joke), but it is what it
> is.
>
> On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat  wrote:
>
>>
>> What exactly is Lift-Core. When I read Chapter 7 of the Lift book, it
>> says that Lift-Core is
>>
>> "The engine of the framework responsible for the request/response
>> lifecycle, the rendering pipeline, invoking the user's functions, etc.
>> We don't directly cover the core in this book because essentially all of
>> the functionality that we do cover sits on top of the core."
>>
>> But when I look in the source code under lift-core, there's nothing
>> there except a pom.xml file that appears to pull a bunch of
>> dependencies, namely, lift-util, lift-webkit, lift-mapper, lift-machine,
>> lift-record, lift-textile, lift-facebook, lift-amqp, lift-xmpp, and
>> lift-widgets.
>>
>> So does "lift-core" comprise these widgets? Or is the lift-core
>> something else? (The diagram in the book shows the Mapper, for example,
>> as being separate from the Core.)
>>
>> Thanks for any help.
>>
>> Chas.
>>
>>
>>
>
>
> --
> 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
>
>
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-10 Thread David Pollak 
A long time ago, I insisted that Lift was everything that we had in all the
Lift packages.  When DavidB split Lift into different packages, he called
the "whole thing that includes all Lift packages" Lift Core.  It would
probably be better named "Lift Bloat" (this is a joke), but it is what it
is.

On Sat, May 9, 2009 at 11:49 PM, Charles F. Munat  wrote:

>
> What exactly is Lift-Core. When I read Chapter 7 of the Lift book, it
> says that Lift-Core is
>
> "The engine of the framework responsible for the request/response
> lifecycle, the rendering pipeline, invoking the user's functions, etc.
> We don't directly cover the core in this book because essentially all of
> the functionality that we do cover sits on top of the core."
>
> But when I look in the source code under lift-core, there's nothing
> there except a pom.xml file that appears to pull a bunch of
> dependencies, namely, lift-util, lift-webkit, lift-mapper, lift-machine,
> lift-record, lift-textile, lift-facebook, lift-amqp, lift-xmpp, and
> lift-widgets.
>
> So does "lift-core" comprise these widgets? Or is the lift-core
> something else? (The diagram in the book shows the Mapper, for example,
> as being separate from the Core.)
>
> Thanks for any help.
>
> Chas.
>
> >
>


-- 
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
-~--~~~~--~~--~--~---

[Lift] Re: Confusion about Lift-Core

2009-05-10 Thread Timothy Perrett 

You would use lift core if you wanted to include all this jars in your  
project. It in itself does not "do" anything and it's just a pom module.

Does that help?

Cheers, Tim

Sent from my iPhone

On 10 May 2009, at 07:49, "Charles F. Munat"  wrote:

>
> What exactly is Lift-Core. When I read Chapter 7 of the Lift book, it
> says that Lift-Core is
>
> "The engine of the framework responsible for the request/response
> lifecycle, the rendering pipeline, invoking the user's functions, etc.
> We don't directly cover the core in this book because essentially  
> all of
> the functionality that we do cover sits on top of the core."
>
> But when I look in the source code under lift-core, there's nothing
> there except a pom.xml file that appears to pull a bunch of
> dependencies, namely, lift-util, lift-webkit, lift-mapper, lift- 
> machine,
> lift-record, lift-textile, lift-facebook, lift-amqp, lift-xmpp, and
> lift-widgets.
>
> So does "lift-core" comprise these widgets? Or is the lift-core
> something else? (The diagram in the book shows the Mapper, for  
> example,
> as being separate from the Core.)
>
> Thanks for any help.
>
> Chas.
>
> >
>

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---