|
|
Post by votan on Oct 2, 2008 6:47:32 GMT -5
I'm trying to pack the upload function in a nice design..... but as the upload causes the app to wait for an event right after the upload function gets called, everything below the uploader is not displayed on the page.
Is there a way to overcome this problem?
In my case I have some tables I need to display below the upload function.... but currently the design ends right below the upload function , due to the above reasons...
|
|
|
|
Post by carlgundel on Oct 2, 2008 9:42:42 GMT -5
You bring up a good point. The UPLOAD statement was designed to work like an INPUT statement, which causes the break in page layout you describe.
I need to reconsider how it works, and perhaps add the ability to make it an event driven widget like so:
UPLOAD "prompt", filename$, [uploadHandler]
In the meantime, you might consider creating a separate upload program that you RUN and RENDER into the page where you like.
-Carl
|
|
|
|
Post by votan on Oct 2, 2008 11:19:53 GMT -5
I tried doing it with the run and render functions.
but when I try to run and render the fileupload directly, the upload requester comes up correctly, but quits with the "debug / full stack" page, saying "Message not understood: #uploaded:", when hitting the "upload" button.
If I try to run it via a function call to the file, the system hangs and nothing goes anymore.... not even the runtime timeout brings the system back and I have to restart RB.
Maybe I'm just missing something?? Can you maybe give me an example how you would do it?
btw.... making the upload function "editable" would be a cool thing, too... like already possible with the sessionexpired.html file..... cause the look is pretty basic and I would like to change the layout.... and actually also the button-texts, as I need this function in a multi-language program...
|
|
|
|
Post by carlgundel on Oct 2, 2008 12:09:54 GMT -5
I tried doing it with the run and render functions. but when I try to run and render the fileupload directly, the upload requester comes up correctly, but quits with the "debug / full stack" page, saying "Message not understood: #uploaded:", when hitting the "upload" button. If I try to run it via a function call to the file, the system hangs and nothing goes anymore.... not even the runtime timeout brings the system back and I have to restart RB. Maybe I'm just missing something?? Can you maybe give me an example how you would do it? btw.... making the upload function "editable" would be a cool thing, too... like already possible with the sessionexpired.html file..... cause the look is pretty basic and I would like to change the layout.... and actually also the button-texts, as I need this function in a multi-language program... I don't think you're missing anything. It looks like there's a bug in there. I'll get on it.  As for multi-language features, that's something I should consider for the next round of development. -Carl |
|
|
|
Post by Brent on Oct 3, 2008 13:14:04 GMT -5
Carl, I'd like to see a brand new UPLOADBOX widget rather than expanding UPLOAD. You could give it methods like LIMITSIZE(bytes), SAVEDIR(folder$), and NAME$(). Sure would open up a lot of possibilities, in my opinion.
|
|
|
|
Post by carlgundel on Oct 3, 2008 16:47:46 GMT -5
Yes, I think that it makes sense to make the UPLOAD statement into a widget. There's probably no reason not to support its original usage too if it doesn't prove to be a hassle.  -Carl |
|
As for multi-language features, that's something I should consider for the next round of development.
