08:30:13 RRSAgent has joined #svg 08:30:13 logging to http://www.w3.org/2010/11/05-svg-irc 08:30:15 RRSAgent, make logs public 08:30:17 Zakim, this will be GA_SVGWG 08:30:17 I do not see a conference matching that name scheduled within the next hour, trackbot 08:30:18 Meeting: SVG Working Group Teleconference 08:30:18 Date: 05 November 2010 08:30:25 scribe: anthony 08:30:29 scribeNick: anthony 08:30:34 chair: Erik 08:31:02 Present: Doug, Erik, Krisk, anthony, Adrian 08:31:18 Zakim, remind me in 8 hours about whatever 08:31:18 ok, ed 08:31:22 Present+ Patrick 08:31:26 Present+ Jun 08:31:40 minutes of html wg testing tf -> http://www.w3.org/2010/11/04-html-wg2-minutes.html#item04 08:31:54 Topic: Testing Strategies and Guidelines 08:32:25 AB: Above is the link to HTML WG discussion on testing 08:32:47 ... The discussion started with a description of the process we have been following 08:32:55 ... how people submit tests 08:32:59 ... someone reviews them 08:33:07 ... similar to SVG process 08:33:15 ... discussion on what tests have been submitted so far 08:33:22 ... currently organised by feature area 08:33:27 ... folders for each feature 08:33:43 ... goal of that was to avoid problems that happened in CSS where tests where 08:33:51 s/where/were/ 08:33:56 ... tied to parts of the spec 08:34:04 ... makes it difficult to change parts of the spec 08:34:10 ... They spoke about ref tests 08:34:13 ... and harnesses 08:34:21 ... it turns out there wont be a single harness 08:34:28 ... there may be several 08:34:36 ... There was discussion about templates 08:34:52 ... There'll be an inventory test file 08:34:56 ... that lists all the tests 08:35:05 ... and what the type the test is 08:35:13 ... and any extra data required to run the tests 08:35:25 ... that way people can build their own harness if they like 08:35:38 ... One of the other goals was that some people had 08:35:45 ... was the granularity of the tests 08:36:01 ... whether to have one test per file 08:36:21 ... or to have a test that tests a whole range of different things 08:36:55 ... There is a balance of how many assertions you should have in a test file 08:37:06 ... Common sense approach 08:37:15 ... if you see a test with lots of assertions 08:37:19 ... then it may need to be change 08:37:35 ... it will come down to the group consensus 08:37:41 DS: Probably a good balance 08:37:53 ... will be grouping tests 08:38:02 ... according to similar features 08:38:20 AB: There was an upper bound of features 08:38:26 ... that you wouldn't want to test in a single test file 08:38:30 ... the definition of what's a feature 08:38:34 ... is a bit vague 08:38:44 DS: When you're talking about scripted interfaces 08:38:49 ... All the interfaces of an element 08:38:59 ... might be a particular good way to go 08:39:09 AB: Have a number of tests of get element by class name 08:39:21 ... would make sense to bundle those together 08:39:27 KK: Depends on how deep you want to go 08:40:02 ... different APIs are more interesting 08:40:33 ... some methods need more in depth testing 08:40:36 DS: Point taken 08:40:47 ... May want to tests more variations 08:41:02 KK: Good start is one test for every method 08:41:05 ... that's a good coverage 08:41:16 AB: The next thing people talked about was 08:41:32 ... the difference between manual and automatic test 08:41:40 ... If it is possible to do an automated test 08:41:43 ... then it should be done that way 08:41:57 PD: Does that include static visual comparison? 08:42:08 KK: Had agreement that static content was visual 08:42:14 ... that there is a page with the reference 08:42:22 DS: You familiar with the SVG framework 08:42:25 KK: No 08:42:37 KK: The motivation is that, my point of view 08:42:49 ... the browser vendors have some information they can use there 08:43:04 ... there is a set of canvas tests that are rendering specific 08:43:08 ... but don't have reference tests 08:43:14 ... but they are able to use them 08:43:29 AB: So then we had some discussion about hosting the tests 08:43:35 ... on the test.w3.org 08:43:53 ... there are some tests that require a server side element to them 08:44:00 ... for example form submission 08:44:07 ... you need to check what submitted is the correct thing 08:44:16 ... and there was some discussion on how that would work 08:44:26 KK: For example if you're going to test cookies 08:44:31 ... or header of HTML page 08:44:42 ... want to change the header of cookies 08:44:52 ... which by default is not an option 08:45:01 AB: One thing which my apply to SVG 08:45:13 ... is the ability to send the information slowly 08:45:22 DS: Right, for resource doesn't come through 08:45:33 ... we talked this briefly in the web apps working group 08:45:44 ... for tests that need special server configuration 08:45:53 ... we need to let the systems team well ahead 08:46:03 ... we are testing these features 08:46:14 ... if we are going to have tests which are going to run server side tests 08:46:25 ... then they need to review that for performance and security 08:46:43 ... W3C and the systems team will accommodate these tests 08:46:49 ... just need to be careful 08:46:54 ... we just need to get in early 08:47:13 AB: People supported the idea of sharing these server side scripts 08:47:24 ... with other working groups 08:47:31 ... reduces the effort required by systems team 08:48:11 ... will avoid duplication and if you can create a test that uses existing script 08:48:25 KK: Because the cost is so high 08:48:39 AB: It was about people not having to waste time to create another test 08:48:46 ... around that frame structure 08:49:34 DS: We want a cohesive web platform 08:50:03 ... Adobe made something similar to XHR which was post XHR but before it was standardised 08:50:39 ... that's the sort of problem we can avoid by adopting a technology 08:50:58 KK: If you take a bet on a bleeding edge as your tests, you may get burned down the road? 08:51:11 DS: I'm taking about having tests as part of the specification process 08:51:29 ... there a some subtle things that tests will show up 08:51:42 ... what I'm saying is since we'll be looking at tests 08:51:49 ... we get a sanity check on the features 08:51:53 ... we should document that 08:52:00 ... in some obvious place 08:52:07 ... so people can reproduce that 08:52:22 ... maybe someone might find a flaw and help us correct it 08:52:48 .... W3C is examining what the role of tests are in the group 08:53:03 ... we don't want to do ISO conformance tests 08:54:09 KK: My point of view is that, if working group create a lot of tests 08:54:12 ... we run into these issues 08:54:15 ... in terms of scale 08:54:31 ... Paul says that XQuery had 18,000 cases, which is a lot of tests 08:54:41 ... so if working groups start to create a lot of tests 08:54:47 ... these are problems that will come up 08:54:53 PD: Problems? 08:54:55 KK: Scale 08:55:10 ... the SVG tests are about 4-500 you read the description 08:55:11 ... and run it 08:55:14 ... it's not a big deal 08:55:38 PD: My question is interoperability the goal or testing the goal? 08:55:48 DS: Our tests are simply to test the spec 08:55:54 ... to test the spec is implementable 08:56:04 ... W3C is looking at how we can best serve the web 08:56:57 ... All I'm saying we don't know where we go with the tests, but it looks like we are expanding the role of tests 08:57:36 PD: I'm trying to figure out the size of those 08:57:41 ... the level of coverage we want 08:57:45 ... how much coverage 08:57:54 ... maybe we just got to figure out where we want to go 08:58:16 AB: I think we need the coverage to ensure the spec has interoperability 08:58:28 ... The one other thing we had a discussion about 08:58:34 ... was the approval process 08:58:46 ... this really is on point on the discussion on size and scale 08:58:52 ... as the number of tests grows 08:59:16 ... the burden on the working group to review the tests 08:59:18 ... increase 08:59:26 ... because it is more work to review the tests then create it 08:59:43 ... and there was discussion about ways to short cut the process 08:59:58 ... for example if all the implementations pass the test and it's worng 09:00:00 Hyeonsoo has joined #svg 09:00:06 ... then it may mean that the spec should change 09:00:15 DS: We've run into this in the past 09:00:21 ... where we've found bugs in the spec 09:00:26 ChrisL has joined #svg 09:00:29 ... because of the tests we were writing 09:00:37 ... we understood the intent 09:00:45 ... that's one of the benefits of early testing 09:01:02 PD: One thing about developing early is aligning tests with a set of statements in the spec 09:01:30 A Method for Writing Testable Conformance Clauses and its Applications -> http://dev.w3.org/2008/dev-ind-testing/extracting-test-assertions-pub.html 09:01:31 AB: That was discussed briefly in HTML and people concluded that they wouldn't try to associate specific sections of the spec 09:01:54 ... it is often convenient to look at different parts of the spec for a test 09:02:23 PD: I'm talking more about having a rejection process rather than an acception process 09:02:31 AB: That's sort of the opposite end of the scale 09:02:57 ... assuming that the test is right until otherwise stated was also talked about 09:03:10 ... the problem with that model is you have a test suite of uncertain quality 09:03:18 ... which is the purpose of the test suite 09:03:25 ... is to test the quality of the spec 09:03:30 ... The other thing that people said 09:03:41 ... if you start by saying that if all implementations pass 09:03:46 ... and spec is wrong 09:03:51 ... what if 3 out of 4 pass 09:03:56 ... and 4th one does what the spec says 09:04:03 ... and the test is wrong compared to the spec 09:04:07 ... how does that work 09:04:14 ... and that is really where we left the discussion 09:04:25 ... is 3 out of 4 a good metric to pass the test 09:04:38 PD: We've come across that before as well 09:04:49 KK: Even if it s approved 09:04:57 ... there will be motivation to investigate that 09:05:06 ... someone will check the test and spec 09:05:18 ... the reality is the cost doesn't scale at all 09:05:31 ... and it effects things in a bad way 09:05:57 PD: Was there is there any discussion about adding resources from interest groups? 09:06:14 KK: People say 150,000 tests, but we'll see what happens right 09:06:18 ... it takes time to make tests 09:06:26 ... hopefully everyone contributes tests 09:06:38 ... I think that's just peoples guess about number of tests 09:06:48 DS: You could probably do a density test 09:07:05 dbaron has joined #svg 09:07:07 ... about conformance tests per page or assertion 09:07:15 PD: It's where they cross boundaries 09:07:44 ... and that's where the interoperability is 09:08:07 DS: I thought it might worth while automating this 09:08:14 ... and get the community to help review tests 09:08:23 ... set up an infrastructure 09:08:35 ... we're looking at how people can be part of W3C 09:08:44 ... if we can crowd source in test review 09:08:49 ... by providing incentives 09:08:59 ... I think the percentage of people that would want to do this 09:09:02 ... is small 09:09:07 ... because a lot of the time 09:09:18 ... people will look at tests for tutorials 09:09:34 ... for people doing development they are already looking at these tests 09:09:41 ... so in a way they are reviewing them 09:09:56 ... if a lot of people say this test is wrong 09:10:00 ... then we should look at it 09:10:09 ... and there's the opposite end of the scale 09:10:16 PD: I think the benefit is huge 09:10:23 ... is this goal or actual? 09:10:48 DS: We didn't get much interest from the browser vendors when we looked at this last year 09:11:00 ... but my idea was to set up a portal for people to submit tests 09:11:19 ... since we have a large community it is a way of overcoming the scaling problems 09:11:45 ... This seems to be a good opportunity across the board 09:12:07 PD: So now you have built this up in SVG and I think Erik seems to like it 09:12:23 DB: One thing I wonder about is if you're trying to crowd source reviewing for tests 09:12:28 ... what are you reviewing for? 09:12:38 ... there are a number of different things you are reviewing for in tests 09:13:01 ... this implementation is wrong, or the test is not testing things correctly 09:13:35 ... Depending on what you're reviewing for I'm somewhat skeptical 09:13:48 ... because it takes a lot of energy to review correctly 09:13:48 plinss_lyon has joined #svg 09:14:01 DS: Each test could have a thread in forum 09:14:08 ... for people to comment 09:14:28 ... we want to interact as low as possible to begin with 09:15:08 ... other people who know what they are doing can teach people 09:15:15 ... and if many people say this test is wrong 09:15:25 ... then it would be flagged 09:15:48 PD: There are a number of people in the SVG community who examine the tests very well 09:16:19 KK: I think crowd testing works if the work your asking for is simple 09:16:24 ... complex things will not get done 09:17:15 ... It'll required a lot of resources 09:17:56 DS: Just seeing what goes on in the SVG community has lead me to believe this might work 09:18:08 PD: Could be pilot in the SVG Working Group 09:18:53 DS: All I'm saying is there are number of people in the community to probably have this run in a forum 09:19:03 ... we might not get anything out of it 09:19:09 ... or it might turn into something we didn't expect 09:19:18 ... Patrick, you seemed to like the idea 09:19:24 ... so maybe we could pilot it 09:20:05 ED: We could test it to see 09:20:09 ... if there is interest 09:20:45 KK: What problem are you trying to solve? 09:20:57 DS: Get more tests possibly, more so sanity checking of the test 09:21:08 s/of the test/of the tests/ 09:21:24 ... There have been times where the test has gone through the review 09:21:53 ... and then we've looked it later and said this test is wrong 09:23:04 PD: John is going to help us get the transforms tests with help of Sandy and Anthony 09:24:08 ACTION: Doug to Talk with Patrick and Erik about crowd sourcing test reviewing and figure out how to set it up 09:24:09 Created ACTION-2897 - Talk with Patrick and Erik about crowd sourcing test reviewing and figure out how to set it up [on Doug Schepers - due 2010-11-12]. 09:24:39 ED: Just curious about the strategy to take to write the tests 09:25:05 AB: The web apps working group is looking at using what has been established by the HTML working group 09:25:12 ED: I've looked at that 09:25:27 ... and we are using the framework on two of the tests 09:26:01 KK: The belief in the HTML working group is you can use these are reference tests 09:26:54 ... I think SVG is really complicated in these requirements 09:27:00 ... with the reference tests 09:27:19 DS: Jonathan Watt has been looking at automating these tests as much as possible 09:27:29 rrsagent, make minutes 09:27:29 I have made the request to generate http://www.w3.org/2010/11/05-svg-minutes.html adrianba 09:28:13 ED: So we are already using things similar to ref tests 09:28:24 KK: CSS also has similar things with their tests 09:28:34 ... they have a hard time running the test suite 09:29:13 PD: Do we have a way to create an automatic testing harness with Canvas 09:29:40 DS: Where we are right now - we are working on tests for SVG 1.1 2nd edition 09:29:50 ... just cleaning up the spec that came out in 2001 09:29:57 s/using things similar to ref tests/using techniques similar to ref tests in some of the tests/ 09:30:11 ... We have improved and included a lot of tests we had originally 09:30:23 ... not to make work for ourselves than we can handle 09:30:36 ... it's meant to get everyone up to speed 09:30:40 ... and then move on 09:30:43 ... for SVG 2 09:30:45 ... for the modules 09:31:03 ... we see a large benefit of using the HTML working group frame work 09:31:12 ED: Is there a process for putting tests there? 09:31:19 ... is that something we need to decide to do? 09:31:42 DS: We would like to port our tests over that framework 09:31:58 AG: So where do I stick the tests that we make for Transforms? 09:32:29 KK: So the new tests would be made in mercurial 09:33:22 PD: We should get a proposal on what the categories for the spec are 09:33:29 ... here is a functional area 09:33:35 ... that makes a complete scenario 09:33:56 ... and agree that these are the features that are ok 09:34:26 KK: If you want to do all the tests at the end you have to pick chapters 09:34:28 ... if you're not 09:34:35 ... you're going to have pick a feature 09:34:53 PD: If you were to have tests on transforms 09:35:12 ... would you have tests on different features, like transforms on video, shapes, etc 09:35:44 AB: You say things like, in order to run these tests you need certain things to be implemented 09:36:06 ... lets not try and branch out too much on the requirements 09:37:11 KK: If you always try to keep your dependencies as low as possible then you don't run into risks 09:37:15 ... then build up on it later 09:41:09 RESOLUTION: Anthony continues writing CSS Transforms spec with tests, works with JohnJ and Sandro from MSFT to add more tests to the Mercurial server. In parallel, Doug, Erik and Patrick will explore sourcing resources through the community 09:41:57 rrsagent, make minutes 09:41:57 I have made the request to generate http://www.w3.org/2010/11/05-svg-minutes.html adrianba 09:42:17 action: to: shepazu to start conversation with Simon Willison to understand how to kick start a wide sourcing project 09:42:17 Sorry, couldn't find user - to 09:42:25 RESOLUTION: Anthony continues writing CSS Transforms spec with tests, works with JohnJ and Sandro from MSFT to add more tests to the Mercurial server. In parallel, Doug, Erik and Patrick will explore sourcing resources through the community 09:42:30 action:shepazu to start conversation with Simon Willison to understand how to kick start a wide sourcing project 09:42:46 action: shepazu to start conversation with Simon Willison to understand how to kick start a wide sourcing project 09:42:46 Created ACTION-2898 - Start conversation with Simon Willison to understand how to kick start a wide sourcing project [on Doug Schepers - due 2010-11-12]. 09:43:24 DS: I think there is value in having people go from the spec to the tests and the tests to the spec 09:43:29 AB: You're right it would be useful 09:43:39 A Method for Writing Testable Conformance Clauses and its Applications -> http://dev.w3.org/2008/dev-ind-testing/extracting-test-assertions-pub.html 09:43:42 ... but the maintenance would be expensive 09:44:08 DS: This is something that the widgets web apps group came up with this methodology 09:44:15 ... so that you could easily mark up the spec 09:44:25 ... so you could easily find testable assertions 09:44:27 Hyeonsoo has joined #svg 09:45:49 AG: Done this with compositing 09:45:50 http://dev.w3.org/SVG/modules/compositing/master/Overview.html 09:46:02 Hyeonsoo has joined #svg 09:46:26 DS: I wasn't suggesting that we hard code links between tests and particular parts of the spec 09:46:33 ... just that there may be intermediary thing 09:46:39 ... could be a manifest or index 09:46:46 ... for tests to assertions 09:46:54 AB: Sure 09:46:59 ... it would certainly be helpful 09:47:07 ... and would be demonstrating to the director 09:47:15 ... that you can map assertions and test cases 09:48:19 KK: Assertions seem like they are the bare minimum 09:48:27 ... in some cases you need to combine them 09:50:59 Hyeonsoo has left #svg 09:51:01 Hyeonsoo has joined #svg 09:51:31 DS: I was going to suggest we (SVG Working Group) consider adopting the assertion conformance markup for we write specs 09:51:41 ... or something along those lines 09:51:52 ... and how we can approve the testing frame work 09:52:29 KK: For SVG 2 you will move to Mercurial? 09:52:32 DS: Yes 09:53:13 http://dev.w3.org/SVG/modules/integration/SVGIntegration.html 09:54:20 DS: [gives history of integration spec] 09:57:53 action: pdengler to help shepazu drive SVG "Integration" specification to editors draft 09:57:53 Created ACTION-2899 - Help shepazu drive SVG "Integration" specification to editors draft [on Patrick Dengler - due 2010-11-12]. 10:01:11 [break] 10:02:04 rrsagent, make minutes 10:02:04 I have made the request to generate http://www.w3.org/2010/11/05-svg-minutes.html adrianba 10:07:47 hidetaka has joined #svg 10:17:54 dsinger has joined #svg 10:29:46 jun has joined #svg 10:32:38 scribeNick: PDENGLER 10:34:21 topic: Implementation Report 10:35:26 pdengler: We have the updates that were requested of us through various threads are being delivered today, including renames 10:35:43 pdengler: I will work with Erik to get those deliverables to him directly to make sure our renaming is done correctly 10:36:41 ed: Did this include a change to the implementation report page 10:36:48 pdengler: I am not sure it did, but I will find out shortly 10:37:36 pdengler: Based upon where we landed, the minimal adjustments we would want to make is a sort on test name to make it clearer to developers which features were available across browsers 10:38:22 ed: Do you have the full run of IE9 10:38:47 pdengler: No, but le me get you a date, it shouldn't take that long. 10:39:17 ed: I've been going through the approved harness and fixing a bunch of issues. So some of the revision numbers are not correct (fixing reference images) 10:39:26 jun has joined #svg 10:40:45 pdengler: Chris is still doing a handful of WOFF fixes still. 10:41:22 topic: last call issues 10:41:33 ed: Should we try to distirubte the actions to get them done more quickly 10:41:51 http://www.w3.org/Graphics/SVG/WG/track/products/24 10:43:36 ed: We could discuss the filter bias property. Hardly any impelmentations do anything with this feature. And there is no test right now 10:43:55 ISSUE-2335? 10:43:55 ISSUE-2335 -- Last Call Comment: Clarify feConvolveMatrix bias property -- raised 10:43:55 http://www.w3.org/Graphics/SVG/WG/track/issues/2335 10:45:34 ed: The issue is that it is not useful the way it is specified. But no one implements this yet. 10:47:17 actoin: anthony to investigate support for bias in cannon impelmentation 10:47:29 action: anthony to investigate support for bias in cannon impelmentation 10:47:30 Created ACTION-2900 - Investigate support for bias in cannon impelmentation [on Anthony Grasso - due 2010-11-12]. 10:49:03 ed: Proposal is to agree with the discrepency and push the claridication/correction into SVG 2.0 depending upon Anthony's report 10:49:56 ed: (looking through LC issues) 10:50:39 http://www.w3.org/Graphics/SVG/WG/track/issues/2340 10:52:07 ed: This one is already resolved by ChrisL's check in. 10:54:04 ed: We would benefit from load balancing the remaining LC issues 10:59:15 action: ed to send out reminder mails to resolve issues; consider establishing delivery dates 10:59:15 Created ACTION-2901 - Send out reminder mails to resolve issues; consider establishing delivery dates [on Erik Dahlström - due 2010-11-12]. 11:01:35 jun has joined #svg 11:07:06 [lunchbreak] 11:08:55 jfkthame_afk has left #svg 11:59:49 jun has joined #svg 12:01:36 anthony has joined #svg 12:09:44 Hyeonsoo has joined #svg 12:12:19 pdengler has joined #svg 12:14:41 scribe: anthony 12:14:45 scribeNick: anthony 12:14:55 present+ Hyeon 12:15:49 Topic: Establishing high level scenarios for SVG 2 12:16:13 PD: Are we going to be able to land a set of specs and tests 12:16:22 ... that says this is how CSS applies to SVG 12:16:30 ... don't really care about how it's done 12:16:35 ... but that's a goal in mind 12:16:41 ED: Yes 12:16:48 ... that's the Integration specification 12:17:08 PD: If our deliverable is Integration spec 12:17:19 ... and we make any necessary updates as CSS integration is done 12:17:29 ... then I think it is a matter of setting dates 12:17:50 ... that we have to be aggressive about 12:18:02 Hyeonsoo has joined #svg 12:18:41 DS: I'm curious about being realistic about things 12:18:49 ... are there some deadlines that we have to meet? 12:18:58 ... for example Tiny 1.2 ran to a hard deadline 12:19:09 ... because of the JIS group wanted to standardise it 12:19:21 ... and needed it to be done by Dec 12:19:28 ... are there implementation hard deadlines 12:21:06 ... I would like to know what the time lines are from the different browser vendors 12:21:15 shepazu has joined #svg 12:25:09 PD: Willing to add extra resources if that is want is needed 12:25:14 DS: Testing is a big task 12:25:26 PD: One thing I can help do at least is help people get through specs 12:27:22 Topic: Time lines 12:27:48 PD: High level time frame is say June 2011 12:28:18 ... stable specs for Transforms 2D and 3D (CSS/SVG) 12:29:04 ... Filters, Gradients (lower priority), Animations, SVG Integration 12:30:20 JF: Our priority is 2D/3D Transforms and Gradients 12:30:48 PD: Anthony working on Transforms and Gradients, Doug on Integration 12:31:11 ... myself on Animation and Erik on Filters 12:31:18 DS: I am interested in animation 12:32:05 AG: We'll also have help from other people in other groups as well 12:32:12 ... Dino, Simon Frazer 12:32:26 DS: I would also really like to have Adobe in on the conversations about Animation as well 12:33:39 ... and I'm concerned about is having the authoring tools 12:34:20 AG: It would be good to have Alex D in the discussions as well 12:34:27 DS: And Vincent Hardy 12:35:50 myakura has joined #svg 12:37:59 ... I want to have some concept of state in animation 12:38:19 ... If I say have a button and I would like to have two different things happen depending on if it is on or off 12:38:38 ... Just some simple concept of state 12:39:22 http://www.w3.org/TR/2009/WD-SVGCompositing-20090430/ 12:39:29 AG: SVG Compositing is ready to go 12:39:44 ... so may as well do it as well 12:39:57 DS: I'm really concerned with the DOM 12:39:59 ED: Me too 12:40:02 ... it's on my top list 12:40:12 DS: The DOM is very inefficient 12:40:27 ED: I'm interested in the simplifications 12:40:32 ... to make it easier to use 12:40:53 AG: Similar to uDOM? 12:41:05 ED: More so about simplifying base value 12:41:06 http://www.w3.org/Graphics/SVG/WG/wiki/Simple_SVG_API 12:42:04 hidetaka has joined #svg 12:42:24 DS: I don't want to bother with insertAt 12:42:37 ... like if you don't give it anything it just appends it 12:42:43 http://www.w3.org/Graphics/SVG/WG/wiki/images/6/64/SVGCSSTPAC.pdf 12:44:33 http://www.w3.org/Graphics/SVG/WG/wiki/SVG_2_DOM 12:44:55 PD: On page 6 12:45:01 ... there's the puts 12:45:12 ED: One of the things suggested already 12:45:25 PD: Only trick is that it returns a string when you query the base value 12:45:30 ... it returns it a string 12:46:02 ... the only issue is if you use the set-er you have to change the unit type 12:46:24 ... so if I set the string with rect = px then you have to make it to be that 12:46:30 ED: Depending on what you get as the input 12:46:36 ... there is a function like that 12:47:05 ... for me it's more about aligning with the DOM core 12:47:17 ... it is easy and left the old ones as aliases 12:47:28 ... we had to add more code to do the array syntax 12:47:38 PD: I would love to have this as something we solve 12:49:11 DS: We should remember we have Cameron in the group 12:49:18 ... and he is good with the IDL stuff 12:50:49 PD: I would like to add the DOM fixes to that urgent push 12:53:31 AG: Could probably get Cameron to do that if he's interested 12:53:36 DS: I'd be interested as well 12:53:41 PD: What's the work? 12:53:45 ED: Not much work I think 12:53:55 PD: Whatever work needs to be done or think needs to be done 12:54:10 ... should ask him if he thinks it could be done 12:54:59 ... I'm thinking about if people can code against the HTML DOM will be able to code against the SVG DOM 12:55:25 homata has joined #svg 12:55:28 las 12:56:06 ACTION: Doug to Coordinate with Cameron to scope SVG DOM simplifications and establish a spec with a delivery date 12:56:06 Created ACTION-2902 - Coordinate with Cameron to scope SVG DOM simplifications and establish a spec with a delivery date [on Doug Schepers - due 2010-11-12]. 12:57:32 tbah has joined #svg 12:59:33 ED: Only concern I guess is we will be done with 1.1 12:59:41 ... and we will have to add the dates to the charter 12:59:54 Zakim, call Saint_Clair_3B 12:59:54 sorry, shepazu, I don't know what conference this is 13:00:13 ED: How long does the charter have to go? 13:00:20 DS: 2 years 13:00:21 Zakim, room for 2? 13:00:22 ok, shepazu; conference Team_(svg)13:00Z scheduled with code 26633 (CONF3) for 60 minutes until 1400Z 13:00:34 Zakim, call Saint_Clair_3B 13:00:34 ok, shepazu; the call is being made 13:00:35 Team_(svg)13:00Z has now started 13:02:21 How does one call in? 13:02:27 Zakim, who's here? 13:02:27 On the phone I see no one 13:02:28 On IRC I see tbah, homata, hidetaka, myakura, shepazu, Hyeonsoo, pdengler, anthony, jun, RRSAgent, fantasai, anthony_work, karl, ed, trackbot, heycam, Zakim 13:03:46 dsinger has joined #svg 13:05:02 adrianba has joined #svg 13:08:21 Zakim, whos' here? 13:08:21 I don't understand your question, ed. 13:11:55 Zakim, who's here? 13:11:55 On the phone I see no one 13:11:56 On IRC I see adrianba, dsinger, tbah, homata, hidetaka, shepazu, Hyeonsoo, anthony, jun, RRSAgent, fantasai, anthony_work, karl, ed, trackbot, heycam, Zakim 13:22:32 ChrisL has joined #svg 13:22:58 Topic: coons patches / gradients 13:23:00 http://tavmjong.free.fr/SVG/MESH/Mesh.html 13:23:19 TB: Link to a webpage I've prepared 13:23:35 ... The motivation method is they are useful to producing vector art 13:23:45 ... and we also get discussions similar to this on the mailing list 13:23:51 ... there are 4 types 13:23:56 ... gradients I could find 13:24:01 ... they are listed 13:24:17 ... [goes through different gradient types in paper] 13:24:29 ... we've been talking through mostly coons patch gradients 13:25:04 ... one thing you can do with coons patch gradients 13:25:08 ... is emulate other gradients 13:25:36 ... There's a four point coons patch gradient 13:25:43 ... couldn't find anywhere this is used though 13:26:22 ... One thing I noticed looking on the web, is the patches are always done with a rectangular grid 13:27:00 ... One problem is you can fold it on top of itself 13:27:18 ... and so if you have a sharp turn in curve and it has transparency 13:27:23 ... could be problems 13:27:43 ... so putting this in SVG is defining how you would render this 13:28:01 ... each patch shares two colours and one bezier path 13:28:12 ... you can zig-zag your patches along 13:28:26 ... existing SVG gradients there are linear and radial 13:28:32 ... and they have stops 13:28:39 ... which doesn't really fit with coons patches 13:28:49 ... because the colours are defined in the corners 13:29:10 ...The mesh is defining the shape of the object 13:29:21 CL: You could use the shape as a clipping path 13:29:27 TB: You could do that 13:29:34 ... but they are not used like that in the wild 13:29:48 ... you're interested in taking the grid and deforming it to fit with a shape 13:29:58 ... essentially it already is being self clipped 13:30:09 ... There is one case where you would want to fill it an object 13:30:18 ... and that's when you would do that with conical gradients 13:30:36 ... You set up a rectangular grid 13:30:59 ... It seems like a good idea to set up the gradient like a grid 13:31:05 ... Illustrator seems to do this as well 13:31:52 ... So go along the rows 13:31:56 ... which define the sides and colours 13:32:01 ... in the corners 13:32:12 ... The coon patches are defined in terms of bezier curves 13:32:19 ... Could use other paths 13:32:34 ... and use approximations to bezier curves 13:32:46 ... I've listed there one possible syntax 13:33:25 ... Divide and conquer method could be used to render it 13:33:47 ... There is an experimental Cairo implementation that implements this 13:34:04 ... using Forward-rasterize 13:34:19 ... Jasper replied back with some comments 13:35:00 ... he gave me an example 13:35:03 ... where you have a gradient 13:35:11 ... and you map those using a transform function 13:35:15 ... to a mesh gradient 13:35:40 CL: On the top left patch 13:35:59 ... you have to have 3 points on subsequent squares 13:36:16 ... just wondering how this would work if you animated it 13:36:23 ... or edited it through script 13:36:42 DS: It almost seems there is some relationship between tiling and super paths 13:36:51 TB: I'm not sure it's something you would animate 13:37:12 ... It's quite a bit a work, and why you'd want to animate it 13:37:24 DS: If you gave this to David Daley he'd animate it 13:37:31 ... because he looks for cool stuff 13:37:42 ... If someone had a particular goal in mind 13:38:07 ... We do have consider animation 13:38:42 ... One concern I have is with conflating the paint sever with the mechanices 13:38:46 ... of the shapes 13:38:55 ... the actual geometry of the shape 13:39:02 ... One thing I don't like about Diffusion Curves 13:39:09 ... if you look at the lines that are being defined 13:39:16 ... there's no shape you are clicking on 13:39:29 s/mechanices/mechanics/ 13:39:40 TB: You do have the outer bezier curve defining the shape 13:40:09 AG: I think any gradient extensions we add should be a paint server 13:40:15 ... otherwise you break the model 13:40:40 CL: I can imagine that ball effect you have there 13:40:42 ... with the lighting 13:40:50 ... that you'd want to animate that 13:41:13 TB: Getting this drawn is a lot time by hand 13:41:36 ... I can understand what you want to do and it would be great if you could do that 13:41:49 ... most people are not going to do these things by hand 13:42:15 ... I wanted to do something more complicated than sphere 13:42:18 ... just didn't have more time 13:42:32 DS: I think it's great you spent the time in putting this together 13:43:05 ... The first image I looked at made me think they are limited 13:43:15 TB: I wasn't able to do complicated drawings 13:43:25 ... but you can find complicated examples of their usage on the web 13:43:44 adrianba has joined #svg 13:43:48 http://www.khulsey.com/adobe_illustrator_gradient_mesh.html 13:44:07 CL: I means that the authoring tool is needed to do this 13:44:10 ... because if you pick up a point 13:44:18 ... you'll need the tool to move other points 13:44:22 TB: You could animate it 13:44:26 ... but it is not trivial 13:44:39 http://en.wikipedia.org/wiki/File:Phong-shading-sample.jpg 13:44:47 CL: Did you see anyone using phong shading meshes instead 13:44:56 ... If you follow the link there 13:45:08 ... you'll see the same mesh using two different methods 13:45:14 http://en.wikipedia.org/wiki/Phong_shading 13:45:17 ... the phong shading is much smother 13:45:25 ... because you are interpolating the normals 13:45:38 ... the reason that came up and we tried using tri-mesh 13:45:52 ... using Gourand shading 13:45:57 ... and it didn't look smooth 13:46:06 s/smother/smoother/ 13:46:38 ... It's used a lot in 3D (Gourand) shading 13:46:45 ... as a step up from wire frame 13:46:55 ... then you apply phong shading and it looks real 13:47:03 ... which means there is hardware support for both 13:47:21 ... The coons patches are cool but they are all done in an authoring tool 13:47:26 ... and then rendered in software 13:47:48 TB: A triangle mesh you could animate each point 13:48:44 CL: The Triangle mesh proposal I made in terms of animation was easy to animate 13:49:59 coons patches are on the cairo to-do list 13:50:04 TB: So animating triangles is kind of a problem 13:50:12 http://cairographics.org/todo/ 13:50:19 CL: I see Coons patches are on the Cairo to-do list 13:50:21 TB: Yes 13:50:28 ... it's experimental at the moment 13:50:36 ... and there are a couple of examples they have there 13:50:40 ... might not be the best implementation 13:50:45 ... but there is at least a sample 13:51:26 ED: From analysing this, did you look at what PDF are doing with this? 13:51:38 TB: Yes, PDF and postscript are doing something exactly the same 13:51:45 ... and you can add on a new patch one at a time 13:52:00 ... you can zig-zag them back and forth 13:52:15 ED: Well where do we want to go with this? 13:52:26 CL: The question is it supported by libraries 13:52:33 ... and does it give us what we want 13:54:23 ... My concern is it requires an authoring tools as well 13:55:48 other method - http://graphics.cs.uiuc.edu/~tianxia/pdfs/imgvect_preprint.pdf 13:56:52 TB: Animations aside, using this method you can produce life like images 13:56:58 AG: There are other methods out there to produce life like images as well 13:57:03 ... such as Diffusion Curves 13:58:32 TB: Looks like they are doing triangle beziers on the side 13:59:40 AG: I think it is worth having some use case and requirements 14:00:22 JF: We should study available methods 14:00:33 ... some methods can be used on a wide range of images 14:00:47 ... and some methods can be applied to a particular type of image 14:00:58 ... so we need to know the requirement 14:04:25 trackbot, status 14:05:37 ACTION: Tavmjong to Work with Tab Atkins on gradient extensions use case and requirements 14:05:37 Created ACTION-2903 - Work with Tab Atkins on gradient extensions use case and requirements [on Tavmjong Bah - due 2010-11-12]. 14:06:21 ED: Thanks Tav for doing the work 14:06:34 Team_(svg)13:00Z has ended 14:06:36 Attendees were 14:38:51 cslye has joined #svg 14:51:02 jun has joined #svg 14:53:54 scribe: ChrisL 14:54:06 topic: retrospective on 2010 14:54:27 cl: problem was shrinking below critical mass, too few members to do the work 14:54:48 ... and also not knowing that going to LC means we had to go to CR and PR, not PER 14:55:08 ... lots of work n 1.1SE test suite, much better, but was this the best time to do it 14:56:21 ds: inevitable the way it happened, microsoft was not prepared to be takling 2 for excample, so focus was on 1.1 14:56:39 ... now we have a broad interop o 1.1 features, so optimal time to move to svg 2 14:56:58 ... we have buy-in now 14:57:53 cl: great to have cam back 14:58:22 erik: yes, you can see commits from cam as soon as he came back 15:00:36 cl: spoke to suresh about wildfox joining svg wg 15:01:29 (discussion on assorted svg-related hiring opportunities we notice) 15:03:24 ds: moving to one telcon a week, proposed by heycam 15:03:36 ... but need to be more active on the list 15:05:28 Resolved: one telcon a week on Thursday 15:07:47 ag: happy to be an hour earlier, may be better for patrick too 15:07:57 erik, chris: better for us 15:08:04 ag: ok for heycam? 15:08:43 ... better in nz 15:09:09 proposed: one hour earlier for svg 15:10:01 action: erik to mail wg proposing new time 15:10:02 Created ACTION-2904 - Mail wg proposing new time [on Erik Dahlström - due 2010-11-12]. 15:26:14 (discussion on svg meeting in tokyo co-located with css wg meeting in June 2011) 15:42:07 ed: need to get milestone dates for the next charter, so we need to decide on priorities 15:44:41 ds: will put those dates in the charter 15:46:51 ed: don't want svg 2 to be a 1.3 with minimal changes 15:46:57 ds: animation will be better 15:47:10 ed: great, but nt really a new feature 15:48:04 ed: the name has already stuck 15:48:12 ag: will have new stuff in it 15:48:42 ed: don't mind if there are many new modules and svg2 is a good feature set, moving modules ahead at their own page 15:48:54 ... at soe point we still need to group the together 15:49:06 ag: though we said a year afte rthat, so June 2012 15:49:16 s/soe/some/ 15:49:16 s/page/pace/ 15:52:02 s/though/thought/ 15:52:15 s/afte rthat/after that/ 15:52:21 cl: modules move based on their effort, degree of developer interest, and trest suite status 15:52:42 s/what i typed/what I meant/ 15:54:42 ds: are we going to include modules byreference or by inclusion? 15:56:10 cl: joint specs, so we clearly need to do it by reference 15:58:31 (discussion on how best to reftest features like filters; how to avoid platform differences in text antialiasing etc) 16:01:31 cslye has joined #svg 16:03:12 action chris to add Helder missed issues to LC tracker 16:03:13 Created ACTION-2905 - Add Helder missed issues to LC tracker [on Chris Lilley - due 2010-11-12]. 16:03:31 http://lists.w3.org/Archives/Public/www-svg/2010Aug/0009.html 16:03:40 http://lists.w3.org/Archives/Public/www-svg/2010Aug/0014.html 16:03:49 http://lists.w3.org/Archives/Public/www-svg/2010Aug/0015.html 16:05:07 first one is about changes. but next publication will list changes since last (LC) publication 16:07:28 we need a good and complete list of changes between the last /TR publication and the next one 16:08:54 action: chris to respond to Helger to explain that changes appendix is relative to last published version 16:08:54 Created ACTION-2906 - Respond to Helger to explain that changes appendix is relative to last published version [on Chris Lilley - due 2010-11-12]. 16:13:49 not clear how to edit in place the first edition to give dated links 16:14:11 http://www.w3.org/TR/2003/REC-SVG11-20030114/ecmascript-binding.html 16:14:46 action: chris to talk to comm team anout editing in place svg 1.1 first edition to absolutize some undated links to ecmascript appendix 16:14:46 Created ACTION-2907 - Talk to comm team anout editing in place svg 1.1 first edition to absolutize some undated links to ecmascript appendix [on Chris Lilley - due 2010-11-12]. 16:16:22 his third comment is a test case typo. not a lc issue. we fix it live in the meeting 16:17:21 adjourned 16:17:26 rrsagent, make minutes 16:17:26 I have made the request to generate http://www.w3.org/2010/11/05-svg-minutes.html ChrisL 16:31:18 ed, you asked to be reminded at this time about whatever 16:37:35 FAQ on Emoji - http://www.unicode.org/faq/emoji_dingbats.html 16:47:24 https://twitter.com/svgwg 17:24:44 shepazu has joined #svg 18:04:58 eseidel has joined #svg 21:58:57 eseidel has joined #svg 23:13:50 plinss_lyon has joined #svg