<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for vectomatic</title>
	<atom:link href="http://www.vectomatic.org/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.vectomatic.org</link>
	<description>standard dynamic 2D graphics in web browsers</description>
	<lastBuildDate>Fri, 23 Jul 2010 11:27:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>Comment on July release by Bret</title>
		<link>http://www.vectomatic.org/lib-gwt-svg/july-release/comment-page-1#comment-370</link>
		<dc:creator>Bret</dc:creator>
		<pubDate>Fri, 23 Jul 2010 11:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=480#comment-370</guid>
		<description>Lukas, this is a great library.  I have one question about your lib-gwt-svg example &quot;Events&quot; page.  This is the example with the circle and and the square that can be moved with the mouse.  If I add the following line after the square is created. 

      // rotate the square 45 degrees
      square.setAttribute(&quot;transform&quot;, &quot;rotate(45,40,40)&quot;);


How can I correctly handle the transform for setting the x and y to track the mouse?
    public void onMouseMove(MouseMoveEvent event) {
        if (dragging) {
            OMSVGPoint d = getLocalCoordinates(event).substract(p);
            square.getX().getBaseVal().setValue(x0 + d.getX());
            square.getY().getBaseVal().setValue(y0 + d.getY());
        }
        event.stopPropagation();
        event.preventDefault();
    }</description>
		<content:encoded><![CDATA[<p>Lukas, this is a great library.  I have one question about your lib-gwt-svg example &#8220;Events&#8221; page.  This is the example with the circle and and the square that can be moved with the mouse.  If I add the following line after the square is created. </p>
<p>      // rotate the square 45 degrees<br />
      square.setAttribute(&#8220;transform&#8221;, &#8220;rotate(45,40,40)&#8221;);</p>
<p>How can I correctly handle the transform for setting the x and y to track the mouse?<br />
    public void onMouseMove(MouseMoveEvent event) {<br />
        if (dragging) {<br />
            OMSVGPoint d = getLocalCoordinates(event).substract(p);<br />
            square.getX().getBaseVal().setValue(x0 + d.getX());<br />
            square.getY().getBaseVal().setValue(y0 + d.getY());<br />
        }<br />
        event.stopPropagation();<br />
        event.preventDefault();<br />
    }</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on June news by Ivar</title>
		<link>http://www.vectomatic.org/lib-gwt-svg/june-news/comment-page-1#comment-327</link>
		<dc:creator>Ivar</dc:creator>
		<pubDate>Tue, 29 Jun 2010 05:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=428#comment-327</guid>
		<description>I just found this library after having investigated a few options - most notably gwt wrapper projects for the raphaeljs library. I&#039;m not especially interested in the overhead of VML support so this looks very exciting!</description>
		<content:encoded><![CDATA[<p>I just found this library after having investigated a few options &#8211; most notably gwt wrapper projects for the raphaeljs library. I&#8217;m not especially interested in the overhead of VML support so this looks very exciting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vectomatic current state and future directions by admin</title>
		<link>http://www.vectomatic.org/svg/vectomatic-current-state-and-future-directions/comment-page-1#comment-265</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 20 May 2010 20:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=94#comment-265</guid>
		<description>I haven&#039;t written any code yet, I am focusing on lib-gwt-svg at the moment. But I have a few technical ideas on how it is going to operate.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t written any code yet, I am focusing on lib-gwt-svg at the moment. But I have a few technical ideas on how it is going to operate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vectomatic current state and future directions by Todd Terry</title>
		<link>http://www.vectomatic.org/svg/vectomatic-current-state-and-future-directions/comment-page-1#comment-264</link>
		<dc:creator>Todd Terry</dc:creator>
		<pubDate>Thu, 20 May 2010 09:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=94#comment-264</guid>
		<description>I see. Are you actively working on it? Do you already have something ready? :-)</description>
		<content:encoded><![CDATA[<p>I see. Are you actively working on it? Do you already have something ready? <img src='http://www.vectomatic.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vectomatic current state and future directions by admin</title>
		<link>http://www.vectomatic.org/svg/vectomatic-current-state-and-future-directions/comment-page-1#comment-255</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 15 May 2010 08:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=94#comment-255</guid>
		<description>If I were to keep on going with the same fundamental design decisions (use canvas, write every widget from scratch), the version 1 code would be an adequate foundation. But since I want to start on new bases (SVG, external widget library), I do not believe I will be able to reuse much of the existing code. For instance, with SVG I will not need to do my own picking or my own rendering; and if I use a third-party widget library, I will not have to write all this custom widget code, which is very time consuming.</description>
		<content:encoded><![CDATA[<p>If I were to keep on going with the same fundamental design decisions (use canvas, write every widget from scratch), the version 1 code would be an adequate foundation. But since I want to start on new bases (SVG, external widget library), I do not believe I will be able to reuse much of the existing code. For instance, with SVG I will not need to do my own picking or my own rendering; and if I use a third-party widget library, I will not have to write all this custom widget code, which is very time consuming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vectomatic current state and future directions by Todd Terry</title>
		<link>http://www.vectomatic.org/svg/vectomatic-current-state-and-future-directions/comment-page-1#comment-253</link>
		<dc:creator>Todd Terry</dc:creator>
		<pubDate>Fri, 14 May 2010 14:47:43 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=94#comment-253</guid>
		<description>Why the rewrite, is the current code base not stable enough or problematic in some areas? Going though the code it seems very well written, I&#039;m impressed.</description>
		<content:encoded><![CDATA[<p>Why the rewrite, is the current code base not stable enough or problematic in some areas? Going though the code it seems very well written, I&#8217;m impressed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vectomatic current state and future directions by admin</title>
		<link>http://www.vectomatic.org/svg/vectomatic-current-state-and-future-directions/comment-page-1#comment-252</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 14 May 2010 14:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=94#comment-252</guid>
		<description>Hi Todd,

Thanks for the encouragements. Actually, I am more thinking of a complete rewrite on a different basis (keep GWT, but use SVG + a yet to be determined UI toolkit). This is why I am developing lib-gwt-svg. I am currently refining this library and learning the ropes with simpler projects like lib-gwt-svg-edu and lib-gwt-svg-chess, but the idea is to get started on an actually usable / &quot;industrial&quot; vectomatic2 once these pieces are in place. 
Regarding version 1, my plans are to make just enough changes to keep it running and also fix bugs which always make a poor impression but I hope that by next year it can be replaced by the new version.</description>
		<content:encoded><![CDATA[<p>Hi Todd,</p>
<p>Thanks for the encouragements. Actually, I am more thinking of a complete rewrite on a different basis (keep GWT, but use SVG + a yet to be determined UI toolkit). This is why I am developing lib-gwt-svg. I am currently refining this library and learning the ropes with simpler projects like lib-gwt-svg-edu and lib-gwt-svg-chess, but the idea is to get started on an actually usable / &#8220;industrial&#8221; vectomatic2 once these pieces are in place.<br />
Regarding version 1, my plans are to make just enough changes to keep it running and also fix bugs which always make a poor impression but I hope that by next year it can be replaced by the new version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vectomatic current state and future directions by Todd Terry</title>
		<link>http://www.vectomatic.org/svg/vectomatic-current-state-and-future-directions/comment-page-1#comment-246</link>
		<dc:creator>Todd Terry</dc:creator>
		<pubDate>Thu, 13 May 2010 17:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=94#comment-246</guid>
		<description>Thanks for this editor, the code is pretty amazing. Are you planning on further developing/bugfixing it? It uses a lot of deprecated classes (mostly GWT 2.0 event handling) and undo is sometimes flaky. Cheers!</description>
		<content:encoded><![CDATA[<p>Thanks for this editor, the code is pretty amazing. Are you planning on further developing/bugfixing it? It uses a lot of deprecated classes (mostly GWT 2.0 event handling) and undo is sometimes flaky. Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on lib-gwt-svg goals and design by Allen Wu</title>
		<link>http://www.vectomatic.org/lib-gwt-svg/lib-gwt-svg-goals-and-design/comment-page-1#comment-116</link>
		<dc:creator>Allen Wu</dc:creator>
		<pubDate>Thu, 15 Apr 2010 13:11:39 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=248#comment-116</guid>
		<description>Dear Lukas,

Thank you very much for your advice which resolves my problem.

Best regards,

Allen Wu</description>
		<content:encoded><![CDATA[<p>Dear Lukas,</p>
<p>Thank you very much for your advice which resolves my problem.</p>
<p>Best regards,</p>
<p>Allen Wu</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on lib-gwt-svg goals and design by admin</title>
		<link>http://www.vectomatic.org/lib-gwt-svg/lib-gwt-svg-goals-and-design/comment-page-1#comment-114</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 14 Apr 2010 21:37:15 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/vectomatic/?p=248#comment-114</guid>
		<description>Allen,

I have done some research on this topic and here is what I have found out. It really boils down to what browser you are using. SMIL animation at this point is really work in progress on all browsers, except for Opera (the code I gave you fails in FF37a4 but actually does work in Opera10.10).

Your analysis is quite accurate, the fact that the instantiation fails on some browser comes from the fact that the browser either does not support the tag at all, or reports its javascript type incorrectly.
Here are the results of my tests (on Linux). There are 4 tags in SMIL animation. The following table shows the javascript type returned by the browser when you create the tag from script, using Document.createElementNS:

&lt;code&gt;Tag name                 &#124; animateMotion           &#124; animateTransform           &#124; animate           &#124; animateColor
Chrome 5.0.373.0 (44067) &#124; SVGElement              &#124; SVGAnimateTransformElement &#124; SVGAnimateElement &#124; SVGAnimateColorElement
Firefox 3.7 alpha4       &#124; Element                 &#124; SVGAnimateTransformElement &#124; SVGAnimateElement &#124; Element
Opera 10.10 (44067)      &#124; SVGAnimateMotionElement &#124; SVGAnimateTransformElement &#124; SVGAnimateElement &#124; SVGAnimateColorElement
&lt;/code&gt;

My advice to you is thus:

1. If you really want to use SMIL animation at this point, use Opera, as it seems to be the only browser which does it correctly.

2. To try to get the things to improve, you can report bugs to mozilla and webkit. For mozilla this is a bit early since they have never claimed to fully support SMIL animations at this point. I will file the bug though when they reach beta if things have not improved. I do not precisely know the status of SMIL in Chrome.

3. If you need to develop something today, you can do your own animation by combining the lib-gwt-svg and com.google.gwt.animation.client.Animation and changing the parameters of your SVG scene by code. I know this approach works since I use it in &lt;a href=&quot;http://www.vectomatic.org/lib-gwt-svg-edu&quot; rel=&quot;nofollow&quot;&gt;http://www.vectomatic.org/lib-gwt-svg-edu&lt;/a&gt; to animate my transitions

Regards
Lukas</description>
		<content:encoded><![CDATA[<p>Allen,</p>
<p>I have done some research on this topic and here is what I have found out. It really boils down to what browser you are using. SMIL animation at this point is really work in progress on all browsers, except for Opera (the code I gave you fails in FF37a4 but actually does work in Opera10.10).</p>
<p>Your analysis is quite accurate, the fact that the instantiation fails on some browser comes from the fact that the browser either does not support the tag at all, or reports its javascript type incorrectly.<br />
Here are the results of my tests (on Linux). There are 4 tags in SMIL animation. The following table shows the javascript type returned by the browser when you create the tag from script, using Document.createElementNS:</p>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">Tag name &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | animateMotion &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | animateTransform &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | animate &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | animateColor<br />
Chrome 5.0.373.0 (44067) | SVGElement &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| SVGAnimateTransformElement | SVGAnimateElement | SVGAnimateColorElement<br />
Firefox 3.7 alpha4 &nbsp; &nbsp; &nbsp; | Element &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | SVGAnimateTransformElement | SVGAnimateElement | Element<br />
Opera 10.10 (44067) &nbsp; &nbsp; &nbsp;| SVGAnimateMotionElement | SVGAnimateTransformElement | SVGAnimateElement | SVGAnimateColorElement</div></div>
<p>My advice to you is thus:</p>
<p>1. If you really want to use SMIL animation at this point, use Opera, as it seems to be the only browser which does it correctly.</p>
<p>2. To try to get the things to improve, you can report bugs to mozilla and webkit. For mozilla this is a bit early since they have never claimed to fully support SMIL animations at this point. I will file the bug though when they reach beta if things have not improved. I do not precisely know the status of SMIL in Chrome.</p>
<p>3. If you need to develop something today, you can do your own animation by combining the lib-gwt-svg and com.google.gwt.animation.client.Animation and changing the parameters of your SVG scene by code. I know this approach works since I use it in <a href="http://www.vectomatic.org/lib-gwt-svg-edu" rel="nofollow">http://www.vectomatic.org/lib-gwt-svg-edu</a> to animate my transitions</p>
<p>Regards<br />
Lukas</p>
]]></content:encoded>
	</item>
</channel>
</rss>
