Robin --- In [email protected], Robin Berjon <[EMAIL PROTECTED]> wrote: > andrewgirow wrote: > > If you mean that they overlap better that Don Demsak said? > > No, integrate. You just seem to have your own meaning of integrate that > doesn't cover other valid uses. > > > 2. Instead of integrating SVG amd SMIL animations such a way that SVG > > would deal with graphics and SMIL would deal with animations and > > time, the SVG INCORPORATED INSIDE (COPY AND PASTE AND CHANGE) Timing > > and Animation modules FROM SMIL. > > SMIL defines the way(s) in which host languages may use its features. > SVG complies to that. Not everything has been integrated yet, but it's > being done. I'm not sure you could've picked an example of a spec more > designed for reuse and integration that SMIL was -- you're proving my > very point here :)
Look, I am not a researcher, but programmer. In my world (programming) when you say *integrate* means that you use some API and *link* your code (SVG) to another code (SMIL). When you do * *copy � paste* of some of the code, that happened in SVG 1.2 I named it as *copy - paste*. Again, you might be right, its understanding of code and efforts reuse from the programmer point of view. Nothing more. Second, again from the programmer point of view when I have two modules: A and B and I read short descriptions like that: Module A: http://www.w3.org/Graphics/SVG/About "SVG is a platform for two-dimensional graphics. It has two parts: an XML-based file format and a programming API for graphical applications." Module B: http://www.w3.org/AudioVideo/ "The Synchronized Multimedia Integration Language (SMIL, pronounced "smile") enables simple authoring of interactive audiovisual presentations. SMIL is typically used for "rich media"/multimedia presentations which integrate streaming audio and video with images, text or any other media type." I never expect to find many parts of B module replicated in A. In the programmers world its called bad design of modules or they designed without looking at each other or without thinking how to use them together. Or they are not intended to use together from the begining. If you say that CDF will change this, it means that not only one person thinks that there is something wrong here. Best, Andrew Girow http://www.tinyline.com > > > 3. More the better... Later thinking that what was done it is not > > enought SVG INCORPORATED INSIDE video, audio and media elements from > > SMIL. (COPY AND PASTE AND CHANGE) > > Same as above. SMIL is designed to be integrated, SVG integrates more > and more of it as people feel increasingly confident that they can > implement the two together. > > > 5. You name it. I dont know what W3C will add during the next 2 > > weeks ;). May be its time to change the SVG to some more relevant > > name? May be XAML? > > SVG was probably not an excellent name choice, it wasn't done with > marketing thoughts to support it. As you will soon see in the output of > the CDF WG (called WICD so far), these specs were designed for > integration, and languages that know how to be hosted directly in a > foreign namespace (eg SMIL, XForms) is one of the approaches used for > that. I'm not saying there are zero issues -- otherwise there'd be zero > work going on -- but there's much more that works than doesn't work. > > -- > Robin Berjon > Research Scientist > Expway, http://expway.com/ ----- 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/
