On 4/19/05, Shihgian Lee <[EMAIL PROTECTED]> wrote: > > What you demonstrate here I would also argue is worse for page authors, > > who now have to be concerned with script writing as well as layout of > > simple HTML tags. You can argue that a page author would know > > Javascript as well, and you may be right in most cases, but the idea > > that everyone seems to be pushing is that the page authors should really > > be glorified graphics artists who just do markup and worry about layout, > > not code. That doesn't jive, to me at least, with the example you post. > > +1. I agree with Frank's point of view over Martin's. Usually in a > larger organization, you have to work with different groups of people > with different roles i.e. page authors/UI experts. Page authors/UI > experts don't have to know about scripting and just focus on page > layouts or usabilities. If you are in a smaller organization where one > person does it all, then that is fine. Frank's proposal adds great > values in the organization I am working in.
Glorified graphics artists do not do markup, they create nice mockups in Photoshop, which adore big bosses, who tell those unglofied ones to implement unearthy coolness in code. And those implementing this fancy stuff better know [at least about existence of] Javascript, XHTML, CSS, XML, DOM, XSLT, Flash and other buzzthings along with Photoshop. Those who do not know, create pages which look ok with single window and font size, at best. The separation between "server-side programmers", "Javascript coders" and "graphic artists" is a wrong thing. Ok, the initial visual design is done by artist in Photoshop, but everyting else is programmed. Javascript is the same part of the toolbox, as Struts tags or JDBC. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
