Awesome! That's a nice way to bypass the issues I was running into. I
suppose that if someone wanted to control it on a per-form basis then they
could do it themselves via their own field mappings.
Derek
On Wed, Jul 1, 2009 at 12:20 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
It is not about dropping Lift, it is about starting to use it. I want
it very much but i need to consider all pluses and minuses before we
jump in. External server for uploading could be a solution but it will
not be in Scala and will require some other tools to be involved. I
am still looking
On Tue, Jun 30, 2009 at 11:32 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Tue, Jun 30, 2009 at 2:22 PM, Viktor Klang viktor.kl...@gmail.comwrote:
Create a tmp-file, store the localpath in S.param and register a delete on
request done
will be more streamlined than potentially
It would also be nice to be able to provide progress feedback. The page
returned after the form submission can then use comet to display a
progress bar or something like that. (The media upload at Vimeo comes
to mind as a good example of this!)
Also, I would suggest some smarts when
K... I'll check some code in later today.
On Wed, Jul 1, 2009 at 9:05 AM, Andrew Scherpbier and...@scherpbier.orgwrote:
It would also be nice to be able to provide progress feedback. The page
returned after the form submission can then use comet to display a
progress bar or something like
Okay... I've checked in new code.
In LiftRules, there's:
/**
* The function that converts a fieldName, contentType, fileName and an
InputStream into
* a FileParamHolder. By default, create an in-memory instance. Use
OnDiskFileParamHolder
* to create an on-disk version
*/
var
Wow! This is very cool. Can't wait to try it out.
--Andrew
David Pollak wrote:
Okay... I've checked in new code.
In LiftRules, there's:
/**
* The function that converts a fieldName, contentType, fileName and
an InputStream into
* a FileParamHolder. By default, create an in-memory
Create a tmp-file, store the localpath in S.param and register a delete on
request done
will be more streamlined than potentially monkeypatching it in
Thoughts?
-- Viktor
On Jun 30, 2009 11:08 PM, Derek Chen-Becker dchenbec...@gmail.com wrote:
Well, as usual something that seemed simple at
On Tue, Jun 30, 2009 at 2:22 PM, Viktor Klang viktor.kl...@gmail.comwrote:
Create a tmp-file, store the localpath in S.param and register a delete on
request done
will be more streamlined than potentially monkeypatching it in
Thoughts?
Huge hack
-- Viktor
On Jun 30, 2009 11:08 PM,
What kind of priority is this issue? I think I can abstract things in such
a way that it works correctly, but it'll take a couple of days.
On Tue, Jun 30, 2009 at 2:08 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
Well, as usual something that seemed simple at first glance is now looking
It's just an open item, and one that I had hoped I could contribute on. If
you have some ideas on restructuring the param handling I can take it from
there. No rush.
Derek
On Tue, Jun 30, 2009 at 3:33 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
What kind of priority is this issue?
This has been hurting me for quite a while now (raised it on list
about 2 months ago) and could really do with getting it fixed.
As derek points out, it's not a small change which is why I've done
nothing about it to date - a little too much core hacking to feel happy
If you think your able
I am also contemplating to use Lift but lack of big file upload is the
showstopper. We need to upload images, and big video files and
currently there i snot way to do it in Lift, i need something else to
handle that which makes the whole stuff more complex than needed.
Spooling into temp file
I'm not too familiar with the topic but instead of dropping lift, as a
temporary workaround can't you have the upload be handled by another servlet
which will save it and then redirect?
-
Vlad Seryakovvserya...@gmail.com wrote:
I am also contemplating to
Derek Chen-Becker dchenbec...@gmail.com writes:
Well, as usual something that seemed simple at first glance is now looking
somewhat complex. I'm thinking of reworking the fileUpload handling to allow
a user to register either a (String, String, Array[Byte]) ⇒ Any or (String,
String,
15 matches
Mail list logo