because I haven't yet encountered a use case where they correspond to
expected behaviour if the user happens to know how to work with a
tabbed browser.
--
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to
Hi,
I had a similar discussion on this list a while ago.
http://groups.google.com/group/liftweb/browse_thread/thread/69898fb5191a074d
I haven't found THE idiomatic answer in Lift. For now I'm using
StatefulSnippets for the more complex cases; they work quite well.
SessionVars are almost always
not sure if I posted the link:
http://groups.google.com/group/liftweb/browse_thread/thread/69898fb5191a074d
--
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group,
Hello fellow Heavylifters,
the following small utility classes could be useful for those who
develop somewhat classic data-oriented applications in Lift and with
Mapper:
http://wiki.github.com/tromberg/Winglet/
In short:
* Do more with less template and snippet code
* Only execute the parts
I've been happy with the CSV support provided by h2database because
that was already included in the PocketChange example
http://www.h2database.com/html/tutorial.html#csv
But there are over a dozen alternatives I think. Google for java csv
library
It's a good idea IMHO to use a library for
Just discovered this issue (1.1-m8): The sign-up form will not display
field errors by default. The user therefore gets the impression that
the application has simply stopped responding. The validation I
checked (and this may be the only one) was the unique e-mail address
validation. If the e-mail
Well LiftRules.exceptionHandler was new to me so thanks. Great way to
deal with the really unexpected (like OutOfMemory). Would do in the
short run.
However, the other Tim is correct in that I (and probably other
people) really want to handle this like similarly to a validation
error on any other
Hi Tim,
thanks for raising this, I did wrap the whole thing like so:
LiftRules.maxMimeSize = 6 * 1024 * 1024
LiftRules.maxMimeFileSize = 5 * 1024 * 1024
LiftRules.handleMimeFile = (fieldName, contentType, fileName,
inputStream) = {
try {
Hi,
I think it is documented somewhere in the Liftbook that one should not
use body tags inside a surround tag, but Lift doesn't seem to
complain.
I thought I would document the phenomenon I had here since people
usually look in the mailing list first.
I had used two nested surround templates,
override def validations = validPriority _ :: super.validations
funny, I had stumbled on exactly the same line of code when beginning.
Took me more than a day to understand what's going on. Especially
because when you copied code from the PDF version of the Liftbook/Lift
getting started guide,
Naftoli,
thanks for providing these insights into the inner workings of
Stateful Snippets. The mapSnippet solution sounds interesting. I knew
that snippets don't live on when not needed, but assumed that IF one
is alive in the current session, you would always get that one
instance. Hence at
Hi,
has anyone investigated or built a way to support tabbed browsing when
there is considerable view/workflow state? Or have I missed an elegant
way for this to be done in Lift?
If I am not mistaken, Lift currently supports
1. Sending continuations (things that will need to be done) from one
Jeppe We've made primary/secondary navigation where primary
navigation is ...
I did something similar..found it difficult to work with the default
snippets.
But found it hard, when writing my own group snippet, to identify the
current Loc within the LocGroups Locs.
So Jeppe, would be very
Dear all,
on every findAll request, lift seems to send the query twice (tested
1.0 and 1.0.2, working from the PocketChangeApp example on h2database,
and using
DB.addLogFunc((query, time) =
Log.info(query + : + time + ms)))
for logging
1. e.g. right after login; this must be framework
14 matches
Mail list logo
