<div>Hi!</div>
<div> </div>
<div>It looks very cool, so please create a squeak package on squeaksource and assign me as developer!</div>
<div> </div>
<div>AFAIK Inline SVG hast too many drawbacks (especially on IE), so the main goal should be the rendering for linked SVG documents.</div>
<div> </div>
<div>BTW: Which version are you using!</div>
<div>I think it should be developed for Seaside 2.9!</div>
<div> </div>
<div>br</div>
<div> </div>
<div>Gerhard</div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 4/9/08, <b class="gmail_sendername">Lukas Renggli</b> <<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Holger,<br><br>Gerhard is also interested working on that. So I suggest that you<br>collaborate ;-)<br>
<br>> The first issue is the canvas. Subclassing the existing canvas seems to be<br>> a bad idea:<br>> - SVG has an extensive set of tags. Combining this with the extensive set<br>> of HTML tags will end up in one large bulky mess<br>
> - the SVG anchor has the same tag as the HTML anchor, but requires the<br>> xlink namespace for the href attribute, so it requires a different anchor<br>> brush<br>> - SVG and HTML cannot be freely mixed, so it's not necessary to combine the<br>
> both in a single class.<br><br>I suggest that you create your own "namespace" that you can retrieve<br>from the html canvas. This would be an object that knows the<br>underlying rendering context, but only has the SVG relevant methods.<br>
<br>So that you can write:<br><br> html svg line<br> from: 1 @ 1;<br> to: 100 @ 100<br><br>Or for embedded SVG rendering I imagine writing something like:<br><br> html svg: [ html renderSvgOn: html svg ]<br><br>
Where renderSvgOn: would look like:<br><br> renderSvgOn: svg<br> svg line<br> from: 1 @ 1;<br> to: 100 @ 100<br><br>> Currently, I've subclassed WACanvas, not WARenderCanvas. Rendering inlined<br>
> SVG will require switching the canvas. Currently I see no problems here, but<br>> maybe I'm wrong.<br><br>I think that's the way to go.<br><br>> Another issue is inlining SVG vs. separate SVG documents. Quite often I've<br>
> seen some caveats about inlining SVG (e.g. see<br>> <a href="http://wiki.svg.org/Inline_SVG">http://wiki.svg.org/Inline_SVG</a>). On the other hand, I see some disadvantages<br><br>I have no experience with that.<br>
<br>I think inlining seems simpler to start with. Have a look at the<br>#iframe brush to see how to create a specific document as part of the<br>page.<br><br>> Embedding with <object><br>> -----------------------<br>
> I've tried to implement rendering of external SVG documents that are<br>> included as <object> in the HTML document, and kind of succeeded:<br>><br>> <a href="http://www.smallish.org:7777/seaside/SVG/example">http://www.smallish.org:7777/seaside/SVG/example</a><br>
<br>Wow, that looks already very cool.<br><br>Cheers,<br>Lukas<br><br>--<br>Lukas Renggli<br><a href="http://www.lukas-renggli.ch">http://www.lukas-renggli.ch</a><br>_______________________________________________<br>seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br>