Brink Kale
Offline
Post: 53599077_121 created on Mon Nov 09, 2009 2:45 amPosted: Mon Nov 09, 2009 2:45 am
![]() |
I instantly understood why it worked from a theoretical point of view but, it took me at least a week to understand the concept (code-wise) as well as finding my own workarounds where necessary. At first I was under the impression that it was a sacrificial element that traded one ability vs the other (custom sections on Oldschool) but, after further understanding the code behind them both (once you get a good grasp on the custom sections, you start understanding hidden scrollbars so much better) I realized that my logic was flawed. xD In total, it took me about four or five months to come to terms with (what I would consider) a much better understanding of hidden scrollbars and the likes.
My question; "A horse walks into a bar . . ." Sorry, wrong question! D= My actual question is: Do you consider trying to learn the core of why different things work (yes this applies even in C.S.S)? For instance, if you found a code that does something that interests you. Do you only analyze the code itself or do you try to understand exactly what the code does and how it reacts in different environments? Would you try to simplify that code, strip it of excess elements and template it? Would you mind if people learned from your code, ceaselessly ripping it apart to satisfy their inner hunger for moar (once they credit you of course =D) and used it later in their own codes (commercial or personal)? |
|

















