4 ms·

i appreciate you took the time to read through everything and respond so throughly, but you seem to be missing the whole point. you can try re-reading the comm

i appreciate you took the time to read through everything and respond so throughly, but you seem to be missing the whole point. you can try re-reading the comments on this thread but if you've never dealt with really rich javascript apps, i can see why this is hard to grasp.

mdg 17y ago
> i appreciate you took the time to read through everything and respond so throughly, but you seem to be missing the whole point. You are right, I do not understand why I would want to place CSS inside an object literal instead of just placing the CSS in a CSS file. >you can try re-reading the comments on this thread but if you've never dealt with really rich javascript apps, i can see why this is hard to grasp. Ok, I see (not in any order): 1. "Here, something like this already exists, see [link]" 2. "This wont work / This will be slow / What is the point of this" 3. "Server-side preprocessing already works" 4. You refuting anyone who disagrees with you.
- axod 17y ago
  "Server-side preprocessing already works" != Rich javascript apps.
  - mdg 17y ago
    The link makes no mention of RIA. Where were you going with this comment?
    - axod 17y ago
      Surely you can at least see the need for some easy to use styling in js? CSS is good for static content. It is pretty useless for dynamic webapps.
- JimBastard 17y ago
  How would you load that CSS file dynamically into your DOM? pretend you had 1,000,000 CSS classes that could be used in your one-page JavaScript application. you cannot load all of these with <link> on page load.......too much data.....you'd have to start dynamically loading .css files using AJAX requests......and you realize that dynamically inserting a <link> tag isn't cross-browser...so you try to parse the .css file in JS.....but then you realize that you have no way of natively parsing a .css file in JavaScript.....so you find / build a .css parser.....which is slow as balls.......then you want to start manipulating these classes and have no place to access them......so you have to store them in memory somewhere....might as well use nested JSON! pretend you didnt know what your CSS classes were going to be until run-time.....like creating dynamic DOM views based on user input.....you would have to store your CSS properties in memory regardless....might as well use nested JSON! pretend you had an entire javascript application stack and several tools for managing JSON documents on the server and the client..... if i'm refuting people who disagree with me....this is not my fault. i am simply responding to peoples comments and questions. i'm always open to insightful suggestions and recommendations..... edit: also i'd like mention your comment about line numbers is kinda silly.....i could just make it one line.....its JavaScript. i said 4 lines since it was : function declaration, for loop, if conditional one liner, else conditional one liner....... if you are really that upset about the line number count please let me know the correct amount of line numbers and i'll be sure to update my page
  - mdg 17y ago
    A million CSS classes? Is your "rich web app" even usable if it is going to be styled a million different ways? I hope you were exaggerating with that number. Are these real problems you face or are these just examples you make up because you (I assume you are the one who designed JSSS) have a solution looking for a problem?
    - JimBastard 17y ago
      i see you are incapable of understanding the word "pretend" or visualizing n-problem scenarios....if you still don't get it...i give up... and im using this code in production.....and its working out great......its a really simple concept.....

mdg 17y ago

> i appreciate you took the time to read through everything and respond so throughly, but you seem to be missing the whole point. You are right, I do not understand why I would want to place CSS inside an object literal instead of just placing the CSS in a CSS file. >you can try re-reading the comments on this thread but if you've never dealt with really rich javascript apps, i can see why this is hard to grasp. Ok, I see (not in any order): 1. "Here, something like this already exists, see [link]" 2. "This wont work / This will be slow / What is the point of this" 3. "Server-side preprocessing already works" 4. You refuting anyone who disagrees with you.

axod 17y ago
"Server-side preprocessing already works" != Rich javascript apps.
- mdg 17y ago
  The link makes no mention of RIA. Where were you going with this comment?
  - axod 17y ago
    Surely you can at least see the need for some easy to use styling in js? CSS is good for static content. It is pretty useless for dynamic webapps.
JimBastard 17y ago
How would you load that CSS file dynamically into your DOM? pretend you had 1,000,000 CSS classes that could be used in your one-page JavaScript application. you cannot load all of these with <link> on page load.......too much data.....you'd have to start dynamically loading .css files using AJAX requests......and you realize that dynamically inserting a <link> tag isn't cross-browser...so you try to parse the .css file in JS.....but then you realize that you have no way of natively parsing a .css file in JavaScript.....so you find / build a .css parser.....which is slow as balls.......then you want to start manipulating these classes and have no place to access them......so you have to store them in memory somewhere....might as well use nested JSON! pretend you didnt know what your CSS classes were going to be until run-time.....like creating dynamic DOM views based on user input.....you would have to store your CSS properties in memory regardless....might as well use nested JSON! pretend you had an entire javascript application stack and several tools for managing JSON documents on the server and the client..... if i'm refuting people who disagree with me....this is not my fault. i am simply responding to peoples comments and questions. i'm always open to insightful suggestions and recommendations..... edit: also i'd like mention your comment about line numbers is kinda silly.....i could just make it one line.....its JavaScript. i said 4 lines since it was : function declaration, for loop, if conditional one liner, else conditional one liner....... if you are really that upset about the line number count please let me know the correct amount of line numbers and i'll be sure to update my page
- mdg 17y ago
  A million CSS classes? Is your "rich web app" even usable if it is going to be styled a million different ways? I hope you were exaggerating with that number. Are these real problems you face or are these just examples you make up because you (I assume you are the one who designed JSSS) have a solution looking for a problem?
  - JimBastard 17y ago
    i see you are incapable of understanding the word "pretend" or visualizing n-problem scenarios....if you still don't get it...i give up... and im using this code in production.....and its working out great......its a really simple concept.....