Oh, so given an ASP page, if the designer decides to rearrange the page, and say move a
table cell from one location to another, there is no way in which they could possibly
juxtapose some code that is dependant on the order of execution?
THEY DEFINITELY COULD - and I have seen this happen countless times. If a designer changes
some design in the ASP page, then not only the look and feel need to be tested, but also the
logic on the page!!! Why do you think that ASP.Net has been developed??? Even the monkeys at
Microsoft have acknowledged this as an issue.
Also, the designer working on an ASP page can only view the resultant HTML after running the
ASP code on a server. With XSL all they need is a few samples of resultant XML to apply the
XSL to, and they can easilt test their design.
(PS: The same is true for programmers screwing up the design in ASP pages when making
changes - a concession made since my wife is a designer and just kicked me;) )
Slashdot Mirror
iCanard??? I don't get it...
Oh, so given an ASP page, if the designer decides to rearrange the page, and say move a table cell from one location to another, there is no way in which they could possibly juxtapose some code that is dependant on the order of execution?
THEY DEFINITELY COULD - and I have seen this happen countless times. If a designer changes some design in the ASP page, then not only the look and feel need to be tested, but also the logic on the page!!! Why do you think that ASP.Net has been developed??? Even the monkeys at Microsoft have acknowledged this as an issue.
Also, the designer working on an ASP page can only view the resultant HTML after running the ASP code on a server. With XSL all they need is a few samples of resultant XML to apply the XSL to, and they can easilt test their design.
(PS: The same is true for programmers screwing up the design in ASP pages when making changes - a concession made since my wife is a designer and just kicked me ;) )