+ Reply to Thread
Results 1 to 2 of 2

Thread: Weird coding/templating choices

  1. #1

    Question Weird coding/templating choices

    Hi all

    This is specifically addressed to the devs.

    I've noticed some weird choices in terms of coding/templating.
    Why, for example, would you choose to hide some html (using the class "hide" with "display: none") in some circumstances instead of simply not including the html in the generated code?

    In the "listing_details.tpl", for example, why write ...
    Code:
    Only registered members can view the code.
    ... instead of...
    Code:
    Only registered members can view the code.
    In the first case the html for the thumbnails is included in the page but hidden from view by using the class "hide".
    In the second case it is not included in the source code at all, hence making the generated code lighter and cleaner.

    P.S: I added the "$isLogin" because it appears that visitors that are not logged-in can only see 1 photo. (is this a setting that I missed?)

  2. #2
    Another example in the same file...

    Code:
    Only registered members can view the code.
    Why use a condition to check if photos are allowed and, if they are not, generate some html that will be hidden via the "hide" class?

+ Reply to Thread