Hi, Francis- | Thanks for the .js file. I will definitely use it if I take | to FireFox. My issue isn't that code can't be globally changed,
So, you've been given both the technical reasons and the easy solutions. Jim and I have provided you with simple workarounds for what you perceive as a "problem". In fact, none of this is new; I told you about the issue on your own svg-and-the-dom list *2 years* ago [1]. You were warned long before you created the content that you are now claiming FF breaks. So, obviously, this is not about technical issues, which is what this list is here to help authors and developers resolve. | my issue is the mentality of MOZ. If they can't work | with the needs of developers, and have, what I call, a | "validator" mentality, then I want nothing to with them. You know, if Adobe releases a new viewer, you're going to have to deal with this then. Since it will almost certainly use sXBL, it will have to be just as strict as MozSVG is now. | Creative developers have enough on their plate to deal with. Like what??? We *gave you the solution*!!! You don't have to deal with anything. It's done. | When the environment they choose is more focused on | strictness, and no,no's that can be handled easily by | intelligent programming on their part, taking the mundane | burden off the developer, As I demonstrated at length last night when I posed the AnthologyML use case, doing things the Right Way *is* taking the mundane burden off the programmer. It ensures that properly written code will work anywhere, and it provides methods to handle common use cases that would be hard or impossible otherwise, at the mere cost of 5 keystrokes. Pretty dang useful, IMO, and a good technical design and implementation. By the way, you still haven't fulfilled the challenge you asked for. But no need to, I deliberately presented you with a situation that explicates why we need namespaces. | then it tells me it is out of touch with reality, No..... | at least my reality:). Yes. In any case, it's clear that this is just an ego game with you, not a serious technical issue. Come on, get real! Stop complaining about silly crap, and get on board with helping create that future that you have so eloquently spoken of in the past. You're a creative guy, and I know you like to argue, but why not argue about real issues? How can you influence that future? By teaching newbies the correct way of doing things (rather than confusing them with extraneous nonsense), and by coding to standards, so that people can learn from you by example. That way, when users find your content in FF, it will work, and help show them how cool SVG is... otherwise, it will break, and people will dismiss SVG as buggy. Okay, I'm done arguing. If you're for real, you will take the message we've all been telling you to heart. If you are just here to mess with the community spirit, I won't play your game anymore. I will limit my comments to correcting the mistakes you tell newbies. [1] http://groups.yahoo.com/group/svg-and-the-dom/message/3 Regards- Doug [EMAIL PROTECTED] www.vectoreal.com ...for scalable solutions. ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/1U_rlB/TM --------------------------------------------------------------------~-> ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
