[webkit-dev] Audio directory layout
crogers at google.com
Tue Mar 30 17:57:10 PDT 2010
Most of my files so far use wtf stuff (OwnPtr, RefPtr, and Vector) so I
guess there are dependencies.
On Tue, Mar 30, 2010 at 5:55 PM, Adam Barth <abarth at webkit.org> wrote:
> Will there be dependencies on the rest of WebCore? If not,
> platform/audio might sense as a peer to platform/graphics.
> On Tue, Mar 30, 2010 at 5:45 PM, Chris Rogers <crogers at google.com> wrote:
> > Thanks everyone for your answers.
> > Darin, I agree that "audio" might be confusing since HTMLAudioElement
> > not be in there, but it still might be the simplest name. Otherwise, how
> > about:
> > WebCore/audio-engine
> > or
> > WebCore/audio-processing
> > ??
> > On Tue, Mar 30, 2010 at 5:31 PM, Darin Adler <darin at apple.com> wrote:
> >> On Mar 30, 2010, at 5:19 PM, Adam Barth wrote:
> >> The platform directory contains a lot more than just
> >> platform-specific files. It's the platform upon which WebCore is built.
> >> example, KURL is in platform even though it's shared by all the ports. I
> >> think the main consideration for whether to put things in platform
> >> to the dependencies. For example, platform doesn't depend on the rest
> >> of WebCore.
> >> That’s right.
> >> The WebCore/platform directory’s name is a bit of a pun. It contains the
> >> platform abstraction, exposing things present in the underlying
> >> system such as a way to find out about events and screen sizes and such,
> >> also contains other basics that provide a “platform” for the rest
> >> of WebCore code, without dependencies on that code. It can be though of
> as a
> >> largely-separate lower level module within WebCore.
> >> The platform directory does not contain all platform-specific files. Nor
> >> should it. Directories such as WebCore/loader and WebCore/plugins
> >> platform-specific subdirectories as needed.
> >> As for whether audio should be a top-level concept, that might
> make sense.
> >> It seems similar to notifications and storage, which are top-level
> >> Code that is specifically about how the web models audio, and not how
> >> is integrated with the underlying audio capabilities of the OS, more
> >> naturally would go somewhere outside the platform directory. A top level
> >> directory named audio might be confusing since HTMLAudioElement would
> not be
> >> in there.
> >> -- Darin
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev