Menu

#203 Handling of large images, etc

workingwiki
open
nobody
None
5
2013-05-07
2012-08-10
No

Right now, large images are handled like other large files by GPF: it assumes you don't want to display them. Don't know if that is ideal.

Also (I guess this belongs on the same ticket), large files go to a "link" page rather than a "download" page – if you tried to display it directly, presumably you would prefer the download.

Finally (still the same ticket?), I thought we had agreed that the default for display=link would be make=later, but it's make=now.

Discussion

  • Lee Worden

    Lee Worden - 2012-08-10
    1. yes.

    2. yes, I think so.

    3. do you have any trace of those conversations? I think it would be easier than asking you to review the reasoning for me. (Also, I don't believe I've implemented later yet, so we only have yes and no.)

     
  • Jonathan Dushoff

    I remember them as verbal conversations. I don't think there's a lot of reasoning. The idea was just like the pdflink tags; if they're not being used now, we don't need to make them now unless the user specifically says so.

    The current make=true is "really" make=now, and make=false is "really" later. The makefile default link is "never", we should also have an "always", I guess.

    To be explicit, there are four possibilities (view with large tabstop) [reformatted - lw]:

    Make Now? | Make Later? | Names | ~~~~~~~~~
    --------- | ----------- | ----------------------- | ~~~~~~~~~
    N | N | never, makefile-default | ~~~~~~~~~
    N | Y | false, later | ~~~~~~~~~
    Y | N | true, now | ~~~~~~~~~
    Y | Y | always | ~~~~~~~~~

    I think now, never, always, later are the clearest names.

     

    Last edit: Lee Worden 2012-08-30
  • Lee Worden

    Lee Worden - 2012-09-06

    Would you happen to have examples of a big image and a big link-style file that I could use for testing?

     

Anonymous
Anonymous

Add attachments
Cancel