Thumbnails without AspJpeg

Even if ASPJpeg is not installed on your server you can still configure ASPRunnerPro to show thumbnails (assuming you generate thumbnails manually or use another software for this purpose).
ASPJpeg is only required to generated thumbnails/resize image files. It's not required to display images.

Yes, I understand it, but how to do it?
As I've mentioned:
I have very simple case:
ID,

thumbnail

largePic
List table shows the thumbnail

click thumbnail to show the LargePic via ibox
both are set as file/image
I just need a little directions
I do not want to store files in the database
Please assist with this simple solution. I know I am almost there <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=69012&image=1&table=forumreplies' class='bbc_emoticon' alt=':)' />

Hi, can someone please help and revisit my question?

Thank you

Hello,

I have tried today to do the most simplest task (previously parts of it worked now they don't)

1. started asprunner
   
2. clicked create new project
   
   3.clicked "new database"
   
3. in the box Table name gaveit a new name (photogallery)
   
4. added field ID , set is as primary (somwhow the autoincrement still showed as greyed out)
   
5. added field "thumnbnail" type text size 50 by default
   
6. added field "largepic" type text size 50 by default
   
7. clicked "create table button
   
   9.clicked "next" until reaching the "FIELDS screen
   
   there i unchecked "large" fromt he List page only
   
8. clicked until i reached the visual Editor screen
   
9. clicked list page double clicked the thumbnail
   
10. clicked view as image : checked the display as thumbnail, then clicked Edit as "file"
    and i got this: you need field at least 300 charachters long to upload files
    ok, i went to tables screen clicked modify table and when i tried to set the size to 300 i got error: ID sispatch error 3105 -too long
    soo, what to do?

Modify field size right in the database.

so, basically use actuall MS Access to build database to avoid this issue, right? and then import it into ASP runner?ok.
I will do that and revisit this thread in ashort while, as i am still unable to use application by default to have thumbnails linked to larger pictures.

ok, I understood that there is a need for aspjpeg, thank you, however, on the demo site the thumbnails are NOT showing up- instead there are larger pictures displayed (when image width and height are set to 80x120)
http://demo.asprunne...st.asp?a=return
if this is not possible, please explain how to make sure that without Aspjpeg component we can utilize asprunner to have thumbnails(already created in photoshop) being linked to the larger version via ibox??????????
thanks

The only way round this, is to create two field names where you store file names. One for thumbnail and one for bigger picture. On the listing page show the thumbnail an on the item detail listing page show the bigger picture only. On edit show both.

This is the only way round this as if you use larger pictures as thumbnails it will slow the site down.

I can live with this if it is for internal use, but if you have customers adding item they don't have a clue what to do.
I have made a request a few years ago but it has still not been implemented in the software. It got brushed under the carpet.

Not all ISP have aspjpeg installed, there is another variant on this which is also not supported by asprunner. So it would be better if it would be implemented and not restrict programmers.

Maurits,
could you clarify what exactly your request were?
The main issue is that ASP as a language doesn't have any image manipulation capabilities (PHP does though) and that's why we have to use third party components to generate thumbnails. ASPJpeg seems to be the most popular one and we have implemented it.
If you want to another component to generate thumbnails - you can do that as well. Yes, you will have to write BeforeAdd/BeforeEdit event code for this purpose. Probably purchasing $199 ASPJpeg component is a better solution.
Not really understanding what this complain is about.

Hello, I got installed (trial version) of aspjpeg 64 bit - it did not work(no matter what setting we tried to use), then I tried aspjpeg32 bit(default settings) and it worked (meaning that the ibox and the thumbnails were generated and displayed)
the only problem was that IE version 9 was not capable of displaying anything(no progress bar, no dragging feature and was not responsive to any clicks), only Firefox 18.0.1 was able to utilize my application.
now, my aspjpeg is 30 day trial, and it would be nice to know what exactly should we write in the before add/edit/list events so that we can utilize the program?
it should be fairly simple, I guess ?

I have had another dig about for ASP image resizing, I found this.
If your server supports ASP.net you could try this. Sample code available.
http://www.imageresizing.quickersite.com/index.html
Code has to be adjusted a bit, not tried it yet, but my server seems to cope with the VB.NET sample code and works with out the ASPJPEG component installed. Not had proper time to fully test it in ASPRUNNER.
If the sample works, see if we can use the trick to work in ASPRUNNER Classic, somewhere after/before record added.

The idea described at http://www.imageresizing.quickersite.com/index.html is pretty neat (and Pieter is a great guy overall).
Unfortunately there are quite a few issues here:

• your server needs to support ASP.NET. Not a big deal.
  
• this sample code doesn't create thumbnail files. It resizes images on the fly creating an adidtional load on the server. To make it work right you need to rewrite this code allowing to resize image right after they are uploaded. This might require a bit of additional setup - ASP.NEt account need to have WRITE permissions on the folder where thumbnails/images are stored
  
• since ASPX file is not a part of the main ASP application this adds an additional security concern meaning even users that are not authentication can execute this ASPX file.
  Anyway, this might a good workaround for internal applications. We'll see what we can do.