Jake, I understand where you're coming from. The source of the problem is, of course, that Domino is, at its heart, a means of getting Notes applications onto the web -- and Notes applications do not consist of storing or displaying reams of handcrafted HTML. The fact that you've led the charge to treat it as just another web platform doesn't change the basic premise of the system.
By the way, when did 32K of HTML at one go become acceptable? When I was your age, we got our HTML over 1200 baud connections on a good day, and we were thankful for it. Most of the time, we got the letters one at a time by semaphore from the top of the nearest mountain, and after we had parsed it and hand-written the pages with quill and ink, our fathers would beat us and send us to bed without supper.
As for alternating colours in the views (Marcin) -- the JavaScript onload is many, many times faster than the WQO option, and there's no comparison at all in terms of server hit. Using an agent to write the content of a view verbatim is unconscionable. Oh, and @DocNumber CAN'T be a "real number" -- it's just an incrementing service-time placeholder, and can conceivably be different on a given document for every single user of the database.
Jake, I understand where you're coming from. The source of the problem is, of course, that Domino is, at its heart, a means of getting Notes applications onto the web -- and Notes applications do not consist of storing or displaying reams of handcrafted HTML. The fact that you've led the charge to treat it as just another web platform doesn't change the basic premise of the system.
By the way, when did 32K of HTML at one go become acceptable? When I was your age, we got our HTML over 1200 baud connections on a good day, and we were thankful for it. Most of the time, we got the letters one at a time by semaphore from the top of the nearest mountain, and after we had parsed it and hand-written the pages with quill and ink, our fathers would beat us and send us to bed without supper.
As for alternating colours in the views (Marcin) -- the JavaScript onload is many, many times faster than the WQO option, and there's no comparison at all in terms of server hit. Using an agent to write the content of a view verbatim is unconscionable. Oh, and @DocNumber CAN'T be a "real number" -- it's just an incrementing service-time placeholder, and can conceivably be different on a given document for every single user of the database.