- From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Date: Fri, 25 Jan 2013 18:09:21 +0200
- To: "Hirsch Frederick (Nokia-CIC/Boston)" <Frederick.Hirsch@nokia.com>, ext Dominique Hazael-Massieux <dom@w3.org>
- Cc: "<jackalmage@gmail.com>" <jackalmage@gmail.com>, "<public-device-apis@w3.org>" <public-device-apis@w3.org>
Hi Frederick, Dom, On 24.1.2013, at 21.15, Hirsch Frederick (Nokia-CIC/Boston) wrote: > [speaking not as chair] > > My concern was not with regards to the specific bug. > > I still think it not very good to have editors drafts where the date changes when you view them so you have no idea when the editor actually made an update, and I also think it is bad practice to rely on javascript generation which may fail in various contexts when it is fairly straightforward to generate plain html. Thus I haven't changed my view on the best practice. > > If Dom is able to automate this in the DAP context that would be great. As an editor in another work group I have made generating HTML as part of my personal work flow and it has been no big deal. Ok. I crafted a small command line utility [1] to automate this. Now you can say: $ phantomjs respec2html.js Overview.src.html Overview.html or $ phantomjs respec2html.js http://dvcs.w3.org/path/to/Overview.src.html Overview.html ... to do the conversion. I think this makes the work flow smooth enough, so that we can start publishing ED snapshots at Overview.html and put the ReSpec source at Overview.src.html. Do the fellow editors have concerns with this? I plan to apply this to all the specs I edit currently (Battery Status API, HTML Media Capture, Ambient Light Events, Proximity Events, and Vibration API). -Anssi [1] https://github.com/anssiko/respec/blob/respec2html/tools/respec2html.js [I sent a pull request to Robin, so you may find this from the official darobin/respec repo soon too.]
Received on Friday, 25 January 2013 16:10:20 UTC