Does it matter from a developer's point of view if lift:bind and
lift:with-param are actually snippets or not? If they can be
converted into snippets, and by virtue of doing so can retain their
existing names, then why not just leave them alone?
I'd rather see the framework go the other way:
is this too bad?
lift:display
user:name/
user:address/
/lift:display
No, it's not bad. But allowing non-lift prefixes would neatly solve
your problem by changing the definition of the lift prefix from
this is a snippet to this is a Lift tag, don't worry about how it's
Following the example in Exploring Lift section 5.3.1, I set up some
of my site map pages to redirect to a login page if the user is not
already logged in. My implementation of the failMsg function is
slightly different, though: Before redirecting, I save the request
URI to a SessionVar so the
I'm working on a LiftView implementation and have noticed that views
and snippets, despite being very similar, are structured differently.
Could these be unified?
Snippet: Any class in a snippets package is a snippet. Classes that
extend DispatchSnippet use a dispatch PF while others are
business logic.
Any attempt to unify these two concepts will lead to greater problems in the
future.
Thanks,
David
On Sat, May 23, 2009 at 7:43 PM, Willis Blackburn
willis.blackb...@gmail.com wrote:
I'm working on a LiftView implementation and have noticed that views
and snippets
will lead to greater problems in the
future.
Thanks,
David
On Sat, May 23, 2009 at 7:43 PM, Willis Blackburn
willis.blackb...@gmail.com wrote:
I'm working on a LiftView implementation and have noticed that views
and snippets, despite being very similar, are structured differently
, but once you're dealing with state, etc., you
should be graduating to declaring the methods that your snippets support,
thus enforcing the DispatchSnippet being the base class of StatefulSnippet.
On Mon, May 18, 2009 at 6:04 PM, Willis Blackburn
willis.blackb...@gmail.com wrote:
I'm
.
On Mon, May 18, 2009 at 6:04 PM, Willis Blackburn
willis.blackb...@gmail.com wrote:
I'm back with another question.
I see that StatefulSnippet extends DispatchSnippet. I understand what
DispatchSnippet is about. But what is the reason that a
StatefulSnippet must also
Hi all. I just picked up Lift and Scala a couple of weeks ago. I have
been using mostly Wicket for the last couple of years. I have ordered
David's Scala book and a Lift book from Amazon, but they're not here
yet, so I am hoping that someone can help me with some conceptual
issues.
In Wicket,
:04 AM, Willis Blackburn
willis.blackb...@gmail.com wrote:
Hi all. I just picked up Lift and Scala a couple of weeks ago. I have
been using mostly Wicket for the last couple of years. I have ordered
David's Scala book and a Lift book from Amazon, but they're not here
yet, so I am hoping
I'm back with another question.
I see that StatefulSnippet extends DispatchSnippet. I understand what
DispatchSnippet is about. But what is the reason that a
StatefulSnippet must also be a DispatchSnippet? Aren't these concepts
(stateful vs. stateless, dispatch vs. reflection) unrelated?
11 matches
Mail list logo
