WebAPI Meeting: Tuesday 28 May @ 10 AM Pacific [1]

2013-05-27 Thread Andrew Overholt

Meeting Details:

* Agenda: https://wiki.mozilla.org/WebAPI/2013-05-28
* WebAPI Vidyo room
* A room we can find, San Francisco office
* Spadina conf. room, Toronto office
* Allo Allo conf. room, London office

* Vidyo Phone # +1-650-903-0800 x92 Conference #98413 (US/INTL)
* US Vidyo Phone # 1-800-707-2533 (PIN 369) Conference #98413 (US)

* Join irc.mozilla.org #webapi for back channel

Notes will be taken on etherpad:

https://etherpad.mozilla.org/webapi-meetingnotes

All are welcome.

Andrew

[1]
http://www.timeanddate.com/worldclock/fixedtime.html?msg=WebAPI+meetingiso=20130528T10p1=224am=30 


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Code Review Session

2013-05-27 Thread Anthony Jones
On 25/05/13 04:16, Ehsan Akhgari wrote:
 On 2013-05-24 11:46 AM, Benoit Girard wrote:
 Another option is to use clang-format, which can lexically parse diff
 files.

A pre-upload check would give the fastest feedback.

It would help me (and those who review my code) if there is an easy way
to check my patches from the command line before doing hg bzexport. Even
if it is only for white space. What we need is a way to specify which
file paths the standard formatting rules apply to. I just need to figure
out how to install clang-format.

If this proves to be successful then we could consider putting effort
into other style conventions.

Anthony

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Code Review Session

2013-05-27 Thread Justin Lebar
This is only tangentially on topic, but I have a git pre-commit hook
which detects .orig files and trailing whitespace.  It's saved me a
lot of embarrassment.

I also have a git tool which will fix trailing whitespace in your patch.

https://github.com/jlebar/moz-git-tools#pre-commit
https://github.com/jlebar/moz-git-tools#git-fix-whitespace

On Mon, May 27, 2013 at 10:54 PM, Anthony Jones ajo...@mozilla.com wrote:
 On 25/05/13 04:16, Ehsan Akhgari wrote:
 On 2013-05-24 11:46 AM, Benoit Girard wrote:
 Another option is to use clang-format, which can lexically parse diff
 files.

 A pre-upload check would give the fastest feedback.

 It would help me (and those who review my code) if there is an easy way
 to check my patches from the command line before doing hg bzexport. Even
 if it is only for white space. What we need is a way to specify which
 file paths the standard formatting rules apply to. I just need to figure
 out how to install clang-format.

 If this proves to be successful then we could consider putting effort
 into other style conventions.

 Anthony

 ___
 dev-platform mailing list
 dev-platform@lists.mozilla.org
 https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: We should drop MathML

2013-05-27 Thread Henri Sivonen
On Fri, May 24, 2013 at 4:33 PM, Benoit Jacob jacob.benoi...@gmail.com wrote:
 I also thought that it was obvious that a suitably chosen subset of TeX
 could be free of such unwanted characteristics.

So basically that would involve inventing something new that currently
does not exist and are currently isn't supported by Gecko, Trident,
Blink or WebKit. Furthermore, to integrate properly with the platform,
math should have some kind of DOM representation, so a TeX-like syntax
would still need to parse into something DOMish.

On the other hand, presentation MathML is already mostly supported by
Gecko and WebKit, parses into a DOM (from text/html, too) and has had
years of specification development behind it to figure out what the
sufficiently expressive feature set is.

So instead of being in the point where there's a mature spec and two
of the four engines still to go, we'd go back to zero engines and no
spec.

Presentation MathML may not be pleasant to write by hand, but we don't
put a Markdown parser in the browser, either, for those who don't like
writing HTML. (And we don't put a JIT for $LANGUAGE for those who
don't want JS.) Those who rather write Markdown can run the conversion
on their server. Likewise, those who rather write a subset of TeX can
run itex2mml on their server.

-- 
Henri Sivonen
hsivo...@hsivonen.fi
http://hsivonen.iki.fi/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform