[webkit-dev] Web APIs and class name collisions

[Adam Barth]

One common thing we do is prefix "DOM" to DOM-level concepts.  For example,
DOMWindow and DOMFileSystem.  I'm not sure if we have an established
convention for CSS-level concepts.

Adam


On Thu, Jul 12, 2012 at 9:18 AM, Andrei Bucur <abucur at adobe.com> wrote:

> Hello Webkittens!
>
> While implementing the Region interface (
> http://dev.w3.org/csswg/css3-regions/#the-region-interface ) I've noticed
> that the name "Region" is already taken by a class in platform/graphics.
> I'd like to know what's the best approach in these kind of situations:
>
>    1. Rename the existing WebCore class to something else and use the
>    name "Region" for the Web API so there's parity between the implementation
>    and the spec
>    2. Somehow prefix the Web API implementation class name?
>
> As the Web APIs expand I suppose this situation may occur again in the
> future and I suppose there should be a rule describing what's the best
> approach to take.
>
> Thanks!
> Andrei.
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120712/82945ce5/attachment.html>