On Sat, 06 May 2006 19:23:36 -0500, Robin Berjon <[EMAIL PROTECTED]>
wrote:
> A few small nits with the table of supported things:
>
> - the list of attributes is no disambiguated for those attributes
> that have the same name but different meanings depending on where
> they occur. For instance, there's "type: yes; type: no". In most
> cases it's clear, but in some (like the previous one) it's not.
Yes. We are still thinking about how we do this - suggestions for how we
should present the information welcome ;)
> - the list is clearly Full 1.1 related. What are your plans for
> Tiny 1.2, and if there are any can they be added to the list?
At some point we plan to implement 1.2 Tiny. But it is not our first
priority - our stated plan is 1.1 Basic.
> At the
> very least, and forgetting about the elements and attributes, adding
> the scripting interfaces in Tiny 1.2 to a browser would really kick-
> ass.
Well, for actual implementation plans you have to beg Erik and his team,
and they have to work within the constraints of Opera as a whole...
> Currently, those of us developing for those platforms have to
> jump through a few hoops to debug our content, and being able to do
> so in a browser would change our lives.
The error console (menu Tools -> Advanced -> Error Console) will tell you
assorted things about how to debug code, including SVG, CSS, Javascript
and XSLT. It's not a full debugging and development tool, but I find it
pretty useful.
> The delta is small, and easy
> to implement (much of it could be done in script actually, so I guess
> a user.js might handle it -- though it's of course better in the
> browser).
Feel free to write a user.js to prove it to us :)
> - do you have any specific plans in making some of these resources
> (fonts, gradients, filters, etc.) available from HTML, either as
> fills or as backgrounds?
>
> - supporting only text/ecmascript seems strange, I would assume you
> also plan to do the other variants, especially the non-deprecated ones?
These are really implementation plan questions that I probably can't
answer at the moment.
> - seeing your results against the SVG test suite, however short it
> is, would be nice.
Yes - it's just a question of time. Since we are in beta, and actively
working on the SVG support, that takes a higher priority. If anyone has
time to run a weekly against the test suite, that would be great, but we
are unlikely to have published results before Opera 9 final.
> But I'm picking nits really. Opera: you kick ass!
:) Thanks! (one ! :) ) The credit mostly goes to the implementors and
testers, although the support of people who have been developing SVG and
using or testing against Opera has also been important.
cheers
Chaals
--
Charles McCathieNevile [EMAIL PROTECTED]
hablo español - je parle français - jeg lærer norsk
Peek into the kitchen: http://snapshot.opera.com/
------------------------ Yahoo! Groups Sponsor --------------------~-->
You can search right from your browser? It�s easy and it�s free. See how.
http://us.click.yahoo.com/_7bhrC/NGxNAA/yQLSAA/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/
